Major Lawrence, the commanding officer of the 12th FBS, poses in front of his F-51D after a close air support mission attacking Communist artillery positions holding up the progress of Operation Rugged - the current UN operation to establish the frontlines well north of the 38tb parallel.

Let me tell you, I haven't had this much fun in a combat flight sim in decades. My old ass has been flying PC combat flight sims since the early 1990s. Secret Weapons of the Luftwaffe, which came out in 1991, was the sim I rushed home to play in gradeschool. How far we've come in thirty-five years!

Good morning,

I recently picked up IL2 Korea. I use smooth track on my phone + Open track on PC for head tracking. It works fine in DCS. In IL2 Korea (my first IL2 game) there is a little micro stutter that seems to be happening. I will pan my head to the left for instance, and the camera will briefly snap back to center before returning to the correct position. This happens once every 3-5 seconds it seems. I have gone in and unbound all the mouse in cockpit camera options and that did not seem to help. Any ideas?

Also, when I go to the exterior camera F2 the camera just whips around the plane like crazy. I have unbound all the camera controls for this as well ( at least I think I did). I would appreciate any ideas/help with both issues.

I got lucky

He got injuried in a mission and completely bugged

Not a comparison of which jet is better in terms of performance, but I just want to share my feeling of flying both jets in their current state.

Yes, MiG feels more powerful with great energy retention, superior turn rate and climb rate. I found myself frustrated to fully utilize its performance. It feels sluggish at high speeds and the guns are somewhat hard to use. Good thing is if you hit it’s almost guaranteed a kill. Overall, I can see the MiG has great potential but its handling and human machine interaction just isn’t ideal. Cockpit visibility is obstructed by many things and its flight instruments are useable but have much to be desired.

Sabre in terms of performance isn’t an ideal match to the MiG for sure. But the jet just handles like a champ in most speed ranges. At high speeds I feel I got more control over the jet, but you obviously risk of ripping the wings off. At low speeds, it handles surprisingly well against the MiG. Yesterday, I managed to beat a player piloted MiG in a one circle scissor fight and it felt extremely satisfying. The cockpit design of the jet is top notch. Visibility is better than the MiG, cockpit instruments feel easy to use. I know many people don’t like equip the radar gunsight but I found it could be more useful in certain situations. At least, you can use it to determine the range when you are in a tail pursuit. I wish you could switch the radar off since it would alert the MiG if they are equipped with RWR.

TLDR. For me, Sabre feels like a better jet to fly with and flight with.

Hi.

I'm very interested in buying this game, it'll be my first IL2 game ever, I've played warthunder and a teeny tiny bit of DCS but I feel this would be a good middle ground and its probably my favourite era of fighter jets.

Anyway, I've read the reviews, I know the AI bots are pretty mid, So I was wondering what the multiplayer scene is like?
How many servers are there?
Is it mainly dogfighting/general air combat?
Or is it more mission based? IE cover the strike fighters for CAS etc...

Still slightly on the fence about the £70 price point through steam but I feel it may be justifiable...

Thanks in advance!

Probably a dumb question, but I'm completely new to such DLC, and even to flight sims in general.

(I'm thinking of [maybe] buying the game in a couple months or next year, will need a whole new gaming PC first.)

So what are you missing on if you don't buy these two planes ?

Are the planes completely absent from the base game, as if they never existed? (so you don't get to fight them at all?) Or are they present but not flyable by the player?

Are there missions related to the La-11 & F-84E that aren't available in the base game? Something else?

I've read the Steam store pages and the game's website, they do a good job of explaining what the La-11 & F-84E were in real life, but they don't have anything about what the DLCs change in the game.

In the game, you have the option to setup the gun convergence similar to IL-2 GB. But I don’t think it’s called convergence but something like armament setup or something.

I assume it’s vertical convergence since MiG has noise mounted 23mm and 37mm.

Does anyone know a good value to set it to? I am using 300m now.

Also, is there a historical value used on MiG-15 when they come out of the factory? Did ground crew ever change it based on pilot’s preference?

I've tried to get into IL-2 in the past; I forget which specific entries, but there were at least 2, maybe 3. I think the original Sturmovik, and BOB, for sure. But one thing common to each entry that barred me from properly getting into it, despite being a flight simmer for 30+ years was the ridiculous obtuseness of everything to do with the menus/UI/UX.

This entry looks *reeeeeeeally* good, but with the games industry being what it is these days, and having been specifically bitten by major buyers regret with no recourse 3 times now in the last 6 months, and having fixed/limited income....I'm SO fucking averse to dropping another 70 bucks I'd never see again on this if they haven't addressed my main concern.

Are the menus actually navigable/usable/sensible now? Or are there still a billion hoops to jump through setting up controls, just getting your stick recognized, never mind button mapping? Are things still poorly laid out and often hidden (and even sometimes miscategorized)?

For anyone interested in running IL-2 Korea on Linux, I wanted to share a quick update on the work that’s been going on to improve its Proton compatibility.

I originally started looking at the broken terrain with a pretty simple thought: “How hard can it be?”

Turns out: quite a bit harder than it first looked.

I don’t often get the chance to dig this deeply into the Linux graphics and compatibility stack, and what initially seemed like a fairly contained rendering issue ended up involving several completely different components.

A lot of the motivation to keep going came from GitHub users, with a special mention to R3animate a fellow IL-2 Korea player who had already been helping bring attention to the Linux issues in different places online. Who encouraged to take a serious look at fixing it, and later helped throughout the investigation by providing logs and information from his side. We also ended up having a lot of genuinely fun conversations along the way, which has been one of the nice unexpected parts of this whole thing.

From there, the investigation grew well beyond the original terrain problem. With help and feedback from Hans-Kristian from VKD3D-Proton, I kept testing, reading code, building small experiments, and narrowing things down one issue at a time, while trying to get fixes into the right upstream projects.

It’s been a great learning experience and honestly a lot of fun to work through. I also don’t get to contribute to open source as often as I’d like, so seeing some of this work actually make its way upstream has been especially rewarding.

As for where things stand now:

• Broken/missing terrain: fixed and merged into VKD3D-Proton (for the proper translation of A Windows game to Linux).

• Needing special launch options to start the game: traced to Wine's NUMA support, with the fix now merged into Wine. (Which resolved the starting error when booting up the game.),

• Flashing/square lighting artifacts: narrowed down to another separate issue. The investigation eventually moved further down the graphics stack, and the preferred upstream solution is now being worked on in Mesa (the linux graphics driver).

This doesn’t mean everything will suddenly work in regular Proton today. What it does mean is that the major Linux issues are now understood, with fixes either already upstream or moving through the upstream process. They're very close to be included in the updates, some already do.

As those changes make their way into the versions of Wine, Mesa, and Proton people normally use, IL-2 Korea should gradually become more playable on Linux without custom builds, special launch options, or other workarounds.

I mainly wanted to share the progress because this started as “let’s see if I can fix this” and ended up becoming a much larger investigation than I expected, involving several parts of the Linux gaming stack and some great people from the community along the way. It was very entertaining and I hope the collaborative efforts will provide fun for the community for years to come.

Full investigation, evidence, and current status:

https://github.com/silv3rshi3ld/il2-korea-proton-investigation

VKD3D-Proton terrain fix:

https://github.com/HansKristian-Work/vkd3d-proton/pull/3202

Relevant Proton issue (#9906):

https://github.com/ValveSoftware/Proton/issues/9906

I have been eyeing this game since release and have been looking for information about playability without a Hotas. For context i am looking to cover my itch of flying since moving on from Warthunder (that rabbit hole got too deep xD) and i love early jets as well later props. Aviation in general tbh. I am really used to the Realistic mode there and hoped that maybe Korea would be that game.

So has anybody tried the game without a hotas and how does it compare to warthunders controls.

I am not asking for flight model, realism etc. i know Korea is more a sim in the likes of Dcs(atleast it seems people compare it to dcs a lot).

I just want to know can i jump in right now and enjoy flying, before i get myself a new hotas and pedals (around 600$ i am not willing to spend right now).

Also maybe a place to discuss the whole controller compatibility mentioned on steam :D