Rift-S users, share startup.cfg?

[SIA_Mal]

Hello everyone,

 

Im trying to setup my startup.cfg file for better spotting with no luck.

So, can anyone share the file, so i can try it?

 

Im also putting mine here.

 

Runing IL-2 on a Rift-S and a 2070 SUPER.

 

startup.txt

[[DBS]Browning]

Spotting changes are coming in about 10 days (but maybe longer). Wait until then before you try anything in this area.

[TWC_NINja]

@TWC_Mal I edited your file to almost match mine... not sure what rig you have, but I'm running a Reverb on 9700k and 2080S.

 

I have some other settings set higher, but basically turned up the draw distance and removed bloom and HDR. Also set the gamma to 0.7 and unchecked full screen.

 

I don't use antialiasing with my Reverb, but if you need it for the Rift, you can turn that back on.

 

Hopefully this helps.

 

startup.txt

Edited September 14, 2020 by TWC_NINja

[dburne]

 I have never modified the startup file for my VR experience.

[firdimigdi]

i9 9900k, rtx2080, rift s - 8vs8 head to head quick mission at 1500m altitude maxes out at ~10ms frametime with this config - if performance is an issue you can take the supersampleRatio in opencomposite.ini down to 1.1 to still have easily readable instruments and some acceptable level of AA

 

startup.cfg - relevant section

Spoiler

[KEY = graphics]
      3dhud = 0
      adapter = 0
      bloom_enable = 0
      canopy_ref = 1
      desktop_center = 1
      detail_rt_res = 1024
      draw_distance = 0.274000
      far_blocks = 0
      fps_counter = 1
      fps_limit = 0
      full_height = 480
      full_width = 640
      fullscreen = 1
      gamma = 0.80000
      grass_distance = 0.00000
      hdr_enable = 0
      land_anisotropy = 1
      land_tex_lods = 0
      max_cache_res = 1
      max_clouds_quality = 2
      mgpu_compatible = 0
      mirrors = 2
      msaa = 0
      multisampling = 0
      or_ca = 0.00000
      or_dummy = 0
      or_enable = 1
      or_height = 2128
      or_hud_rad = 5
      or_hud_size = 0.85
      or_ipd = 0.06350
      or_sipdc = 0.30000
      or_width = 1984
      post_sharpen = 0
      preset = 2
      prop_blur_max_rpm_for_vr = 155
      rescale_target = 1.00000
      shadows_quality = 3
      ssao_enable = 0
      stereo_dof = 5.00000
      vsync = 0
      win_height = 1080
      win_width = 1920
[END]

opencomposite.ini

Spoiler

 

enableAudio=false
supersampleRatio=1.2

 

 

If you are not running opencomposite already I suggest you do so and ditch steamvr.

Edited September 15, 2020 by Firdimigdi

[Guest deleted@134347]

personally the only noticeable difference in spotting with the current version of the game can be seen between FXAA and MSAA.

 

FXAA - less definition and the enemy planes can dissolve in to the back ground right front of your eyes

MSAA - more definition, the planes still dissolve but much further out....

 

my 2 cents.

[SIA_Mal]

And no notifications on my email. So, sorry for the late replies.

From top to bottom:

Thanks DBS, i read something about incoming changes but didnt know they were almost out.

 

Hey Ninja, will try that as it it and try some changes later. Spook sent me his too but something there wasnt right for Rift-S. No idea whats a Reverb. I got a I5-9400F, 16GB RAM, RTX 2070 SUPER, IL-2 on a SSD-SATA.

 

dburne, i believe changing the startup file is a matter of preference. I can play in VR with default parameters but cant see that far. 3km away is bad. And there are other things that matters too, like ,  Nvidia profile, supersampling directly in Oculus Debug Tool.

 

Firdimigdi - Didnt know about that on opencomposite, will play with it and your startup.

 

Didney_World - Yep, planes go poof when they are really low.

 

Thank all for the good infos and files. Time to start working on them.

 

See you on the skies, i hope.

 

[TheAmazinGreat]

If you are going with open composite I would recommend Oculus Tray Tool. Use it in place of debug tool and make a profile for IL2 launcher.exe. This way it will save your SS values per game and they don’t have to be set on restart like ODT. Set it to run on startup and after getting settings you like you don’t have to touch it again. And with the switch to open composite I’m pretty sure you lose the graphics/SS adjustability through SteamVR so you would tweak it through OTT. 

 

On startup.cfg recommend start with the settings in the sticky and tweak OTT, and MSAA for performance/quality. 

[TWC_NINja]

53 minutes ago, TWC_Mal said:

No idea whats a Reverb. I got a I5-9400F, 16GB RAM, RTX 2070 SUPER, IL-2 on a SSD-SATA.

 

 

@TWC_Mal The headset I use is the HP Reverb, with a higher resolution (2160x2160 per eye) than the Rift S.

I had a Rift S for a bit and decided to go with the Reverb because of the sharper image/clarity.

My specs are a tad higher than yours (9700k, 32Gb RAM, RTX 2080S), so some of my settings are set a little higher even though I'm pushing more pixels.

Also, I'm running the Reverb at 60Hz refresh, so less taxing on the GPU.

 

Do heed the recommendations on Opencomposite and Oculus Tray Tool - you will get better results than using SteamVR with Rift S.

[SIA_Mal]

Im using OpenComposite. And i searched you can write opencomposite.ini and put the SS setting there. Not sure were to save the ini, in game folder or were i downloaded the opencomposite program.

I did the system wide installation.

 

So i dont see the need for the Oculus Tray Tool for the moment.

 

And Ninja, not sure if your file will work on my setup as its a different headset. The same may happen with Spook file.

[TWC_NINja]

1 hour ago, TWC_Mal said:

And Ninja, not sure if your file will work on my setup as its a different headset. The same may happen with Spook file.

 

@TWC_MalI only edited some of the values in your file so you can just open the file I uploaded and copy the [KEY = graphics] section into your startup.ini

I think Spook's did not work because, just like mine, it's a .txt file.  

[SIA_Mal]

I copied the section of Spook file into mine. Great visibility but eyes hurt. No idea why. So i tried to go back to mine and change line by line , some lines the game changed back to my default. Weird.

 

But, as your file is basically mine with a few changes, that might work. Thanks.

[TheAmazinGreat]

1 hour ago, TWC_Mal said:

I copied the section of Spook file into mine. Great visibility but eyes hurt. No idea why. So i tried to go back to mine and change line by line , some lines the game changed back to my default. Weird.

 

But, as your file is basically mine with a few changes, that might work. Thanks.

 

Go to properties on your startup.cfg  and make it read only so the game does not change it. 

[SIA_Mal]

Yeah, i know. Thats how i keep the bloom off.

I wasn't using in read-only because i was testing many things.  And i thought only bloom would be changed by the game.

 

[Georgio]

17 hours ago, TWC_NINja said:

@TWC_Mal The headset I use is the HP Reverb, with a higher resolution (2160x2160 per eye) than the Rift S.

I had a Rift S for a bit and decided to go with the Reverb because of the sharper image/clarity.

My specs are a tad higher than yours (9700k, 32Gb RAM, RTX 2080S), so some of my settings are set a little higher even though I'm pushing more pixels.

Also, I'm running the Reverb at 60Hz refresh, so less taxing on the GPU.

 

Do heed the recommendations on Opencomposite and Oculus Tray Tool - you will get better results than using SteamVR with Rift S.

 

I have a Reverb G2 arriving next month to replace my Rift S.

Are there any issues running WMR with IL-2, I saw the thread about scaling a few years ago, assuming this got sorted in a patch?

Can you still use Open Composite with WMR, I only use SteamVR for native steam titles?

[dburne]

57 minutes ago, Georgio said:

 

I have a Reverb G2 arriving next month to replace my Rift S.

Are there any issues running WMR with IL-2, I saw the thread about scaling a few years ago, assuming this got sorted in a patch?

Can you still use Open Composite with WMR, I only use SteamVR for native steam titles?

 

Open Composite only works with Oculus.

[SIA_Sp00k]

May be the interpupillar distance (IPD) what is causing your eye strain Mal.   Can you adjust IPD with the Rift S?    Measure the distance of your pupils with a ruler and adjust the IPD to that distance.  Samsung Odyssey plus has a wheel under the headset. Rift S may be changed in the software?

 

...enter competent authority on the Rift S now.......

[SIA_Mal]

On 9/17/2020 at 7:47 AM, TWC_Sp00k said:

May be the interpupillar distance (IPD) what is causing your eye strain Mal.   Can you adjust IPD with the Rift S?    Measure the distance of your pupils with a ruler and adjust the IPD to that distance.  Samsung Odyssey plus has a wheel under the headset. Rift S may be changed in the software?

 

...enter competent authority on the Rift S now.......

For Rift-s, IPD is software only.

Ninja file worked good, not sure if he changed that. I checked before the patch of 17/09/2020.

Now i need to test with this new spotting changes.