Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
multiplayer-playmode-1.6.1
Issue ID
MTTB-1757
Regression
Yes
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
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
- Audio Mixer “+” buttons overlap with UI when the Audio Mixer window layout is set to Horizontal
- "Clear" button in the "Set project display name" closes all the pop-up instead of clearing just a name from the field
- Video Player renders no video on specific devices when using Vulkan
- The Editor slows itself down by showing tons of warnings when the majority of TransformAccessArrays content are NullRefs
Resolution Note:
There are no fixes planned for this Bug