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 github.com/NvPhysX. 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.
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…
I’ve upgraded my project to 4.15 a long time ago, reverting back to 4.14 is out of the question with the amount of work that has been invested. Other than that 4.14 had a nasty bug that it impossible to work with for me.
Hey man, yes it sucks!
Child actors are such a core piece of functionality I’m absolutely baffled that an official release version had such a huge bug in it.
I’m having the problem that I always build all the core game functionality first, then create the environments and look into possible optimizations last. Due to the child actor bug I encountered during this first step, I’ve now hit a brick wall during the third step. It makes me kind of sad, I have to launch this project next monday and the maximum screen size with a GTX1080 I can reliably run is 140. It’s still really blurry. Even with all static lighting, instanced stereo, actor merging, optimized culling/LOD’s and all that I can’t hit my personal standard of clarity, which is a screen size of 180, which I feel I could probably have hit easily with VRWorks, at least comparable clarity using multires and lens matched shading. Not having a blurred out image increases the realism immensely.
With 4.15’s main feature being forward shading, which is geared mainly at VR, I’m secretly hoping a fork is in the making…
I’m on 4.15 now, upgraded from 4.14. No VRWorks forks for that… ALso it turned out I did not have a subscription to the github repo of Nvidia, which is why I thought the repo’s were gone. Kind of stupid, github showing 404 whenever you do not have access has confused me since day one :’). I requested it now.
Well NVIDIA said they will keep their Tech updated with 2-3 weeks after the official release from Epic. They’ve merged flex to 4.14 at the beginning of March and flex is now updated to 4.15. VR Works been stuck on 4.11 for a long time and it seems to me NVIDIA got up to speed with the merges altogether so I have my hopes high.
It does but it hasn’t been updated from 4.11 for quite a long time, none of their branches have. It seems that after GDC, NVIDIA got up to speed with updates to their tech as far as UE4 implementation is concerned.
Wow, there is an eye tracker in the Vive?! That’s amazing! I work in a VR lab for psychological experimentation and this opens up a vast collection of possibilities for future research! Which software platform was this on?
I’m joining the chorus asking for an update of the VRWorks branch to 4.15. I’ve been using it since it included UE4’s forward shading (4.14). Along with the above reasons, I’m wanting to be able to start using the new audio mixer.