Anyone able to run UE5.0 City Sample with VR Preview?

I tried with Quest 2 + Airlink by activating the OpenXR plugin in UE5.0 but I could not succeed. Please those who have tried it can share their experiences?

Assertion failed: PrevHZB == nullptr || PrevHZB == GraphBuilder.RegisterExternalTexture(Context->PrevHZB) [File:D:\build++UE5\Sync\Engine\Source\Runtime\Renderer\Private\InstanceCulling\InstanceCullingMergedContext.cpp] [Line: 123]

UnrealEditor_Renderer
UnrealEditor_Renderer
UnrealEditor_Renderer
UnrealEditor_Renderer
UnrealEditor_Renderer
UnrealEditor_Renderer
UnrealEditor_Renderer
UnrealEditor_Renderer
UnrealEditor_Renderer
UnrealEditor_Core
UnrealEditor_Core
UnrealEditor_Core
UnrealEditor_RenderCore
UnrealEditor_RenderCore
UnrealEditor_Core
UnrealEditor_Core
kernel32
ntdll

Same problem here…

wish I saw this a few months ago, Im still having the same problem. Sorry to ressurect a dead thread but any solutions?

I think Nanite and Lumen support for VR is very close. Because the following statement is used in the roadmap published for UE 5.1:

Improved Workflows for XR Development

  • Moving towards rendering feature parity
    • Initial Stereo support for Nanite and Lumen, PC/Deferred Renderer only.

Same problem a year later with 5.1.1. Does anybody know the work around?

is a problem with mass ai plugin and VR … still no updates?
Note if you remove npcs and cars will work hahahah but what i need is the logic of AI working in VR

So, I’m not sure if I should post this here and if anyone finds it problematic please comment!

It’s in InstanceCullingMergedContext.cpp

I literally just “disabled” the check for the Hierarchical Z-Buffer and with a Source build of 5.2.1 and this little change I can run the Full demo in VR.

I havent built the project with this change though, so take this solution with a lot of caution!

Line 124: check(PrevHZB == nullptr || PrevHZB == GraphBuilder.RegisterExternalTexture(Context->PrevHZB) || PrevHZB != nullptr);

1 Like

what type to disable the code?

r.InstanceCulling.OcclusionCull 0

3 Likes

Thank you!!!

I guess it could be enough to switch to more suitable rendering settings and shaders for VR.

The fun fact is, that in a shipping build for VR, this error does not occur while it exists in the editor VR preview mode (Tested in UE 5.2)

Switching to more suitable config for VR rendering worked for me also to be able to run the VR preview right in the editor. Anyway, I have quite a lot trimmed project.

There was a mention of the connection of the error with MassAI plugin within the thread - it seems to be a nonsense for me - from the logic perspective as well as performed test and my experience - I use some parts of the Mass AI and still I am able to run it in the VR.

What were the config settings you had for the citysample demo to run in VR Preview?