2 payload related bugs, and a radar one (ru)

[Gazehound]

1. When playing a mission made with 1.02, on 1.1 - a su-25 tasked with SEAD is changed to a MiG27k. The plane will not show in the payload section of the editor (picture isnt there) and you cannot adjust its blank payload, even after changing the task and the plane.

 

2. (Mulitplayer) Sometimes when creating a new payload for the su25t, the pylon indicator is different to that of the list. So if you select a pylon and press [clear], a different pylon is cleared, and one pylon is not selectable. You must exit to [coalitions] and choose your plane again, and start over with the payload.

 

3. If you have your radar scan zone offset to either side, or pointing up/down, and you switch to NAV mode and back to BVR mode, the indicator at the bottom of the hud indicates an offset scan, but the MFD shows straight ahead/level, until you adjust it slightly and all the indicators jump to the correct position.

 

Apologies if these are known. :icon_wink

[GGTharos]

1. Don't use 1.02 missions. The object IDs have changed.

 

2. strange...this on 1.02 missions or 1.1?

 

3. Nice one, we'll check it in 1.11 and see if we can get it corrected.

[Gazehound]

1. Don't use 1.02 missions. The object IDs have changed.

 

2. strange...this on 1.02 missions or 1.1?

 

3. Nice one, we'll check it in 1.11 and see if we can get it corrected.

 

1. Ok!

2. 1.1, Su25t

3. :D Thanks

[Guest ruggbutt]

I have some missions I made for LMR in 1.02. Can I just go back and edit payloads and such so I don't have to remake them?

[GGTharos]

One way to deal with it which may work is indeed to load those missions up and correct any errors that you see - then, you save the mission and it -should- be ok.

[Alfa]

1. When playing a mission made with 1.02, on 1.1 - a su-25 tasked with SEAD is changed to a MiG27k. The plane will not show in the payload section of the editor (picture isnt there) and you cannot adjust its blank payload, even after changing the task and the plane.

 

This is not due to change of object ID and the problem cannot be fixed. It occurs because anti-radar missiles(and thus the SEAD task) no longer are available for the "baseline" Su-25 in V1.1.

 

What happens is that, in V1.1, the sim will revert to the first aircraft type in the list compatible with the SEAD task - but this being in conflict with what is specified in the mission file.

 

Solution would be to:

 

a). in V1.02, change the aircraft in the mission to a type which is compatible with the SEAD task in V1.1 - e.g. the MiG-27 - and save the change before running it in V1.1.

 

b). re-make the mission from scratch in V1.1 :)

 

Cheers,

- JJ.

[Guest ruggbutt]

I got it. I've been using the "fixed" MeInit file for realistic A10 and Su33 payloads, so I had to change those.

[Gazehound]

This is not due to change of object ID and the problem cannot be fixed. It occurs because anti-radar missiles(and thus the SEAD task) no longer are available for the "baseline" Su-25 in V1.1.

 

What happens is that, in V1.1, the sim will revert to the first aircraft type in the list compatible with the SEAD task - but this being in conflict with what is specified in the mission file.

 

Solution would be to:

 

a). in V1.02, change the aircraft in the mission to a type which is compatible with the SEAD task in V1.1 - e.g. the MiG-27 - and save the change before running it in V1.1.

 

b). re-make the mission from scratch in V1.1 :)

 

Cheers,

- JJ.

Thanks, I suspected that. I recommend 1.02 mission builders to use the su24M for SEAD, not the Su25 :icon_excl