Official Hybrid Renderer V2 (0.4.0)

I've made a ticket/case for this now too, case 1313303.

 

I updated to latest HR but it doesn't fix it for me. These are reflections from the skybox and not point light like in the sample scene. It also seems like this is mostly about intensity. I need to set skybox intensity about 3x higher to achieve the same effect for Entities as I do for GameObjects

 

Is there any way to completely disable light probes for entity? Even if I set Light Probes to Off in a MR, HR still adds AmbientProbeTag to entity and huge pile of light probe properties (eating a lot of chunk space). But I am using unlit material for this entity...
@SebastianAaltonen

 

Also culling not working great with camera.layerCullDistances (I think because of chunk render bounds)

 

Looks like camera.layerCullSpherical doesn't work too.

 

Yes, even without any light probe in the scene, it still use up a lot of chunk space.
Now I separate the logic and rendering to two entity. Linked with a "RenderEntity" component
But if I have to update the material property every frame from some logic, this is bad for performance because of the random access reference...

 

Will there be a plan to increase GPU instancing to a number greater than 1023?
I think it is important in DOTS considering we can have hundreds of thousands of objects in a scene. The hundreds of "AddBatch" calls is quite expensive in a game loop.

 

I have this exact problem, my own old solution before hybrid renderer v2 was significantly faster when I draw 40000 of my objects, but I can't use that because DrawProceduralIndirect is unusable with V2...

 

I think the 1023 limit is inherited from Material Property Block.

 

MaterialPropertyBlock's itself haven't these restrictions, in default rendering path Graphics.DrawMeshInstanced has, if you'll use DrawMeshInstancedIndirect, DrawMeshInstancedProcedural you can have more than 1023 MPB's. In case of HR is BatchRenderGroup C++ side restrictions I suppose.

 

Weird batching behavior:

• Spawning ~3000 entities in System A using material A: 1 Hybrid Batch group
• Spawning ~134 entities in System B using material B: 1 Hybrid Batch group
• Spawning both (System A and B) : 49 Hybrid Batch group (alternating small batches of A and B material)

Any idea how to prevent this and end up with 2 batches?

(using ENABLE_HYBRID_RENDERER_V2, URP pipeline Asset, SRP batching is on, both materials use custom URP unlit Shadergraph )

UPDATE: Fixed it by changing one of the two Shaders from "transparent" to "opaque". Guessing it is not related to Hybrid Batch creation after all, but rather has something to do with https://docs.unity3d.com/ScriptReference/TransparencySortMode.html

 

Hi @JussiKnuuttila. Any new progress for case 1312138 and what is causing this bug as previous version dun have this bug? Seems like regression. I believe the bug for this case should highest priority bug to fix.

 

If I remember correctly previous version" is 0.10.0-preview.21 and "current version" is 0.11.0-preview.42.

 

Hi, I'm using Hybrid Renderer 0.11.0 and URP 10.2.2 in 2020.2.2. There is a problem when I instantiate prefab with light components: the instantiated light is not lighting the instantiated mesh. If I create a new gameobject in editor in playmode, it could be lit though. If not using URP, light is working correctly. I don't know it's a URP problem or Hybrid Renderer problem. Hope someone could help me?

 

Switch to Hybrid Renderer 0.11.0 and URP 10.3.2 in 2020.2.7, problem still exists.

 

Thanks for reply. So if I understand correctly, there are some solutions to this problem:
1, switch to built-in rendering or HDRP, hybrid renderer support local lights to them.
2, implement myself a global light transform synchronization system.
3, wait URP forward+ lighting mode.
Am I right? which solution do you suggest?

 

Another thing is I notice, when I switch hybrid renderer V1, the light works fine. Should I stick to V1? How much performance difference between V1 and V2?

 

If understand correctly, seems like DOTS entities can't render the graphics properly at mobile platform right compare with classic Game Object? Btw which version of Hybrid Renderer will actually fix this?

 

Will point light be supported?

 

Thank you so much for so detailed answer, I will try it.
I have successfully enable deferred rendering, It's working now.
Here is how to do it.
https://forum.unity.com/threads/urp-limited-number-of-pixel-lights-why.1048142/#post-6923480

 

when a shadergraph shader has active targets as both hdrp and urp, hybrid renderer 2 does not work in urp mode and throws this error.



the only solution right now is to duplicate the shader and have one be hdrp and another urp

 

Could you give a hint about when Forward+ is likely to appear? I understand that you probably don't want to say anything conclusive, but are we looking at more like 1 month, 3 months, 6 months, or more?

 

also, another bug i've noticed is that realtime shadows are still calculated for objects that have been baked into the shadowmap. the two are then overlapped

 

How do you change the lightmaps for an entity? doing

Code (CSharp):

1. EntityManager.SetsharedComponentData(ent, new Lightmaps{ new texture2darray... });

does not work. the only thing that works is changing the pixel data of the already present lightmaps

 

I got it working and its a big relief to finally have the trifecta of dots, urp and point lights/shadows working together, so thank you hybrid renderer team!

However... it appears when using entities rendered with the Render Objects Feature in combination with the hybrid renderer do not receive lighting from point lights. If a bug report is needed Id be happy to file one(I didnt as its using the current srp master straight from github).
Unsure if its by design with it being deferred and if forward+ will take care of it or if its a known/unknown bug.

 

It doesn't seem to have been reported so i post here:
i work since last weekend to install Hybrid_Renderer_V2
First try with URP: all entities turn invinsible, after searching it seems a lot of user have the same problem and there is no solution yet.

second try HDRP: no problem (except maybe huge performance drop).

BUT in both case(HDRP and URP), whenever an entity has a material: hybrid_renderer_V2 seems to add material related components:
is it intended?


at first i thought it was the conversion from builtin to srp , but even after creating new material, those component are still added.
the documentation don't talk about that so. is it intended?
EDIT found those components in the documentation, it's just not precise it adds them by default
EDIT2: Link to the documentation: https://docs.unity3d.com/Packages/c...tinMaterialPropertyUnity_MatrixPreviousM.html

 

@tassarho can you add link, for future readers?

 

I don't know if it's known or not :

Color are not rendered the same way in URP between a GO and an entity

Before playing, same object except for the right one which will be converted to an entity


After playing and conversion ( color is still the same)


Edit : case 1323153

 

Is there any plans to fix GC allocations every frame?

 

Looks like this system is leaking memory hard, even if there are no entities to render. Like Megabyte per second. If I disable this system via Entity Debugger, leak is stopping.
Unity 2020.3, HDRP 10.4, latest HR. Any advise would be appreciated.

 

In Future , They maybe should make ProbeVolume ( SDF ) . And BakedLight ( Ambient ) pass move to Light pass. ( Currently gbuffer pass ) . SH will be no more .

 

Spent several hours researching. So HRS is leaking when there is nothing to render. Around 3GB per hour. As a workaround I am disabling HRS system by another system when there is no entities to render...
@JussiKnuuttila I hope this will help you to solve the problem on the side of HR.

 

have you tried turning off collections safety? might just be the dispose sentinels, or unity editor interlope

 

Leak is happening in the build as well.

 

hello, I have some models which use customized shaders, they look good under normal URP but they just show pink when converted into entity, I suppose it is to do with the hybrid renderer V2. Is it that hybrid renderer V2 only have limited support on customized shaders? or need to somehow convert these shaders into hybrid renderer V2? thanks.

 

Check Material Overrides in Hybrid Rendering docs, if you are using custom shaders created using ShaderGraph.
Also, don't forget to check ECS Samples/HybridURPSamples repo, they got pretty good samples for Custom Material Property overrides.

 

I upgraded from 2021.1.0f1 to 2021.1.1f1 and my projects two main URP shadergraphs both register as "SRP Batcher Compatible", but they no longer run - i get an error that something is wrong with the DOTS_INSTANCING_ON variant.

I ask myself... How can this break in a patch update? Pretty upsetting. One of the shaders is complex, the other is super simple. The shadergraph editor shows no deprecation issues and no errors.

 

Thank you very much, that helped a lot!

 

@JussiKnuuttila : I have the exacts same issue as Thygrrr: all of my URP ShaderGraph shader broke when upgrading to 2021.1.1f. Could you please look into this?

Have for 6 shader this message:

Code (CSharp):

1. A Hybrid Renderer V2 batch is using the shader "Shader Graphs/SpriteGraph", but the shader is either not compatible with Hybrid Renderer V2, is missing the DOTS_INSTANCING_ON variant, or there is a problem with the DOTS_INSTANCING_ON variant.
2. UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)

Downgraded to 2021.1.0 for now where everything went back to normal.