1946 vr mods - 4.12.2m / UP3.4 P2 HF23 / BAT 4.3.0

[boilingmetal]

IL-2 1946 VR MOD - Release & User Guide

True stereo VR for the classic WWII flight sim - 4.12.2m / UP3.4 P2 HF23 / BAT 4.3.0

1. What this mod does

This is a real VR mod for IL-2 1946: each eye is rendered separately and the HMD's 6DOF pose is mapped into the cockpit in real time, letting you truly sit inside these old warbirds.

• True stereo rendering: one frame rendered per eye; IPD and projection matrices are read live from the HMD via OpenVR (adjusting the headset IPD takes effect in-game immediately)
• Full 6DOF: head rotation plus positional movement; you can even lean your head out of the cockpit (beyond the original game's designed range you will see texture glitches, which is expected)
• Low-end friendly: GPU load is light; the CPU is the bottleneck (two pre-rendering passes per frame). A modern i7-class CPU or higher is recommended
• Full VR HUD: the tactical map, flight data, messages, multiplayer command menus and more are all presented as interactive world-space panels (see section 5)

This mod is a refactor of firepolo's OpenVR mod (SAS topic,63444). Without his 2020 attempts and validation of the key technical approach, none of today's progress would have been possible.

Demo videos (click to play)

 

Version support and development direction

Currently supported versions (three):

• 4.12.2m (Steam users can roll back from 4.13.4 in properties) - SAS ModCat 5.3 framework
• UP3.4 Patch 2 Hotfix 23 (latest UP3.4) - UP3 framework
• BAT 4.3.0 (new; covers all four modules - DOF3 / TGA3 / WAW3 / JTW3) - SAS ModAct 5.3 wrapper

Adaptation for older versions (4.10.1 / 4.13.4 / UP3 RC4 / UP3.4 P0/P1) is no longer released - too many accumulated bugs make them not worth keeping. Please use one of the three supported versions above.

Development focus (continuous): CPU load optimization; remaining per-headset 6DOF cases; advanced water rendering behavior in VR.

Update log / Changelog

Latest: 2026-09-05 - BAT 4.3.0 support + VR HUD/interaction update + tool-based configuration - click to expand

2026-09-05 - BAT 4.3.0 official support + full VR HUD / interaction update + tool-based configuration (4.12.2m + UP3.4 P2 HF23 + BAT 4.3.0, all three versions synced)

• BAT 4.3.0 support (new): all four BAT modules (Dawn of Flight / Golden Age / World at War / Jet Age) are adapted - the package deploys to each module so VR works whichever module you fly; BAT's NG-era HUD is fully supported (its custom HUD messages/subtitle panels all go through the VR spatial display)
• Configuration tool il2vr_config.exe (new, shipped in the package): double-click to run, built-in help. Visual editing of every VR panel's position/size/content/commands - no more hand-editing config files. Panel defaults now live in one place: vr_aircraft_conf\vr_global_conf.ini (a per-aircraft config file is auto-generated the first time you fly an aircraft)
• Orders panel (new, multiplayer): the radio command menu (flight orders / ground control / wingman commands etc.) is presented as a VR panel - gaze + interact key to execute (no longer relying on the vanilla 2D list)
• Center message panel (new): center-screen messages (mission hints / server announcements) are VR-ized; the message panel is upgraded to a 6-slot ring display with the original visual style restored (white-to-red fade, 10 s retention)
• VR_ZOOM magnifier (new): hold to zoom in 5x instantly (aiming / observing distant targets), release to restore immediately; eye-consistent without parallax error, with automatic view smoothing while zoomed
• Map display-mode cycle button (new, ◎): click on the VR map panel to cycle through all map display modes (equivalent to the desktop right-click menu; choice is remembered)
• vr_esc command (new): full in-game ESC semantics made configurable (default Quit Mission (ESC) button in the Command Box Misc group; can also be bound to any key in Controls - misc group)
• Menu gaze pointer (new): inside the menu overlay your gaze is the mouse - look at an element and the pointer follows; the interact key replaces the left mouse button (buttons / sliders / scrolling all work), no physical mouse needed for menus
• Gaze interaction enhanced: collapsed buttons / command boxes now show the real reticle position within a 2x sensing zone with hit highlight - no more blind aiming
• VR_NEAR_INC / VR_NEAR_DEC (new): fine-tune the near clip in-game per aircraft (0.01 m per press, written into that aircraft's config automatically) - solves near-clip clipping on individual aircraft
• Flight data panel: NG info-line extraction added (speed/status/weapons rows; full NG four-block layout on BAT) - more data on screen
• Misc fixes: aircraft-select 3D preview far-side clipping fixed; message panel occasionally showing only two rows fixed; command box background made translucent; map panel button column reworked
• Packaging change: releases are now JSGME snapshot folders - unzip into your JSGME MODS folder and activate; the config tool and defaults ship inside the package

2026-08-30 - VR ESC command (UP3.4 P2 HF23)

• New vr_esc command: full in-game ESC semantics (exit mission back to main menu; closes the tactical map / in-game menu bar first if open); bind it to any key or use the Command Box Misc group Quit Mission (ESC) button
• Existing-config note: if you already have a command box config ([VRCommandBox] section generated), append a line cmd_N = Misc|Quit Mission (ESC)|vr_esc (N = highest existing number + 1), or delete the config file and let it regenerate (customization would be lost)

2026-08-17 - Netplay head-look sync + netplay menu overlay fix + in-game icon anchor fix (4.12.2m + UP3.4 P2 HF23)

• Netplay head-look sync: the HMD's yaw/pitch is now fed into the net control message, so other players see your pilot's head follow your headset; non-VR falls back to the original logic - no side effects
• Netplay menu overlay fix: the Esc menu / chat box no longer mixes with the 3D scene in multiplayer; the multiplayer briefing map is no longer captured by the map overlay
• In-game icon anchor fix: fixed friendly/enemy icon misalignment, sliding and oversized text in the VR eye pass (2D ortho projection now matches the eye FBO 1:1, clipping confined to the eye FBO, Render3D0 reloads the OpenVR projection)

2026-08-09 - 6DOF fix + cockpit gaze-interactive button panel (4.12.2m; UP3.4 P2 HF23 aligned in the same batch)

• Fixed 6DOF anomalies on Pimax-class HMDs: translation-axis mapping fix (old mapping crossed forward/back with left/right - confirmed root cause, verified in-game)
• Recenter rework: RECENTER button at the bottom center of the main menu (3-second countdown, click again to cancel); unified Seated tracking space; recenter takes only current yaw + position with pitch/roll set absolute-level; all uncontrolled auto-recentering removed
• New cockpit gaze-interactive button panel (see section 5.7); new hotkeys VRHUD_ACTIVATE / VRHUD_RELOAD
• UP3.4 P2 HF23 fully aligned with 4.12.2m

2026-08-06 - VR flat menu mirror + 3-pass direct rendering (4.12.2m)

• Menus (main menu/briefing/settings/pause/multiplayer lobby) are presented as world-space panels with a directly usable mouse - no more giant menu plastered to your face
• Rendering architecture upgrade: both eyes render directly at the headset resolution (no longer locked to the desktop window resolution); factor now truly controls the in-headset render resolution; fixed far-terrain artifacts (depth/stencil attachment), desktop window stretching and VSI over-reading

2026-08-03 - Cockpit glass clipping fix + VR sky crescent fix + enhanced flight data panel (4.12.2m + UP3.4 P2 HF23)

• Fixed cockpit glass/transparent parts floating misaligned (SteamVR projection near-plane = half the passed value; new near/far clip config vr_world_near etc.)
• Fixed the VR sky crescent (far-plane configurable); flight data panel enhanced (speed/altitude+VSI/heading/G with color warnings); briefing map restored to the game's default rendering
• UP3.4 P2 HF23 fully aligned with 4.12.2m

Earlier versions (summary)

• 2026-08-02 - UP3.4 P2 HF23 official adaptation (briefing freeze fix, aligned with the 4.12.2m mainline, all 33 official P2 baseline changes); VR HUD panel system released (flight data + popup messages + VRHUD_TOGGLE)
• 2026-08-01 - VR tactical map HUD (spatial panel) + map hotkey group (zoom/pan/focus/reset) + VRMAP_RECENTER recenter key + vr_debug logging
• 2026-07-27 and earlier - 4.12.2m pure-matrix HMD pipeline, 6DOF, FOV self-protection, glass/sky fixes etc. (see earlier posts for the full history)

2. Downloads (important - check your combination first)

Each MOD package matches exactly one game version + one MOD framework - do not mix them. All release packages are JSGME snapshot folders (hashed-class folder + game-root files + the vr_aircraft_conf config folder inside), unzip into your JSGME MODS folder and activate (see section 3).

4.12.2m - development mainline

• Game version: 4.12.2m (Steam rollback from 4.13.4 in properties)
• MOD framework: SAS ModCat 5.3
• MOD package: il2vr_4122_dev202609052245_full.zip (same update batch as BAT/UP: orders/center panels + VR_ZOOM + menu gaze pointer + vr_esc + map mode cycle + 6-slot messages + config tool; includes all previous features)
• MOD folder: #SAS\MOD_VR\

UP3.4 P2 HF23 - current UP3.4 target

• Game version: UP3.4 Patch 2 Hotfix 23 (latest UP3.4)
• MOD framework: UP3 framework (JSGME activation into #UP#\IL2_VR\)
• MOD package: il2vr_up34p2hf23_dev202609052245_full.zip (same update batch, feature-aligned)
• MOD folder: #UP#\IL2_VR\
• Note: UP3.4 P2 HF23 has no built-in class conflicts; if VR is missing or 2D popups are not suppressed alongside other MODs, see FAQ Q8

BAT 4.3.0 - new

• Game version: BAT 4.3.0 (all modules: DOF3 / TGA3 / WAW3 / JTW3)
• MOD framework: SAS ModAct 5.3 wrapper (built into BAT)
• MOD package: il2vr_bat43_dev202609052245_full.zip (same update batch; the package deploys one 0_vr_mod copy to each of the four modules, so VR works whichever module you fly)
• Deployment: #WAW3\0_vr_mod\ etc. (placed automatically by JSGME activation; never write into Classes-BAT)
• Note: BAT's NG HUD custom config (conf.ini [Mods] section) is untouched; after switching BAT modules (il2fb.ini - [Settings] - ModType) no extra steps are needed

Download links

• 4.12.2m: il2vr_4122_dev202609052245_full.zip
• UP3.4 P2 HF23: il2vr_up34p2hf23_dev202609052245_full.zip
• BAT 4.3.0: il2vr_bat43_dev202609052245_full.zip

Which one should I use?

• Want the Steam 4.12.2 version: use the 4.12.2m build
• Want UP3.4 (incl. the classic multiplayer rooms): use the UP3.4 P2 HF23 build
• Want BAT (the most content-complete community pack): use the BAT 4.3.0 build

3. Quick start (same steps for all three versions; 4.12.2m as the example)

Prerequisites

1. The matching game version (see above) + SteamVR installed and running
2. Any SteamVR-compatible HMD (community-tested models in section 6)
3. Visual C++ 2022 runtime x86: vc_redist.x86.exe

Installation (JSGME, recommended)

1. Unzip the package - put the resulting folder (e.g. il2vr_4122_dev202609052245_full) into your JSGME MODS folder: jsgmemods\ for 4.12.2m / UP3.4, BATMODS\ for BAT 4.3.0
2. Activate the MOD in JSGME (BAT users with other MODs: no conflicts, any order is fine)
3. Start SteamVR - start the game - enter the cockpit and press the recenter key (or use the RECENTER button at the bottom center of the main menu)

Manual installation without JSGME: copy everything inside the folder to the game root (hashed class files into #SAS\MOD_VR\ or #UP#\IL2_VR\ or the module's #XXX\0_vr_mod\; the four dll/font files to the game root; the vr_aircraft_conf folder to the game root).

Configuration: start the game once, then run the config tool

• All VR panels (map / flight data / messages / orders / buttons) are managed by the bundled configuration tool il2vr_config.exe (inside the vr_aircraft_conf folder; double-click to run; full instructions are built into the tool): drag panels to reposition with live preview, tick commands, choose language
• The first time you fly an aircraft, the game auto-generates its empty per-aircraft config and applies the global defaults - no manual file creation
• Don't like the default panel positions? Open the tool - drag the panels where you want - save, then press VRHUD_RELOAD in-game to apply instantly

conf.ini settings to change

Only these; leave everything else untouched:

• [window]: FullScreen=0 (windowed mode is required), SaveAspect=0; width/height are up to you (the window is only a desktop mirror preview - it does not affect in-headset sharpness)
• [Render_OpenGL]: only needed when hardware rendering is ON (HardwareShaders=1): ForceShaders1x=1 (otherwise flickering) and water=0 (water reflections are misaligned in VR)
• [VR] factor: in-headset render resolution = HMD recommended x factor (0.5 = half resolution, 1.0 = native 1:1). Start with 0.5, then raise it according to your GPU
• [VR] everything else (near/far clip, menu position, magnifier parameters...) has sensible built-in defaults - no need to add anything; panel layout parameters are managed by the config tool - no need (and not recommended) to hand-edit them
• [Console]: troubleshooting only - LOG=1, LOGFILE=log.lst (see FAQ)

Three rules you must follow

1. Windowed mode: FullScreen=0, SaveAspect=0. The MOD uses the window as its rendering context; in-headset sharpness is decided by factor, independent of the window size
2. High-DPI: on 2K/4K screens with desktop scaling other than 100%, enable "High DPI scaling override - Application" in the il2fb.exe compatibility properties, otherwise the game may not start
3. Upgrading from an old version (2026-08-17 or earlier): delete the old MOD files completely first (JSGME users: deactivate the old snapshot before activating the new one). Never overwrite-install

4. Rendering settings and performance

• Hardware rendering (HardwareShaders=1) vs VR: the incompatible parts require ForceShaders1x=1 + water=0 (see above). If hardware rendering is OFF, no extra settings are needed
• Sharpness formula: in-headset resolution = HMD recommended (x SteamVR supersampling) x factor. The desktop window and NVIDIA DSR do not affect in-headset sharpness; raise factor or SteamVR supersampling for more clarity
• External AA: forbidden. Forcing AA/DSR on il2fb.exe in the NVIDIA panel causes a black screen (see FAQ Q2)
• Performance expectation: light GPU load, CPU is the bottleneck (two scene renders per eye + old single-threaded engine). An i7-class CPU or higher is recommended; frame drops at low altitude / busy scenes are to be expected - motion smoothing (90 Hz) helps
• Flickering image (eye-blink feel): make sure ForceShaders1x=1 is set

5. VR HUD & operations guide (please read - these features exist for a reason!)

All VR spatial panels live in world space in front of you: look at a panel and it lights up from its faded state (gaze fade: fades out when you look away, fades in when you look back) - aim the reticle at a button - press the interact key. That is the unified interaction model of this MOD: no controller lasers needed - your head is the mouse.

5.1 Hotkey overview (Controls - misc group; every key can be bound to keyboard or joystick)

• VRMAP_RECENTER - VR recenter (press once after entering the cockpit; the main menu RECENTER button lets you do it in advance)
• VRHUD_TOGGLE - show/hide all VR panels (map / flight data / messages / buttons)
• VRHUD_ACTIVATE - the gaze interact key (see 5.2); default binding J
• VRHUD_RELOAD - hot-reload panel/aircraft config (apply config changes without restarting the game)
• VRHUD_MENU_CLICK - the interact key inside menus (auto-synced to your VRHUD_ACTIVATE binding - nothing to set up)
• VR_ZOOM - the magnifier: hold for instant 5x zoom (see 5.8)
• VR_NEAR_INC / VR_NEAR_DEC - fine-tune the near clip in-game (+-0.01 m per press, remembered per aircraft)
• vr_esc - full ESC semantics (exit mission / close current UI), bind to any key
• VRMAP_ZOOM_IN/OUT, PAN_*, FOCUS_PLAYER, RESET - map panel zoom / pan / focus player / reset
• M mode button (the ◎ on the map panel) - cycle map display modes (equivalent to the desktop right-click menu; choice remembered)

5.2 Gaze interaction basics (the core of every click in this MOD)

• Reticle: the small ring at the center of your view, always following your head
• Hit: when the reticle points at a button/text area on a panel, the target highlights (collapsed small squares show the real reticle landing point within a 2x sensing zone for easy aiming)
• Execute: press VRHUD_ACTIVATE (default J) while highlighted = click; some controls (map/list) support press-and-drag
• Dwell: some collapsed controls auto-expand/switch after a short gaze (0.3-0.5 s) and auto-collapse after you look away for a while
• The interact key clicks cockpit button panels in missions and GUI buttons in menus - one key, the game decides the context automatically

5.3 Tactical map (spatial panel)

Open the in-game map (vanilla key) - the map appears as a spatial panel in front of you:

• Pan / zoom: VRMAP_PAN_* / VRMAP_ZOOM_* - dragging on the panel works too
• A column of vector buttons sits on the panel's right edge (hover highlight, click flash): X = close map, + = zoom in, - = zoom out, focus player, and ◎ = cycle map display modes (on desktop you need the right-click menu for this - in VR this is the only entry; on 4.12.2m there is no multi-mode map system, so ◎ does nothing - expected)
• The panel auto-hides when the map is closed; position/size not to your taste - drag it in the config tool

5.4 Flight data panel

• Normally shows just the speed line (the data you need most); gaze at the panel for a moment and it expands into the full data area - speed (IAS+TAS) / altitude + vertical speed / heading / G, plus aircraft info lines and engine status lines (rows vary slightly by version/aircraft)
• Click the panel to cycle units (metric / nautical / imperial / follow game setting; choice remembered)
• Color warnings for overspeed / overload / high G (white-yellow-red), G overload flashes red; mirror mode (watching another player) converts automatically
• Panel in the way? VRHUD_TOGGLE hides everything, or adjust opacity/position in the config tool

5.5 Message panel & center/orders panels

• Message panel: vanilla popup messages (throttle % / gear / flaps / radiator etc.) appear in a 6-slot ring on a VR panel - white-to-red fade, 10 s retention; on BAT it also automatically picks up the ~140 messages BAT added (C&C, ships, target towing etc.)
• Center panel: center-screen text (server announcements etc.) is VR-ized so it no longer fights the vanilla 2D text
• Orders panel (multiplayer): the radio command menu is VR-ized - flight/wingman/ground-control commands appear as a button list; gaze + interact key executes directly, and typing in chat is unaffected

5.6 Command Box (the universal fallback panel)

Didn't configure button panels for a plane? The Command Box is the universal fallback - every aircraft has it:

• Layout: a row of quick buttons on top (default 6: Gear / Canopy / Map / Engine / Bail Out / Quit (ESC)) + 6 category tabs in the middle (Flight / Power / Engines / Weapons / Systems / Misc) + the current category's command buttons below
• Usage: gaze at a tab for 0.3 s to switch category; gaze at a command + interact key to execute (yellow flash feedback on click)
• It collapses to a 6 cm square when idle; gaze 0.3 s to expand; commands/tabs/language (en/zh/ru) are all editable in the config tool
• The Misc group includes VR-specific entries such as Quit Mission (ESC), VR Zoom and VR Near +/-

5.7 Cockpit gaze button panels (per-aircraft, optional)

Define a "clickable cockpit" per aircraft: e.g. put a Gear button next to the Bf-109's gear handle - gaze + interact key retracts/extends the gear, like reaching out:

• An empty per-aircraft config is auto-generated on first flight; add panels/buttons with the config tool (full in-game command picker with categories and search)
• No config = fully playable anyway (Command Box fallback); pure-HOTAS players can hide all panels with VRHUD_TOGGLE
• Reference: ready-made button-layout templates are available in the config tool for one-click apply

5.8 Magnifier VR_ZOOM

• Hold the VR_ZOOM key (default V) = instant 5x zoom, release to restore - for watching distant enemies/ground targets
• Optically correct: both eyes scale in sync without parallax error and without a "miniature model" feel; view smoothing while zoomed (adjustable: conf.ini [VR] vr_zoom_m = magnification, vr_zoom_smooth = smoothing strength, 0 = off)
• Different from map zoom: this is a full-scene optical zoom; the cull distance does not change, so distant objects will not pop out of existence while zoomed

5.9 Menu overlay & gaze pointer

• Main menu / settings / briefing / pause / multiplayer lobby no longer "plaster to your face": menus appear as a world-space panel about 1.5 m in front, same aspect ratio as the desktop window (defaults are fine; position/size if needed: conf.ini [VR] vr_menu_x/y/z/yaw/pitch/roll/width)
• Inside menus your gaze is the mouse: the gaze pointer follows your view and GUI buttons/lists/drag bars all work with the interact key - the physical mouse also still works

5.10 Per-aircraft detail: near-clip auto tuning

• The near clip (vr_world_near) decides whether cockpit-close objects are clipped/clipping through. The global default is already reasonable; for the odd aircraft that still clips: press VR_NEAR_INC/DEC in flight (+-0.01 m per press; the current value is shown on the message panel)
• Adjustments are remembered per aircraft (vr_aircraft_conf\{aircraft}.ini) and auto-applied next flight; the key auto-clears when back to default

6. HMD compatibility (community-tested summary)

• Valve Index: development baseline
• Quest 2 / Quest 3 (wireless - Steam Link / Virtual Desktop): working (tested by Ronno72, Jocko, MikeD etc.); Pimax Crystal Super users report perfect 6DOF and crisp visuals
• Pimax Crystal / Light / Super: working; the 6DOF translation-axis mapping was fixed in newer builds - use the latest package
• Meganex 8K MkII (direct): working, crisp instruments, 6DOF 1:1
• Other SteamVR headsets: feedback welcome

General tips:

• Sharpness: raise factor (max 1.0 = 1:1) or SteamVR supersampling; Pimax - keep Parallel Projection ON; Pimax crash troubleshooting: set the SteamVR render resolution from "Auto" to custom and halve it first
• Streaming (Quest/Pico): Steam Link works out of the box; if Quest Link / Virtual Desktop goes black, see the appendix (two open-source fallback routes: ALVR / WiVRn + OpenComposite)
• External AA causes a black screen - do not enable; terrain quality is a matter of taste (after forcing shader 1.x, quality presets do not affect stability)

7. FAQ (community troubleshooting)

Q1: Game crashes on startup (EXCEPTION_ACCESS_VIOLATION in GLContext.CreateWin32)
-> Delete opengl32.dll from the game root (usually a ReShade leftover - IL-2 does not need it)

Q2: Headset is black but the desktop game runs fine
-> Check the NVIDIA control panel: are you forcing anti-aliasing/DSR on il2fb.exe? Restore "Application-controlled". For streaming-related black screens see the appendix

Q3: Flickering image (eye-blink feel)
-> [Render_OpenGL] ForceShaders1x=1

Q4: Cockpit-close clipping / see-through (windshield, glass, fuselage)
-> Fixed by default (vr_world_near default 1.8 = 0.9 m actual clip). For the odd aircraft that still clips: press VR_NEAR_INC in flight to raise it (remembered per aircraft)

Q5: Blurry / resolution stuck low in the headset
-> Raise factor (max 1.0) or SteamVR supersampling. The desktop window only affects the mirror preview, not headset sharpness

Q6: My antivirus reports il2vr.dll as a trojan?
-> False positive. The only "high-risk-looking" file in the MOD is the author-written VR bridge DLL (an OpenVR semantic converter, unsigned) - Defender is prone to flagging unsigned DLLs. Not sure? Upload it to VirusTotal for a second opinion, or add the game folder to your antivirus exclusions

Q7: Nothing changed / odd behavior after upgrading
-> Old MOD files were not fully removed (JSGME users: deactivate the old snapshot first, then activate the new one); double-check the game version vs package version match (the 4.12.2m package =/= the UP3.4 package =/= the BAT package)

Q8: Installed but no VR effect / 2D popups not suppressed (class-resolution conflict)
-> Symptoms: VR disabled or vanilla 2D popup messages still showing. Cause: with multiple versions of the same class present, the framework loads the one from a higher-priority MOD folder. Fix: find the conflicting MOD and remove its conflicting files (back up before deleting). The only known historical conflict lives in the "! UP 3.4 Hotfix" folder (UP3.4 P2 HF23 itself does not have this problem). BAT users: make sure nothing was placed into Classes-BAT

Q9: Black screen entering missions on the UP3.4 version
-> First confirm that UP3.4 Patch 2 Hotfix 23 is actually installed (using the wrong package without the patch crashes at startup). If the latest package still reproduces it, please report back with the section-8 info plus log.lst and I will investigate

8. Test report template (please reply with your data!)

1. Game version + MOD framework: 2. MOD package file name: 3. Headset model: 4. Streaming method:
5. Result: 6. Instrument readability: 7. Framerate / latency feel: 8. 6DOF feel:
(attaching your conf.ini [VR] section and log.lst helps; log switches: [Console] LOG=1/LOGFILE=log.lst + [VR] vr_debug=1)

Especially welcome: Quest/Pico streaming success stories per method (Steam Link / VD / ALVR / WiVRn); factor settings experience on high-resolution headsets (Pimax / Meganex etc.) - it will be folded into the compatibility table.

9. Known limitations and roadmap

Known limitations:

• CPU load: one full scene render per eye + one desktop mirror; busy scenes (low altitude / heavy action) may drop frames. i7-class CPU or better + motion smoothing recommended; CPU-parallelization research is ongoing
• The message panel may garble Cyrillic (Russian) characters - not yet fixed (English/Chinese are fine)
• Advanced water rendering behaves abnormally in VR (reflection misalignment etc.) - engine-level issue, under investigation
• Residual per-headset 6DOF cases on older models (known cases fixed in the latest package; feedback welcome)

Roadmap:

1. Keep the three versions aligned and maintained (4.12.2m / UP3.4 P2 HF23 / BAT 4.3.0)
2. Command Box / button-panel usability: more default button-layout templates and per-aircraft presets
3. Long term: OpenXR submission migration (drop the SteamVR dependency, improve streaming compatibility); CPU parallelization

10. Credits

• firepolo - original OpenVR mod and the il2vr C++ code
• SAS~CirX & SAS~Storebror - ModAct; Valve - OpenVR SDK
• Test pilots: Sparviero, Ronno72, FTC_Topper, ROSS_Papa_JA2, carsmaster, Jocko, Joffski, mcgen, BrownFloyd, MikeD, heloguy, mak and others

Appendix: streaming compatibility attempts (Quest/Pico wireless, speculative)

The MOD relies on the legacy OpenGL pipeline; Quest Link / Virtual Desktop have dropped legacy OpenGL support in recent years and may show a black screen (not verified one by one). Steam Link is known to work without any adaptation. If Steam Link fails, two open-source fallback routes (not verified one by one - feedback welcome):

• Route A: ALVR (keeps the SteamVR pipeline) - PC: github.com/alvr-org/ALVR/releases + headset client push
• Route B: WiVRn + OpenComposite (bypasses SteamVR straight to the headset) - OpenComposite: github.com/QuestCraftPlusPlus/OpenComposite/releases (overwrite the game-root openvr_api.dll with its openvr_api.dll) + WiVRn: github.com/WiVRn/WiVRn/releases

Any questions - reply in this thread, ideally with the section-8 info and a debug log. Happy flying!

Edited yesterday at 03:09 PM by boilingmetal

[ROSS_Papa_JA2]

Привет! Если у меня будет стоять версия v 4.13.4m - Platinum Collection. Как поиграть в нее в шлеме ВР?

[boilingmetal]

@ROSS_Papa_JA2 I expect to complete the adaptation for 4.12.2 and 4.13.4 by August.

[ROSS_Papa_JA2]

Спасибо, буду ждать

[ROSS_Papa_JA2]

Еще может глупый вопрос)) Если я в мою игру версии 4.13.4 вставляю ваш мод ВР, то она не летит в принципе? 

[ROSS_Papa_JA2]

Тема очень интересная, очень надеюсь, что у вас получится адаптировать вр для более "свежих" версий Ил-2 1946. Попытался найти в доступе в инете версию 4.09, но успеха быстрого нет. Все что увидел гораздо версии выше. И в стиме версия 1946 тоже выше, что у вас под мод ВР. И даже купил в стиме))) в надежде на успех в августе.

Edited July 10 by ROSS_Papa_JA2

[boilingmetal]

1 hour ago, ROSS_Papa_JA2 said:

Тема очень интересная, очень надеюсь, что у вас получится адаптировать вр для более "свежих" версий Ил-2 1946. Попытался найти в доступе в инете версию 4.09, но успеха быстрого нет. Все что увидел гораздо версии выше. И в стиме версия 1946 тоже выше, что у вас под мод ВР. И даже купил в стиме))) в надежде на успех в августе.

You need to downgrade from 4.12.2 to 4.10.1. You can use Google's AI mode to help you find the downgrade tool.

[ROSS_Papa_JA2]

4 часа назад, boilingmetal сказал:

You need to downgrade from 4.12.2 to 4.10.1

Нашел рабочую версию 4.09. Поставил последовательно 4.10 ... 4.10.1... Проверил, игра запускается и пишет нужную версию. Далее поставил мод из вашей папки  il2vr_4.10.1m_dev202607072219 ( скопировал файлы поверх в папке игры)... поставил фикс из папки il2vr_up34p2hf23_dev202607090418 ( также скопировал их папку с игрой ( с заменами соглашался). 

В конф.ини прописал строчку [VR]
                                                     factor=0.5

Где должны находиться папки #UP# и #SAS ? 

Что ставить в разрешение экрана? У меня монитор 2560 х 1440.    Шлем паймекс лайт, 5080 видеокарта. Вин10.

Запускаю стим вр. Игра в стиме запускается, в режим ВР не переходит. Контроллеры шлема работают, но мышь не активная ( С мышью разобрался)))) Теперь все нормально с мышью).

Как ВР должно запуститься из папки #UP#. Что делаю не так?

Edited July 10 by ROSS_Papa_JA2

[Drewm3i-VR]

Wow!

Wonder if it could work with BAT or the newer version of Ultrapack?

https://www.sas1946.com/main/index.php?board=264.0

Or the graphics extender? What about OpenComposite?

Excellent work and very exciting!

[boilingmetal]

15 hours ago, ROSS_Papa_JA2 said:

Нашел рабочую версию 4.09. Поставил последовательно 4.10 ... 4.10.1... Проверил, игра запускается и пишет нужную версию. Далее поставил мод из вашей папки  il2vr_4.10.1m_dev202607072219 ( скопировал файлы поверх в папке игры)... поставил фикс из папки il2vr_up34p2hf23_dev202607090418 ( также скопировал их папку с игрой ( с заменами соглашался). 

В конф.ини прописал строчку [VR]
                                                     factor=0.5

Где должны находиться папки #UP# и #SAS ? 

Что ставить в разрешение экрана? У меня монитор 2560 х 1440.    Шлем паймекс лайт, 5080 видеокарта. Вин10.

Запускаю стим вр. Игра в стиме запускается, в режим ВР не переходит. Контроллеры шлема работают, но мышь не активная ( С мышью разобрался)))) Теперь все нормально с мышью).

Как ВР должно запуститься из папки #UP#. Что делаю не так?

If you already have a clean version of 4.10.1, then you already have a perfect foundation for the game. Next is the installation of mods, which depends on what kind of mod framework you use. If you have a clean 4.10.1, it is recommended that you use the SAS mod framework. In that case, your game mods should be loaded from the #SAS# directory, just as I did in the 4.10.1 mod archive.

Secondly, if you use a relatively new header like pimax, it is very likely that it will have some misalignment problems with the header compatible with openvr_api in my mod package. The solution to this problem is similar to playing other non-steam games in HMDs like pimax and pico. You may need Virtual Desktop or other compatible streaming solutions, or try the OpenComposite mentioned by @Drewm3i-VR.

The resolution problem you mentioned, this will be forcibly replaced by api reading your HMD resolution from steam vr, and then multiplied by factor. In fact, you don't need to set specific values yourself, you just need to pay attention to factor.

I am also testing compatibility with my friend on other HMDs. There are some issues that can only be discovered after more people try them. Keep flying, my friend.

11 hours ago, Drewm3i-VR said:

Wow!

Wonder if it could work with BAT or the newer version of Ultrapack?

https://www.sas1946.com/main/index.php?board=264.0

Or the graphics extender? What about OpenComposite?

Excellent work and very exciting!

I'm asking my friend to test OpenComposite. The dll in the original mod did encounter problems on pico, and I haven't got any feedback since I asked him switched to OpenComposite dll. As for the compatibility of 4.12.2, I may realize it at a later time. At present, I will focus on optimizing the function of this mod on UP3 multiplayer online server. Its 6dof is cut by the camera movement of the native game, which will make it difficult for us to observe backwards, which is a headache.

Edited July 11 by boilingmetal

[ROSS_Papa_JA2]

7 часов назад, boilingmetal сказал:

If you already have a clean version of 4.10.1, then you already have a perfect foundation for the game. Next is the installation of mods, which depends on what kind of mod framework you use. If you have a clean 4.10.1, it is recommended that you use the SAS mod framework. In that case, your game mods should be loaded from the #SAS# directory, just as I did in the 4.10.1 mod archive.

Привет! Я очень далек от "старичка" ила и не представляю о чем вы вообще говорите?))  Как мне поставить мод от SAS в версию 4.10.1 ? Чтобы она заработала в режиме ВР? Может вам стоит показать видео как вы установили нужные файлы и правильный путь запуска игры в режиме ВР?

BИ еще уточнение. В стиме сейчас версия 1946  4.13.4m  и если делать, то надо делать мод под нее.

Edited July 11 by ROSS_Papa_JA2

[boilingmetal]

9 hours ago, ROSS_Papa_JA2 said:

Привет! Я очень далек от "старичка" ила и не представляю о чем вы вообще говорите?))  Как мне поставить мод от SAS в версию 4.10.1 ? Чтобы она заработала в режиме ВР? Может вам стоит показать видео как вы установили нужные файлы и правильный путь запуска игры в режиме ВР?

BИ еще уточнение. В стиме сейчас версия 1946  4.13.4m  и если делать, то надо делать мод под нее.

I suggest that you use google AI to help you give operational advice for your environment. I use the mod framework of SAS Modact 3 in 4101m. You can ask these questions directly and ask AI to answer your questions in Russian.

I am referring to the AI mode of Google Search. I find that it provides answers more based on real existing web pages. When it comes to solving precise problems, it is even more reliable than Gemini. Gemini sometimes still fabricates non-existent GitHub repositories or web pages, but google.com/ai basically provides assistance based on web facts.

So for questions about using mods in 1946, it will rely more on core forums like SAS1946 to help you search for and select appropriate solutions. To be honest, it is stronger than my ability to articulate and reason. This is much more direct than the two of us, both non-native English speakers, guessing at each other through English.

Looking forward to your successful attempt.

Edited July 12 by boilingmetal

[ROSS_Papa_JA2]

11.07.2026 в 22:21, boilingmetal сказал:

Looking forward to your successful attempt.

Увы, успехов нет. Игра запускается, доходит до появления в кабине самолета и там вылетает, режим ВР не запускается. Возможно не так работал модификатор, нашел только доступные для скачивания версии модаст 5.30 и модаст v4 для 4111m. Версии 3 для 4101 не нашел. 

Остается надежда на ваш успех для версии 1946  4.13.4m.

[=BW=777]

5 часов назад, ROSS_Papa_JA2 сказал:

Увы, успехов нет. Игра запускается, доходит до появления в кабине самолета и там вылетает, режим ВР не запускается. Возможно не так работал модификатор, нашел только доступные для скачивания версии модаст 5.30 и модаст v4 для 4111m. Версии 3 для 4101 не нашел. 

Остается надежда на ваш успех для версии 1946  4.13.4m.

Есть бета версия битвы за британию, с поддержкой VR. Я пробовал, все работает, но выглядит мягко говоря очень печально, особенно земля. Что уже говорить про старичка. Это все равно что пытаться оживлять труп. Можно создать кадавра, но удовольствия, от его созерцания вы не получите, скорее наоборот. Пусть старичок остается на своем заслуженном и достойном месте легендарного авиасимулятора. То что к нему прикручивают различные криворукие мододелы вызывает лишь сожаление.

[ROSS_Papa_JA2]

32 минуты назад, =BW=777 сказал:

Есть бета версия битвы за британию, с поддержкой VR. Я пробовал, все работает, но выглядит мягко говоря очень печально, особенно земля. Что уже говорить про старичка.

Я тоже как-то запускал блиц с модом ВР, да, проблемно выглядит Тормоза лютые. Но тут другое)) Запустил в стим вр 1946, да, ВР от мода топикстартера не подхватился, но картинка в окружении вдруг показалась лучше, чем в прости госпади VTOLe VR, и форсе фидбек на моей мозе заработал отлично !!! И я подумал, а почему бы и не иметь такого "старичка" с громадной базой самолетов, модов, кампаний и тд, и тп. Весь вопрос, чтобы работал ВР. По уверению топикстартера его вариант 1946 в версии 4.10.1 полетел отлично и очень плавно. Так что я бы не отказался вернуться в реку дважды. 🙂

PS Я бы от варианта Рыцарей неба 1917 в режиме ВР тоже бы не отказался)

Edited July 13 by ROSS_Papa_JA2

[cmbishop]

Hello Boilingmetal,
Thank you very much for your work!
However, I can’t seem to get the VR to work.
I followed your installation instructions carefully, and when I launch the game, it appears in windowed mode. When I start the flight, I can see the 2D model on the screen, but I’m not seeing anything in the VR headset (HP Reverb 2 on Steam VR with the Oasis driver). When I switch between windows to find the Steam VR window, I can see that it’s searching for ‘il2fb’ but can’t find it.
Do you have a solution you could suggest? 
Thanks again!

[GOA_AveFenix=VR=]

Hello, its possible to run this mod with OpenComposite / OpenXR without passing throught steamVR? 

 

Regards. 

[boilingmetal]

15 hours ago, GOA_AveFenix=VR= said:

Hello, its possible to run this mod with OpenComposite / OpenXR without passing throught steamVR? 

 

Regards. 

 

21 hours ago, cmbishop said:

Hello Boilingmetal,
Thank you very much for your work!
However, I can’t seem to get the VR to work.
I followed your installation instructions carefully, and when I launch the game, it appears in windowed mode. When I start the flight, I can see the 2D model on the screen, but I’m not seeing anything in the VR headset (HP Reverb 2 on Steam VR with the Oasis driver). When I switch between windows to find the Steam VR window, I can see that it’s searching for ‘il2fb’ but can’t find it.
Do you have a solution you could suggest? 
Thanks again!

I only have a Valve Index, so I really don't have the means to test games using OpenXR or HP's HMD. However, I think the usual tricks for playing older non-SteamVR VR games on these HMDs should work, including warp and bridge libraries like OpenComposite.

[ROSS_Papa_JA2]

1 час назад, boilingmetal сказал:

only have a Valve Index, so I really don't have the means to test games using OpenXR or HP's HMD. However, I think the usual tricks for playing older non-SteamVR VR games on these HMDs should work, including warp and bridge libraries like OpenComposite.

"Все VR-продукты из Steam, совместимые со шлемами HTC Vive, HTC Vive Pro, Oculus Rift или Windows Mixed Reality, работают и с Valve Index — и наоборот."

Это не я придумал, это из описания вашего шлема. Но все VR-продукты из Steam точно так же легко и непринужденно работают и на Ревербе г2, и на всех Паймексах. Если у вас игра 1946 запустилась в режиме ВР на вашем шлеме через стим ВР, то она точно также должна запуститься и на паймексе, и уж тем более на ревербе г2. Надо точно показать в картинках или видео, как вы установили моды в игру, как они стали  активны в модасте SAS, как вы запустили ВР. Не никакой разницы что у вас такой шлем, а у нас другие шлемы от другого производителя, они все работают в системе VR из под стима. 

Edited July 14 by ROSS_Papa_JA2

[=BW=777]

13.07.2026 в 15:23, ROSS_Papa_JA2 сказал:

PS Я бы от варианта Рыцарей неба 1917 в режиме ВР тоже бы не отказался)

Ну это то вообще просто решить - купи "Летающий цирк" и всего делов. 

[ROSS_Papa_JA2]

13 часов назад, =BW=777 сказал:

Ну это то вообще просто решить - купи "Летающий цирк" и всего делов. 

Весь цирк есть, с его 40 самолетами, вместо более 100 в рыцарях, включая Илью Муромца. Это я еще  про режим форсе фидбек в рыцарях не заостряю вопрос, он там идеален  в отличии

Edited July 15 by ROSS_Papa_JA2

[boilingmetal]

On 7/14/2026 at 10:48 PM, ROSS_Papa_JA2 said:

"Все VR-продукты из Steam, совместимые со шлемами HTC Vive, HTC Vive Pro, Oculus Rift или Windows Mixed Reality, работают и с Valve Index — и наоборот."

Это не я придумал, это из описания вашего шлема. Но все VR-продукты из Steam точно так же легко и непринужденно работают и на Ревербе г2, и на всех Паймексах. Если у вас игра 1946 запустилась в режиме ВР на вашем шлеме через стим ВР, то она точно также должна запуститься и на паймексе, и уж тем более на ревербе г2. Надо точно показать в картинках или видео, как вы установили моды в игру, как они стали  активны в модасте SAS, как вы запустили ВР. Не никакой разницы что у вас такой шлем, а у нас другие шлемы от другого производителя, они все работают в системе VR из под стима. 

I think your suggestion is correct. I am currently on vacation and accompanying my family, so I can't get my HMD. I will supplement the specific MOD installation, startup process screenshots or videos around the 27th. At the same time, I will try my best to complete the version adaptation of 4.12.2 before August.

[boilingmetal]

On 7/15/2026 at 5:21 PM, ROSS_Papa_JA2 said:

Весь цирк есть, с его 40 самолетами, вместо более 100 в рыцарях, включая Илью Муромца. Это я еще  про режим форсе фидбек в рыцарях не заостряю вопрос, он там идеален  в отличии

Dude, try this:    https://www.mediafire.com/file/ubw037fokolhlu8/il2vr-4.12.2m_Sasmodcat530_dev20260725.zip/file

My environment is SteamVR + valve index, I developed this mod based on the older openvr_api.dll v1.23.7. If I delete the old version of the DLL (provided in the zip package) and try to use the system's latest SteamVR API, the game crashes. If I try to use OpenComposite, the game also crashes( Maybe it's because I'm using SteamVR? So I can't use OpenComposite's openvr_api.dll? ). I think there are still many things I haven't figured out regarding the adaptation from the game to the system's VR driver. For now, I can only say that I have managed to get the bridge working in my own environment.

To facilitate your testing, I will list the technology stack used in my actual environment:
1、4.12.2 steam version
2、install sas modcat 5.3 for 4.12.2
3、add IL-2_Selector_5.1.2（I use it to get dumps and some necessary debug logs, but I suppose it's not essential）
4、start steam vr 2.16.7 + valve index
5、Install my mod（Includes openvr_api.dll v1.23.7）and run the game

That's all.

Edited July 25 by boilingmetal

[ROSS_Papa_JA2]

4 часа назад, boilingmetal сказал:

1、4.12.2 steam version
2、install sas modcat 5.3 for 4.12.2
3、add IL-2_Selector_5.1.2（I use it to get dumps and some necessary debug logs, but I suppose it's not essential）
4、start steam vr 2.16.7 + valve index
5、Install my mod（Includes openvr_api.dll v1.23.7）and run the game

Установил, как указано.

Игра запускается в режиме мода ВР.  Успел посмотреть в шлеме даже кусок интро.)) Но далее игру крашит.

[boilingmetal]

5 hours ago, ROSS_Papa_JA2 said:

Установил, как указано.

Игра запускается в режиме мода ВР.  Успел посмотреть в шлеме даже кусок интро.)) Но далее игру крашит.

I think we've already taken the first step!

If possible, could you try enabling the game's logging feature and show me the log generated after the game crashes? Of course, you'll need to manually adjust the settings in conf.ini.

conf.ini:

[Console]
HISTORY=1024
HISTORYCMD=1024
LOAD=console.cmd
SAVE=console.cmd
LOG=1
LOGTIME=1
LOGFILE=log.lst
LOGKEEP=0

Finally, make sure you are using version 4.12.2m

Looking forward to resolving your compatibility issues soon. Today I tested the gunner's VR perspective, and it's even more interesting!

 

 

Edited July 25 by boilingmetal