Zappers PIMAX Crystal Settings using Open VR

[Zapper]

This post was edited 2603002300UTC to reflect my latest changes. It is a copy of my startup.cfg with my included notes. I'd really appreciate feedback on the settings and what they actually do in the game.

Spoiler

These are my latest settings as of 2603082300Z

There include my notes from last few days of adjustments. I think the startup.cfg is about as good as I can get it.

I have a chronology of the changes made at the start of the file. NB These are local times in Aussie.

 

I began with the settings advised in IFLYSIMS YT Video and went from there using experiments and @Dash,Polder inputs. When my startup.cfg was a good as I could get it I also changed the GPU Upscaling settings in Pimax App but without much improvement.

 

// 2603082043 This is straight after setting up iaw IFLYSIMS video
// Must run Pimax with ADMIN priveleges to run IL2 from Pimax App. 
// 2603082200 Flew with TBAS. Spotting OK at distance but needs better close in for ID without zoom. Trees look flat so will increase land anistropy amd detail. land LODS is already at 3 so not changed
// 2603082237 Zap changed: or hud rad and or hud size, or render eye, 
// 2603082348 Flew in CB 109 and shot down 4. Spotting at distance is pretty good with sparkles, close up could be better. Clouds at times look boxy or pixellated but this is the best I have seen for some time in Pimax.
// 2603082350 might be worth trying 4k textures again as FPS is still 72
// 2603090737 4K textures ON. RESULT: No impact on performance so leaving it on
// 2603090752 multisampling changed fm 2 to 4 RESULT: No performance impact
// 2603090800 multisampling changed fm 4 to 6 RESULT: Edges of water bodies ugly and city buildings small. ACTION: Leave it at 4
// 2603090822 Try Post sharpen on //2603090831 RESULT St Elmos fire on leading edges. cities jagged etc. RACTION: Leave it OFF
// 2603090834 changed preset = 3 to 4 No visible performance impact. Didn't change distant water bodies or buildings/ ACTION: Leave it at 4
//
// 2603090846 CONCLUSION: This is as about as good as I can get startup.cfg for spotting and general view. Leave it at this and try Pimax App variations next
//2603090855 changed Pimax App GPU Upscaling/Sharpmess from .3 to 1.0. Nothing really noted, maybe a little less pretty
//2603090907 returned Pima App Upscaling/Sharpness back to 0.3 and /Super Resolution from 1.5 to 2 RESULT: Aircraft seemed a bit edge torn up close and no other imprvement so back to 1.5 and 0.3

 

[KEY = account]
    login = ""
    password = ""
[END]

[KEY = camera]
    cinematic = 1
    head_smooth = 1.00000
    hmd_restricted = 0
    shake = 0
    vr_zoom_speed = 0.30000
[END]

[KEY = force_feedback]
    amplitude = 1.00000
    enabled = 1
    force = 1.00000
[END]

[KEY = graphics]
    3dhud = 0
    adapter = 0
    bloom_enable = 0
    canopy_ref = 0
    desktop_center = 1
    detail_rt_res = 2880 //2603082044 Zap changed this from default of 2048 to half Pimax res of 1440 //2603082237 Zap changed this from 1440 to 2880 to try and improve trees and thereby target contrast with ground
    draw_distance = 0.81800
    far_blocks = 1
    fps_counter = 0
    fps_limit = 0
    full_height = 1024 //spalsh screen size
    full_width = 1280 //spalsh screen size
    fullscreen = 0 //LI2 team recommend set to 1 for better fps. It only affect flat screen display
    gamma = 0.80000
    grass_distance = 200.00000
    hdr_enable = 1
    land_anisotropy = 16 //2603082200 Changed from default of 2 to 16
    land_detail = 7 //2603082200 Changed from 3 to 7
    land_tex_lods = 3 //2603082200 unchanged 
    max_cache_res = 1 // 2603082044 Zap changed this from 1 to 0 to turn 4k textures OFF //2603090737 4K textures ON. RESULT: No impact on performance so leaving it on
    max_clouds_quality = 4 // 2603082044 Zap changed this from 3 to 4 for ULTRA to help spotting
    mgpu_compatible = 0
    mirrors = 2
    msaa = 0
    multisampling = 4 // 2603090752 changed fm 2 to 4 RESULT: looks considerably better with no perfomance impact. // 2603090800 multisampling changed fm 4 to 6 RESULT: Edges of water bodies ugly and city buildings small. ACTION: Leave it at 4
    or_ca = 0.00000
    or_dummy = 0
    or_enable = 1
    or_height = 2880 // 2603082044 Zap changed this from 2410 to Pimax native 2880
    or_hud_rad = 0.30000 //2603082237 Zap changed this from 1.5 to 0.30000 iaw Dash
    or_hud_size = 0.5000 //2603082237 Zap changed this from 0.75000 to 0.50000 iaw Dash
    or_ipd = 0.03980
    or_render_eye = 1 //2603082237 Zap changed this from 0 to 1 to force only 1 view for OBS recording
    or_sipdc = 0.00000
    or_width = 2080 // 2603082044 Zap changed this from 2038 to Pimax native 2880
    post_sharpen = 0 // 2603090822 Try Post sharpen on //2603090831 St Elmos fire on leading edges. cities jagged etc. RESULT: Put it back to OFF
    preset = 4 //2603090834 changed from 3 to 4 RESULT No visible performance impact. Didn't change distant water bodies or buildings/ ACTION: Leave it at 4
    prop_blur_max_rpm_for_vr = 55 ////2603082237 Zap changed this from 155 to 55 iaw Dash
    rescale_target = 1.00000
    shadows_quality = 3
    ssao_enable = 1
    stereo_dof = 5.00000
    vsync = 0
    win_height = 1440
    win_width = 2560
[END]

[KEY = input]
    exclusive = 1
    mouse_plane_control = 0
    old_trackir = 0
    turrets_angle_limit = 0.00000
    turrets_dc = 0
[END]

[KEY = interface]
    forces_color_mode = 0
    language = "eng"
    log = ""
    scale = -1
    showcompas = 1
    showicons = 1
    units = "metric"
[END]

[KEY = network]
    available_ip = ""
    client_download_traflimit = 1024
    client_ip = ""
    client_upload_traflimit = 1024
    downloader_port = 28100
    tcp_port = 28000
    udp_port = 28000
[END]

[KEY = sound]
    debug_radio = 0
    interface = 0
    interface_music = 0
    quality = 1
    volume = 0.14000
[END]

[KEY = system]
    bin_log_folder = ""
    debug_render = 0
    gamelog = 0
    keep_binary_log = 0
    mission_text_log = 0
    modes = 0
    playoffline = 0
    reset_configs = 0
    reset_effects = 0
    reset_textures = 0
    sdebug = 0
    show_net_skins = 1
    skin_dir = "graphics\Skins\"
[END]

//2603082044 BELOW HERE IS PASTE FROM REFERENCE DOCUMENT TO ENABLE SRS AND TACVIEW
//SRS Settings:
[KEY = telemetrydevice]
    addr = "127.0.0.1"
    decimation = 2
    enable = true
    port = 4322
[END]

//TACVIEW Settings:
[KEY = track_record]
    fx_sound = 2
    record_graphics_effect = 1
    record_ground_vehicles = 1
    tacviewrecord = 1
[END]

[KEY = updater]
    language = "eng"
    locales = "eng"
    seed = 0
[END]

 

 

Edited March 8 by Zapper
2603070000UTC updated with latest settings and notes

[Zapper]

I am curious as to where the Splash Screen pulls the values for Resolution etc. The screenie shows 4096x2160 but I have it set to 1024x768 in startup.cfg.

In the same file I have max_cache_res = 1 which (as I understand it) turns 4K textures OFF but shows here as checked. How can I know in game if I have 4k textures ON?

I realise the Resolution puildown is for the Monitor display and has no bearing on VR.

My question is: Is there another configuration file that IL2.exe references on startup?

[Dash,Polder]

land_anisotropy = 16, you can go that high, it's just the anisotropic filtering right of the Nvidia control panel, so set it at 16 there also to match in the Sturmovik BOS profile.

land_detail = 7, can be set to a max of 7 but both of these can only manually be set in the file outside of the game. 

Both these settings will revert back to default should you make any in game graphics change and save it in game, so you'll have to go back and manually reset them in the file every time you change and save your graphics settings.  I won't fly without them on, they bring quality visuals for close ranges.

fps_limit = 100, if your running VR set your monitor refresh rate to a cap near matching the headsets fps.  No sense in trying to crank out different levels of frequency all off the same graphics card.  You can cap the refresh rate here and in control panels global setting under the Preferred refresh rate for the monitor, or you can set it to application controlled there and use this in game setting.  Too far of a variation in frequency will cause micro jitters.  You can't be running a 200 fps monitor and a 70 fps HMD off the same GPU and not expect some static when pushed to the edge.  

You should enable HDR in a pimax, it'll give better definition with spotting, especially intermediate ranges with it's light casting and shadow effects on the planes.   hdr_enable = 1

or_hud_rad = 0.30000 will put a nice curve radius in your map and menu UI,

or_hud_size = 0.50000 will adjust the size, make it smaller fitting better inside your pit, now you have a more life sized map easier to use sitting inside a cockpit flying.  Adjust the transparity slider of your map lower to get rid of some of the brightness, it acts as a dimmer.

prop_blur_max_rpm_for_vr = 155, you can adjust this value and get nice results, I run mine at 55 RPM's.

[Zapper]

Hi Dash,

Many thanks for your reply. Although I have been flying sims awhile I have never really got this far down in the weeds with settings.

A steep learning curve. One snag is figuring out what each startup.cfg line changes in the GUI. I was surprised to see that the Presets of LOW, HIGH, BALANCED and ULTRA only change the Preset variable. 

 

I really do appreciate your input and am trying each suggestion.

Mucho Gracias,

Zap

[Zapper]

@Dash,Polder

Might I ask your recommendation for PPD please?

My options are 35PPD Glass, 35PPD Poly, 42PPD Poly and Big FoV

EDIT: Disregard my question. I used the Autodetect function and have 35PPD. Glass or Polycarbonate doesn't really matter

Cheers,

Zap

Edited March 5 by Zapper

[Zapper]

On 3/5/2026 at 8:22 AM, Dash,Polder said:

land_anisotropy = 16, you can go that high, it's just the anisotropic filtering right of the Nvidia control panel, so set it at 16 there also to match in the Sturmovik BOS profile.

land_detail = 7, can be set to a max of 7 but both of these can only manually be set in the file outside of the game. 

Both these settings will revert back to default should you make any in game graphics change and save it in game, so you'll have to go back and manually reset them in the file every time you change and save your graphics settings.  I won't fly without them on, they bring quality visuals for close ranges.

fps_limit = 100, if your running VR set your monitor refresh rate to a cap near matching the headsets fps.  No sense in trying to crank out different levels of frequency all off the same graphics card.  You can cap the refresh rate here and in control panels global setting under the Preferred refresh rate for the monitor, or you can set it to application controlled there and use this in game setting.  Too far of a variation in frequency will cause micro jitters.  You can't be running a 200 fps monitor and a 70 fps HMD off the same GPU and not expect some static when pushed to the edge.  

You should enable HDR in a pimax, it'll give better definition with spotting, especially intermediate ranges with it's light casting and shadow effects on the planes.   hdr_enable = 1

or_hud_rad = 0.30000 will put a nice curve radius in your map and menu UI,

or_hud_size = 0.50000 will adjust the size, make it smaller fitting better inside your pit, now you have a more life sized map easier to use sitting inside a cockpit flying.  Adjust the transparity slider of your map lower to get rid of some of the brightness, it acts as a dimmer.

prop_blur_max_rpm_for_vr = 155, you can adjust this value and get nice results, I run mine at 55 RPM's.

May I ask where you get the parameters for each of these settings and what Setting (if any) it corresponds to in SETTINGS/GRAPHICS?

[Dash,Polder]

Most of them don't, they're extra's I've collated and collected over the years from various old forum posts and other users.  Things like the prop rpm was added after people had issues in the early days, but never given an in game setting.  The land setting always worked but were not really general user knowledge, these are extended and above the in game defaults, setting the landscape filters should do changes but they'd be lower.  You can look most up in the old locked forum, thing is they do work.