Search Issue Tracker
Fixed
Fixed in 2022.3.69f1, 6000.0.61f1, 6000.2.9f1, 6000.3.0b7, 6000.4.0a3
Votes
4
Found in
2022.3.62f1
6000.0.55f1
6000.1.16f1
6000.2.0f1
6000.3.0a4
6000.4.0a1
Issue ID
UUM-114187
Regression
No
Unnecessary Warnings are logged when running Player with -batchmode -nographics
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Open Build Profiles (File > Build Profiles)
4. Click “Build”
5. Create and select the “Build2“ folder
6. In File Explorer, go to the “Build“ folder
7. Move the “run.bat” file to the “Build2“ folder
8. Run the “run.bat“ file
9. Open “hostLog.txt”
Expected result: Unnecessary Warnings can be suppressed
Actual result: Warnings are present
Reproducible with: 2022.3.62f1, 6000.0.55f1, 6000.1.16f1, 6000.2.0f1, 6000.3.0a4
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Note:
Discussions thread: https://discussions.unity.com/t/stop-shader-log-spam-when-running-with-batchmode-nographics/1672623
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment