Search Issue Tracker
Fixed
Fixed in 6000.0.58f1, 6000.2.4f1, 6000.3.0b1
Votes
1
Found in
6000.0.11f1
6000.1.0a7
6000.2.0a1
6000.3.0a1
7000.0.0a1
Issue ID
UUM-75914
Regression
Yes
The "Camera.Render" hangs the process of geometry baking in the textures when using HDRP
How to reproduce:
1. Open the “ReproCameraRender“ project
2. Open the “OutdoorsScene“
3. Open the “Assets“ folder in the Project window
4. Open the “New Impostor“ asset in the Inspector window
5. Click on the “Build“ button
Expected result: The baking process will take only a few minutes
Actual result: The baking process may hang or take a really long time (up to 1H. I recomend downscaling the settings in the builder so you can be at ~5min instead for testing)
Reproducible with: -2023.2.0a6,- 6000.0.11f1
Not reproducible with: 2021.3.40f1, 2022.3.38f1, 2023.2.0a5
Note: 2023.2.0a6 regression was causing by something else solve by some times. It is a different issue.
Producible with: DX12 - Split
Not reproducible with: DX11, DX12 - Legacy, DX12 - Native
Reproducible on: Windows 10 Pro (22H2)
Not reproducible on: macOS 14.5 (Intel)
Note: if the baking succeeds just click on the “Clear“ button on the “New Impostor“ asset, to clear the pre-baked data
Through first investigation, it seams that in this usage, something prevent the m_DependentFenceCreates in GPUFenceDependencyChecker::RemoveDependencyFromAllWaitingFences to forget element. This is the best explanation for exponentially increasing time (see attached images from Superluminal)
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
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note:
-