and the cockpit lights when you see the cockpit from outside view of the aircraft. this also happens with mig models

Mc.200 series, close external view, there's a greyish something in the upper front part of the cockpit where usually a mirror is fitted in the Mc.202 series. It should be either removed from the 3D model or enabled as a real mirror, if historically correct.

Screen freeze bug with static runways
 

Together with some other pilots, I have experienced this weird freeze phenomenon, seemingly caused by static runway objects. We have used these objects to form "tunnels" in the valleys for several air racing courses. Whenever one flies close to several of these runways, the screen freezes, all HUD and all text disappears, only the plane icons are left besides the picture itself. Also, as seen in the picture, the cockpit textures also disappear. It happens when you are in cockpit view, or have atleast one other plane in sight in external views.

Here is a screenshot of what happens:
http://i.imgur.com/hymPh.jpg
Screenshot by Tommy-

This must have something to do with the 4.11 patch, since we have used the same racing courses in previous versions without ANY problems like this. If there is a way to solve this, I thank you in advance.

I came across a quirky little bug in the FMB in version 4.11.1. It concerns the 'Waypoint Options' feature.

If you use this feature and set a particular waypoint to 'Patrol', the flight (in the MIS file) might look something like this:

[USN_VF_10A00]
Planes 1
Skill 1
Class air.P_38J
Fuel 100
weapons default
[USN_VF_10A00_Way]
TAKEOFF 39257.95 18077.12 0 0 &0
NORMFLY 34876.31 20568.50 500.00 300.00 &0
TRIGGERS 0 0 0 5 0 0 <-----------------------Patrol Settings!
NORMFLY 24124.97 17979.00 500.00 300.00 &0
NORMFLY 42218.69 11161.08 500.00 300.00 &0
LANDING 40639.26 17279.62 0 0 &0


In the example above, the 'Triggers' line contains the Patrol settings. So far, no problems.

If you load this mission into the FMB and click on the Patrol waypoint and change it to a 'GAttack' waypoint, you will have problems. If you try to reload the mission, you will get a 'Loading Mission' error (see 1st screenshot). That particular flight will not load into the mission. Also, depending on the particular mission, you may lose other flights or even other units, such as vehicles and ships. Below is what the MIS file will look like if this happens:

[USN_VF_10A00]
Planes 1
Skill 1
Class air.P_38J
Fuel 100
weapons default
[USN_VF_10A00_Way]
TAKEOFF 39257.95 18077.12 0 0 &0
NORMFLY 34876.31 20568.50 500.00 300.00 &0
GATTACK_401 31500.13 28009.22 500.00 300.00 &0
TRIGGERS 0 0 0 5 0 0 <--------------------------This line should not be here!!
NORMFLY 24124.97 17979.00 500.00 300.00 &0
NORMFLY 42218.69 11161.08 500.00 300.00 &0
LANDING 40639.26 17279.62 0 0 &0


The bug is that the TRIGGERS line is not deleted when the GATTACK line is added. This leads to the 'LOADING MISSION' error. In any case, this flight will not appear in the mission.

A quick workaround is to manually delete the TRIGGERS line from the MIS file. To prevent this issue from happening in the first place, always change your Patrol waypoints back to normal, SAVE, and then proceed.

*Just a little comment from me; One reason this problem may arise is because the 'Normfly' waypoints and the 'Patrol' waypoints all look the same. I could have sworn we had requested that DT add something to the Patrol waypoints so that the mission builders could tell the difference between the two.

The way it is now, we have to click on every waypoint in order to find out which are Normfly and which are Patrol. Clicking the 'Prev' or 'Next' waypoint buttons does not help because a Patrol waypoint is still displayed as 'Normfly' (see 2nd screenshot). You would need to click on the 'Waypoint Options' tab and then click on each tiny waypoint to find the information (see 3rd screenshot). We really need a graphical clue that a particular waypoint is a Patrol waypoint.....please. Thank you.

Aviar

Here is another little map (Kyushu) bug:

Vehicles cannot completely cross the bridge in grid AO-10. They get stuck on the eastern end of the bridge (see screenshot).

Aviar

+1

I really appreciate all your hard work you are putting into this simulator, but it would be nice if you could look into this issue. We now have several tracks with the same problem and fixing them isn't always easy, as you need several players flying relatively close together for this bug to occur.

Thanks

4.11 to 4.11.1
 

S~
G'day and help,
IL2 clean virginal 4.11 with hotfix, game loads fine.
downloaded and ran 4.11.1 to game. game now doesn't even load, it just sits there. any ideas please ?
thanks
Sharkzz
ps, i have done it 3 times, reinstalled 4.11+ hotfix, run game and loads OK, install 4.11.1 on top and can't even get a % CTD, it just won't start up.
not sure what to do now.

Have you used the same 4.11.1 download for every installation? Sounds like the download might be broken.

I Built a "Operation Vengeance" Mission on the Solomons mid 43 map and find it very difficult to get all flights close on course. If I dont set the waypoint on my leading the other flights just veer off and head directly towards Bougainville instead of heading west after passing Cape Esperance. If I set all the waypoints on my flights waypoints, the the other flights crash partly on the Mountains of Guadalcanal or in best case they are circling above my flight. Until I leave the flight path. Then they just cirkle like lost orientation. I have to command them to the next waypoint but are not able to command them in formation to come with me. Wavetop altitude of 30m leads to crashes. I usually lost up to 8 aircraft on the way towards Treasury Island Worst of all, whenever I head nort and pass Treasury Islansd, Framreate breaks in and I get a crash du to some internal error. Unfortuinately no CTD, I have to kill the application on the hard way. Very unpleasant. Larger Starting delay 20minutes or more sometimes works sometimes does not.

I think there are...three... maybe four problems in there.

Lets start with the waypoints. It sounds like your waypoints are too close and the flights are passing and missing them. That or the Select option is set too early. Use that to target the lead flight only after they have taken off and are on the second or even third waypoint. Use the earlier waypoints to get them slightly setup.

The crash is either because you haven't patched to 4.11.1 or something else. Not sure. Frame rate also sounds like a weird problem. I've flown all over the map and had very few frame issues... there are a couple of slightly heavier areas but it's fairly frame friendly.

Maybe a CPU loading issue?