VR experiences IL-2 Korea

[ekoksk]

10 hours ago, pr0x said:

Aslında yukarıda yazdıklarım sizin için tamamen doğru olmayabilir, çünkü 13900k işlemcisinde hiper iş parçacığı yalnızca performans çekirdeklerinde bulunur. Önemli olan, il2series.exe'yi yalnızca performans çekirdeklerinde, diğer her şeyi ise verimlilik çekirdeklerinde çalıştırmanız gerektiğidir.

Does this apply to AMD processors as well?

[Aapje]

1 hour ago, ekoksk said:

Does this apply to AMD processors as well?

AMD doesn't have performance cores, but if you have an X3D-CPU with two CCDs, then the game should run on the CCD with the X3D-cache.

So this is not an issue for the 7800X3D/9800X3D/5800X3D since they only have one CCD, while processors like the 9950X3D and 9900X3D have two.

BTW, this is also why the 9900X3D is not great for gaming since even though it has 12 cores, only 6 of those cores are on the CCD with the X3D cache, which is less than the 8 cores with X3D for the 9800X3D.

Edited August 12 by Aapje

[pr0x]

9 hours ago, ekoksk said:

Does this apply to AMD processors as well?

The pictures I posted is the setup used for an AMD Ryzen 9 9950X3D.

The general principle, whether Intel or AMD, is that the game should run alone on the most powerful cores. The naming convention varies a bit, but the _less powerful_ cores are usually referred to as efficiency cores, meaning they are designed to run smaller tasks like background tasks efficiently rather than max performance. If your CPU has hyper-threading/multi-threading, the amount of cores to select changes. So in my case I have multithreading on all 16 cores - hence why I select 0-15 for the game and 16-31 for everything else. The 13900k only has hyper-threading on some of the cores, so the CPU affinity is probably going to be different.

If your cores are all the same, then the only thing I would do in Process Lasso is to make sure that efficiency mode is always off and to enable performance mode - i.e. set the g flag - on il2series.exe.

Edited August 12 by pr0x

[Aapje]

That's not really accurate. Intel's efficiency cores are lower frequency cores that lack certain somewhat rare instructions. Programs that do have those instructions have to be run on the performance cores.

In contrast, X3D is just an extra feature added to a CCD that is otherwise identical. And at least for the earlier generations of X3D, CCD's without the X3D-cache could be clocked higher. So programs that had (almost) no benefit from the X3D-cache, but did benefit from faster clock speeds, would run faster on the non-X3D CCDs.

[FlightBud]

On 8/11/2026 at 8:00 PM, pr0x said:

Actually, what I wrote above might not be entirely true for you, since the 13900k only has hyper-threading on the performance cores. The key thing is that you need to run il2series.exe on the performance cores only, and everything else on the efficiency cores.

Thanks!

im not sure how to do that. What would I need to change compared to the pictures you posted?

[pr0x]

19 minutes ago, FlightBud said:

Thanks!

im not sure how to do that. What would I need to change compared to the pictures you posted?

I can't really answer that because I don't know what the UI would look like for your CPU. An easier and almost as good optimization would be to simply right-click  il2series.exes, click on "Induce performance mode" and select "Efficiency mode->Always->Off". It should then have the g and the e flags set in the process list.

[Panzerlang]

More messing around with Pimax. I tried the Pimax settings, crop AND wide FOV. Simple crop, 5% both ways (that's the min value on the sliders). Without wide FOV it's a rectangle, with a horrible blue edge. With wide FOV the shape of the crop is nicer and no blue edge. That also gave me 90 to high 80's FPS but, more importantly, very smooth frametimes. NIS on of course. And that's also with the Ultra preset in the game's own settings.

[NuVen]

In the Pimax FOV Fine settings using Right & Left Inner at 7% and Vertical and Horizontal both at 5%, the image has less of the "black bar" ghosting from the opposing eye view and seems to have less eye strain. If you hold two fingers at your nose between your eyes the inner overlap to construct a 3-D image is missing, similar to the effect of having two lenses at a distance from your eyes in the HMD.

Update: Changed the Right & Left Inner to 5%, Horizonal to 7%, and Vertical to 5%. The reported FOV in game is 103. Now the menu and task editor are comfortable to look at. Seems the game software cannot process the full FOV the HMD is capable of. The setting works well in Great Battles, as well. OpenXR toolkit, used for Great Battles, has Horz 113.4, Vert 105.6 and Overlap 88.8 (78%).

Edited August 17 by NuVen

[YoYo]

I've added a fairly comprehensive guide to the tutorials section on the current IL-2 Korea optimization settings for VR. Of course, I'm still heavily relying on the developers' work here, as this is a graphical regression, even before the IL-2 GB era. However, this allowed me to achieve significantly nice results after numerous tests (notice how many options affect performance here!) at the moment (72 frames over Seoul, similar at most airports). I hope this is just a temporary solution and that work is still ongoing at 1CGS.

 

[TheTonester]

Hi all…in my monitor colours are fine but in my headset they look drab, much like DCS used to look which is why i stopped flying it. GB always looked vibrant in comparison..below are the settings im using… can anyone suggest what i should try to brighten it up?

 

[pr0x]

I've discovered an important bug in VectorXR for those of you who use that. It's a bug that causes major fps drop (I'm going from 90 to 50). The bug happens when you use an input device with VectorXR and then unplug that device. I'm not exactly sure what causes the bug, but I wouldn't touch VectorXR at all until they fix this.

For anyone else using VectorXR I'd be interested in seeing if this is reproducible. You can test it as follows:

- Setup a joystick or other peripheral device with VectorXR's pivot feature and make sure it's active.

- Make sure VectorXR's API layer is active (SteamVR->Settings->OpenXR->Manage OpenXR Layers)

- Start the game and a flight

- Plug the device out. You should see a big performance drop.

- Plug the device in. You should be back to normal fps.

For some reason it doesn't seem to happen when your framerate is already low, i.e sub 60 fps.

[YoYo]

Try Gamma 1.0 at the first step, I also saw a post somewhere that it should not exceed 0.75 as well.

[YoYo]

7 minutes ago, pr0x said:

I've discovered an important bug in VectorXR for those of you who use that. It's a bug that causes major fps drop (I'm going from 90 to 50). The bug happens when you use an input device with VectorXR and then unplug that device. I'm not exactly sure what causes the bug, but I wouldn't touch VectorXR at all until they fix this.

For anyone else using VectorXR I'd be interested in seeing if this is reproducible. You can test it as follows:

- Setup a joystick or other peripheral device with VectorXR's pivot feature and make sure it's active.

- Make sure VectorXR's API layer is active (SteamVR->Settings->OpenXR->Manage OpenXR Layers)

- Start the game and a flight

- Plug the device out. You should see a big performance drop.

- Plug the device in. You should be back to normal fps.

For some reason it doesn't seem to happen when your framerate is already low, i.e sub 60 fps.

Okay, but it's a niche bug, and it's not really a VectorXR issue, but rather a cable or motherboard issue. Who disconnects their equipment while gaming? Should I not use VectorXR because of that? It's a bit of a strange idea. I have no complaints, USB works fine, and I'd be quite annoyed if my hardware disconnected spontaneously while gaming.

If this is happening to you, I would look for a problem with the cable, the connection itself, or the motherboard.

[RogwaR]

23 минуты назад, YoYo сказал:

Хорошо, но это узкоспециализированная ошибка, и это не совсем проблема VectorXR, а скорее проблема кабеля или материнской платы. Кто вообще отключает своё оборудование во время игры? Должен ли я не использовать VectorXR из-за этого? Это немного странная мысль. У меня нет претензий, USB работает нормально, и меня бы очень раздражало, если бы моё оборудование самопроизвольно отключалось во время игры.

Если у вас возникла такая проблема, я бы посоветовал проверить кабель, само соединение или материнскую плату.

Друго мой, мыслите шире. Суть проблемы которую описали не в том что устройство отключается, суть в том что игра неадкватно реагирует на отключение устройства. После покупки и нескольких недель мучений у меня сложилось мнение что разработчики просто прикрутили на старый движек Dx12 и преподнесли как "новую разработку" по факту у Кореи те же проблемы что и Ил2 Великие сражения. Те же джиттеры при стабильных 72-80 fps то же рваное изображение на внешних видах когда поворачиваем камеру. Все опять упирается в тот же Delta Time 50hz как и на старом ИЛ и ниче делать судя по всему не будут, все требования к HW намеренно завышены чтобы железо хоть как-нибудь переваривало кривой код. Если честно уже надоело все это, обратился с вопросом о возврате игры, получил отказ. Корея в VR пока не играбельна.

Edited August 17 by RogwaR

[pr0x]

26 minutes ago, YoYo said:

Okay, but it's a niche bug, and it's not really a VectorXR issue, but rather a cable or motherboard issue. Who disconnects their equipment while gaming? Should I not use VectorXR because of that? It's a bit of a strange idea. I have no complaints, USB works fine, and I'd be quite annoyed if my hardware disconnected spontaneously while gaming.

If this is happening to you, I would look for a problem with the cable, the connection itself, or the motherboard.

Huh? Motherboard issue? Where do you get this from?

You think a broken cable can cause fps drops?

11 minutes ago, RogwaR said:

Друго мой, мыслите шире. Суть проблемы которую описали не в том что устройство отключается, суть в том что игра неадкватно реагирует на отключение устройства. После покупки и нескольких недель мучений у меня сложилось мнение что разработчики просто прикрутили на старый движек Dx12 и преподнесли как "новую разработку" по факту у Кореи те же проблемы что и Ил2 Великие сражения. Те же джиттеры при стабильных 72-80 fps то же рваное изображение на внешних видах когда поворачиваем камеру. Все опять упирается в тот же Delta Time 50hz как и на старом ИЛ и ниче делать судя по всему не будут, все требования к HW намеренно завышены чтобы железо хоть как-нибудь переваривало кривой код. Если честно уже надоело все это, обратился с вопросом о возврате игры, получил отказ. Корея в VR пока не играбельна.

This is not a game issue. It's an issue with VectorXR.

This never happens when the VectorXR API layer is not active.

[TheTonester]

1 hour ago, YoYo said:

Try Gamma 1.0 at the first step, I also saw a post somewhere that it should not exceed 0.75 as well.

Thanks bud…will give it a crack

[Aapje]

1 hour ago, pr0x said:

I'm not exactly sure what causes the bug, but I wouldn't touch VectorXR at all until they fix this.

I don't understand this conclusion. This bug only impacts you if you do something that people don't commonly do, and only causes a temporary performance issue. It's not like it breaks your system.

If you have some burning need to disconnect devices during play, then I guess that VectorXR is not for you, but I see no reason not to use it for anyone else.

[YoYo]

1 hour ago, pr0x said:

Huh? Motherboard issue? Where do you get this from?

You think a broken cable can cause fps drops?

Of course, there could be a problem with the motherboard, the connection (pins), or the cable itself, if your hardware is disconnecting while the game is running. Generally, any software will have some symptoms related to this. My joystick once popped out while I was flying in DCS, and I immediately got a CTD the whole simulator. This isn't a software issue, but a symptom of your connection. Nothing should connect or disconnect while playing to USB ports. 

[Hetstaine]

1 hour ago, TheTonester said:

Thanks bud…will give it a crack

Tonester, how about you brighten up your whole outlook and take a d amn shower so you don't stink up this whole place you old mutt! Long time no see flyboy 😘

[pr0x]

1 hour ago, YoYo said:

Of course, there could be a problem with the motherboard, the connection (pins), or the cable itself, if your hardware is disconnecting while the game is running. Generally, any software will have some symptoms related to this. My joystick once popped out while I was flying in DCS, and I immediately got a CTD the whole simulator. This isn't a software issue, but a symptom of your connection. Nothing should connect or disconnect while playing to USB ports. 

It's not an issue of anything disconnecting. It's an issue that happens WHEN a disconnection happens (for whatever reason). Do you understand the difference?

EDIT:

Actually, it's not even that. It's a bug that happens simply because something is in a state of disconnection. You don't have to disconnect anything, it suffices that whatever device you use with VectorXR is disconnected while playing the game.

Edited August 17 by pr0x

[Jaegermeister]

5 hours ago, TheTonester said:

GB always looked vibrant in comparison..below are the settings im using… can anyone suggest what i should try to brighten it up?

I have an HP Reverb G2 and it looks great in game. I run gamma at 1.

Have you tried turning off HDR in your Windows settings? Not in game, in Windows. I have read that this issue has been fixed, but I have not turned it back on to test it.

[Motoadve]

I tried many different settings and performance is no good, and the worst part is that not only bad performance, also quality, low resolution, not even my Varjo Aero at the highest PPD, my 5090 and AMD 9800X3D can make it look good, specially other planes, they look low resolution with jaggies.

[Aapje]

3 hours ago, pr0x said:

Actually, it's not even that. It's a bug that happens simply because something is in a state of disconnection. You don't have to disconnect anything, it suffices that whatever device you use with VectorXR is disconnected while playing the game.

Yes, and that does not just magically happen to everyone.

[pr0x]

35 minutes ago, Aapje said:

Yes, and that does not just magically happen to everyone.

No, it happens to precisely those people who happen to have a disconnected device setup with VectorXR.

[Talisman]

Hello Folks,

I am having a very good VR experience with the Somnium VR1 headset, Visionary Edition, and am loving IL-2 Korea 😍

Is anyone else using the Somnium VR1?  If so, how is it going for you?   

Happy landings,

Talisman

NVIDIA GeForce RTX 5090 32GB

AMD Ryzen 7 9800X3D 8-Core 5.2GHz

64GB RGB DDR5 6000MHz 

Joystick:  MSFFB2
Pedals:  MFG Crosswind
Throttles:  VIRPIL CDT-VMAX & 2 x Saitek Throttle Quadrants
Button Box:  ReaperWare 12-Mini
Haptic Gaming Seat/Chair Pad:  HF8 with SimShaker-Wings
Haptic Earphones:  Corsair HS60
 

Edited August 17 by Talisman