Search Issue Tracker
Active
Under Consideration for 2.3.X
Votes
7
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
- Certain textures are incorrectly marked in the render pass list when observed through Render Graph Viewer
- "Assertion failed on expression" error occurs when multiple Animation Components are instantiated after changing the Culling Type
- MacOS persistentDataPath uses old path when built compared to Editor Play mode
- Crash on RaiseException when entering Play Mode in a specific project
- Debug Console does not reappear when disabling and re-enabling Debug.developerConsoleEnabled
Add comment