My new Rift! Woohoo! But a couple of questions...

Mmh, isn't the HMD setting in Elite preferences and the pixel density in Oculus pref the same?
I see no difference.

Yes. Not actually much point setting pixel density in the tray tool (nor pixels per pixel in the oculus debug tool) as the in-game HMD Quality sets the exact same thing (unless the tray tool has finer granularity and there's a very particular value you want to set).
 
Yes. Not actually much point setting pixel density in the tray tool (nor pixels per pixel in the oculus debug tool) as the in-game HMD Quality sets the exact same thing (unless the tray tool has finer granularity and there's a very particular value you want to set).

That's a key point iyam. For people with systems on the edge, subtle tweaks can help immensely.
1.2 might be OK performance-wise where ED's 1.25 might be just too high.

Has anyone looked to compare oculus debug tool with ED's pixel density efficiency?
 
Has anyone looked to compare oculus debug tool with ED's pixel density efficiency?

I could be wrong but my understanding is that the ED HMD quality is EXACTLY the same thing as the debug/tray tool setting, i.e. it's just a way of telling the Oculus software to upscale what it's rendering to the headset (and not a question of ED actually doing anything itself).
 
I could be wrong but my understanding is that the ED HMD quality is EXACTLY the same thing as the debug/tray tool setting, i.e. it's just a way of telling the Oculus software to upscale what it's rendering to the headset (and not a question of ED actually doing anything itself).

For me, it was quite noticeable. Trying settings of 2.0 in HMD Quality, and then 2.0 in the Tray Tool (after, ofcourse, returning HMDQ to 1.0), I get a much better framerate with the Tray Tool.
 
I could be wrong but my understanding is that the ED HMD quality is EXACTLY the same thing as the debug/tray tool setting, i.e. it's just a way of telling the Oculus software to upscale what it's rendering to the headset (and not a question of ED actually doing anything itself).

It really should be.
But then again the performance difference is way beyond noticeable.

Running hmd-q at 1.25 stations like the black blade runner or foundry factory type stations would drop to 45 and present noticeable artefacting.

Testing with just debug tool at 1.33 these stations are running at 90 in 99% of the time.

And it looks as good hmd-q 1.5.
 
For me, it was quite noticeable. Trying settings of 2.0 in HMD Quality, and then 2.0 in the Tray Tool (after, ofcourse, returning HMDQ to 1.0), I get a much better framerate with the Tray Tool.

Interesting. I'll give it a try. Maybe I'm completely wrong then. Would be great if we could get a dev to give us a definitive answer. If I remember I'll try and corner someone at the expo.
 
I would agree, i've been testing all sorts of things the last two weeks, and 1.5 on the tray tool definitely gives better performance thatn 1.5 HMD quality in game.
Plus, i can set 1.4 in the tray tool, which is a sweet spot where i get 90fps 100% of the time, on 1.5 its about 98% of the time (dipping to about 85fps with lots on screen).
With HMD at 1.5 in game, i get odd dips to 45fps here and there, not many to be honest, but none at all via the tool tray.
 
I would agree, i've been testing all sorts of things the last two weeks, and 1.5 on the tray tool definitely gives better performance than 1.5 HMD quality in game.

I don't see this. I just tested in a few very specific fixed situations and the performance is exactly the same for me. I suspect any better performance is just anecdotal based on slightly different situations. But while flying around there may be some actual performance increases that don't show up while just sitting in one place. Regardless, I do like that I can set 1.3 or 1.4 - I just wish I could set it at 1.35 like in the debug tool. But the best thing about the tray tool for me is the usb power management and registry hacks.
 
Back
Top Bottom