Supersampling with Oculus works again!

thafred · May 26, 2016

Just searched on Steam discussion for a image quality fix for assetto Corsa when I discovered this thread: debug tool

Download Oculus SDK 1.4, extract, open OculusDebugTool from the folder "Tools".
change the value of "Pixels Per Display Pixel Override" to 1.5, hit enter and launch EDLaunch.exe from the debug tool.

Works perfectly on my DK2, image quality is back to 0.6 levels and I´m very happy that Assetto Corsa and Elite Dangerous look better than the SweetFX mods I used to play on. You lucky CV1 owners will also find the image to clear up nicely

Only downside is framerate (about the same hit as Ingame SS in 0.6) but with a little ATW magic it´s not too bad.

Happy flying Commanders!

HeavyGroovez · May 26, 2016

I've found the sweet spot for me is 1.5x.

The difference it makes is astonishing.

I'm running a 1080 and I can just about nail 90fps everywhere. If I go up to 1.75 I start getting frame drops - only small ones but im really sensitive to any and all hitches so I aim for a perfect 90.

thafred · May 26, 2016

Great it works for you too!

I think impact is the same on framerate but thanks to atw you dont feel it as much. I had to swwitch from high to vrhigh but need more testing

Im on i7 920 and gtx980 btw

rich_hard1 · May 26, 2016

Using the Debug Tool at 2.0 and in Game at 2.0x produces negligible difference with the consumer rift, and loses tracking at times. Not an ideal solution, I still vouch that Frontier needs to fix it, as it was 'pre' SDK1.3. I got better busy as with SteamVR and 0.8!

thafred · May 26, 2016

In my posts I was refering to the ingame ss in 0.6 sdk days, i didnt think ss was working at the moment?

Maybe worth to try only the debug tool fix and revert back to 1x ingame?

jannix · May 27, 2016

Yes, the debug tool with 1.4 SDK seems to work. But it still has a pretty substantial hit on framerate here. Drops from a solid 90 fps to 45 fps. The performance impact with "Pixels Per Display Pixel Override" set to 1.5 seems comparable to setting in-game Supersampling to 1.5 on my setup. Both are a little bit below that acceptable fps limit for me, so I had to turn it back off.

dutchy2000 · May 28, 2016

Well depending on your system it may or may not work, but for me with 980Ti it actually fixes the completely blurriness of the text in 2.1, rep for thafred, thanks man.

CMDR Pausanias · May 28, 2016

thafred said:
Just searched on Steam discussion for a image quality fix for assetto Corsa when I discovered this thread: debug tool

Download Oculus SDK 1.4, extract, open OculusDebugTool from the folder "Tools".
change the value of "Pixels Per Display Pixel Override" to 1.5, hit enter and launch EDLaunch.exe from the debug tool.

Works perfectly on my DK2, image quality is back to 0.6 levels and I´m very happy that Assetto Corsa and Elite Dangerous look better than the SweetFX mods I used to play on. You lucky CV1 owners will also find the image to clear up nicely

Only downside is framerate (about the same hit as Ingame SS in 0.6) but with a little ATW magic it´s not too bad.

Happy flying Commanders!

I have found the same thing, since the update (and in BETA for that matter) text was blurry, UI wasn't too bad but in 2.1 you can barely read the text outside the cockpit and the Galaxy Map text is poor. I'm using a DK2 just to clarify.
I am not a confident PC user and am worried about messing with this when it's working to a degree, would you mind doing a step by step list to achieve the above please? Such as do I need to un-install SDK 1.6?, etc.
Frontier should still be 'helping' DK2 users whilst CV1's are still being shipped so late rather than just say 'not supported' and the text was fine before 2.1 Engineers so they should be able to sort it?
I have a 980 graphics card.

NoshDaMinsk · May 28, 2016

Latest Engineers update, I noticed the text was awful, so tried the following:-

Changed HUD to green, using these settings:-

<MatrixRed>0.18, 0, -1</MatrixRed>
<MatrixGreen>-1, 1, -1</MatrixGreen>
<MatrixBlue>0.15, 0.32, 1</MatrixBlue>

Also shows RED enemies - quite handy.

Run the DeBugger tool (which, incidentally, I had tried on DCS - 1.8 setting, with a high res cockpit for the KA50 looks remarkable). Used 1.5 in the settings.

In ED set graphics levels to ULTRA.

Launched the game and the text is really clear, graphics look lush and no FPS hit for me.

Black smearing is there - tweaked GAMMA and found 25% the best setting for me - still smears, though, and looks vile....

Running with a DK2, 980TI, 32 gigs of DDR4000 RAM and i7-6700

Nosh

stevesideas · May 28, 2016

What am I doing wrong? I try to launch ED.exe directly through the debug tool and ED then tells me I need to launch through the launcher. If I try to launch through the launcher the debug tool tells me it cannot run and requires elevation.

Slochy · May 28, 2016

Don't launch it using the Debug tool, simply leave it running in the background when starting Elite the usual way.

ghcannon · May 28, 2016

stevesideas said:
What am I doing wrong? I try to launch ED.exe directly through the debug tool and ED then tells me I need to launch through the launcher. If I try to launch through the launcher the debug tool tells me it cannot run and requires elevation.

Try running everything as administrator. (right click->run as admin)

stevesideas · May 28, 2016

Just running the tool without changing anything makes the safety screen and ED judder.

HeavyGroovez · May 28, 2016

stevesideas said:
Just running the tool without changing anything makes the safety screen and ED judder.

1. Run the tool
2. Set the override to 1.5 and hit enter
3. Launch Oculus Home
4. Experience judder
5. Close debug tool
6. Judder will stop
7. Launch Elite from wherever and you are good to go

stevesideas · May 28, 2016

HeavyGroovez said:
1. Run the tool
2. Set the override to 1.5 and hit enter
3. Launch Oculus Home
4. Experience judder
5. Close debug tool
6. Judder will stop
7. Launch Elite from wherever and you are good to go

Thank you

stevesideas · May 28, 2016

Well, that's definately an improvement ! It doesn't seem quite as sharp as prior to 1.3sdk. The text seems to shimmer more but it is a good improvement over the SS you get in ED and I cannot see any frame drop at the moment. I'm running a 980gtx (standard). Will the CV1 be that much better than this ?

Thanks for sharing this find !

horizone · May 28, 2016

Holy smoke, this makes it great!

CMDR Pausanias · May 28, 2016

Hi DK2 users with blurry text, I have tried to list here what I did to sort this in more depth, thanks to thafred and a bit of messing about.

DO NOT DELETE your latest Oculus SDK Runtime!
1) https://developer.oculus.com/downloads/ will take you to the Oculus downloads page.
2) Select Oculus SDK for Windows V1.4.0 by hitting DETAILS
3) DOWNLOAD 1.4
4) When its finished find the OCULUS DEBUG TOOL.exe on your machine in DOWNLOADS > ovr_sdk_win_1.4.0_public > OculusSDK > Tools
5) Run it
6) Change PIXELS PER DISPLAY PIXEL OVERRIDE to 1.5 hit ENTER (Perhaps pin this to your task bar?)
7) Run ED Launcher as normal
Now I had lots of juddering when ED was loaded but CLOSE the DeBug Tool Window and it clears the judder, perfect text again!!!
I think you can close the ODBT as soon as ED even starts to load.
I notice my Blue Light is out on the sensor when the ODBT is running but comes on when you close it. Blue light on Headset is on all the time.

To run:-
After computer start-up and switching your Oculus on (Orange light) click the Oculus Debug Tool you've pinned to your task bar first.
Enter a value in the Pixels Per Display field (I've settled on 1.75 with my GFX980 card) but experiment with values. Any higher and I get juddering.
Run ED from it's launcher as normal, mine auto loads my Oculus SDK software.
When the START screen appears it's juddery for me, close the Debug Tool down, the juddering stops.
Play with superb graphics!

PS - I use a Green HUD, nice text but the Engineers Photos are a funny colour!!!!

If any of the above needs a tweak please say so.

Raptoyd · May 29, 2016

Pausanias said:
Hi DK2 users with blurry text, I have tried to list here what I did to sort this in more depth, thanks to thafred and a bit of messing about.

DO NOT DELETE Oculus SDK 1.6!
1) https://developer.oculus.com/downloads/ will take you to the Oculus downloads page.
2) Select Oculus SDK for Windows V1.4.0 by hitting DETAILS
3) DOWNLOAD 1.4
4) When its finished find the OCULUS DEBUG TOOL.exe on your machine in DOWNLOADS > ovr_sdk_win_1.4.0_public > OculusSDK > Tools
5) Run it
6) Change PIXELS PER DISPLAY PIXEL OVERRIDE to 1.5 hit ENTER (Perhaps pin this to your task bar?)
7) Run ED Launcher as normal
Now I had lots of juddering when ED was loaded but CLOSE the DeBug Tool Window and it clears the judder, perfect text again!!!
I think you can close the ODBT as soon as ED even starts to load.
I notice my Blue Light is out on the sensor when the ODBT is running but comes on when you close it. Blue light on Headset is on all the time.

PS - I use a Green HUD, nice text but the Engineers Photos are a funny colour!!!!

If any of the above needs a tweak please say so.

Thank you going to try this after the last update the game is definitely more playable than before and this might even help more

rich_hard1 · May 29, 2016

Actually it's now proven that you need to first set elite to X1.0 SS, then close Elite. Then open 'home', then run the debug tool set it to 1.5x, open elite as usual, N.B. keep the tool open in the background (this will keep SS and tracking active).