CreateMissingRenderBoundsFromMeshRenderer Removed in Hybrid Renderer 0.3.4

I updated to the Hybrid Render 0.3.4 along with the rest of the DOTS related packages and it looks like the CreateMissingRenderBoundsFromMeshRenderer system got removed, this seems to be why all the entities I have stopped being rendered. I'm creating all my entities in Code, not from GameObjects or Prefabs being converted. I looked through the packages and the only place I can see RenderBounds being created now is in MeshRendererConversion.cs.

Do I now need to be creating RenderBounds on any code created entities that want to render?

This works fine if I revert back to the Hybrid Renderer 0.3.3 and the CreateMissingRenderBoundsFromMeshRenderer system is back.

 

I found the same thing while updating my project the other day. For now I've added RenderBounds manually when I add the RenderMesh component, using

mesh.bounds.ToAABB()

. I was going to make a post about it, but I came to the conclusion that they're assuming/encouraging everyone to be using GameObjectConversion now, and it won't be too hard for me to move to that too when I get around to it.

However it would be nice if the changelog for the package included details like this...

 

Yeah it's just annoying, mesh.bounds can only really be touched from the main thread, I have a whole lot of creation of rendered entities that goes on inside jobs. I may end up just creating my own version of CreateMissingRenderBoundsFromMeshRenderer just because with everything I'm doing being dynamic creation I don't have a use really for GameObjectConversion.

 

same here, just updated to hybrid renderer to 0.3.4 and it's not rendering at all. Is this behaviour intended or can we expect a fix for this ?

EDIT: I could fix it by adding the RenderBounds component and assigned the mesh bounds via .ToAABB() Thx for the hint @LastResortMatthew

 

Talk about no love for this package, cant' even be bothered to create release notes for breaking changes.

 

FYI a real pain with the hybrid renderer, and actually a persistent issue throughout almost all feature level DOTS packages, has been the inability to easily order where they run. In a real game completing jobs in the rendering group that can have dependencies from simulation is pretty much a non starter. And the only fixes are less then desirable. Custom player loops which in this scenario get a bit complex, and you have to reason about where ECS internals are plugging into them also to time it right. Or create dev versions of the packages.

Once your scenario is using the bulk of feature level packages this actually gets extremely complex. I think what would probably help a lot is abstract out group creation and wrap it with a settings object of some type. So we can easily override what groups packages run in. Packages ordering their own systems via each other is fine, but pretty much everything else in a real game you end up wanting fine grained control over, and there really isn't a good reason to have that internal.

 

Is that URP support optimised for mobile in development too?

 

So I need to add RenderBounds during entity cretion? Docs says that if we provide RenderMesh and LocalToWorld object will be rendered. But if to use only these two components - its not renderd

 

I was able to add entity programmatically if to manually configure RenderBound via values form Mesh.bounds

Code (CSharp):

1.  
2.        Entity leaderEntity = entityManager.CreateEntity(
3.             typeof(RenderMesh),
4.             typeof(Translation),
5.             typeof(LocalToWorld),
6.             typeof(RenderBounds)
7.              );
8.  
9.         entityManager.SetSharedComponentData(leaderEntity, new RenderMesh
10.         {
11.             mesh = ourMesh,
12.             material = ourMaterial,
13.         });
14.            
15.         entityManager.SetComponentData(leaderEntity, new RenderBounds(){
16.             Value = new AABB()
17.             {
18.                 Center = new float3(ourMesh.bounds.center.x, ourMesh.bounds.center.y, ourMesh.bounds.center.z),
19.                 Extents = new float3(ourMesh.bounds.extents.x, ourMesh.bounds.extents.y, ourMesh.bounds.extents.z)
20.             }
21.         });
22.  

 

https://docs.unity3d.com/Packages/com.unity.rendering.hybrid@0.3/manual/index.html

This one.

 

Do you have an approximation of when the Hybred Renderer v2 will be released?
Also does the Hybred Renderer v2 will implement the occlusion culling and dynamic batching ?

 

does this means less Draw Calls or a totally different Technology ?

 

hey @SebastianAaltonen,
i have a question about the Frustum Culling used in the Hybred Renderer Package.
im trying to play with ECS stuff and create my own Hybred Renderer based on Graphics.DrawMeshInstanced.
i saw the Intersect* functions inside the FrustumPlanes struct but i dont see any Intersect function taking a planes mask as parameter.
generally there is some cases where some planes can be ignored like when the ChunkWorldRenderBounds is partially included in the frustum culling planes so all Entities within that chunk should compute Intersection only with interseting/out planes.
do you guys use another way to calculate Frustum Culling or other Intersect functions are implemented in other parts?

 

Awesome. Btw I heard there is plan to develop full pure DOTS renderer. Is that Hybrid Renderer the first step to slowly getting there?

 

UnityEngine render backends do you mean the C++ graphics part of Unity core engine?

 

@SebastianAaltonen I really appreciate the efforts to optimize performance, you're doing a great job. But in my case, some ojects seem to be culled while still on screen (I presume their Chunkrenderbounds are not correct ??). I have tons of performance left, is there a tag or some other way to exclude those specirfic entities from culling?

 

Just as a heads up, I don't think this works correctly when changing a chunk's archetype in place by removing either a Disabled component or a Prefab component. That action doesn't affect change nor order versions yet the system doesn't operate on chunks with Disabled or Prefab components causing the chunk bounds to go stale undetected.

 

Unfortunately, I don't have a project to reproduce it. This is just a pitfall I have run into when working with chunk components and from reading the RenderBoundsUpdateSystem code, it seems like it may be hitting the same pitfall since it uses change and order filters to keep a chunk component cache up-to-date but does not include prefab and disabled components in the query.