Valve Index best settings

[RedeyeStorm]

Hello all,

 

I recently bought a Valve Index and I am loving it compaired to my old Oculus Rift. I have one issue though and that is on the winter Moskow map I have shimmering textures for forrest and the field texture that looks like a ploughed field.

 

I found that it could be made acceptable by eithter setting in the Nvidia control panel multisampling to 4 or anisotropic filtering to 16. The first gives me performance problems the latter not. I have been testing with the Pe2 and the Ju88. The multicrew bombers are in my experience more demanding then the fighters. With both ways my fps goes down to 30 but where it is unplayable with multisampling it is perfectly fine with anisotropic filtering.

 

My question is wether or not any  Index user has the same issue and or a better solution?

 

My specs: Intel I7 6850K overclocked to 4.3 Ghz, 16 Mb ram, Nvidia GTX 1070.

Edited April 6, 2020 by [Pb]RedeyeStorm
Title changed to reflect content.

[SCG_Fenris_Wolf]

Considering you are using a GTX1070 (drastically underpowered for an Index)

 

Better keep hands off the Nvidia Control Panel. Keep everything at default, except for performance setting - set it to prefer maximum performance.

SteamVR, video settings -> drag supersampling resolution to 1760.

Select ingame AA at 2x.

Select ingame Landscape Filter = blurry.

Select ingame shadows = off (they flicker if not on extreme, and lowering them is a big weight off your GPU's shoulders).

 

There is not much you can do with that kind of GPU to be honest.

[VR-DriftaholiC]

I have an Index but I don't think it's really related. I prefer to use SteamVR super-sampling over in game AA. If you can handle it turn off motion smoothing (reduces load) and run a lower frame rate like 80 to keep it from having earlier in intense scenes. I find the in game AA mess with spotting. The landscape blur filter costs like 5 fps vs 1 of sharpen, actually I find no filters bearable if you have the land  lod's cranked which mostly impacts video memory usage and it's the least demanding overall. Lower your view distance to reduce horizon shimmer and up the cloud detail to reduce cloud shimmer if they are still in front of the haze caused by the lowered horizon distance. I'm told none of these settings affect plane render distance. I find high for shadows does not flicker and only rarely I see the pixelation of not having them set higher only costs a few fps vs off where extreme costs closer to 8. You can open the developer frame time graph and take a note where the render times are in what kind of scenes. I find I'm mostly CPU limited and only grass distance, low presets and far city blocks off can really reduce this. Most the other options tax the GPU. 

 

I wish I could say here are my settings use them but it's going to depend on your hardware and preferences with a little time consuming testing especially with the forced game restarts when adjusting things.

 

I should add, antistropic filtering shouldn't have an affect aliasing as all. I believe it's the technique used on the land textures (and maybe all textures if you set it on in control panel) when you set the landscape sharpen filter on. I find I'm mostly looking down on the textures in a flight sim vs looking down the textures themselves where antistopic would really make a difference.

 

Edited April 5, 2020 by driftaholic

[SCG_Fenris_Wolf]

He's on a gtx 1070. It's harder to reduce shimmering on that than to outrun a Bf-109 in an i-16.

Edited April 5, 2020 by SCG_Fenris_Wolf

[RedeyeStorm]

Thanks guys,

 

I am quit happy with a fps around 40/45 and my system manages that. All my shimmering terrain problems went away when I selected the blurry terrain filter. So most of my post was nonsense I am afraid. I have clouds on high with Coconuts preset and no issues there. I have SS at 140 in SteamVR.

 

I am afraid that my personal preference so far has me always going back to 4x AA. The jaggies otherwise really bother me. As I mostly play SP I am used to blip labels and the map which offset the difficulty in spotting (here’s hoping to a fix by the devs some day). But I will try your suggestion @SCG_Fenris_Wolf.

 

I have returned most Nvidia setting back to default except sharpening at 0.33 and texture filter on high quality and the performance setting off course.

 

Thanks for the help.

[VR-DriftaholiC]

I would try something like this at 80 fps in the index, re-projection off and then slowly work the super sampling up from 100 to 150 if it can

 

[KEY = graphics]
    adapter = 0
    bloom_enable = 0
    desktop_center = 0
    detail_rt_res = 2048
    draw_distance = 0.2
    far_blocks = 0
    fps_counter = 0
    fps_limit = 0
    full_height = 2240
    full_width = 2016
    fullscreen = 0
    gamma = 1.00000
    grass_distance = 0.00000
    hdr_enable = 0
    land_anisotropy = 1
    land_tex_lods = 3
    max_cache_res = 1
    max_clouds_quality = 2
    mgpu_compatible = 0
    mirrors = 2
    multisampling = 0
    or_ca = 0.00000
    or_enable = 1
    or_height = 2240
    or_hud_rad = 1.50000
    or_hud_size = 0.75000
    or_ipd = 0.06722
    or_sipdc = 0.00000
    or_width = 2016
    post_sharpen = 0
    preset = 0
    rescale_target = 1.00000
    shadows_quality = 3
    ssao_enable = 0
    stereo_dof = 5.00000
    vsync = 0
    win_height = 568
    win_width = 1024
[END]

Edited April 6, 2020 by driftaholic

[RedeyeStorm]

@driftaholic,

 

I have been trying to find how to disable re-projection in Steam VR but have been unsuccessful. In the oculus it was CTR+keypad1 but that doesn’t do anything now. Any tips?

[VR-DriftaholiC]

Settings > Video or General >  Motion Smoothing

[RedeyeStorm]

Okay, that is disabled. I got the impression that reprojection was something different then smoothing. Thought it’s effect where more like Oculus’s ASW. My frames on the rift where always fluctuating between 45 to 80 fps with ASW off. With the Index they never raise above 45 and only go to 90 (playing at 90hrz) in the menu’s.

[VR-DriftaholiC]

I believe "motion smoothing" = ASW + Re-projection and the legacy mode found under advanced settings is only one of the two algorithms 

 

Try setting it to 80. If it can't maintain the FPS it will Halve it. You may be able to maintain 80 FPS but not 90. There may be some more optimizations that can be made to get you to 80 FPS at least in the air. The way VR displays use black frame insertion for blur reduction really requires higher frame rates then 45.. If you can't maintain 80 you might be able to maintain 72hz by setting it to 144hz. But personally I would keep lowering settings until you can maintain 80 FPS at least. Lets hope the new render model will reduce some CPU loads.

 

Here's what I did in the NVCP. Though this will change when the update drops. I'm not sure what IL-2 uses for pre-rendered frames so I left it up to the developers. NV forces this to 1 by default but since we are typically CPU bound loosening this might help with stutters. I did notice a difference in performance when I made this changes, I did them all at once so I'm not sure where the hiccup was. I tried clamping the negative LOD bias but it seemed to have a negative affect on ground textures at a distance. This allows them to run at a higher LOD then set by the game but it seems the game drops detail for ground too soon in my opinion. I'm not sure the 10 series allows for image sharpening but I believe Nvidia's process is more efficient then the in game method so you can experiment with that if you feel like you want sharpening on. 

 

 

Edited April 7, 2020 by driftaholic

[RedeyeStorm]

Hey @driftaholic,

 

Thanks for your help. I will check out your advice and see if it works for me. I do use the nvidia sharpening setting. I have it at 0,33 and in my opinion makes the cockpit dials better readable. Give it a try.