Search Issue Tracker
Active
Under Consideration for 2.3.X
Votes
6
Found in [Package]
2.3.7
Issue ID
ADDR-3859
Regression
No
Error “PersistentManager::ReadObject must be called from the main thread“ when using async addressable loading with async instantiation for prefabs that contain a particle system with a sub emitter
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/OutdoorsScene.unity” Scene
3. Enter the Play Mode
4. Observe the Console
Expected result: No Errors exist
Actual result: Error “PersistentManager::ReadObject must be called from the main thread“ is present
Reproducible with: 2.2.2 (6000.2.0a2), 2.3.16 (6000.0.37f1, 6000.1.0b5, 6000.2.0a2)
Could not test with: 1.23.1 (2022.3.56f1) (Assets\AddressableLoadTest.cs(19,20): error CS1061: 'AsyncInstantiateOperation<GameObject>' does not contain a definition for 'GetAwaiter' and no accessible extension method 'GetAwaiter' accepting a first argument of type 'AsyncInstantiateOperation<GameObject>' could be found)
Reproducible on:
Play Mode
Not reproducible on:
Windows Standalone Player
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Errors “RenderPass: Attachment 0 is declared as depth attachment but RGBA8 sRGB is not a valid depth format.“ and “BeginSubPass: Not inside a Renderpass“ are present when using Native RenderPass with a RenderTexture that only has depth output
- ArgumentOutOfRangeException is thrown when an empty DropdownField is clicked at runtime
- [tvOS] "EXC_BAD_ACCESS" error is thrown when Painter2D.ClosePath is called
- Bad Naming Convention in Shortcuts Window for Sprite Shape Editing
- Bad Naming Convention in Shortcuts Window for Shader Graph
Add comment