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
Issue ID
1380063
Regression
No
[PLM] Switching Lightmapping backends repeatedly causes crashes, visual output degradation, and file-system issues
Steps to reproduce (most stable repro on Linux):
1. Open the attached repro project
2. Open GITT > GI Testing Tool
3. Run SmokeTests_LightmapperResetTest
4. Observe a difference in image diff
5. Restart the Editor
6. Multi-select and run LightmapperResetTest, LoadBakedScene, MoveLighWhileBaking
7. Observe difference in image diff and asserts in the second or third test.
8. Attempt to open the Editor Log or save the scene
9. Observe the same asserts thrown, related to the file system
Notes:
- This was reproduce on Yamato and locally on Linux machines.
- File system asserts only reproduce on Linux.
- Image diff failure reproduces unstably on Windows (DX11) as well.
- Could not test with Yamato on MacOS
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
This bug will be fixed by enablement work that is in progress now. To that end we are postponing this and will retest once that lands.