...HMD Quality at 1.0. And in the tray tool I've set pixel density to 2.0.
Still blurry though.
Mmh, isn't the HMD setting in Elite preferences and the pixel density in Oculus pref the same?
I see no difference.
...HMD Quality at 1.0. And in the tray tool I've set pixel density to 2.0.
Still blurry though.
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).
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 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.