Announcement

Collapse
No announcement yet.

[VRWorks][Unreal] VRWorks in Unreal Engine 4.13 branch seems not to work well

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    [VRWorks][Unreal] VRWorks in Unreal Engine 4.13 branch seems not to work well

    Hello, I am developing a game demo on Unreal. In order to apply the new features in graphics card (I work on GTX 1060), I downloaded the unreal engine 4.13 with VRWorks branch (https://github.com/NvPhysX/UnrealEng...-Graphics-4.13) and built the engine.
    I turned the RealisticRendering project(in epic learn resources) into a VR setup and tested the GPU rendering features. However, the results were not I expected them to be.

    In the test, I used a HTC Vive to look at this scene stilll in the project:
    Click image for larger version

Name:	scene.jpg
Views:	1
Size:	47.7 KB
ID:	1201213

    Before I turned the features(MultiRes Rendering, Lens Matched Rendering and SinglePassStereo) on:
    Click image for larger version

Name:	before.jpg
Views:	1
Size:	132.8 KB
ID:	1201214

    After turned on...
    Click image for larger version

Name:	after.jpg
Views:	1
Size:	130.8 KB
ID:	1201215

    #2
    You have to actually apply the different settings for them.

    vr.multiresrendering 0-3
    vr.lensmatchedshadingrendering 0-3

    vr.multires and vr.lensmatchedshading just enabled support for them, the rendering postfixed commands set the level of them.

    Also i'll note that the full VRWorks branch is missing a ton of compatibility checks for AMD cards, specifically I had to fix them auto checking for SLI with an NVIDIA api call and causing instant crashes if the user had an AMD card (doesn't implement the API). Also some of the rendering features are straight broken with AMD on that branch currently (shadow flicker, orientation based rendering artifacts).

    The multiresrendering only branch works fine with AMD currently, you might want to consider sticking with that one if you want to use either of them at the moment.


    Consider supporting me on patreon

    My Open source tools and plugins
    Advanced Sessions Plugin
    VR Expansion Plugin

    Comment


      #3
      Thanks! It works pretty well now! It's kind of amazing~
      Click image for larger version

Name:	worked.jpg
Views:	1
Size:	83.3 KB
ID:	1119177

      Comment


        #4
        BTW, may I ask the approximate date of the release of unreal 4.14 branch with VRWorks integrated? Cuz applying both VRWorks' functions and forwarding rendering in 4.14 engine in demo will be really cool~

        Comment


          #5
          Settings confusion

          Originally posted by mordentral View Post
          You have to actually apply the different settings for them.

          vr.multiresrendering 0-3
          vr.lensmatchedshadingrendering 0-3

          vr.multires and vr.lensmatchedshading just enabled support for them, the rendering postfixed commands set the level of them.

          Also i'll note that the full VRWorks branch is missing a ton of compatibility checks for AMD cards, specifically I had to fix them auto checking for SLI with an NVIDIA api call and causing instant crashes if the user had an AMD card (doesn't implement the API). Also some of the rendering features are straight broken with AMD on that branch currently (shadow flicker, orientation based rendering artifacts).

          The multiresrendering only branch works fine with AMD currently, you might want to consider sticking with that one if you want to use either of them at the moment.
          from what i understood from the vrworks docs I thought Multi res and lens matched shading were exclusive options, either one or the other. Their demo enforces that as well. However in unreal I am allowed to tick both. Can somebody explain this ?
          Also I have the same confusion related with instanced stereo ( which is from unreal) against single stereo pass (nvidia) which I also expect to conflict, but you can also choose them both. Help?

          Comment


            #6
            Originally posted by E951 View Post
            from what i understood from the vrworks docs I thought Multi res and lens matched shading were exclusive options, either one or the other. Their demo enforces that as well. However in unreal I am allowed to tick both. Can somebody explain this ?
            Also I have the same confusion related with instanced stereo ( which is from unreal) against single stereo pass (nvidia) which I also expect to conflict, but you can also choose them both. Help?
            If you have lens matched on then the multires value does nothing. Lens matched is a derivative of multires and automatically uses it. They give you the option to just use multires by itself if you want.


            Consider supporting me on patreon

            My Open source tools and plugins
            Advanced Sessions Plugin
            VR Expansion Plugin

            Comment


              #7
              comparing the results of gpuprofile

              Originally posted by mordentral View Post
              If you have lens matched on then the multires value does nothing. Lens matched is a derivative of multires and automatically uses it. They give you the option to just use multires by itself if you want.
              Thank you!
              At the moment I am using the gpuprofile frame capture to see any changes. I do it while I am running this in the vrpreview mode. The window on my desktop screen is still open. Is this a good way to profile this ? I noticed that instanced stereo has a value of 0 ms for the base pass for one of the views. Then I tried the single pass stereo , both views are equal ms. When I have no option on, basepass for view one and view 2 are also equal.

              I also got confused cause in the flex demo from the vrfunhouse (which is an older unreal version) has instanced stereo, multi res and lms turned on.
              I'm trying to make some sense of it, so I can decide if this would help me on my project.
              Also if anybody can give me any tips on how to properly profile the vr rendering I am all ears.
              instanced stereo
              Click image for larger version

Name:	ue vw 4.13 instanced stereo.png
Views:	1
Size:	56.4 KB
ID:	1119186
              nothing:
              Click image for larger version

Name:	uevw 4.13 nothing.png
Views:	1
Size:	85.5 KB
ID:	1119188
              single pass stereo:
              Click image for larger version

Name:	uevw 4.13 single pass stereo.png
Views:	1
Size:	85.6 KB
ID:	1119187

              Comment


                #8
                forgot to set the value as well

                after calling the fc you suggested above to the other user, having single pass stereo on does give one view for 0 ms just like the instanced stereo. also multisample worked.

                Comment


                  #9
                  Take a look at SceneView.cpp SetupVRProjection, you can see if LensMatchedShading is On and is supported it will be used, otherwise MultiRes is checked. This is great as you can leave both on for Maxwell and Pascal cards and it will use the best features available

                  Comment

                  Working...
                  X