Search Issue Tracker
By Design
Votes
0
Found in
2021.3.14f1
2022.1.24f1
2022.2.0f1
2023.1.0a20
Issue ID
UUM-21304
Regression
No
Meshes cannot be read during import process when running in batch mode
Steps to reproduce:
1. Download the “BatchModeRO” project
2. Open Command Prompt window
3. Go to the Unity version folder (eg. cd c:\Program Files\Unity\Hub\Editor\2021.3.4f1\Editor)
4. Run the command “-executeMethod ProcessThings.RunAsync -nographics -batchmode -logFile build.log -PROJECT_PATH” (instead of PROJECT_PATH write BatchModeRO project path. Eg. C:\Desktop\IN-22969_BatchModeRO-3\IN-22969_BatchModeRO-3. -- (minus) before the path is needed)
5. Open the “build.log” file in the Editor folder
Expected result: The “Rock_lg02” mesh was imported successfully
Actual result: Error "Not allowed to access uv on mesh 'Rock_lg02' (isReadable is false; Read/Write must be enabled in import settings)" occurs
Reproducible with: 2021.3.14f1, 2022.1.24f1, 2022.2.0f1, 2023.1.0a20
Could not test with: 2020.3.41f1 (Package error)
Reproduced on: Windows 10
Note: The error does not occur when Read/Write is enabled in import settings
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
The async work is picked up again inside the player loop, which also runs outside playmode. As a result the mesh UVs are accessed inside the player loop which rightfully throws an error that read/write should be enabled on the mesh.
The issue can also be reproduced inside the editor although at a much lower rate. In batch mode the application does not spend time redrawing the inspector etc., so the chance of the work getting resumed inside the player loop tick is much higher.