Oculus Debug Tool: Pixels Per Display Pixel Override

[Drexx]

You dont need the Oculus Debug Tool,

 

the Pixel Density Option is Built into DCS / Options / VR Tab.

 

Dunno why you'd see a difference, unless the Debug tool is using a different option now.

 

I know they disabled the DirectDisplayConfig.exe On/Off Command to enable you to easily adjust color/brightness settings..

 

The driver based pixel density is much more clear, since its a lower lvl option, try both you will see the difference, I think you need to run the debug tool first, with oculus home closed, then put on the headset after the debug pixel density change is done, oculus home boots up (and you will see a difference in oculus home), then boot any game, DCS look amazing with this!!!!! - you can read text in many cases

[fulcrum_64th]

So one just downloads the latest Debug tool and change PD to 1.3? I also changed ASW to auto. I just run DCS and all seems very smooth. How does one see is the DCS settings really got overridden by the Debug tool settings ?

[Drexx]

So one just downloads the latest Debug tool and change PD to 1.3? I also changed ASW to auto. I just run DCS and all seems very smooth. How does one see is the DCS settings really got overridden by the Debug tool settings ?

 

You should see a difference right away in oculus home (look at the carpet) when it boots up (I make sure oculus home is closed, open the debug tool and change the pixel override to around 1.5 or 2.0), put on the headset (oculus home relanches at this point), it will be clearer ( setting override 1.5 or higher) but 'in game' set the override to 1, don't have both running they wont override, they will stack (not good)..

[Aries144]

So one just downloads the latest Debug tool and change PD to 1.3? I also changed ASW to auto. I just run DCS and all seems very smooth. How does one see is the DCS settings really got overridden by the Debug tool settings ?

 

Set the PD in DCS VR settings to 1. Set the Pixels Per Display Pixel Override in the SDK to the highest your hardware allows. Typically between 1.3 and 2. Higher is better, but requires more powerful hardware.

[Burnhard]

I'm interested in knowing weather this actually is any improvement over the DCS PD setting.

[Aries144]

Try it. Both myself and Drexx think it is.

[dolfo]

I'm interested in knowing weather this actually is any improvement over the DCS PD setting.

 

BIG improvement I think.

[Einherjer]

Are you talking about the debug tool or the tray tool ?

[fulcrum_64th]

native oculus debug tool from their sdk

 

I "might" be seeing improvement. Maybe a placebo effect :megalol:

Edited April 16, 2017 by fulcrum_64th

[Einherjer]

Oculus Debug Tool: Pixels Per Display Pixel Override

 

And is there a difference to the PD Setting of the tray tool from oculus? It also seems to make a better effect than the ingame PD setting

 

Edit: oh I see , the tray tool a custom tool , but the effect seems to be the same

Edited April 16, 2017 by Einherjer

[simo1000rr]

How do i know if im Running Oculus Home Beta from Not ? i want to try this out but the OP said that it wont work with the Beta driver .

[epolta]

I tried it (the debug tool)... I'm calling Placebo... I cant' tell the difference between it and the in game PD... but if it makes you happy.. go for it! At the end of the day I'm at the point now where I just want to turn of the FPS and play... besides my eyes are probably too old to tell the difference.

[fitness88]

I'm using the Beta version for Oculus can someone please send me the link for Oculus Debug Tool that will work with it.

What's the difference between debug tool and tray tool?

[Bearfoot]

I'm using the Beta version for Oculus can someone please send me the link for Oculus Debug Tool that will work with it.

What's the difference between debug tool and tray tool?

 

Tray tool wraps the command-line debug tool with a GUI, and adds facility to control some other things, e.g. your USB power management. But largely the same. So, either/or.

[fitness88]

Tray tool wraps the command-line debug tool with a GUI, and adds facility to control some other things, e.g. your USB power management. But largely the same. So, either/or.

 

 

 

Thanks Bearfoot, I'll wait till I have a compatible version of Oculus to run with the ODT.

[simo1000rr]

Ok i tried this Debug tool last night . i can confirm its no a placebo thing , there is definitely a noticeable sharpness in the cockpit text . on top of that i can read the some of the stuff better like the Radar screen in the F15. i dont know how is it possible but it does. also i noticed that the game performance is better.

 

another thing, there is an option in the debug tool regarding GPU adaptive performance. what you guys set it to? i set mine to disable.

[fitness88]

Ok i tried this Debug tool last night . i can confirm its no a placebo thing , there is definitely a noticeable sharpness in the cockpit text . on top of that i can read the some of the stuff better like the Radar screen in the F15. i dont know how is it possible but it does. also i noticed that the game performance is better.

 

another thing, there is an option in the debug tool regarding GPU adaptive performance. what you guys set it to? i set mine to disable.

 

 

 

 

What version of Oculus Debug Tool are you running, in my help file it says version 0.3 but I also see file version 1.13.0.34162 in the ODT.exe properties.

The 2 options are off/default, I think it's set to default by default.

ASW should be set to auto.

 

Are you supposed to keep the Oculus Debug Tool running minimized or open on the desktop once you make your settings for pixels?

And the ingame setting for pixel is irrelevant because the ODT overrides it...is this correct?

Edited April 17, 2017 by fitness88

[simo1000rr]

What version of Oculus Debug Tool are you running, in my help file it says version 0.3 but I also see file version 1.13.0.34162 in the ODT.exe properties.

The 2 options are off/default, I think it's set to default by default.

ASW should be set to auto.

 

Are you supposed to keep the Oculus Debug Tool running minimized or open on the desktop once you make your settings for pixels?

And the ingame setting for pixel is irrelevant because the ODT overrides it...is this correct?

 

Ya im running the same file version as the one you mentioned above ( 1.13.0.34162) which is the latest debug tool from Oculus website ( 1.13.0) .

 

once you run the debug tool you have to leave it running in the background , doesn't matter minimized or maximized as long as you keep it running. Of course the debug tool override the game setting but still you have to keep the in-game setting at 1.0 since they will both try to run. i tried bumping the in-game one and it caused the performance to drop that's how i know they both try to run .

 

Edit : Also if you go in he oculus home , under settings >beta . make sure that the beta channel thing is on off . meaning that you are not participating in any beta test.

 

for the ASW i set it to disabled, i dont like the way it acts plus if your graphics card is VR capable this ASW should't be kicking off.

Edited April 17, 2017 by simo1000rr

[fitness88]

Ya im running the same file version as the one you mentioned above ( 1.13.0.34162) which is the latest debug tool from Oculus website ( 1.13.0) .

 

once you run the debug tool you have to leave it running in the background , doesn't matter minimized or maximized as long as you keep it running. Of course the debug tool override the game setting but still you have to keep the in-game setting at 1.0 since they will both try to run. i tried bumping the in-game one and it caused the performance to drop that's how i know they both try to run .

 

Edit : Also if you go in he oculus home , under settings >beta . make sure that the beta channel thing is on off . meaning that you are not participating in any beta test.

 

for the ASW i set it to disabled, i dont like the way it acts plus if your graphics card is VR capable this ASW should't be kicking off.

 

 

 

Thank for the info simo1000rr. So you need to do the same start up every time by launching OR...then ODT...then game, BTW do you use 'Game Mode'? I was told the reason ASW should be set to on/auto is that when your FPS drops below 90, it will maintain a 90FPS for the Rift by interpolating frames I believe, regardless of what FPS you see on the screen.

[dburne]

Why not just grab and use the Oculus Tray Tool and set it to do all this at startup?

I set a profile for Pixel Density for games that don't have built in support for it, and also ASW settings. I also have a profile for Oculus Home.

 

Set it and forget it. Don't even have to have the Debug Tool, the file it needs is included with the Tray Tool.

[simo1000rr]

Thank for the info simo1000rr. So you need to do the same start up every time by launching OR...then ODT...then game, BTW do you use 'Game Mode'? I was told the reason ASW should be set to on/auto is that when your FPS drops below 90, it will maintain a 90FPS for the Rift by interpolating frames I believe, regardless of what FPS you see on the screen.

 

The order of which you should run it us , debug tool first then the oculus run time then what ever game you like, you should notice right away that the runtime looks more crisp

[fitness88]

Why not just grab and use the Oculus Tray Tool and set it to do all this at startup?

I set a profile for Pixel Density for games that don't have built in support for it, and also ASW settings. I also have a profile for Oculus Home.

 

Set it and forget it. Don't even have to have the Debug Tool, the file it needs is included with the Tray Tool.

 

 

 

Thanks dburne, I think I had that tool but it may have gotten trashed also I realize I need to have matching versions of tools to Oculus. What version of Tray Tool are you using.

Have you tried Mustang's terrain mod, quite nice especially the mountains, they actually look real!

https://forums.eagle.ru/showthread.php?t=133618

 

 

I flew with a M-2000C last night for awhile, nice handling plane! I wonder if the probe obstructs the pilot's view?

[fitness88]

The order of which you should run it us , debug tool first then the oculus run time then what ever game you like, you should notice right away that the runtime looks more crisp

 

 

 

I see...I read a bit different but I'll try it your way till I can get the Tray Tool dburne mentioned.

[Einherjer]

Oculus Debug Tool: Pixels Per Display Pixel Override

 

I use the tray tool (0.68) works great and many useful options and voice commands for the overlay and spacewarp... oh and i use it with oculus Beta and it works

 

Edit - with the Beta from tonight it stopped working, now iam back on stable

Edited April 18, 2017 by Einherjer

[dburne]

Thanks dburne, I think I had that tool but it may have gotten trashed also I realize I need to have matching versions of tools to Oculus. What version of Tray Tool are you using.

Have you tried Mustang's terrain mod, quite nice especially the mountains, they actually look real!

https://forums.eagle.ru/showthread.php?t=133618

 

 

I flew with a M-2000C last night for awhile, nice handling plane! I wonder if the probe obstructs the pilot's view?

 

The latest version of OTT is .68, and it works great.

 

Have not tried any terrain mods yet.