Search Issue Tracker
Fixed
Fixed in 6000.3.4f1, 6000.4.0b4, 6000.5.0a5
Votes
0
Found in
6000.4.0a2
6000.4.0a5
Issue ID
UUM-130734
Regression
Yes
UUM - Starting Virtual Player after Project upgrade throws Asset Database errors
Steps to reproduce:
- Open the attached project
- Open Multiplayer Play Mode window (Window -> Multiplayer -> Multiplayer Play Mode)
- Start a Virtual Player
- Observe the Virtual Player's Console window
Actual results: "Asset Database is set to Read Only, but it has found out-of-date assets. This should not happen!" and "Refresh completed but there are assets queued up for importing. Check for code that modifies assets which gets called after OnPostProcessAllAssets." errors are thrown in Virtual Player's Console
Expected results: No errors are thrown when Virtual Player is started
Reproducible with versions: 6000.3.0a2(1.6.1), 6000.3.0f1 (2.0.1), 6000.4.0a5(2.0.0), 6000.5.a2(2.0.1)
Not reproducible with versions: 6000.0.63f1 (1.6.1), 6000.2.14f1 (1.6.1), 6000.3.0a1(1.6.1)
Tested on (OS): macOS 26.1
Notes:
- The issue is most consistent when opening the project without the Library folder on a new Editor version.
- The issue is not tied to the MPPM package. Opening the project on 6000.3.0a1 will not reproduce the errors. Re-extracting the project and opening it with 6000.3.0a2 will reproduce the errors even though the MPPM package is 1.6.1 for both Editor patches.
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
Resolution Note:
The cause of this issue is the VFXManager.asset file, whenever kCurrentRuntimeDataVersion is incremented when runtime data changes, it expected to automatically being upgraded in user project which is not the correct behaviour and the VFX graph team has plans to to take this out for 6.5. The fix for 6.5 for this issue will be included in this refactor
Resolution Note (fix version 6000.5.0a5):
The cause of this issue is the VFXManager.asset file, whenever kCurrentRuntimeDataVersion is incremented when runtime data changes, it expected to automatically being upgraded in user project which is not the correct behaviour and the VFX graph team has plans to to take this out for 6.5. The fix for 6.5 for this issue will be included in this refactor
Resolution Note (fix version 6000.4.0b4):
The cause of this issue is the VFXManager.asset file, whenever kCurrentRuntimeDataVersion is incremented when runtime data changes, it expected to automatically being upgraded in user project which is not the correct behaviour and the VFX graph team has plans to to take this out for 6.5. The fix for 6.5 for this issue will be included in this refactor
Resolution Note (fix version 6000.4.0b4):
The cause of this issue is the VFXManager.asset file, whenever kCurrentRuntimeDataVersion is incremented when runtime data changes, it expected to automatically being upgraded in user project which is not the correct behaviour and the VFX graph team has plans to to take this out for 6.5. The fix for 6.5 for this issue will be included in this refactor
Resolution Note (fix version 6000.3.4f1):
The cause of this issue is the VFXManager.asset file, whenever kCurrentRuntimeDataVersion is incremented when runtime data changes, it expected to automatically being upgraded in user project which is not the correct behaviour and the VFX graph team has plans to to take this out for 6.5. The fix for 6.5 for this issue will be included in this refactor