Where is the best place to supersample? Tray tool, Steam or in-game?

I've always used the tray tool unless there is an in-game option.

Anyone with more time tested out each method? Does either offer better performance?

Posted Apr 7, 2018, 7:28 AM UTC

532
profanicus•

For interests sake and to try get some kind of data rather than rely on notoriously poor human memories, perceptions, and biases I made some comparison screens. :)

Each screen shows the same scene with the SS value set either by the game, SteamVR, or Oculus.

Keep in mind there are slight differences due to minor headset wobble (it's very sensitive!) and small time differences in taking each shot.

And as you will see from the Left/Right Viewport stat, each method does request a slightly different render resolution (likely due to conversion errors in the scales used)!

Considering that, the screens look to be of identical quality to me.

  • Shots were taken using the screenshot function of the OculusMirror tool that comes with the Rift
  • Screens are from a single eye and don't include the distortions
  • Window size was set at the native eye render resolution of 1344x1600 so it should be 1:1
  • Screens include the Oculus Debug Tool overlay showing render resolutions and pixel density
  • TAA was turned off

I used cubeupload to try keep it lossless. Make sure to click the '+' when hovering over each pic to zoom to 1:1.

Default game with no supersampling: http://i.cubeupload.com/XK4BDx.png

Set to 2x in the SkyrimPrefs.ini: http://i.cubeupload.com/QMyLCO.png

Set to 200% in SteamVR: http://i.cubeupload.com/wuU028.png

Set to 1.43 in the Oculus Debug Tool: http://i.cubeupload.com/u1Ue5o.png

(sorry, I don't know how to embed pics here)

5
Beepboopbob1•

Thanks for taking the time to do this. I remember some guy in the Fallout 4 VR sub was so sure that the two SS methods were different that he spent days trying out different combinations and made a post with random descriptors for each one like muddy vs soupy or sharp vs crisp. I pointed out how scientifically useless it all was and how a single screenshot would settle everything but he ignored me and I was too lazy to prove it to him.

1
profanicus•

No problem!

I wish I'd locked the headset down somehow to stop the wobbles, and maybe tweaked the numbers a bit to try get the render resolutions identical, but I think it shows well enough that there's no real difference wherever you choose to set the SS.

Which makes total sense to me, since they're all just different places to set the same thing (render scale). Those claiming big differences should be the ones posting the proof.

Regarding Fallout 4 VR, I guess it's possible Bethesda wrote some custom supersampling option for that rather than just set render scale... but given how it's an even lazier port than Skyrim I'd wager they took the easiest option. ;)

1
adamnedshameOP•

This is great thanks for doing that.

There is a second question that arises... how was the actual gameplay performance with each setting? Did you notice more frame drops etc with any of them...?

1
profanicus•

I didn't actually play with any of them enabled, as I was trying to keep the headset in the exact same spot/orientation for each shot. Even if I did, I'd want to try get proper data and not rely on feel. :)

However, I highly doubt there is any difference since all you're doing with any of these three methods is setting the resolution that the game is rendering at internally. The actual rendering is done the same way regardless.

1
barackstarVive•
3
adamnedshameOP•

Yeah that actually prompted my question. I understand the values differ. Interested in performance for identical resolutions using different supersampling methods

3
profanicus•

All Supersampling/Pixel Density is basically doing is rendering the scene at a higher resolution, which then gets shrunk to fit the HMD.

Whichever method you use to set the Pixel Density, it's just the one parameter in the end.

I mean, if you set it in three different places (in-game, Steam, Traytool) it's not like it's rendering the scene three different times in three different ways, or picking one of three different rendering pathways - it's combining the three values to arrive at a final number, and then requesting the game engine render a frame at a resolution based on that number.

So the actual scene rendering is still done in the same place regardless of where you set that parameter, and the final image is still processed and composited in the same place too (the Rift APIs).

The only difference I would expect, is if an in-game setting claims to be Supersampling but is actually not doing a straight render scale method (like maybe using Adaptive Supersampling or something).

Of course I could be totally wrong here and would love for any actual VR devs to weigh in. :)

3
BuckleBean•

This is the correct answer. It doesn't matter where you set your supersampling values. I leave the in-game settings alone & set steam VR to 2.0 using openVR advanced settings because I use 2.0 for everything & it makes my life easier. But I could drop steam to 1.0 & crank up the Skyrim slider or leave them both at the 1.0 equivalent and set the oculus tray tool to 1.43 or whatever. It makes no difference which method you choose. However, when you combine them, they multiply. The image clarity goes up & FPS goes down because you're rendering at like 8k or whatever. It's much easier, IMO, to pick one method & stick to it because I don't feel like doing the math.

2
adamnedshameOP•

Yeah I think I follow you. I can see how it's the same thing... But is there a performance difference in getting there with different methods? I would hope there wouldn't be a difference... But has one of them been done sloppily maybe... or if it resamples at a certain point in the chain it may be creates more opportunities for screen tearing or something

1
profanicus•

See, I don't think they're really different methods. Just different ways of setting the internal rendering resolution. Whichever one you use, it will still end up using your particular HMD's API. So I doubt there'd be any performance difference at all.

2
adamnedshameOP•

Yeah I guess even if they aren't different methods I still wonder if the way the config is sent to the hmd (probably not correct phrasing) has an effect... like I always felt safer doing it with tool tray because it meant nothing extra was happening in the game... although as you say it may be irrelevant

1
profanicus•

Since you need to restart the game whenever you change any of those values for it to take effect, I don't think it's like the config is being sent to the HMD all the time - only when you first start up the game.

And you know Tool Tray is a 3rd party utility that hacks a value not natively exposed to the end user by Oculus right? If you're worried about nothing extra happening in the game, why run some extra piece of software that sits outside the game, outside SteamVR, and outside Oculus Home doing it's own thing? ;)

But yeah I get the attraction to using stuff closer to native where possible and that's cool, I'm just trying to help determine what's best. And the answer (until there's evidence to the contrary) is 'whatever you like, it doesn't really matter'. :)

2
adamnedshameOP•

Yeah I've played around a little since... And only now is what you said making complete sense... It's a setting in the same place as you say... method is irrelelevant other than multiplying etc. It's pretty obvious when you start playing around. I had in my head it was more of an independently done thing rather than a master setting - that's totally the wrong language but ... Yeah .. this is clearly corrdct

1
profanicus•

I read somewhere that claimed Oculus users should use the in-game setting, and everyone else the SteamVR setting. I have no idea if that was based on any proper testing/evidence...

If anyone has actually done any performance/quality tests with the various methods it'd be interesting to see - but I suspect it'd make little measureable difference whichever you use.

I tend to just use the most convenient, which in this case (on Rift) is the in-game setting.

1
Robs2016M6S•

Nah.. I disagree with using the in game setting. I find the SSAA provided by tray tool to be far superior to any game with in game SSAA.. Obduction is one of them.. you can max the SSAA slider in that game and it will help some but when I use tray tool instead and even at just 1.6 its WAY sharper than the slider maxed out in game... and yes I revert the in game slider back to the lowest setting when using tray tool... I get the same results with Skyrim and Chronos as well.

2
profanicus•

Hmm, are there any comparitive screenshots?

I would have thought that a pixel density of 1.6 should be the same whether it's set by an in-game setting or by the Tray Tool.

1
Robs2016M6S•

I don’t know if it would show up in screen shots but the difference in the headset was very obvious...

1
profanicus•

I did some comparison screenshots using the OculusMirror tool, and they all look practically identical.

2
Beepboopbob1•

That makes zero sense. The numbers are the same, therefore the image is the same, therefore the screenshots are the same.

1
wuhwuhwolves•

Tray tool only. My understanding is that it kind of works in layers. The top layer is oculus tt, it controls what is actually rendered to the headset. If you SS on the lower layers (steam and skyrim vr) it's not going to have a visible effect without tray tool, because you'd still be looking at the super sampled image through a low resolution in oculus.

AFAI can tell steam SS does nothing for oculus users. Or at least it works that way for me. I can max out steam SS and it changes nothing for me.

1
adamnedshameOP•

This is what I've always done too based on nothing more than a hunch and a feeling

1
mikendrix•

I think the SS provides the same result wherever you set it.

The difference may be on the activity of Asynchronus Time/Space Warp : wich one is really running when using a Rift without having set anything on Oculus Tray Tool ?

1
profanicus•

The difference may be on the activity of Asynchronus Time/Space Warp : wich one is really running when using a Rift without having set anything on Oculus Tray Tool ?

I'm pretty sure that all the different reprojections such as SteamVRs/ASW/ATW are handled by the HMD run-times.

So there's no difference and you don't have to do anything, as it's always done by the headset software itself.

1
[deleted]•

[deleted]

1
marcryc•

So after reading all this what we saying just use 2.0 as in debug tool and leave steam at manual and Skyrim as at lowest?

Oh and is there any difference using debug tool or the tray tool?

1
adamnedshameOP•

Just use one method. Doesn't matter which one

1
marcryc•

Which is the highest for the oculus?

1