Search Issue Tracker
Duplicate
Votes
19
Found in
2022.3.31f1
Issue ID
UUM-73234
Regression
Yes
[Quest] Error “ArgumentOutOfRangeException: Index was out of range." is present when GameObject with Mesh Renderer component that has Material attached is selected in Hierarchy
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Connect Quest with Oculus Link
4. Enter the Play Mode without any GameObjects selected in Hierarchy
5. Select the Floor GameObject in the Hierarchy
6. Observe the Console window
Expected result: No Errors exist
Actual result: Error “ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.“ is present
Reproducible with: 2022.3.23f1, 2022.3.31f1
Not reproducible with: 2021.3.39f1, 2022.3.22f1, 6000.0.4f1
Reproducible on:
VLNQA00379, Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650
Quest 3 (user reported)
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Notes:
- Does not reproduce without VR connected
- Moving the cursor throughout the Inspector when Floor GameObject is selected produces the same Error
- Moving the cursor in the Select Material window when selecting new Material for Mesh Renderer or Test List (Script) Component reproduces the Error
- Selecting “/Assets/Materials/New Material.mat“ and moving the cursor through Inspector reproduces the Error
- Step 5 will not reproduce the issue if the Mesh Renderer component is removed, or if the list holding materials is empty
- Reproducible with Oculus XR and OpenXR
- Reproducible with Windows Platform and Android Platform
- Reproducible with new URP project
-
ChengkaiXu_UCL
Jun 04, 2024 12:54
Here is the discussion about this bug on Unity Forum: https://forum.unity.com/threads/xrpass-getviewport-exceptions-in-editor.1577916/#post-9872187
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
null
Duplicate of another internal issue: UUM-69269: ArgumentOutOfRangeException when rendering a camera set to allow HDR and MSAA