VR experiences IL-2 Korea

[brickcommander]

13 minutes ago, pocketchange said:

Just a heads up - this was fixed for me when I recalibrated my VR space to seat only in SteamVR. It is a little disappointing that apparently I'll have to do this every time I switch, but this and a 115% world scale makes an insane difference for cockpit immersion.

I also played around with the graphics settings a lot today, and on my bigscreen beyond 2 + 9070XT setup the only options that actually affect GPU performance seem to be the general presets (anything other than low at native resolution ends up with horrible frametimes, ~19ms) and VR Resolution Scale. I'm at 75% Resoltution Scale on the Balanced Preset now and actually get the smooth 75Hz I need.

As for Upscaling - it flat out doesn't work, but I've also never seen it used in a VR Game? Wouldn't it look quite bad, as any temporal effect would with the rapid head movements VR Displays do? If it does work it would be a great fix for full release since resolution really is the main performance drain on GPU.

I am not on steam vr so I am not sure if i have a similar solution via virtual desktop. Will check when i get home.

 

I will say that DLSS upscaling is actually working quite well for me. If i run a mission in the same graphics settings, my gpu usage goes from 100 with frame rate drops to about 80 percent with dlss quality and a smooth 72 fps. And it actually looks great.

 

After a lot of tweaking, i had to lower settings and use dlss to get good performance IN vR, but it looks a lot better than GB on max even with balanced preset and very medium settings

[pocketchange]

10 minutes ago, brickcommander said:

I will say that DLSS upscaling is actually working quite well for me. If i run a mission in the same graphics settings, my gpu usage goes from 100 with frame rate drops to about 80 percent with dlss quality and a smooth 72 fps. And it actually looks great.

Damn, then I'm jealous! FSR seems to not work at all, at least theres no visual or performance difference for me. But I agree it looks far better than GB regardless.

[Husar]

I can fly on empty map on 72 fps machet Quest 3 Hz with occasionally drops below 72 (cites). But graphics do look worse than in a Il 2 GB to be playable .... core graphics engine is very outdated (losts of issues) and unpolished and DLSS does't help to much - just make somhowe playable

Looks like new tech doesn't feet this game engine well in present game stage - constant issues with textures clarity, objects low draw distance, load popup in short distance, terrain geometry intrusive changes, shadows flickering ... lots of issues to fix until August. 

Edited yesterday at 11:38 AM by Husar

[McTroll]

On 6/25/2026 at 9:31 PM, nrosko said:

Very disappointing performance & experience in vr for me. 

I should of known better, all the warning signs were there when i watched the youtube previews & I could see it was a slideshow.  

I have a quest 3 & playing through VD

RTX5090 ryzen9 7950x3D 64gb ram

Anything from 20fps -72fps  The quest refresh is 72 so that is my target. Unfortunately it was dropping well below that. Suffers with the same issue as great battles where the fps drops as soon as you get to other aircraft but its now way worse. If i use dlss it helps a bit but still really poor performance & it looks really bad. 

Other issues, ground textures really slow to load in & it often looked like minecraft. Pilot position is way off, i pressed 5 to reset the position but it didn't help.

Menu is vomit inducing its like its zoomed in camera & moves with your head. 

Lots of artifacts flashes or light i couldn't get rid of. 

Some of these issues will be fixed but I find it hard to believe that at this stage they will find a significant boost in performance in time for release & quite frankly ever. Surely by now they would be 90% there with performance its not a 0.1 alpha release?  

 

   

I can get 72 fps with a similar setup and high graphics. Need to use DLSS though , which to b honest is my goto now. VD on GOD Mode, no spacewarp.

[=ILS=_Abu_27]

On 2026/6/26 at AM5点28分, Merlins51 said:

菜单随着你的头部移动，感觉很糟糕。

但更糟的是，当我接近驾驶舱极限时，驾驶舱会随着我的头一起晃动。如果我向前倾、向后倾斜过多，或者向左或向右倾斜，整个驾驶舱视角都会跟着我一起推（而不是我直接穿过模型）。极度破坏沉浸感，令人恶心。我甚至无法往驾驶舱低头看，整个地板都会被移开。说实话，我真不敢想象谁会觉得这是个好主意。编辑：显然可以通过在设置中关闭“限制VR视角”来关闭这个功能。

我有一台9800x3d、5080、64GB的显示器，用有线连接玩Quest 3。开箱即用时，世界纹理毫无特征且模糊。我得调整一些设置，看看别人的评论，看看能不能改进。

这个问题其实很困扰人，让人极度出戏，可惜很多人只是简单的告诉你关掉vr限制视角就可以了，却不知道在多人服务器中都是强制vr限制，非常不舒服。

[=ILS=_Abu_27]

现在 我勉强把画面调到和il2gb一个水准的设置，但是帧数需要降到72帧了。 vr分辨率还是尽量保持了将近95%。 座舱画面是非常好的，但是座舱外的画面总是不尽人意，不过毕竟是先行版，可以等待调整。 可是我遇见的最大的问题是我的 XRNS 失效了，无论是是用xr版本 还是切换到vr版本，都是无效了，很头疼，不知道哪位达人可以帮我解决这个问题呢，它就偶尔好了一次。 

[Jade_Monkey]

2 hours ago, AEthelraedUnraed said:

I said "knows", not "can know" 🙂. Even without DirectX, there's always decompilation so unless the code is heavily obfuscated or something, it's never impossible to figure out what happens. But AFAIK no-one has done so, so my point stands.

I hope you're not suggesting that DLCs should be something for the rich?

According to the latest Navigraph Survey, around 10% of players primarily fly VR (this is geared towards flight sims in general, but it's probably the best stats we've got). Based on the Steam Hardware & Software Survey, a maximum of 10.61% of all headsets feature eye-tracking (every ambiguity counted as eye-tracking - in reality it's likely *much* less). That means that perhaps 1% of all IL2 users would benefit from this. Even if this 1% are all going to buy all upcoming DLCs (which they won't), even if they'd all stop buying DLCs until foveated rendering is implemented (which they wouldn't), I doubt this "percentage that has the money to buy more DLC in the future" has that much of an influence on 1CGS's total revenue to make it worth the investment at this point in time.

That survey is not specific for flight sims. That percentage is a lot higher for the relevant population of simmers.

[wuVR]

I mean, there´s a Reason they did not  fully Release, and made it "Early Access" first.
Now we know why, just lots of issues and for sure some Fix-Patches are needed.
All we can do now, is document feedback as best as possible.

[Flyingjock23]

I am having an unplayable experience with the above system in Black Thursday mission, disabled OpenXR and still negligable improvement.

have tried numerous tweaks and reductions but 22FPS when inside bomber formation.

in general the landscape and graphics lack sharpness for me. 

in fairness it was running better in OpenXR but as advised there are compatibility issues there

Just to add the above issues are for VR with quest 3 I run Great Battles with most settings on full including reflections etc and get a more or less stable 120FPS.

Running Korea outside of VR is very good on my system FPS around 110 FPS in the air 80 FPS in the ground and heavy dogfighting inside bomber formation 55FPS

 

 

Edited 5 hours ago by Flyingjock23
Just more information

[Cellinsky]

When I try to use the systems menue in vr, I get some sort of parameters screen, but not the menue with the new manipulators. Isnt this supported in vr yet?

[Jade_Monkey]

23 minutes ago, Cellinsky said:

When I try to use the systems menue in vr, I get some sort of parameters screen, but not the menue with the new manipulators. Isnt this supported in vr yet?

The multi-menu works for me in VR. It's actually one of my favorite additions.

[AEthelraedUnraed]

1 hour ago, Jade_Monkey said:

That survey is not specific for flight sims. That percentage is a lot higher for the relevant population of simmers.

How do you know that? The Navigraph survey doesn't provide info on VR hardware.

[MoleUK]

3 hours ago, pocketchange said:

Just a heads up - this was fixed for me when I recalibrated my VR space to seat only in SteamVR. It is a little disappointing that apparently I'll have to do this every time I switch, but this and a 115% world scale makes an insane difference for cockpit immersion.

I also played around with the graphics settings a lot today, and on my bigscreen beyond 2 + 9070XT setup the only options that actually affect GPU performance seem to be the general presets (anything other than low at native resolution ends up with horrible frametimes, ~19ms) and VR Resolution Scale. I'm at 75% Resoltution Scale on the Balanced Preset now and actually get the smooth 75Hz I need.

As for Upscaling - it flat out doesn't work, but I've also never seen it used in a VR Game? Wouldn't it look quite bad, as any temporal effect would with the rapid head movements VR Displays do? If it does work it would be a great fix for full release since resolution really is the main performance drain on GPU.

DLAA/DLSS can have drawbacks in VR re: ghosting/smear. It depends what your tolerance is, and it tends not to be as bad on the new presets (L and M) and at higher resolutions. DLAA tends not to have as much ghosting/smear as DLSS generally.

DLAA can work extremely well in VR at reducing aliasing shimmer. Far better than MSAA as that tends not to work very well in games that are deferred render. That's the tradeoff.

But like you it does not appear to work at all for me currently, I still haven't had the time to properly tinker yet though. Interesting to hear not much impact other than on the presets, I will try that when I get the time.

[Slo-Mo]

I made an basic .cmd file that allows me to easily switch btw Flatscreen and VR setting as well as diff key bindings for zoom. You ofc need to set your own paths, fix with the startup.cfg and general.actions files and then create a shortcut to the .cmd file. Tought I share it for those of you whom have both TrackIR and VR as myself and often switch btw them.

Note 1: download the .txt file and rename it with .cmd extension

Note 2: for some reason launching the IL2Series.exe (option 3) does not work, crashes at launch. When using Option 4 "Start IL-2 Launcher" and pressing the Play button it works fine.

 

Korea IL-2 Start menu.txt

Edited 22 hours ago by Slo-Mo

[YoYo]

1 hour ago, MoleUK said:

DLAA/DLSS can have drawbacks in VR re: ghosting/smear. It depends what your tolerance is, and it tends not to be as bad on the new presets (L and M) and at higher resolutions. DLAA tends not to have as much ghosting/smear as DLSS generally.

DLAA can work extremely well in VR at reducing aliasing shimmer. Far better than MSAA as that tends not to work very well in games that are deferred render. That's the tradeoff.

But like you it does not appear to work at all for me currently, I still haven't had the time to properly tinker yet though. Interesting to hear not much impact other than on the presets, I will try that when I get the time.

That's right. DLSS in flight simulators isn't a solution, even for computers and graphics cards released in 2020 and before. Since then, we've had two generations of cards. DLSS causes some blurring and ghosting, even with the latest M and Quality presets. Personally, I only use DLSS in MSFS, where there's a smooth flight experience for views and procedures. In IL-2 Korea, the image must be razor-sharp; it's dynamic flight and combat, where every detail counts, which can be easily missed with DLSS or FSR (for example, a wriggle formation on the horizon). For me, flying with DLSS is absolutely not a solution in a combat simulator. The game needs optimization, which the developers should devote their time to now, and that's all there is to it, so that you can use MSAAx2 over cities and during air combat without a FPS drop.

[Blitzen]

I'm getting "bumpy" performance and lower FPS in cockpit view and if I am reding correctly others are as well.I have triedsome of the solutions here but is there one that works ir are we all waiting for a hot fix?

[YoYo]

6 minutes ago, Blitzen said:

I'm getting "bumpy" performance and lower FPS in cockpit view and if I am reding correctly others are as well.I have triedsome of the solutions here but is there one that works ir are we all waiting for a hot fix?

Oh yes! 👍

The plus is that we will have good performance in VR above the water. 

Edited 21 hours ago by YoYo

[Galraak]

If only there was just the problem B29 mission... I just did the last F80 review mission, and it's CHAOTIC again... 20/30 FPS when you approach ground targets, it's just ridiculous with a 5090. Nothing has been done to optimize the game, they will have a lot of work.

[brickcommander]

16 minutes ago, Galraak said:

If only there was just the problem B29 mission... I just did the last F80 review mission, and it's CHAOTIC again... 20/30 FPS when you approach ground targets, it's just ridiculous with a 5090. Nothing has been done to optimize the game, they will have a lot of work.

I am pretty sure the 5090 isn't the problem. These scenarios are CPU bound and no graphics card is going to solve that issue.

 

 

[Blitzen]

22 minutes ago, brickcommander said:

I am pretty sure the 5090 isn't the problem. These scenarios are CPU bound and no graphics card is going to solve that issue.

 

 

Me? 30's witha 4080 card,so this is not encouraging news my friend...

Edited 20 hours ago by Blitzen

[TCW_Brzi_Joe]

I ran some graphics benchmarks today with Korea on my PC (Intel i5-14600, 32GB RAM, RTX 4090, Pimax Crystal at 4312 × 5100 native resolution).

To keep the test consistent, I used the exact same plane, scenery (avoiding cities), altitude (1 km), weather, and time of day:

---

DLSS Ultra Performance: 62 fps
DLSS Performance: 50 fps
DLSS Balanced: 44 fps
DLSS Quality: 38 fps

FSR Ultra Performance: 66 fps
FSR Performance: 59 fps
FSR Balanced: 53 fps
FSR Quality: 45 fps

Upscaling Disabled: 35 fps

---

Aggressive upscaling modes (DLSS/FSR Ultra Performance) give higher framerates but look terrible. Lower upscaling improves the picture quality, but the low FPS causes headaches. In its current state, it is simply unplayable.

For comparison, IL-2 Sturmovik: Great Battles (BOS) runs at 75–80 fps using the exact same hardware settings with no upscaling enabled.

 

Possible solutions:

1. Better optimization of the Korea engine.
2. Proper implementation of Quad Views (which works well even for VR headsets without eye tracking via "Fixed Foveated Rendering").
3. OpenXR Toolkit support (e.g., using vertical FOV reduction, CAS sharpening, etc.).

[=ILS=_Abu_27]

From my testing, a few key points are to pick the balanced preset for visuals instead of VR optimization. Set anti-aliasing to FXAA at 4x–8x, and enable SSAO.

 

I can now hold a steady 72 FPS with graphics cranked to 95% on the Pimax Dream Air, hitting a sweet spot that balances visual quality and smoothness. I’ve attached a clip from my recent test that showcases the visuals and fluidity.

 

I really enjoy the new game build and look forward to further optimizations — I can’t go back to the BOS version anymore 🙂

【Korea IL2 阿布vs克鲁平在半岛上空的激战-哔哩哔哩】 https://b23.tv/SsHLxms

[Avimimus]

A quick response to a couple of posts here:

1. At this point in time, it is official policy that machine translation has become good enough (and easily accessible enough) that we don't need to have multiple forums for different languages (except for the off-topic forums).

2. You can choose to translate text and respond to it or just ignore messages if they are not in your preferred language. But please be polite and courteous to each other regardless of your languages or nationalities.

[Galraak]

1 hour ago, brickcommander said:

I am pretty sure the 5090 isn't the problem. These scenarios are CPU bound and no graphics card is going to solve that issue.

 

 

I have a 5090 with 7800X3D and 64GB DDR5. It's not normal to have such terrible performance with average settings...

[brickcommander]

1 minute ago, Galraak said:

I have a 5090 with 7800X3D and 64GB DDR5. It's not normal to have such terrible performance with average settings...

If it is cpu bound, only a few settings actually help. Performance should be mostly the same in dense scenarios regardless of graphics settings because the cpu isnt able to prepare the frames fast enough for the gpu to render them.

 

What is needed is cpu optimization, and I am confident the team knows that and is working on it already. I am assuming that is one of the main reasons that the release was delayed.

Snipermanmax said that there will be a update later this week let's see what it does.