HDRP doesnt work?

Unity Engine
,
1

In Unity 2023.1.0b5 I create a new project using the HDRP core preset, then when the HDRP Wizard pops up, I select the HDRP + DXR tab and hit “Fix All”.

After restarting, the console is spammed with the following warning and error:

Render Pipeline error : the XR layout still contains active passes. Executing XRSystem.EndLayout() right now.
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)

NullReferenceException: Object reference not set to an instance of an object
UnityEngine.Rendering.HighDefinition.HDRenderPipeline.UpdateShaderVariablesRaytracingCB (UnityEngine.Rendering.HighDefinition.HDCamera hdCamera, UnityEngine.Rendering.CommandBuffer cmd) (at ./Library/PackageCache/com.unity.render-pipelines.high-definition@15.0.4/Runtime/RenderPipeline/HDRenderPipeline.cs:1082)
UnityEngine.Rendering.HighDefinition.HDRenderPipeline.UpdateGlobalConstantBuffers (UnityEngine.Rendering.HighDefinition.HDCamera hdCamera, UnityEngine.Rendering.CommandBuffer cmd) (at ./Library/PackageCache/com.unity.render-pipelines.high-definition@15.0.4/Runtime/RenderPipeline/HDRenderPipeline.cs:990)
UnityEngine.Rendering.HighDefinition.HDRenderPipeline.ExecuteRenderRequest (UnityEngine.Rendering.HighDefinition.HDRenderPipeline+RenderRequest renderRequest, UnityEngine.Rendering.ScriptableRenderContext renderContext, UnityEngine.Rendering.CommandBuffer cmd, UnityEngine.Rendering.HighDefinition.AOVRequestData aovRequest) (at ./Library/PackageCache/com.unity.render-pipelines.high-definition@15.0.4/Runtime/RenderPipeline/HDRenderPipeline.cs:2304)
UnityEngine.Rendering.HighDefinition.HDRenderPipeline.Render (UnityEngine.Rendering.ScriptableRenderContext renderContext, System.Collections.Generic.List`1[T] cameras) (at ./Library/PackageCache/com.unity.render-pipelines.high-definition@15.0.4/Runtime/RenderPipeline/HDRenderPipeline.cs:2107)
UnityEngine.Rendering.RenderPipeline.InternalRender (UnityEngine.Rendering.ScriptableRenderContext context, System.Collections.Generic.List`1[T] cameras) (at <e932915392764e5aa3442ba792104a92>:0)
UnityEngine.Rendering.RenderPipelineManager.DoRenderLoop_Internal (UnityEngine.Rendering.RenderPipelineAsset pipe, System.IntPtr loopPtr, UnityEngine.Object renderRequest, Unity.Collections.LowLevel.Unsafe.AtomicSafetyHandle safety) (at <e932915392764e5aa3442ba792104a92>:0)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr, Boolean&)

The editor is dead, and I cannot do anything useful. Weird thing, if I enter the Package Manager and remove a random unused package, everything is fine again. Until the next time I restart the project, so this is not a solution.

I am on Windows, 4090 RTX card. HDRP + DXR works fine in 2022.

Any known workarounds?

2

beta … i wouldn’t use it. LTS’ have enough issues and they are the ‘core’ of releases. But thats just my feelings on non LTS’.

3

True, but 2023 has an important raytracing optimization we really need. And we are still long time away from release, so I was hoping the 2023 version would be stable by the time we are done. I do not mind a few growing pains, but a non working editor in an totally empty project is a bit disappointing even for unity and a beta…

4

Unity has always used terms like ‘release’ and ‘beta’ very liberally. The general concensus is that tech streams are beta, betas are alphas, and alphas are just fun experimental toys to play while Unity team tries to get them working.

You absolutely should not be basing your production of a currently active project, no matter HOW early in production, on things that may or may not end up in the release in a may-or-may-not-being-working state. Even with the most reliable software this is asking for trouble and Unity has a real bad track record with this stuff.

5

Just submit a bug report. Else good luck finding someone here that can help you with that.
I have tried 0b1, 0b3 and 0b6. All worked with HDRP, somewhat. I didn’t use the Core preset though, just upgraded my own project.
Just now I tried to run the HDRP sample project on 0b6 trying to do a Mac build, but the editor crashes all the time with it. I am uploading the bug report as we are speaking :smile:

6

I emphasized we need an important optimization introduced in the 2023 version, so saying we should not use it is kind of pointless advice to be honest…

7

This problem got fixed in b7 finally