What's happening with VRWorks support

[anonymous_user_21e38222]

@kAzAAkAs;683623

Hey there people,

I’m finishing up a really big VR project this week. Due to a bug in 4.14 that caused child actor references to crash the engine I upgraded to 4.15.
Point is, there is no VRWorks fork for version 4.15 of the engine. I don’t think this is logical, because it’s biggest feature was forward shading, which was specifically targeted at VR, but now the other VR optimizations are not available.

There used to be a fork of 4.14 on NvPhysX · GitHub. It included the whole package of optimizations: lens matched shading, multires, single pass stereo and VR SLI.
I’ve come to the conclusion that I kind of need VRWorks to deliver my project in an acceptable state. Even with the GTX1080 that’s in the system now, the performance of not high enough to enable a sufficient screen size to get a sharp image. I also can’t revert back to 4.14 anymore, because I have committed way too much changes to my project (150+ hrs) to ever revert back to 4.14… In fact, I cannot even find the VRWorks fork on github anymore.

Is VRWorks being abandoned? I hope not, sounds very promising and I would very much like to use it.

Best of wishes.

Hey kAzAAkAs,

Glad I’m not the only one in the exact same position (moved to UE4.15 because of the child actor ref crash, cannot use VRworks because the branch has not been updated to 4.15 yet and I don’t have enough C++/git experience to merge).

The NvPhysx branches of UE4 for VXGI, Volumetric Lighting, Flex and Flow have been updated to 4.15 recently, we can only hope the VRworks branch will follow in the next few days.
Even rough estimate from Nvidia or any communication about VRworks developpement would be great, our VR projects are in dire need of performance and LMS/MultiRes/VRsli allows to boost significantly frametime/framerate…