Search Issue Tracker
Fixed in 5.1.2
Votes
0
Found in
5.0.1p1
Issue ID
691900
Regression
Yes
ProceduralLoadingBehavior.Cache and DoNothingAndCache do not cache
1. Do not view the material properties in the editor before testing. If you do, the material will be cached in RAM until you restart the editor.
2. Hit play. Note that the material displays with random colors until the generation completes.
3. Stop and restart game. Note that the material displays with random colors until the generation completes again. It is expected that the material would load from cache instead of regenerating.
4. Note the console log showing that "isCachedDataAvailable is false" after generation completes.
Reproduced: 5.0.2p1, 5.0.0b22, 4.6.3f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Add comment