Virtual Reality

[LukeFF]

Please post any Virtual Reality issues here. Please note this topic is strictly for bug reports. Any off-topic banter will be removed at our discretion. Thank you!

[TheNappingMan]

When using OpenXR, I get black textures everywhere.  But only in the headset, the 2D mirror on my monitor is fine.  It's also fine if I pause the game.  Sorry for the blurry cell phone photos, but it's the only way to get an example.

 

Also, ironically, when using the OpenXR toolkit (which we're not supposed to use) it works fine.  But it does cause CTDs.  Also strangely, I've got OpenComposite running, so if I choose OpenVR...it uses OpenXR...and works.  

Core i9-14900K

3090RTX

96gb RAM

Win 10

Latest Nvidia drivers (610.62)

Reverb G2 (V2)

 

[higgins]

When in vr using open vr there is very little head movement possible without the plane/whole view moving as well. Others have reported the same issue. Cockpit dials could be clearer in vr too

4090, 7 9800X 3D 32 ram pimax crystal 

Edited Friday at 07:09 PM by higgins

[OPS_Lipas]

Hi there. Personally, I’ve noticed better performance and more stable frame rates with the OpenXT toolkit, 
even though it causes the game to crash. So, there’s definitely something to it.

Edited Friday at 07:12 PM by OPS_Lipas

[YoYo]

1/ Unfortunately, in VR, the default cockpits are too small. The proportions are clearly fine, but there's a problem with the cockpits being too small. The solution is IPD + and -, which works a bit like World Scale and works, for example, in IL-2 "Battles of.." without issue. Here, we also have the IPD + and - option (as in the screenshot), but it doesn't work (OpenXR). There's absolutely no difference (+30 to -30). I also tested with OpenXR Toolkit, and there we have the + and - option, and it works (113% is perfect for me).

Please verify IPD + and - in IL-2 Korea and fix it, thank you.

2/ Nighttime lights (objects on the map) are rendered strongly in one eye. The other is only 10-20% of that value. The screenshot below shows what the same city looks like at night at the same time (left/right eye). Unfortunately, this creates a disastrous impression, as bright objects are visible only in one eye.

Edited Saturday at 05:28 PM by YoYo

[YoYo]

The menu isn't in one place, but moves with the user's head (right and left). This wasn't a problem in the IL-2 BoX, and it worked fine there – the menu was always in one place regardless of whether the user was moving or tilting their head. The menu also seems too close to the user (the same goes for the map menu, etc.).

Edited Saturday at 05:52 AM by YoYo

[eszyman]

2 minutes ago, YoYo said:

The menu isn't in one place, but moves with the user's head (right and left). This wasn't a problem in the IL-2 BoX, and it worked fine there – the menu was always in one place regardless of whether the user was moving or tilting their head. The menu also seems too close to the user (the same goes for the map menu, etc.).

This "effect" also give me a bit of vertigo, I don't care for it one bit.  Interface is cool though.

[YoYo]

The game requires significant and crucial VR optimization. This applies especially to cities, but also to AI bomber formations (the next step).

Regarding cities, I believe there may be a problem with the LOD of buildings and optimization of building clusters. This means that flying over a city triggers a slideshow. Personally, at such moments, my frame rate drops by more than half (from 72 to 40-30 FPS), making the simulator unplayable in these areas. I'm not even talking about air combat or bombing, just the buildings themselves. There's no such problem in IL-2 BoX; even large European cities (Paris) generate maximum FPS (72 for me). In IL-2 Korea, even medium-sized villages cause a significant FPS drop. Compared to other simulators like MSFS or DCS, large cities deliver maximum FPS for me. In DCS, a city like London (from WW2) gives me a constant 72 FPS, even though it's much more detailed; Dubai and Cairo, Las vegas have the same max FPS. So something is seriously wrong with the optimization in IL-2 Korea of cities and larger villages.

Honestly, I can't even imagine flying multiplayer over cities in IL-2 Korea, because it would be simply unplayable.

I urge you to bring the optimization up to IL-2 BoX FPS standards as one of the top priorities for the 1CGS team.

There's a lot of complaining about the optimization in IL-2 Korea, and practically everyone agrees. Here are some examples of places where frame rates are cut in half. Let's take Seoul as a benchmark. It's practically impossible to fly here, let alone use the airport:

I should add that I'm using an RTX 5090, an i7 13900 CPU, and 64 RAM. So everything should run flawlessly on that hardware. Since I'm seeing drops of 50% or more in VR, what about on other hardware (and I'm using medium settings in IL-2 Korea)? Releasing a game where the minimum specs are essentially an RTX 5090 for VR, and it's still very far from ideal, isn't a good idea so pretty please - fix optimalizations as soon as possible. Thanks!

Edited Saturday at 05:46 PM by YoYo

[BlueLuna]

I occasionally encounter continuous strange serious stutter which feels like the window is not being focused on. This stutter only happens in flight, and only when using VR. I found this quite similar with what I met in old IL-2GB when i type something with Chinese input method in game. But in IL-2GB, I can simply change input method in game to English to avoid this happening, while in Korea it doesn't work. Finally, I found that if I fully exit the game, restart the launcher, change input method to English while the launcher window is focused, then start the game again, the stutter might not happen, but still might happen sometimes. I have to try this till it does not happen, and so it won't happen anymore until i restart the game next time.

[Bananimal]

Unable to zoom camera or change FOV in VR. Likewise, IPD does not work in OpenXR but does work in OpenVR.

[wuVR]

My main gripe with VR is that the IPD-offset seems not to go far enough.
In IL-2GB +18% was just fine for me, now even with +30% i´m still seeing double and would need it to go to 40% to have no Crosseye view.

I also experienced this Zoom-issue, no matter if i set a Button or an axis, the curve responds but i still can´t zoom in.
Same goes for openXR and not beeing able to set IPD.

The thing is, my Steam-overlay is crisp and sharp, but as soon as i am in a menue, i get severe doublevision.
Sadly can´t & won´t play like that, since i am getting a headache.

Edited Saturday at 10:27 AM by wuVR

[Mainstay]

I cant play anymore.... 

IPD is not taken from PIMAX Crystal settings and i dont understand why this isnt the setting the game uses. 

Im seeying crosseyed most of the time in the cockpit and i have to perform weird eyemovement to get my crosshair in the HUD to being sharp. 

Please fix this major issue because its unplayable. 

Im using OpenXR because i hate STEAMVR. 

Edited Saturday at 04:14 PM by Mainstay

[Jade_Monkey]

10 hours ago, BlueLuna said:

I occasionally encounter continuous strange serious stutter which feels like the window is not being focused on. This stutter only happens in flight, and only when using VR. I found this quite similar with what I met in old IL-2GB when i type something with Chinese input method in game. But in IL-2GB, I can simply change input method in game to English to avoid this happening, while in Korea it doesn't work. Finally, I found that if I fully exit the game, restart the launcher, change input method to English while the launcher window is focused, then start the game again, the stutter might not happen, but still might happen sometimes. I have to try this till it does not happen, and so it won't happen anymore until i restart the game next time.

I have experienced that too a couple of times, when deep in a dogfight, everything is fine and one second later it goes into slide show mode. The tracking stops working smoothly too.

It feels similar to when you run out of memory except in the system monitor I can see there is still plenty vram and DDR to use, and also the CPU and GPU are not maxed out.

[Dash,Polder]

OK guy's, there's a fix for the small cockpit and it also allows functionality of a necksafer style swing but in a different manner.  The guy that built the app, God bless him just posted it for public consumption on that other unnamed sim's VR forum.  

App is called 'VectorXR Open Beta'.

Guys personal page is up here,

https://diener.tech/products/vectorxr

I've got it fully functional in Korea, it also runs quadviews, but turn it off in Korea not being supported and all.  Fixes the tiny pit problem and gives a very nice stable swing to look back.  You can do two separate settings for your cockpit, stereo and convergence, each on separate sliders.  So there's four distinct things this app can do, three of them in Korea.

Be wary of the controller button feature, it won't work on a controller with more than 32 buttons, and won't tell you.  You'll know its working, it will give you an audible cue in game and see the results if you set it up correctly, than it's working. 

Oh, and it's free.  Be sure to thank this guy.

[YoYo]

⚠️ But this is a bug thread, gentlemen, not a discussion... why post other things here? We also have a thread about VR experiences in General Discussion, and it's worth discussing there (no offense).

Developers simply need to have information about the data and possibly how to replicate it. That's all.

Edited Saturday at 06:27 PM by YoYo

[Flameout]

Several crashes on my Win 11 32GB sys with Intel 9700 and Nvidia 3080T using a quest 3 wired to my PC have led me to decide to just wait for the devs to work on VR, which I have full confidence they will resolve.  Unlike another sim company where I'm still waiting for them to finish the module I paid some $80 4 years ago to which is still in development even today!  I can use the time right now to learn Korea inside and out as best I can on a flat screen. 1C is a proven performer and unlike another sim company not to be named, cares about their customer satisfaction.  I really am delighted to be back in simming again. 

[Picchio]

I can't report personally since I have not pre-ordered, but this is still an issue for some owners of the Bigscreen Beyond 2e (eye-tracking version).

There have been many reports both in the forum and in BSB2's Discord and the issue still has not been resolved.

Goes without saying that it's highly off-putting to see this situation, together with all the other reports. Yes it's EA now but I find it baffling that this kind of stuff didn't come up during the Closed Beta.

Especially since the issue with BSB2e was reported LONG ago in GB.

What's even more disappointing is the COMPLETE lack of acknowledgement by the devs.

I'll wait for the Steam release anyway but I will have to refund the game in case the problem isn't solved. 

Edited Saturday at 07:30 PM by Picchio

[Gunfreak]

If I play Korea for more then a few minutes, if i quit the game. My whole PC is forced a reboot. My last trackfile is corrupted. My settings are set to default. My openxr is changed to open vr when i restart the game. Sound and graphics options are reset. And once i even lost all my binding.

The game runs fine, it only happens when i quit(either in game or alt/tab and right click the icon) 

I have a 5090OC i7 13700k and 128gb ddr5

edit this is the error report I get
 

Quote

 

Faulting application name: IL2Series.exe, version: 1.0.0.1, time stamp: 0x6a3ac6a2
Faulting module name: HMDOXR.dll, version: 0.0.0.0, time stamp: 0x6a3ac5a2
Exception code: 0xc0000005
Fault offset: 0x0000000000002bb3
Faulting process id: 0xE9C
Faulting application start time: 0x1DD0626B8B386DC
Faulting application path: E:\Program Files\IL2Series\Game\bin\game\IL2Series.exe
Faulting module path: E:\Program Files\IL2Series\Game\bin\game\HMDOXR.dll
Report Id: 8632e1c3-b778-4cdd-82b6-9da250a70d1c
Faulting package full name: 
Faulting package-relative application ID: 

 

 

Edited Saturday at 07:54 PM by Gunfreak

[YoYo]

Another thing that looks simply wrong in VR is the sun. From certain angles, you can barely see anything. The image is too bright, an exaggerated bloom or some other effect. It looks more like an atomic bomb explosion than sunlight. I suspect this problem also occurs in 2D, but in VR, where everything is realistic, it's a major problem. You could go blind from this sun.

Modification request

 

Edited Saturday at 09:49 PM by YoYo

[wuVR]

 

14 hours ago, Dash,Polder said:

OK guy's, there's a fix for the small cockpit and it also allows functionality of a necksafer style swing but in a different manner.  The guy that built the app, God bless him just posted it for public consumption on that other unnamed sim's VR forum.  

App is called 'VectorXR Open Beta'.

Guys personal page is up here,

https://diener.tech/products/vectorxr

I've got it fully functional in Korea, it also runs quadviews, but turn it off in Korea not being supported and all.  Fixes the tiny pit problem and gives a very nice stable swing to look back.  You can do two separate settings for your cockpit, stereo and convergence, each on separate sliders.  So there's four distinct things this app can do, three of them in Korea.

Be wary of the controller button feature, it won't work on a controller with more than 32 buttons, and won't tell you.  You'll know its working, it will give you an audible cue in game and see the results if you set it up correctly, than it's working. 

Oh, and it's free.  Be sure to thank this guy.

That´s a neat Programm, and while it solved my crosseye-issue somewhat
this is only a temporary solution because..
My Cockpit is now as big as a Living-room, and my Body looks like i am Bud Spencer on Steroid´s

Edited yesterday at 08:51 AM by wuVR

[Nikita]

I can't get IL2 Korea to work properly in VR with Pimax Crystal Super: I have severe eye strain and cross eyed effect when playing the game. When looking at a distance beyond the cockpit I feel slightly better but the problem doesn't go away fully. I've tried both OpenXR and OpenVR (SteamVR) options, eye strain still there.

Feels like the distance between left and right image is too large. One press RShift + Numpad + in game to adjust IPD seems to make left and right image closer to each other and improve convergence reducing eye strain, but still not enough and it makes the game unplayable in VR. Doing further RShift & Numpad adjustment only makes things worse and brings images further away from each other.

This situation combined with the fact that all other games like DCS, Half Life Alyx, Gorn and Elite Dangerous and many others work absolutely great without any eye strain leads me to believe that the problem is not in the headset but rather in the game engine of IL2. I have the same issue with IL2 Great Battles. Maybe the game engine doesnt properly read IPD settings of the headset? Maybe it doesnt read IPD offsets?

My software:

• Windows 11
• Pimax Play 2.0.1
• Nvidia GeForce Game Ready Driver 610.62.

My hardware:

• Ryzen 9 9900x 
• 64GB RAM
• RTX 5090
• Pimax Crystal Super Ultrawide

What is really the most frustrating part is that I cant find anyone else having this problem: Youtubers advertising Pimax products seem just fine and never bring this up. They cant be pretending to enjoy playing cross eyed, right? I wish IL2 Korea game allowed more detailed settings for IPD in VR such as horizontal and vertical offsets and not just blunt IPD % adjustments. I really want this game to work for me in VR but so far it delivered nothing but frustration.

Can anyone help with this issue?

Edited yesterday at 08:44 AM by Nikita

[wuVR]

Yeah i´m experiencing the same Issue, with the Reverb G2, everything fine until i start Korea, only other Game i had this problem with, was IL-2 GB.
Something about how the 2 images are projected is false, It´s exhausting eyestrain, and even worse on menues.
Until now, we can only somewhat midigate that by sitting in a too huge or too tiny Cockpit.
Because reliefing Crosseye-view with IPD-Offset only will enlarge/shrink the World.

I´ve tried the opencomposite .dll and VectorXR, both work better than Vanilla-openXR, but still not satisfying.
It´s just broken.
We either need a per eye offset or more distortion options for Vertical/Horizontal offset.
 

Edited yesterday at 09:10 AM by wuVR

[Nikita]

4 minutes ago, wuVR said:

Yeah i´m experiencing the same Issue, with the Reverb G2, everything fine until i start Korea, only other Game i had this problem with, was IL-2 GB.
Something about how the 2 images are projected is false, It´s exhausting eyestrain, and even worse on menues.
Until now, we can only somewhat midigate that by sitting in a too huge or too tiny Cockpit.
Because reliefing Crosseye-view with IPD-Offset only will enlarge/shrink the World.

I´ve tried the opencomposite .dll and VectorXR, both work better than Vanilla, but still not satisfying.
It´s just broken.
We either need a per eye offset or more distortion options for Vertical/Horizontal offset.
 

I'm relieved to see I'm not alone experiencing this. I'm almost feeling gaslighted by seeing people just saying it works out of the box when I'm having exactly same issues with both games IL2 GB & Korea while all other games work great.

 

 

Edited yesterday at 09:14 AM by Nikita

[Nikita]

Just tried setting all horizontal and vertical offsets in Pimax Play to zero and it seemed to have improved the convergence slightly but there are two problems with this:

• Still not playable
• All other games became unplayable with zero offset

I really do hope this issue gets attention from the devs.

 

[Dash,Polder]

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.