Oculus Tray Tool - Default Supersampling has no visual impact

[LOW_Hitman]

When i change the setting "Default Supersampling" in the OTT it seems to take no effect ingame. No matter if i set it to 1.0 or 2.0 - no visual or performance impact.

Ingame PD is set to 1.0

Anyone else with this "issue"?

[Tepnox]

I suppose you mean it does not change while in-game? If so, yes - that is correct. You need to set the default supersampling in OTT before starting DCS.

Do you have a separate profile inside of OTT for DCS running? Make sure you have the correct Supersampling settings there. If you use Multithreading DCS (MT) you need to make a new profile because it is another path and OTT does separate between DCS Singlethreading and DCS Multithreading (different path). If you don't use profiles the settings in the main window should work.

It is quite annoying to figure out the best resolution and hardware limitation while having to permanently launching and exiting the game just to try some other value. Welcome to the club ;D

If you are testing your settings I would also recommend using the "Pixel Density" Visual HUD to see the current pixel resolution that is active to verify if it is working:

 

Beware: If you are using DCS without OpenXR this overlay is not visible (bugged in DCS since years with Oculus Runtime).

If you are using OpenXR (DCS.exe Shortcut with additional target commands: --force_enable_VR --force_OpenXR) the ingame DCS setting for PD is correct with 1.0. OTT setting will then set as a multiplier).

If the OTT Supersampling settings still do not change even after re-launching DCS, try resetting OTT via the Advanced tab. Somtimes OTT itself gets bugged and this could help:

[LOW_Hitman]

Am 15.4.2023 um 00:03 schrieb Tepnox:

I suppose you mean it does not change while in-game? If so, yes - that is correct. You need to set the default supersampling in OTT before starting DCS.

Do you have a separate profile inside of OTT for DCS running? Make sure you have the correct Supersampling settings there. If you use Multithreading DCS (MT) you need to make a new profile because it is another path and OTT does separate between DCS Singlethreading and DCS Multithreading (different path). If you don't use profiles the settings in the main window should work.

It is quite annoying to figure out the best resolution and hardware limitation while having to permanently launching and exiting the game just to try some other value. Welcome to the club ;D

If you are testing your settings I would also recommend using the "Pixel Density" Visual HUD to see the current pixel resolution that is active to verify if it is working:

 

Beware: If you are using DCS without OpenXR this overlay is not visible (bugged in DCS since years with Oculus Runtime).

If you are using OpenXR (DCS.exe Shortcut with additional target commands: --force_enable_VR --force_OpenXR) the ingame DCS setting for PD is correct with 1.0. OTT setting will then set as a multiplier).

If the OTT Supersampling settings still do not change even after re-launching DCS, try resetting OTT via the Advanced tab. Somtimes OTT itself gets bugged and this could help:

Thank you! In the meanwhile i testet different settings. For me it worked best to set the resolution in the oculus software - for example x1.2 4480x2256 and set PD ingame to 1.0 and in the OTT 1.0.

Tried 1.5 (90hz) which is the maximum - absolute sharp image but the fps are not enough for a smooth experience. x1.3 is hard - sometimes smooth - sometimes laggy.  With x1.2 iam safe with perfomance and stability

[Draken35]

24 minutes ago, LOW_Hitman said:

Tried 1.5 (90hz) which is the maximum - absolute sharp image but the fps are not enough for a smooth experience. x1.3 is hard - sometimes smooth - sometimes laggy.  With x1.2 iam safe with perfomance and stability

Try max resolution in the Oculus Software at 72hz. I have micro stutters over cities while at 90hz, but it is very smooth experience at 72hz with, practically, the same AVG FPS

 

[LOW_Hitman]

vor 14 Minuten schrieb Draken35:

Try max resolution in the Oculus Software at 72hz. I have micro stutters over cities while at 90hz, but it is very smooth experience at 72hz with, practically, the same AVG FPS

 

I'll give it a try but with 72hz it cant be as smooth like 90hz or iam missing something? when i move my head its a big difference with 90hz

[Draken35]

1 hour ago, LOW_Hitman said:

I'll give it a try but with 72hz it cant be as smooth like 90hz or iam missing something? when i move my head its a big difference with 90hz

Well, I don't see any real difference between 72 & 90hz other than the min & max FPS and the one stated in my prior post. I guess we all experience VR a bit differently.

 

[Tepnox]

2 hours ago, Draken35 said:

Well, I don't see any real difference between 72 & 90hz other than the min & max FPS and the one stated in my prior post. I guess we all experience VR a bit differently.

 

Then you are blessed sir and this setting saves performance for you. I get nausiating effects while playing with 72 & 80 Hz - so not my cup of tea.

Edited April 16, 2023 by Tepnox

[LOW_Hitman]

I tried 72 vs 90hz - for me it's unplayable with 72hz - fps are the same but any kind of movement is slow and laggy. 90hz with x1.2 gives the best performance on my rig even when it is not as sharp as at 1.5 but absolutley fine.

Thnx for your comments and your thoughts about this.

[LOW_Hitman]

And a final question... I've set the encode bitrate within the ott to 500 (using original link cable) does this setting hurt performance? Iam not sure - sometimes i had that feeling that with a setting of 400 the game runs "smoother" or is it a placebo?

[Tepnox]

12 hours ago, LOW_Hitman said:

And a final question... I've set the encode bitrate within the ott to 500 (using original link cable) does this setting hurt performance? Iam not sure - sometimes i had that feeling that with a setting of 400 the game runs "smoother" or is it a placebo?

It depends on the graphics card. If you set the encode bitrate too high you will get occasionally audio- and image-stutter or dips. In my experience my RTX3090 could handle the bitrate up to 500 Mbit, above that i got these audio- / image dips.

Switched to a RTX4090 and settings up to 960 Mbit for encode bitrate are possible. So you need to test this on your rig. Recommended settings are 300-500 Mbit. Default settings is 200 or 250 Mbit I think.

You should only set a higher setting when compression artefacts on some color patterns are visibile for you and you want to get rid of it. Some people on this forum are fine with 300 Mbit, I personally can tell the difference betweeen 500 Mbit and 960 Mbit and so I prefer much higher settings. Bandwith should be no problem via the link cable, I suppose you get 2.0 Gbit in the speedtest and above. The limiting factor in this case is the graphics card.

Happy testing.

[LOW_Hitman]

vor 9 Stunden schrieb Tepnox:

It depends on the graphics card. If you set the encode bitrate too high you will get occasionally audio- and image-stutter or dips. In my experience my RTX3090 could handle the bitrate up to 500 Mbit, above that i got these audio- / image dips.

Switched to a RTX4090 and settings up to 960 Mbit for encode bitrate are possible. So you need to test this on your rig. Recommended settings are 300-500 Mbit. Default settings is 200 or 250 Mbit I think.

You should only set a higher setting when compression artefacts on some color patterns are visibile for you and you want to get rid of it. Some people on this forum are fine with 300 Mbit, I personally can tell the difference betweeen 500 Mbit and 960 Mbit and so I prefer much higher settings. Bandwith should be no problem via the link cable, I suppose you get 2.0 Gbit in the speedtest and above. The limiting factor in this case is the graphics card.

Happy testing.

Thank you very much! i tried 960 yesterday and exactly as you said i got audio stutters every 10-15 seconds. I'll try different settings 300 sounds good for my 3070ti especially with only 8gigs of vram.

The speedtest shows more than 2.0Gbit so the cable should not be the limiting factor.

Could you please tell me what do you mean with "image dips"? Colour or blurry or tearing?

[Tepnox]

4 minutes ago, LOW_Hitman said:

Could you please tell me what do you mean with "image dips"? Colour or blurry or tearing?

Well I meant exactly what you described ;D

Image Dips could be distortion (warping) or interruptions - thats what I meant.