Skip to main content
leftbigtoe
Up and Coming
October 7, 2014

Performance Issues when using Direct To Rift Mode

Hey guys,

we are experiencing some performance issues with the the Direct to Rift Mode:

    - Running in extended mode with vsync we get solid 75fps
    - turning vsync off it goes up to around 150fps
    - as soon as we use Direct to Rift, it hovers around 62 to 65fps, vsync off or on

The worst part about the 62 to 65fps is that it causes really bad jutter (guess timewarp is not working correctly or something). It would be really great for our application to be able to use the second screen feature of the Direct to Rift mode, so just using extended mode is not really an option.

setup: i7 / 32GB RAM / Titan

Any ideas or people having similar issues?

    6 replies

    cybereality
    Inspiring
    October 7, 2014
    Do these issues happen with the demo scene or Tuscany? Is it only your app with the problem?
    AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
    throwaway69
    Participant
    October 7, 2014
    "cybereality" wrote:
    Do these issues happen with the demo scene or Tuscany? Is it only your app with the problem?

    Hah! Only HIS app with the problem?

    I dunno how you guys are unaware but the number of working rift applications using direct mode (excluding tuscany/demo scene) is approximately ZERO!

    Every single application I've tried in direct mode has either crashed outright before anything was displayed in the rift, or has horrible judder/latency/wrong resolution/orientation. Sometimes you get blue screens that lock up your entire system.

    It's not like the OP is the only one experiencing this! Direct mode is clearly not in a workable state with the current SDK.
    cybereality
    Inspiring
    October 7, 2014
    "throwaway69" wrote:
    I dunno how you guys are unaware but the number of working rift applications using direct mode (excluding tuscany/demo scene) is approximately ZERO!

    Actually, Sightline: The Chair seems to work OK for me in Direct mode. I am aware that people are experiencing problems with Direct mode, and the guys are working on fixing it now.
    AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
    leftbigtoeAuthor
    Up and Coming
    October 8, 2014
    Tuscany is working like a charm on our system, however most demos don't.
    There seems to be a certain bit of magic configuration needed to make it work, Tuscany and a few other demos are the proof that it is possible, would be great to get a hint on what to investigate though, right now we are a bit in the dark. Thought this should be the right place to tackle this issue, some devs apparently pressed the correct buttons ;)
    ZombieJ
    Participant
    October 8, 2014
    "leftbigtoe" wrote:
    Tuscany is working like a charm on our system, however most demos don't.


    In my experience different firewall setups can cause this. At home I can get 2/3 "Direct To Rift" demos working no problem (except for the usual tearing/stuttering/etc. that is associated with DtR mode/the current SDK version). At work I can only run a couple of the same demos at all.

    The differences? I have a GTX 580 at home and a 660 at work, one monitor at home and two at work. All other components that matter are identical. But undoubtedly more important is that my work has a more restrictive firewall than I use at home. If I blow mine wide open when using the rift I get a much better level of functionality. I've specifically tested it too: blocking all outgoing ports at home stops demos that normally work from loading. If you are using the rift at your office perhaps you are in a similarly restricted environment. You may find that setting up a less secure network purely for using the rift with will improve things for you.
    leftbigtoeAuthor
    Up and Coming
    October 17, 2014
    solved my issues and got it running nicely using this how to
    viewtopic.php?f=37&t=12160
    (works for SDK 4.2 & Unity 4.5 as well)
    Terms & ConditionsAccessibility statement