4.4.1: Anyone able to run 'Minimum Default' without judder?'

Running 4.4.1 on a maxed out late 2013 iMac, Mavericks.
The framerate is capped at 60, so I'm getting 30 (max) on the DK2 in extended mode for an empty box.

Frame smoothing is deactivated, min desired frame rate > 75.

What am I doing wrong?

Is the 60 frames cap the issue or the "half-of-max-frame-count" on the DK2?

Interesting.

I ran BluePrint office yesterday on the same hardware but under Win7.

The framerate is around 130 on desktop with the native resolution of the 27" display.

Switching to the Oculus DK2 (extended) and the framerate divides by 4.

While under OSX O'm stuck at 30fps at best, under Windows I'm stuck at around 35fps.

There are tens of thousands DK2s out there - is really no one developing with UE4 for it?
Has everyone secretly solved the issues and is now guarding it as their precious competitive advantage?

Or is there just no interest discussing it?

I'd love to know too. I'm also seeing about 1/4 framerate with extended mode.

That seems about right from my experience. I had Storyteller running at 150FPS on monitor (1440p - all settings max), while Rift users reported getting on the order of 35fps, even on the same/similar hardware as my development machine.

One thing to try is to make sure you have a PostProcessVolume and turn off most of the effects... I think by default most are on, and some of them perform worse in VR than on monitor.

The biggest performance killers so far are

- The UE4-Editor going crazy in the background --> see viewtopic.php?f=60&t=13410&start=20#p182247
- 130% upscaling --> Deactivate with 'hmd sp 100' (costs a little bit sharpness)
- Single buffering in VR (?) and no asynchronous timewarp --> Wait for SDK updates
- Mirroring --> 'hmd mirror off'
- Twice the draw calls --> combine meshes where possible, user fewer objects, wait for UE4 updates for 3D reprojection of background objects instead of simply render them twice
- All quality settings on EPIC on default (WTF) --> Use command line arguments to lower them, see https://docs.unrealengine.com/latest/INT/Engine/Rendering/Scalability/ScalabilityReference/index.html#effects-sgstopeffectsquality
- No dynamic/automatic screen percentage and/or quality settings --> Nag Epic to implement this for VR or try to build it yourself (and then share it, please) ;)
- Dynamic lightning --> Use static lights where possible

You should also disable motion blur and lensflares.

spyro

Thanks spyro for sharing.

Yet I continue to believe an empty box should run faster than 35 frames.
I also continue to believe it's all subject to change, yet I find it discouraging to build on hope.

Last but not least - even if everything changes for the better, or in this case for the much much better, it's impossible to build and demo even simple stuff to clients.

What's the alternative? Is Unity better (at this stage of time for this very purpose) ?

Thanks & Cheers.

"spyro" wrote:
FYI: The standalone version seems faster because the editor in the backgrounds eats all the CPU performance when the game is started in the foreground ADDITIONALLY to the game itself. That's particulary strange as the load of the editor seems much higher in this situation.

Long story short:



Boom, judder is gone, performance is about the same as with the packaged version. Please remind that you have to redo this setting in every project (it resets itself each time). Why the hell isn't this the default setting?!

spyro

Genius. Worked like a charm. I now have silky smooth Performance

"artyom17" wrote:
Try also to reduce the quality by 'hmd sp 100' (use 'hmd sp reset' to reset screenpercentage back).

When I try this command, the screen in my oculus freezes. Interestingly, the output in my monitor still works fine, and it's still doing head tracking, but inside the oculus itself the display freezes.

"perry" wrote:

"artyom17" wrote:
Try also to reduce the quality by 'hmd sp 100' (use 'hmd sp reset' to reset screenpercentage back).

When I try this command, the screen in my oculus freezes. Interestingly, the output in my monitor still works fine, and it's still doing head tracking, but inside the oculus itself the display freezes.

Ive Just noticed this myself in direct to rift mode. In this mode it looks like SP is already fixed at 100 and any calls to change it, even if its the same value freezes the screen(not an issue for me in extended mode where the default is 135).

Im using Epics buid rarther than the oculus build.

Question for everybody, What are your system specs?

I benchmarked Senza Peso(a UE4 demo) The other day only to find out that my system is only using %80 of my gpu sometimes droping as low as 70%.

https://developer.oculusvr.com/forums/viewtopic.php?f=26&t=13835

Clocking my phenom 965 BE to 4.2Ghz didnt seem to improve matters though...

I still need to see what build and SDK they are using....
My own scenes seem to be fine though.