Oculus dk2 dropped frames warning and poor performance

Hi,

When I run the realistic rendering demo I seem to get very good performance when displaying to my primary monitor (by running “stereo on” in the console and leaving the window on the regular display). Specifically, the render time displayed by "Stat Unit’ and "Stat Unitgraph) is consistently around 7ms, well below the ~23 ms necessary for the native 75 FPS of the DK2

However, when I display the demo on the rift itself, the perceived performance is really awful (nowhere near native refresh).

Additionally, I get a lot of really suspicious messages in the engine log that look like this (esp. when moving my head):
[2014.08.28-03.17.48:781][335]LogHMD:Warning: Skipping frame: FinishRendering called with no corresponding BeginRendering (was BackBuffer re-allocated?)

These messages do not appear when I leave the game on the primary window with “stereo on”.

Any Ideas?

System info:
NVIDIA GeForce GTX 780 3072MB
Xeon E3 1270v3 @ 3.5GHZ
Software Info:
Windows 8.1
UE 4.4.1
Oculus DK2 firmware 2.11
Oculus SDK 0.4.1
Oculus Display Driver Version: 1.0.24.0
Oculus Camera Driver Version: 0.0.1.6 and runtime
Oculus running in “extend display mode” (would love to know how to get direct to rift working…)

… so it looks like the problem was using a maximized window (by clicking on the maximize button in the window border). The symptom goes away if I maximize using alt+enter.

Hi 0xF00,

You can also use these Console Commands to help improve FPS.

hmd sp ### (The default ScreenSpace is 130 but you can lower it to a value like 100 or 80 to improve performance.)

hmd mirror off (This turns the rendering off on the monitor and saves the editor from having to render the scene twice.)

If you are working in the same project constantly, these can also be added to the LevelBlueprint as nodes and then be executed on EventBeginPlay.

TJ