Supersampling with Oculus works again!

[gamer101]

The pixel density gets applied whenever you enter or leave the hangar in a station. It also seems to occur when new textures are loaded (approaching stations etc)

I can change the pixel settings in the sdk tool,and have elite show the change on the fly.

Go to a station and land/dock.

Load the SDK tool and enter a pixel density setting (eg 1.500000). Click the mouse back onto your ED window.

In your cockpit, choose "Enter Hangar". The instant you select that option, the screen will adopt your pixel settings. If you look at your dash panel text (Look at the words MASS LOCKED) while you click, you can spot the difference as it gets applied. (Basically, the text develops a lot less shimmer and the crawling AA disappears)

Likewise, if you are already in the hangar, when you choose to return to the surface, the pixel setting will be applied.

In my case, to play ED ....

1. Load oculus home
2. Load the SDK tool
3. Change the pixel density (but leave the SDK tool loaded otherwise it will reset when you exit a hangar)
4. Load Elite

Play the game and enjoy the new image improvement.

As I said, leave the SDK tool loaded, otherwise the pixel density resets when I enter or leave a hangar.

The best option vs performance I have found after several tests and screen captures is ....

Pixel Density 1.2
Set ED SS to 1.0
Enable MSAA in ED

With these settings I can be in the station at 90fps and 80% CPU load, with an image that is better than the ED 1.5SS which in my case, normally runs at 98% GPU and 45fps.

 

[Cmdr Spencer]

Oh Yes!!!

For me, the sharpness is better than any version prior to 1.3 i've played

Unbelievable difference!

This needs to be stickied!

The colours are better, the stars are...sharp, not blurry at all, the way it was meant to be and better than i got with sweetfx

The text - wow, so sharp

Just been to an engineers base, incredible

This has transformed the DK2 experience for me

 

[jannix]

Just updating here. After several more hours, my intermittent bugcheck issues do not look related to this in any way. Must have been thermals. It was a hot few days last week.

 

[Cornelius lucius]

Just a query on using the sdk tool. Does this only work when you are launching ED through Oculus Home?. I have tried various combinations of starting before OH and ED and after etc and I can't seem to see a great deal (if any) of difference with it.
I'm running ED on Ultra with a 980ti and i7 4770 with 32GB of ram.

 

[CMDR KENNEDY]

Just a query on using the sdk tool. Does this only work when you are launching ED through Oculus Home?. I have tried various combinations of starting before OH and ED and after etc and I can't seem to see a great deal (if any) of difference with it.
I'm running ED on Ultra with a 980ti and i7 4770 with 32GB of ram.

No, it also works if launching ED straight from the ED launcher. The difference is quite stark, so I would be surprised if it wasn't evident.

(Although I do accept that our brain is a wonderful machine and it compensates for so many things. After extended playing you can kind of go VR blind after a while and wonder whether you are imagining things that may, or may not, have changed. If that happens, I step away from ED for 24 hours and give my brain time to reset. It is worrying when you dreams have green pixels in them.)

 

[Cornelius lucius]

Hmmm I may have to try again with it then. Hopefully I'll notice some difference this time

 

[stevesideas]

This is interesting. From another thread someone mentioned you could close down the debug tool. If I have the debug tool running even with no change on the pixel density I have a slow down in performance, even when just viewing Oculus home which isn't taxing on the GPU/CPU.

Are you sure you cannot just set the PD and then close the tool for it to maintain the same PD until you exit ED.

 

[gamer101]

This is interesting. From another thread someone mentioned you could close down the debug tool. If I have the debug tool running even with no change on the pixel density I have a slow down in performance, even when just viewing Oculus home which isn't taxing on the GPU/CPU.

Are you sure you cannot just set the PD and then close the tool for it to maintain the same PD until you exit ED.

Yes, I have confirmed this. I need to leave the SDKtool loaded.

If I sit in a station, each time I enter or leave the hangar, the pixel density setting gets applied / re-applied to the display.

I can use this as a way to tweak the PD setting and see the results immediately, simply by bouncing in or out of a hangar.

So if I unload the SDK tool, the next time I leave or enter the hangar, the graphics resets to default. So I have to keep the SDK tool loaded.

So long as I load the Oculus Home first, then the SDKtool, I don't notice a performance drop. But then , like I said, I cannot unload the SDKtool in anycase, otherwise the image resets when I leave the hangar.

Perhaps if I start the game "in space" and spend all my time in space, I could possibly unload the tool.

I am on Windows 10 with a 980ti.

I have found that a PD of 1.2 + SMAA adds a lot of improvement, but allows me to still have 90FPS in the station and hangar. In these locations my GPU is running under 80%. I can improve the image more with a higher PD setting, but then I get lower FPS in stations. I'd rather keep the 90fps everywhere.

Things may differ when I can get my hands on an oc'd 1080ti one day.

I wish there was an entry I could put in the netserver.cfg to make this tweak permanent and not have to load the SDKtool at all.

 

[ZZZRonin]

Yes, I have confirmed this. I need to leave the SDKtool loaded.

If I sit in a station, each time I enter or leave the hangar, the pixel density setting gets applied / re-applied to the display.

I can use this as a way to tweak the PD setting and see the results immediately, simply by bouncing in or out of a hangar.

So if I unload the SDK tool, the next time I leave or enter the hangar, the graphics resets to default. So I have to keep the SDK tool loaded.

So long as I load the Oculus Home first, then the SDKtool, I don't notice a performance drop. But then , like I said, I cannot unload the SDKtool in anycase, otherwise the image resets when I leave the hangar.

Perhaps if I start the game "in space" and spend all my time in space, I could possibly unload the tool.

I am on Windows 10 with a 980ti.

I have found that a PD of 1.2 + SMAA adds a lot of improvement, but allows me to still have 90FPS in the station and hangar. In these locations my GPU is running under 80%. I can improve the image more with a higher PD setting, but then I get lower FPS in stations. I'd rather keep the 90fps everywhere.

Things may differ when I can get my hands on an oc'd 1080ti one day.

I wish there was an entry I could put in the netserver.cfg to make this tweak permanent and not have to load the SDKtool at all.

Nice. Will try this at home !

 

[dogbite]

For the newcomers https://youtu.be/ZsuLujzHK7w

 

[BlackSpaceCowboy]

i'm reviving this thread because those that have a CV1 and a good graphics card... they don't know what they are loosing if they don't try it.


It's amazing how crisp and detailed everythin looks with pixel density in 1.5, tryed it in another games like war thunder ot Valkyrie and it's like i have a CV2 NOW!! shame even with a 980ti cant handle that pixel density well in those games, but ED seems to work much better compared with the "in game" supersampling.

my objective now is to OC my 980ti and see if i have positive results with the frame rate,, if not i definetly will go for a 1080ti when it comes out because playing with the rift that way is like day and night.

This VR thing is suprising me more and more every day.

Are there unnecessary settings that you can lower instead?

I also have a 980ti. I will get around to trying this tweak. I hope I don't need to buy a 1080. I just bought a i7 6700k and my 980Ti is fairly new and it's already "superclocked."

What memory and processor do you have? Would a CPU overclock help?

 

[beelzerob]

I gave it a go tonight on my CV1. Launched Oculus Home, then the Debug tool, then ED from Steam. Sat in the station and just kept switching from Enter Hanger and Exit Hanger (no need to fly).

I could tell as soon as I set the Pixel Density to 1.2 that it was doing something because I began to immediately get judder (I have a GeForce 970). Despite the judder, I believe it is correct that the actual pixel density isn't actually applied until you Enter/Exit the Hanger.

I could tell it was different at 2.0, but it was definitely *subtle* to me. It did reduce the shimmering of text a bit. If I had enough graphical horsepower, then it'd definitely be worth doing (no downside, really), but it was not a "wow" moment for me.

I'm probably going to do the EVGA Step-Up program for my 970 to a 1070 and then hopefully I'll be able to do this.

 

[BlackSpaceCowboy]

Holy shizle this needs a BUMP

got CV1 , in ED i put SS to 1x . then what i do is run debug tool set to 2 then enter. then open oculus home (you get judder) then open elite normaly and login. then i go into open/solo or group (then i get bad judder) then just close DEBUG TOOL and i get tracking back and judder is gone BUT SS stays . And holy moly this sharpen things up. I was totaly blown away from dk2 to CV1 but this put things up a lot more NOOOICE find guys

THXXXX

This worked!

The other suggestions created jidder. You have to close the debug tool to get no jidder. This should be stickied.

I used VR High with SS 1x and 1.5 in the debug tool. Smooth as butter on my 980Ti i7 6700K. Thank you!

 

[subsy]

This worked!

The other suggestions created jidder. You have to close the debug tool to get no jidder. This should be stickied.

I used VR High with SS 1x and 1.5 in the debug tool. Smooth as butter on my 980Ti i7 6700K. Thank you!

Not strictly true - your method will only persist until you enter/exit a hanger.

For persistent setting the correct order is

- open oculus home
- run debug tool and set density to desired value (I'm using 2.0 with a GTX 1080 and DK2)
- leave debug tool open
- run ed launcher and lunch game

 

[Raptoyd]

Not strictly true - your method will only persist until you enter/exit a hanger.

For persistent setting the correct order is

- open oculus home
- run debug tool and set density to desired value (I'm using 2.0 with a GTX 1080 and DK2)
- leave debug tool open
- run ed launcher and lunch game

What are you set at in game?

 

[Oogie Boogie]

Would you put the pixel density higher (SDK tool) or preferably the Supersampling factor?
I have a GTX 1080 with SS 1,0 and SDK 1,5 and it looks already great.

 

[Raptoyd]

Would you put the pixel density higher (SDK tool) or preferably the Supersampling factor?
I have a GTX 1080 with SS 1,0 and SDK 1,5 and it looks already great.

Is that set to VR High also?

 

[Dozer.k.a.o.]

Are there unnecessary settings that you can lower instead?

I also have a 980ti. I will get around to trying this tweak. I hope I don't need to buy a 1080. I just bought a i7 6700k and my 980Ti is fairly new and it's already "superclocked."

What memory and processor do you have? Would a CPU overclock help?

i7- 4770K, 8Gb ram VR in high but shadow set to ultra

I have to say that after the initial excitement i had to move the pixel density to 1.2

I have a lot of stutter now, even with VR low, no pixel density or SS inside the game, i don't know what's going on.

Will format my SSD soon, will install W10 and will move from 8 gb to 16gb, it's stupid that with a 890ti i can't , for example, turn my ship in supercruise without having flickering.

 

[Dozer.k.a.o.]

Would you put the pixel density higher (SDK tool) or preferably the Supersampling factor?
I have a GTX 1080 with SS 1,0 and SDK 1,5 and it looks already great.

Both are like different kind of supersampling.

With PD you have a more crisp image, very noticeable in the elements close to you,, everythin looks nitid and clear, however, it doesn't solve well the jagging lines or the objects in distance.

With SS the image in general is more antialiased, and jagging lines get a huge improvement, nice for elements in distance , or for example flying around stations or outposts.

I personally prefer to use the PD, it's like having a CV1.5 also i think it has less FPS impact, not sure. Maybe in your case would be nice to have SS1.25 and PD1.25... half and half

 

[gamer101]

I run PD of 1.2 and enable MSAA in the game. This is the sweet spot for me where I get noticeable image improvement (much better than ED's SS1.5) but still maintaining 90fps in stations. I have a 980ti.