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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment