Search Issue Tracker
Fixed
Fixed in 1.3.0-pre.1
Votes
1
Found in [Package]
1.0.0
Issue ID
MTTB-201
Regression
No
"Asset Database is set to Read Only" error is thrown when an asset has a Seeker component and a Virtual Player is used
How to reproduce:
1. Open the “multiplayer_bug“ project
2. Select Window → Multiplayer Play Mode
3. Enable a Virtual Player
4. Enter Play Mode
5. Observe the Console of the Virtual Player
Expected result: No errors are thrown
Actual result: An Error is thrown
Reproducible with: 1.0.0-pre.2(6000.0.0a12), 1.0.0 (6000.0.0a15)
Could not test with: 0.6.0, 1.0.0-pre.1 (due to a Fatal Error)
Reproducible on: Windows 10, Windows 11 (user’s device)
Not reproducible on: No other environment tested
Error: Asset Database is set to Read Only, but it has found out-of-date assets. This should not happen!
This is being tracked by the asset database team with
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
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
Resolution Note (fix version 1.3.0-pre.1):
Fixed in 1.3.0-pre.1