Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
5.2.2f1
Issue ID
752350
Regression
Yes
GI Bake fails when not enough RAM
Bake fails with not enough RAM.
The attached project was successfully baked on Zbignev's 32 GBs machine. Also it succeeded on OSX with 16GBs. But failed on Windows 8.1 with 8GBs. As well fails on Windows for user with 24GBs.
Is it possible to guarantee that any bake should succeed with '...' amount of RAM? So we can add it to 'recommended' system requirements?
This is a regression for the customer. Likely caused by Enlighten in 5.3 requiring more memory than in 5.2. Overall the issue exists in 5.2 as well.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Add comment