Search Issue Tracker
Won't Fix
Votes
12
Found in
2022.3.8f1
Issue ID
UUM-47335
Regression
No
IndexOutOfRangeException in Unity.Rendering.Occlusion.Masked.Dots.OcclusionMesh.Transform when Safety Checks are "Force On" or Burst Compilation is disabled
How to reproduce:
1. Open the attached project "indexoutofrange-repro-urp.zip"
2. Move the Scene View Camera near the Scene origin
3. Enable "Force On" Safety Checks (Jobs>Burst>Safety Checks>Force On)
Expected results: No errors thrown in the Console window
Actual results: "IndexOutOfRangeException: Index 1 is out of restricted IJobParallelFor range [0...0] in ReadWriteBuffer." is thrown
Reproducible with: 1.0.14 (2022.3.8f1)
Reproducible on: Windows 10 22H2
Not reproducible on: No other environment tested
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
Following the announcement here (https://forum.unity.com/threads/dots-development-status-and-next-milestones-november-2023.1516672/) we are removing experimental Burst Occlusion Culling feature.
Today this case will be closed. Thank you for taking the time to report this issue.