Virtual Reality

[Nikita]

Update. I just tried using Quest 3 with Virtual Desktop and both IL2 GB and Korea worked fine there.. So I'm puzzled trying to figure out why Pimax Crystal Super is so problematic with IL2 games..

24 minutes ago, Dash,Polder said:

I have great success in a PCL with the VectorXR utility.  Engaging it doesn't just change my perception of scale, I can visually see the pit snap wider like the gun sight and pad are elongated a tad in width, wider physically, even the stamped lettering changes.  It really helps the outside world, the cities become individual houses and buildings again instead of a mono blending.  Much more comfortable on my eyes with it on, just had to play around a bit to tune for proper scale perception.  Even set to zero where it shouldn't be scaling or correcting anything it's better, can still see it visually correcting something on the edges switching it on and off. 

VectorXR may be useful for enhancing an already working setup but was totally useless in my case with Crystal Super. None of the settings actually helped there..

[AeroCrab]

I am also coming from a Quest 3 (now on a Dream Air) and things do seem off for me as well. I've found this entry in a Pimax log:

Quote

[26-06-27 21:16:11.149][15792][notice][PVR] [APP]Recommended peripheral left resolution: (5230 x 4168), right resolution: (5190 x 4168)

and the fact that those are different seems wrong/bad. I've got some other software going on so I need to isolate a bit more.

The relevant log can be found in AppData\Local\Pimax\runtime (I'm running Pimax Play 2.01 - don't know about other versions) as pvr_client_Il-2_log.txt.

<edit> This is all for GB; I haven't spent too much time with Korea yet.

Edited June 28 by AeroCrab

[Nikita]

Oh wow thats a great find! I'll check my logs too when I get back to the game

[Nikita]

2 hours ago, AeroCrab said:

I am also coming from a Quest 3 (now on a Dream Air) and things do seem off for me as well. I've found this entry in a Pimax log:

and the fact that those are different seems wrong/bad. I've got some other software going on so I need to isolate a bit more.

The relevant log can be found in AppData\Local\Pimax\runtime (I'm running Pimax Play 2.01 - don't know about other versions) as pvr_client_Il-2_log.txt.

<edit> This is all for GB; I haven't spent too much time with Korea yet.

Having this log: [26-06-28 21:15:44.377][70524][notice][PVR] [APP]Recommended peripheral left resolution: (6136 x 5906), right resolution: (6136 x 5348)

Also different vertical resolution for the right eye.

But honestly not sure if thats related

[AeroCrab]

I added a check/fix to my custom layer so that I now get matching resolutions:

Quote

[26-06-28 21:56:00.511][16952][notice][PVR] [APP]Recommended peripheral left resolution: (5190 x 4168), right resolution: (5190 x 4168)

and things feel right now (which is of course very subjective and for all I know a placebo thing). In any case, though, it still seems like a bug - I'd be willing to entertain the idea of it being some non-game issue if it A) happened in some other app or B) didn't happen in Korea.

It is interesting that your mismatch is in height while mine is in width. No idea what that might mean. I also don't know whether it only happens at higher resolutions or if I just didn't notice anything (and had no way of knowing) on the Quest.

<edit> I also wonder if this is the cause of the BSB2 "vertical diplopia" thing.

Edited June 29 by AeroCrab

[robzerg]

I can't select any of the animation icons for the aircraft in the Museum; the animation clickbox seems to not correlate to the location of the icon (sometimes if I wave my mouse around I randomly find a selection box off to one side).

[Spitfire1964]

Hi everyone, I have an HTC Pro 2, an i7-13700KF, an RTX 5080, and 64GB of RAM. If anyone has the same setup, it would be great to see the best settings to keep it from constantly crashing...

Edited June 29 by Spitfire1964

[wuVR]

Dusting off the old ReverbG2 with Oasis Driver, i found a temporary Solution for myself
i set an extreme offset that midigates the crosseye-situation for me
then again i do wear glasses, and my settings surely are not for everyone
but maybe someone will have use for this special case
and you might want to dial down your offset a little, since i do need glasses and such

i set an offset for my right eye of positive 42, and negative 42 for my left eye as seen in this snip
i can now enjoy even the menue, without having to re-arrange my brain to watch crosseyed
 

 

Quote

I can't select any of the animation icons for the aircraft in the Museum; the animation clickbox seems to not correlate to the location of the icon (sometimes if I wave my mouse around I randomly find a selection box off to one side).

same here
workaround is to use the lower symbols instead

Edited June 29 by wuVR

[YoYo]

There's something seriously wrong with the nighttime lighting. There's a lack of depth and any light coming from the sky, something illuminating the terrain. I don't know why, and the colors just look off, like some RGB limitation. Here are screenshots taken directly from the simulator at midnight. From above, you can't even see the ground or the clouds (some white effects), but the colors are incorrect (purple, blue, and even a bright green), and basically no stars, moon are visible and the light from them. The area is also naturally underexposed. Clouds should also produce lighting effects (from above from the reflected light). We're in Korea, so night missions are very important. Please refine this.

Here's an example of a night mission from DCS, a good example of what night should look like. Besides, night in IL-2 BoX looks better in VR than in Korea.

 

[wuVR]

these are over-contrast artifacts that result in oily colors and harsh contrast-lines
i know them from a lot of games like DayZ where the only lightsource is in fact an orbiting lightsource above the map
the lack of global illumination from say the stars and/or moon is strange, and makes it neccessary to up gamma/and contrast at night for the player to see anything, but in this case there seems to be a lack of any illumination from the sky at night
could be just due to a bug or some things not implemented yet, but still just wrong
but after all, there´s a  (lot) reason we´re in EA for over a Month

[Comp0site27]

VR Head Position - can't move back

I am finding that I have to centre myself by sitting forward and then sit back so I am in the right position. When in VR none of the head position shortcuts or zooming out do anything (I can zoom in further). Is it just me or am I missing a trick/setting? Quest 3 on VD Thanks

[wuVR]

That´s also something i noticed, 6DoF is limited with closed cockpit, i´d love it to be reverted to
how Great Battles did it, where i could clip through the cockpit, actually liked that
even tho´that might just be my oppinion

[Talisman]

Please help.  Can anyone please suggest a solution to not being able to get the game to load in flat screen mode anymore after I used it in VR?

Thanks in anticipation.

[Redeye]

Move your head to the position you want and press F10. Your head position is saved and pressing Num5 resets your view to that point. Just like in GB.

[Flameout]

I went through maybe similar.  I tried playing in VR.  After a few minutes the game crashed.  restarted the game intending to play flat screen. On the screen were two images - left and right that were intended for VR. Even though it was visually wonky to do, I was able to get the game menu up and deselected VR in preferences, then shut down the game.

Really, I hope the devs add a choice at the start screen (the screen with the big PLAY button) so the user can check/uncheck a box for VR.

[YoYo]

2 hours ago, Talisman said:

Please help.  Can anyone please suggest a solution to not being able to get the game to load in flat screen mode anymore after I used it in VR?

Thanks in anticipation.

Just go into the game and change the options (settings) to 2D, unless there is a problem then you can change it manually in the file.

Try this:

take \IL2Series\game\data\startup.cfg

chaneg this to zero 

or_enable = 0

btw.

• 1 is for OpenVR (Steam)
• 2 is for OpenXR
• 0 for 2D

Edited July 1 by YoYo

[Talisman]

2 hours ago, YoYo said:

Just go into the game and change the options (settings) to 2D, unless there is a problem then you can change it manually in the file.

Try this:

take \IL2Series\game\data\startup.cfg

chaneg this to zero 

or_enable = 0

btw.

• 1 is for OpenVR (Steam)
• 2 is for OpenXR
• 0 for 2D

Big thankyou YoYo.  That has worked.  I notice the game needed to download a lot of stuff before it finally activated in flat screen mode again, so it was a bit worrying what was happening for 20 seconds or so until it settled down (p.s. just seen that there has been an update, so that was what must have been downloading).

I did look at the startup.cfg before I posted, but could not find any clue as to which was the vr/flat screen switch line.  

I hope the developers eventually give us an option on the initial screen after clicking the desktop icon so that we can tick a box to load start in either VR or flat screen as required by the user.  Like the way we can with IL-2 GB and other flight sim titles.

Thanks again.

Happy landings,

Talisman

Edited July 1 by Talisman

[Comp0site27]

5 hours ago, Redeye said:

Move your head to the position you want and press F10. Your head position is saved and pressing Num5 resets your view to that point. Just like in GB.

You the real MVP. Thanks dude

[wuVR]

Night-time City-Lights only appearing on the Left-Eye Screen
Tested with update 0.002 on a ReverbG2

[YoYo]

1 minute ago, wuVR said:

Night-time City-Lights only appearing on the Left-Eye Screen
Tested with update 0.002 on a ReverbG2

Reported, page before.

[Charlo]

7 hours ago, YoYo said:

Just go into the game and change the options (settings) to 2D, unless there is a problem then you can change it manually in the file.

Try this:

take \IL2Series\game\data\startup.cfg

chaneg this to zero 

or_enable = 0

btw.

• 1 is for OpenVR (Steam)
• 2 is for OpenXR
• 0 for 2D

Another handy tip - in startup.cfg scroll down to:

 or_render_eye = 0

 In the above change from 0 to 1 for seeing only one eye's view (though I am unsure which eye). That makes it much easier to work with when you take off your VR headset to fiddle with settings. 

[Dash,Polder]

I'm constantly getting differing LOD changes between left and right eye, it's pretty bad with the miss match.  Not being able to set LOD's out far makes the effects worse, very nauseating and rough on the eyes.  Worst is the forests, the same tree is taller than in one eye which seems half size smaller in the other till it pops and matches, bad part is it keeps popping in and out on one or the other eye, and not that far away, very bad flying near forested hills below their crests.

Might not be so bad if the two sides matched when they popped, I could tolerate that at least.  My eye dominance shifts, never had one fully dominant.

Edited July 2 by Dash,Polder

[YoYo]

2 hours ago, Dash,Polder said:

I'm constantly getting differing LOD changes between left and right eye, it's pretty bad with the miss match.  Not being able to set LOD's out far makes the effects worse, very nauseating and rough on the eyes.  Worst is the forests, the same tree is taller than in one eye which seems half size smaller in the other till it pops and matches, bad part is it keeps popping in and out on one or the other eye, and not that far away, very bad flying near forested hills below their crests.

Might not be so bad if the two sides matched when they popped, I could tolerate that at least.  My eye dominance shifts, never had one fully dominant.

I noticed the same. This applies especially to trees (interestingly, these are not entire areas, but individual trees), but the ground itself can also change between the right and left eye (it bulges out, while in the other it is slightly lower, it takes a moment but is visible).

[Fabry_ASW19]

Disappearing contacts

I only fly VR and I have the same problem that I’ve observed in IL2GB, Other airplanes are only visible up to about 1 mile distance or less (not counting big bombers) this makes my capability of Air to Air Combat extremely low, I can either go spawn camp or wait to be attacked and hope to be really good at defensive, I’ve also noticed it’s really easy to evade even when you fly relatively slow airplanes so I suspect is not just my problem.

I have many hrs of dogfight in many Games from Aces High, IL2GB  to Warthunder(sim) to DCS and while I’m not the best Virtual Pilot I normally do well in ACM.

 

I can still fly Air to Ground and enjoy the game but  I was just hoping that IL2K would use a similar technique as DCS and Warthunder(sim) replacing the distant aircraft model with a visible dot.

I’m also a RL General Aviation and Glider pilot I know for sure I can see a skinny 15m glider at least 2 miles away even in haze and see in which direction is pointing, a Military jet F35 flying 2 miles from me (measured on FLARM) looks scarry big, human eye has a sort of enhance feature for objects of interest or danger, Warthunder and DCS give a more realistic visual, still lacking but better, IL2K Must do better.

 

I consider this a serious bug that need to be fixed for a game where fast jet air combat is the scope.

_______________________________________________

 

My config and setting

 

Intel® i9(8X 3.20GHz + 16X 2.40GHz/36MB L3 Cache)

32GB DDR5-6000MHz

GeForce RTX 5070 Ti - 16GB

 

Running VR Quest3 on Virtual Desktop getting 90 fps at altitude and 48 strafing downtown Seoul

 

Il-2 Korea Settings:

1. • General Graphics
     • Quality: High
     • Screen resolution: same as monitor
     • Full Screen: Disabled
     • Upscaling: Disabled
     • Enable VR HMD: Open XR
   • Visual Effects:
     • Distant Landscape Detail: 4x
     • Horizon Draw Distance: 130km
     • Distant Buildings: Enabled
     • Pilot Body Visibility: Disabled
     • Canopy Reflections: Off
     • Shadows Quality: low
     • Clouds Quality: Normal
     • Grass Quality: Off
     • Mirrors: Complex
   • Advanced Settings:
     • Anti-Aliasing: Off
     • Dynamic Resolution Factor: Disabled
     • Sharpen: Disabled
     • SSAO: Disabled
     • Indirect Lighting: Disabled
     • Terrain Roughness: Off
     • Landscape Filter: Off
     • Lighting HDR: Off
     • Gamma: 0.86
     • 4K Textures: Disabled
     • Cities Optimization: Favor FPS
     • VR Resolution Factor: 100%

[Eldur]

VR seems kinda broken still to me. In both modes (OVR and OXR) the menu is weirdly floating against my head movement. When looking to the right, it moves to the left and the other way round, same with up and down. I also have that x-eyed overlap issue as if there was a software IPD slider that's set way off. Also noticed the menu being like 5-10cm in front of me after recentering which probably causes those issues in the first place, on top of that, if I look at the menu plane from an almost 90° angle, it's at the exact same position on both eyes, basically completely ignoring my actual IPD. In other words, both eyes seem to get the exact same picture, completely lacking any spatial separation. Using Quest 3 via Virtual Desktop. OXR mode bypasses SteamVR as expected and also works without. Also, in both VR modes, recentering via the Quest controller does nothing. I have to press NP5 (or something else with that mapping) instead, which isn't great.