Search Issue Tracker
Fixed
Fixed in 2020.3.42f1, 2021.3.14f1, 2022.1.23f1, 2022.2.0b15, 2023.1.0a12
Votes
0
Found in
2020.3.38f1
2021.3.8f1
2022.1.14f1
2022.2.0b5
2023.1.0a6
Issue ID
UUM-12721
Regression
Yes
AssetBundle indeterminism caused by mesh streaming info
If the same mesh is used in 2 AssetBundles, the first time is streamed and second time it is not(used by vfx for instance). The second occurrence streaming info can be non-deterministic.
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
- 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
- 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 (fix version 2023.1.0a12):
Fix regression where if a mesh was used in vfx and included in an AssetBundle there could be indeterminism in its streaming info offset field.
Resolution Note (fix version 2021.3.14f1):
Fixed bug where a field was not reset back to zero