Search Issue Tracker
Fixed
Fixed in 6000.0.57f1, 6000.2.2f1, 6000.3.0a5
Votes
0
Found in
2022.3.64f1
6000.0.54f1
6000.1.13f1
6000.2.0b11
6000.3.0a3
Issue ID
UUM-113152
Regression
No
GI Cache exceeds limit when using batchmode command-line argument
How to reproduce:
1. Open the attached “IN-109289” project
2. Go to Edit → Preferences → GI Cache
3. Set the Maximum Cache Size to 5 GB and set a custom empty folder location for the cache
4. Close the project and reopen it with these command-line arguments: “-batchmode -executeMethod LightingManager.BakeSceneLighting”
5. Open the Task Manager and search for the Unity Editor
6. Wait until the Unity editor dissappears and the Lighting baking is done
7. Right click the selected custom cache folder and select Properties to make sure the folder size is above 5 GB
8. Run the project again with command-line arguments “-batchmode -executeMethod LightingManager.BakeSceneLightingOtherScene”
9. Right click the selected custom cache folder and select Properties to observe the folder size
Expected result: The GI Cache will be cleaned when attempting a new bake because the 5 GB limit is exceeded
Actual result: The GI Cache keeps growing after the second bake
Reproducible with: 2022.3.64f1, 6000.0.54f1, 6000.1.13f1, 6000.2.0b11, 6000.3.0a3
Reproduced on: Windows 11
Not reproduced on: No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
Add comment