Oculus Debug Tool or In-Game Settings?

[C.J. Solo]

So I'm hoping someone can help me to clarify a few things so that I'm using the right method to get the most out of my Rift (CV1). When it comes to using either using the Debug Tool or In-Game Settings....which should I use?

I've noticed that if I use the Debug Tool (opening before I open Oculus Home & leaving the in-game Supersampling setting at 1.0) I get washed out colors & terrible tracking. If I close the tool once in the cockpit the colors come back & so does tracking but do the Debug Tool settings stick?

Now if I open Oculus Home first then the Debug Tool, set my Pixel Density then launch ED the colors are there & the tracking is much better. I can leave the Tool open.

But back to the main question.....is the tool necessary since we have the option to change the Supersampling in the game? It seems like things are clearer & better detailed with the tool but I'm not sure if this is just mind playing tricks on me since I know the tool is running. Not sure if there is a difference other than more flexibility to run more PPD settings than presets in the game. I run at 1.8 but not sure if there is truly a difference between 1.8 & 1.5 or even 1.8 & 2.0. Since I'm not sure how I can take screenshots of the in-game view with the Rift its a bit hard for me to compare. Alot of 'not sure''s there......

Here are my specs in case they are needed in answering this question:

i7 6850K OC'd to 4.3 Ghz
32 Gig Ram
Sapphire 295x2
Sapphire 290X 8GB version (Crossfire disabled for ED since it doesnt make use of Crossfire)
Win 10 64-bit

 

[Ren Garris]

Here's my recipe-

1. Open Home.
2. Open the Debug. Set Pixel Density to 1.0 - 2.0 I use 1.3. <enter>
3. Leave the tool open.
4. Start Elite.
5. I set SS to 1.
6. I set Gamma to a low level. 2-3 ticks up.
7. HMD quality maxed.
8. Most all other setting are maxed.
I turn off bloom, blur and a few other things.
I would see what looks best to you for the AA, FXAA etc.

Thats about it. Sometimes I tweak things here or there. Steps 1-5 are a must.


i5 6700 ( ithink ) OC 4.2 Ghz
16Gb RAM
GTX 980Ti FTW
Win 10

 

[C.J. Solo]

Here's my recipe-

1. Open Home.
2. Open the Debug. Set Pixel Density to 1.0 - 2.0 I use 1.3. <enter>
3. Leave the tool open.
4. Start Elite.
5. I set SS to 1.
6. I set Gamma to a low level. 2-3 ticks up.
7. HMD quality maxed.
8. Most all other setting are maxed.
I turn off bloom, blur and a few other things.
I would see what looks best to you for the AA, FXAA etc.

Thats about it. Sometimes I tweak things here or there. Steps 1-5 are a must.


i5 6700 ( ithink ) OC 4.2 Ghz
16Gb RAM
GTX 980Ti FTW
Win 10

Thank Ren for the suggestions. I follow steps 1 & 2 but for some reason on my system I can't leave the tool open as I get horrible tracking & washed out colors. I think it has to do with the 295x2. The crazy thing is that if I close it after I get into the cockpit the settings seem to stick. I have SS set to 1 gamma at high (1 tick from right as it helps with God Rays) HMD at max & bloom/blur off. Everything else is maxed or high. Never thought to mess with the type of Anti-aliasing. i'll give that a try & see if that improves anything.

 

[Dozer.k.a.o.]

It's important you run oculus home first and then the debug tool to avoid stutter .

If you close the debug tool after running ED, soon or later will loose the Pixel density settings.. normally after entering into supercruise or accesing to the galaxy map

Both , pixel density (PD) and supersapling in game (ss) have different graphics behaviour, (this is my appreciation).

PD: elements in the mid and close range of your view looks more crisp and detailed, like with higher resolution, but there are a lot of jaggin lines, more noticeable in the elements that are far away.
SS,. makes a more antialiasing in the overall image,, reducing the jaginess inside station or when you see outposts in distance.

It's your decision what looks better to you.

 

[Ren Garris]

I tried PD and SS simultaneously.

Um, no. Jutter city kitty.

I heard the same about closing the tool, it eventually reverts back to default.

C.J. - Check the stickies the VR forum up top. The Oculus section has a few tips if you havent already.

 

[blastard]

Hi Commanders,
I'm following this thread with interest and have been playing with the oculus debug tool too.
I notice several of you have mentioned adjusting the supersampling 'in game'. I've checked the graphics menu in game but can't see any supersampling option. I know it used to be there pre 2.0.
Where exactly is this setting? or are you referring to the ss settings that are adjustable in eg. nvidia control panel.

Sorry for the noob question, its been a loooong day
07

 

[Raptoyd]

Hi Commanders,
I'm following this thread with interest and have been playing with the oculus debug tool too.
I notice several of you have mentioned adjusting the supersampling 'in game'. I've checked the graphics menu in game but can't see any supersampling option. I know it used to be there pre 2.0.
Where exactly is this setting? or are you referring to the ss settings that are adjustable in eg. nvidia control panel.

Sorry for the noob question, its been a loooong day
07

Use your mouse and hit the plus sign next to Quality in the graphics menu

 

[blastard]

Many thanks Raptoid. I was using my usual joystick to action the 'quality' tab and only saw the vr low, vr high etc settings. Should've known to use the mouse instead!. Sorted.

 

[CMDR MAIN SEQUENCE]

Just FYI you can assign a key/button to open the + sign. In Controls it is under Interface Mode I think and it's called Nested UI Toggle. I've assigned my secondary fire button on my HOTAS (annoyingly you can't re-use other GUI keybinds as they clash). One less time you need to revert to mouse in VR.

 

[Jypson]

So I'm hoping someone can help me to clarify a few things so that I'm using the right method to get the most out of my Rift (CV1). When it comes to using either using the Debug Tool or In-Game Settings....which should I use?

I've noticed that if I use the Debug Tool (opening before I open Oculus Home & leaving the in-game Supersampling setting at 1.0) I get washed out colors & terrible tracking. If I close the tool once in the cockpit the colors come back & so does tracking but do the Debug Tool settings stick?

Now if I open Oculus Home first then the Debug Tool, set my Pixel Density then launch ED the colors are there & the tracking is much better. I can leave the Tool open.

But back to the main question.....is the tool necessary since we have the option to change the Supersampling in the game? It seems like things are clearer & better detailed with the tool but I'm not sure if this is just mind playing tricks on me since I know the tool is running. Not sure if there is a difference other than more flexibility to run more PPD settings than presets in the game. I run at 1.8 but not sure if there is truly a difference between 1.8 & 1.5 or even 1.8 & 2.0. Since I'm not sure how I can take screenshots of the in-game view with the Rift its a bit hard for me to compare. Alot of 'not sure''s there......

Here are my specs in case they are needed in answering this question:

i7 6850K OC'd to 4.3 Ghz
32 Gig Ram
Sapphire 295x2
Sapphire 290X 8GB version (Crossfire disabled for ED since it doesnt make use of Crossfire)
Win 10 64-bit

Hey CMDR, what adapter are you using? I'm not having any luck at all with my Sapphire 295x2.