4.11 General debugging

[CzechTexan]

Originally Posted by Tbolt

I'm sure this problem must have been mentioned before, though I've had a look around and can't see anything but when flying a single mission (original or one built with the full mission builder) or campaign the skin on the players aircraft is whatever skin has been selected in the quick mission builder no matter what has been selected in the mission.

Is there a fix for this or is it a bug waiting to be fixed?

It has always been that way. The skin that shows up is always the previous skin that the player chose for that aircraft, QMB, single, campaign or otherwise. You just need to change it before the mission.

[Tbolt]

Originally Posted by CzechTexan

It has always been that way. The skin that shows up is always the previous skin that the player chose for that aircraft, QMB, single, campaign or otherwise. You just need to change it before the mission.

But shouldn't it be designed to default to whatever skin has been selected during the mission build and then you can change it before the mission if you want something different?

In the early days of IL-2 I guess it didn't matter much when you had only 1 or 2 skins per aircraft but now there's a lot more especially if you added a lot of skins - going through a long list of skins trying to work out which skin is correct to match your flight of aircraft before each mission isn't exactly my idea of fun.

I'm surprised no one has asked for this before. I'll stick it in the requests thread.

[Aviar]

Can someone confirm a bug in the Patrol Type selections? When I select Random, in the missions themselves, the only patrol type I get is a Triangle Patrol with 500m legs. (See screenshot 1)

I would assume that 'Random' would randomize the patrol from the present list...Triangle, Square, Pentagon, Hexagon. (See screenshot 2)

*The waypoint 'legs' are also incorrect. They should be 5km for that particular mission (the default setting).

Aviar

[MicroWave]

Hi Aviar,
The problem might be the random generator. With every mission it starts from the same seed and hence you get the same sequence of numbers. I usually place my plane somewhere on the map and fire my guns. This 'breaks' the sequence.
So, in your example you should fire your guns before you reach the waypoint where random pattern is generated. The pattern will probably be different then.

[IceFire]

Here's a new and obscure one.

When using the Italy Online map the new default skins for the Bf109s painted in Italian specific markings do not appear. They do appear on East and West front maps but not on the Italy Online map... judging from the other aircraft it is set up as a MTO map but these skins do not correspond with the MTO. I should have caught this one earlier.

[Aviar]

Originally Posted by MicroWave

Hi Aviar,
The problem might be the random generator. With every mission it starts from the same seed and hence you get the same sequence of numbers. I usually place my plane somewhere on the map and fire my guns. This 'breaks' the sequence.
So, in your example you should fire your guns before you reach the waypoint where random pattern is generated. The pattern will probably be different then.

So what you are saying is 'DO NOT USE THE RANDOM SETTING FOR AN AI FLIGHT'...

Thankfully, I only have a couple of missions that I have to go back and correct. Thanks.

Aviar

[MicroWave]

Originally Posted by Aviar

So what you are saying is 'DO NOT USE THE RANDOM SETTING FOR AN AI FLIGHT'...

Thankfully, I only have a couple of missions that I have to go back and correct. Thanks.

Aviar

It's perfectly fine for AI flights to have random pattern. You just need some player input to break the random sequence. I fire the guns, because I know that this does the trick; maybe some other input also does the trick.
The only thing is that it would be hard to see what pattern was chosen for AI flight, cause you can't see it on the minimap. But player doesn't need to be part of the AI flight.

[Aviar]

I wanted to add another thought to Patrol waypoints. It appears that the 'Radio Silence' setting does not affect the 'added' Patrol waypoints.

As you know, when an AI flight reaches a waypoint, they will call out their altitude and heading. Personally, I use the Radio Silence setting for many AI flight waypoints so these many radio messages do not clutter up the mission.

However, this does not appear to work on Patrol waypoints. It still works on the 'original' waypoint but once the flight starts it's Patrol, it starts calling out each waypoint. (Depending on the settings, this could be a lot of waypoints.)

If you have 4 or 5 AI flights flying Patrol, that could be a LOT of radio calls. Is there any way this issue might be addressed?

Aviar