Bug HybridV2Culling.cs | IndexOutOfRangeException Index is out of range of Length, stops rendering

I am having an issue on LOD entities when removing them which creates the following error:

Spoiler: Error Exception

IndexOutOfRangeException: Index 7 is out of range of '6' Length.
Unity.Collections.NativeArray`1[T].FailOutOfRangeError (System.Int32 index) (at <e414e10bfe5f45729ff122f3359de21b>:0)
Unity.Collections.NativeArray`1[T].CheckElementReadAccess (System.Int32 index) (at <e414e10bfe5f45729ff122f3359de21b>:0)
Unity.Collections.NativeArray`1[T].get_Item (System.Int32 index) (at <e414e10bfe5f45729ff122f3359de21b>:0)
Unity.Rendering.SimpleCullingJob.Execute (Unity.Entities.ArchetypeChunk archetypeChunk, System.Int32 chunkIndex, System.Int32 firstEntityIndex) (at Library/PackageCache/com.unity.rendering.hybrid@0.10.0-preview.21/Unity.Rendering.Hybrid/HybridV2Culling.cs:344)

When this happens everything that is being rendered through Hybrid V2 stops rendering until switching between the game window and the Scene window or executing DOTS>Hybrid Renderer> Recreate all batches.

(you can see all the drones disappear at once)
https://i.gyazo.com/1d0448afd5bc48345f009f6d801205a9.gif



It occurs at like 344 in the HybridV2Culling.cs class :

obviously trying to use an index that no longer exists. When putting an if finalIndex < length it works, but since it is managed it gets reset each time it rebuilds after.

Is there a workaround for this?

 

anyone? i have the exact same problem

 

it went away while changing code that removed and added many entities with renderers, it was on the latest build but i cant repo it and still dont really know what was wrong.

 

Hi there. I got the same issue. I'm using the current 0.11.0-preview.44 Version.

It looks like it is happening, when one mesh of the group leaving the visible area.
In the time where the bug appears, there were no entities created or destroyed, but they might get some components.
I don't get this code there... Couldn't an easy check help there?


Update: I could reproduce it with a simple scene: Create 2 Entities with LOD Groups and renderer below and a camera moving away from them, so just 1 of the entity is visible. Also add a system that randomly add or removes a component, so the entities changing the chunk. When 1 box become visible, the exception occurs.

=> Happens when the entities changing the chunk.

I couldn't create a new project for that. Didn't do that for years and seems the entities package and stuff is not there. Here all the needed files.

TestScene:
https://filetransfer.io/manage-package/7GNHWik3#

Needed Script:

Code (CSharp):

1.  
2. using UnityEngine;
3. using Unity.Entities;
4. using Unity.Jobs;
5. public class AnimateGameObject : MonoBehaviour {
6.     public Vector3 speed = Vector3.left;
7.     void Update() {
8.         transform.localPosition += Time.deltaTime * speed;
9.     }
10. }
11. public class TestSystem : JobComponentSystem {
12.     protected override JobHandle OnUpdate(JobHandle inputDeps) {
13.         var entities = EntityManager.GetAllEntities(Unity.Collections.Allocator.Temp);
14.         foreach (var e in entities) {
15.             if (Random.value > 0.5f) {
16.                 if (EntityManager.HasComponent<Dirty>(e))
17.                     EntityManager.RemoveComponent<Dirty>(e);
18.                 else
19.                     EntityManager.AddComponentData(e, new Dirty());
20.             }
21.         }
22.         entities.Dispose();
23.         return inputDeps;
24.     }
25. }

Another update:
Partial good News: I tested it in the compiled version and it looks fine so far. So i guess its just happening in the editor. I have BURST OFF in the Editor. Maybe it has something to do with that?

 

when i had this issue it was indeed with objects having lod groups on the border of being in view/out of view

 

Still no reply from Unity? Very sad... I spend another time effort for debugging and even creating an easy reproduction project for this bug.

I guess its my last try spend effort on this kind of researches... being already ignored sooo many times now...

 

It's better to use bug report tool at Unity editor so you can get reply from Unity.

 

Ok, thanks.
@optimise: I tried that already, but i would take a long time to setup a project for that simple file, to configure everything it has to be. I tried it, but after 1h to figure out the packages (that are not shown sometimes, due to preview) try to setup i stopped with it...
I did that for another report and spend also half a day on it, but this failed processing, due to its not a "run and broken".
It sometimes looks like we have to do 99% of the developer work, before they even consider to start to looking at it.

Sry, i can't spend half my working day to report a bug in that way. I already spend a day to analyse the unity code that caused the problem and added the scripts needed to reproduce...

 

Any updates on this Topic? I experience now more and more issues with that topic. Also rendering bugs of Meshes that should not be shown anymore, related to that bug and LOD Levels and ALSO in the compiled version...

 

Ok, thanks. Can you link it here, so we can see it?

Maybe you can also check that short script, it takes 1min to try it out i guess...

 

As i said, last time i spend a lot of time to do that and the result was, that it was not even going to the developers... This time i also tried to setup a new game to make it work, but it wasn't possible, due to the packages were not shown and i needed to setup all of the experimental packages again to get it work in a clean environment... If you have an EASY and fast way, that not cost hours to report a bug, i can try that again.

Again: For me it takes half a day to set it up, to save you 1 min of copy paste the 3 files and press a button... This will not going to happen... I'm happy to help you, but not spending hours to save you a minute of work... So my only way for me is to hope, that a bigger customer gets to use this technology and pushes your management to fix that....


For the bug: I ment the bug you work in this sprint, just link it >>HERE<<, so we know, what bug you mean and see when its fixed to retest

 

Ah Ok, thank you very much.

 

Hi, sry, didn't see it.

No, don't have it anymore. But it is actually just:
the TestSystem above run
add 2 rendered similar entities with LOD Groups
than move the camera from "both visible" to "only one" visible, to trigger the "Partial visible" culling mode.

 

Year, the TestSystem just works in the default group (so simulation i guess), so that shouldn't be a problem. My guess was more, that it stores something over a frame, but had no clear idea.
Keep in mind, that it just happens in the editor, i never had that error or related problems in the compiled version! Maybe it helps to detect the problem :\

I never used livelink, just simply in the unity editor, and later compiling to pc version only.

I still use the 0.11.0-preview.44. I wanted to update, but my 2021.2.15f1 is not supported yet

 

Hey, testing this right now, for the code to compile I think you need to do :

Code (CSharp):

1. HybridChunkUpdater.ProcessChunk(chunkInfo, chunk, chunkBounds);
2. hybridChunkInfos[i] = chunkInfo;

 

Thank you very much

I will wait for the 0.50 due to its just a annoying in the editor. As i read its planned for the next months for my version. Hope the migration goes well :\