Task editor, career, and single missions

[302_Miro]

If we get off the machine and get back behind the controls, the markings and additional equipment such as aiming devices are reset.

 

 

[YoYo]

A rather important bug in the game. Targets or objects added by the player won't appear if you fly over them. This also applies to destroyed objects, as well as smoke and fires caused by an attack. How can I replicate this? Add some objects, trucks, etc., attack, set them on fire, or destroy them. Fly over them and look in their direction. The objects disappear. The AAA that was just shooting at you continues firing, but the object itself is invisible, so we're left with empty ground. The smoke that was just there has disappeared and is starting to reappear, and the fire, the same. This is clearly visible by pressing F3 or Ctrl+F3 (flyby key). Even if you turn the plane around, the objects and effects are briefly invisible; they only reappear after a moment, and everything starts over again, and this happens every time you launch an airstrike and attack the same group of targets. This is clearly a bug. There's nothing like this in any simulator I know of, not even IL-2 BoX, so it's a step backward. Please fix the disappearing objects and effects. More about this topic:

Edited July 10 by YoYo

[Juri_JS]

At the moment Command:Flare isn't working for most vehicles and apparently none of the guns. It seems to be only available for vehicles like jeeps.

[plepew]

Graphics bug -  The F-84 tire animation when taxiing is broken.  The treads (flat part of all three gear) don't rotate when the aircraft is taxiing.  This is unique to the F-84.  Other aircraft don't have this issue.

[Juri_JS]

The "city_firesmall_loop" effect isn't working and is causing this error:

[Elf]

'legacy problem' from IL-2 GreatBattles: tailwheel doesn't (visually) align with terrain. At bituminous/concrete taxiways/runways it's visually ok, but at dirt airfields - no... 

[Juri_JS]

Please check the white flare when using Command:Flare. It is loosing it's colour/light effect shortly after firing and only the smoke effect remain.

[YoYo]

Here's an example related to my post above. We have two shots. One is from F3 key, the other from F2. In this case, it doesn't apply to LOD, because after a moment, objects appeared where they weren't.

F3 view, no objects (targets), they appeared after some time, as if it depended on the time and angle:

[mfrunner]

Some other missing textures

[MiGCap]

I flew the "Combat Mission" exam with the F-80C and killed 28 targets (see screenshot). Flew home and landed safely at the home base, but the exam was not passed despite I killed three more targets than necessary.

What is wrong with these exams?

 

 

[YoYo]

Further to my post above, here's a continuation showing disappearing objects (including destroyed ones). This time, without the F3 key, but from the cockpit. You can see the destroyed objects outside, but when you look in the mirror, they're not visible inside the cockpit (craters only).

[MiGCap]

Don't know if that helps, but here ist the flight log data (as zip because mlg. file type is not allowed to attach):

 

missionReport(2026-07-13_02-53-38).zip

[Mark_Krieger]

Animation of F-80C formation lights switches doesn't work correctly. Both switches (fuselage light and tail light) are on when either or both lights are on. They should move independently. 

Edited July 15 by Mark_Krieger

[Xtremist]

The parked aircrafts and vehicles near the runway pop in from very close distance, maybe 1 mile. Max graphics settings... 

[Juri_JS]

Static trucks can't be set to damaged in the mission editor, like it can be done with static planes.

Edited July 16 by Juri_JS

[FuriousMeow]

Forest disappears around Kuandian airport. Its especially noticeable if you approach the North side of the runway from the East side and watch the forest on the East side of the runway. I took screenshots with HDR on which have a greyscale overlay appearance but still can see the loss of the trees. I went back with HDR off and took a few, this shows the trees at another location appearing and disappearing.

T

[Valis]

The MiG-15 has a very faint exhaust trail - but only on LOW and BALANCED graphics settings.

On HIGH and ULTRA setting the exhaust trail is absent.

First image on LOW. Second image on BALANCED.

Edited July 19 by Valis

[FuriousMeow]

Lots of aircraft are missing the opposite side of the outer skin textures. Yak9P, La11, F84E so far I've noticed can see through to the world when panels are shot off - fuselage particularly noticeable. I have screenshots, greyed or washed out though due to HDR, that I'll try to upload tomorrow. 

Edited July 20 by FuriousMeow

[Jade_Monkey]

Maybe this is user error, but the vehicles with trailer options in the loadouts do not show trailers in the mission.

Example here with Dodge C52 but same thing with other trucks.

 

These trailers seem to work fine.

 

[AEthelraedUnraed]

Issue: Wrong identification markings on the F-80.

Description: The F-80 has got the serial number system backwards. In the attached screenshot, I have assigned tail number FT-9840. Using the numbering system in use at the time, that means the tail should show the entire numeric code "9840", while the large-font "Buzz Code" should only show the last three digits "840". This can be seen in the attached Korean War era photograph, where tail number 9708 is assigned Buzz Code FT-708.

Current behaviour: The large "Buzz Code" on the fuselage shows FT-9840; the tail shows 984.

Expected behaviour: The Buzz Code should show FT-840, the tail 9840

[Dash,Polder]

F-51 the canopy rolls back too far on the rail, and the mirror clips right through the armored seat rest and plate and into a plate support rod.

[Mark_Krieger]

Trying to start a career with the F-51D. Group doesn't taxi to the runway even when I give the order nor following me. They start engine after I start engine, but not always and only 3 planes of 12 did a bit of taxi when I gave the order to take off, but without entering the runway.

[LukeFF]

19 hours ago, AEthelraedUnraed said:

Issue: Wrong identification markings on the F-80.

Description: The F-80 has got the serial number system backwards. In the attached screenshot, I have assigned tail number FT-9840. Using the numbering system in use at the time, that means the tail should show the entire numeric code "9840", while the large-font "Buzz Code" should only show the last three digits "840". This can be seen in the attached Korean War era photograph, where tail number 9708 is assigned Buzz Code FT-708.

Current behaviour: The large "Buzz Code" on the fuselage shows FT-9840; the tail shows 984.

Expected behaviour: The Buzz Code should show FT-840, the tail 9840

The coding for buzz numbers is for what's shown on the fuselage, which was always the last three digits of its serial number. The fourth slot is for when two or more planes had the same last three digits in their serial number (most often seen on F-84s).  I.e., there wouldn't ever be an F-80 with the buzz number FT-9840. That first number on the tail in your screenshot is from the aircraft's production number, which looks like a 9, i.e., a serial number of 49708 (the first two digits were from the production year, in this case 1949).

[LukeFF]

1 hour ago, Mark_Krieger said:

Trying to start a career with the F-51D. Group doesn't taxi to the runway even when I give the order nor following me. They start engine after I start engine, but not always and only 3 planes of 12 did a bit of taxi when I gave the order to take off, but without entering the runway.

 

[AEthelraedUnraed]

2 hours ago, LukeFF said:

The coding for buzz numbers is for what's shown on the fuselage, which was always the last three digits of its serial number. The fourth slot is for when two or more planes had the same last three digits in their serial number (most often seen on F-84s).  I.e., there wouldn't ever be an F-80 with the buzz number FT-9840. That first number on the tail in your screenshot is from the aircraft's production number, which looks like a 9, i.e., a serial number of 49708 (the first two digits were from the production year, in this case 1949).

That's exactly my point 🙂 The serial number would have been (4)9708 of which the 4 wasn't always shown. That's what it should show on the tail. The fuselage, as you say, should only display the last three digits, so that's 708.

Right now in IL2:K, the fuselage shows the "full" number 9708 while the tail shows the wrongly abbreviated version 970. Neither is correct.

Edited July 21 by AEthelraedUnraed