37.5 fps lock issue with DK2: strange in-game "fix" (4.6.1.)

Hi everyone,

I’m working on an UE4 Oculus Rift Game that is due to release shortly.

However, i’m still having issues with the 37.5fps lock that has been described in other posts already. I’m working with UE4.6.1 and Oculus Runtime 4.4.

I get good and steady 75fps most of the time (even in the most complex levels), but sometimes on startup of far less complex levels the framerate drops to 37.5fps immediately. Not always, but sometimes.

Now here is what puzzles me: when at 37.5fps, I can simply look away with my DK2, and then look back at the same spot, and voilà: it’s back to 75fps and stays there. However, if I don’t look away, the framerate stays at 37.5fps even when I move. Looking away seems to reset the framerate.

So the issue really doesn’t seem to be performance-related, at least not in my project.

But if simply looking away “fixes” the issue, there has to be a software fix, doesn’t there? Something like telling the engine “ok, you’re at 37.5fps? Try 75fps AGAIN! You already proved you can do it!”

Anyone has been able to “fix” his framerate in the same way?

Also: has anybody experienced an improvement of the issue in UE4.7?

Thanks so much in advance!

You might want to try what I did here : http://fatedblog.com/2015/03/12/getting-your-mind-and-hardware-ready-for-vr/
It may not be your problem but it solved it for me! It’s at the end of the post, in the “Beware of Nvidia Control Panel” section.

Hope this helps!

Mick