Search Issue Tracker
Duplicate
Votes
0
Found in
6000.2.0a10
Issue ID
UUM-104686
Regression
Yes
InvalidOperationException thrown and Mesh turns invisible in Scene View when the URP Package is freshly installed and the SetTextureOffset() is called on a Mesh with more than one Material and Resident Drawer is Enabled
How to reproduce:
1. Open the project “IN-99966_ExceptionMat“
2. Open the “SampleScene.unity”
3. Remove the package Window → Package Manager → Unity Registry → com.unity.render-pipelines.universal
4. Click OK to “Restart” when prompted
5. Install Window → Package Manager → Unity Registry → com.unity.render-pipelines.universal
6. Enter Play Mode
7. Exit Play Mode
8. Observe the Scene View and Console
Expected result: No InvalidOperationException error is thrown and the Mesh is visible in the Scene View
Actual result: InvalidOperationException is thrown in the Console and after leaving the Play Mode the Mesh is not visible in the Scene View
Reproducible with: 6000.2.0a9, 6000.2.0a10
Not reproducible with: 2022.3.61f1, 6000.0.47f1, 6000.1.0f1, 6000.2.0a8
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
- Disabling Resident Drawer does not produce the errors
- Other versions experience issues where changing the Offset of the Material renders the Mesh invisible in the Scene View or Game View. In these specific versions the issue throws a different error and the Mesh is only invisible after leaving the Play Mode
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
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
Resolution Note:
The issue has been fixed while fixing another Burst related bug.
Duplicate of another internal issue: BUR-2839: Errors when importing the Entities package into a 2D project