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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment