Slitherine

quote:

ORIGINAL: stilesw

quote:

It's definitely 483, I checked before posting with the intention of just upgrading the scenario and the editor says the scenario is using the latest DB.483.
Baffled as I did the same with a test scenario, added a MiG-29S and every thing worked and it had R-27 TSARH load outs. I will update the scenario again regardless and see if that fixes it.

I believe I've found the problem.

Did some more digging. Went to Akhtubinsk Air Base and selected Su-27S, 968IISAP, 1 Sqn #02. It says that it is loaded with
4x AA-10 Alamo A [R-27R, MR SARH,
2x AA-10 Alamo C [R-27ER, LR SARH],
2x AA-11 Archer [R-73].
It should not do this since that weapon/loadout is no longer an option.

This would have been the original loadout when the scenario was created using DB3K_478. Since then, the TSARH AA-10 replaced the SARH AA-10.

When you try and load the Su-27S in the subsequent databases (i.e. 483) and check the “Show only usable loadouts” box the TSARH weapons do not show up at all but they do show up as possible loads when you look at the aircraft details in the DB viewer.

The problem happens (and I’ve had it happen to me as well during testing) when the scenario contains units that were loaded out in a previous database that did not have the new weapons. When the scenario is upgraded to DB3K_483 it still regards the aircraft as having a no longer existing weapon/loadout.

The solution is to remove all the aircraft (Su-27S) in question and replace them with a new Su-27S. Since the new aircraft and weapon are now both part of the new DB3K_483 it will load and show the correct loadouts.

Ideally, the scenario author would do this but he cannot be faulted because he would not necessarily have known of the change from SARH to TSARH. Probably the easiest solution for you is to delete and recreate all the AA-10 TSARH aircraft. Of course, don't forget to reassign them to their appropriate missions and necessary unit properties.

Hope this is of help,

-Wayne

quote:

I believe I've found the problem. Did some more digging. Went to Akhtubinsk Air Base and selected Su-27S, 968IISAP, 1 Sqn #02. It says that it is loaded with 4x AA-10 Alamo A [R-27R, MR SARH, 2x AA-10 Alamo C [R-27ER, LR SARH], 2x AA-11 Archer [R-73]. It should not do this since that weapon/loadout is no longer an option. This would have been the original loadout when the scenario was created using DB3K_478. Since then, the TSARH AA-10 replaced the SARH AA-10. When you try and load the Su-27S in the subsequent databases (i.e. 483) and check the “Show only usable loadouts” box the TSARH weapons do not show up at all but they do show up as possible loads when you look at the aircraft details in the DB viewer. The problem happens (and I’ve had it happen to me as well during testing) when the scenario contains units that were loaded out in a previous database that did not have the new weapons. When the scenario is upgraded to DB3K_483 it still regards the aircraft as having a no longer existing weapon/loadout. The solution is to remove all the aircraft (Su-27S) in question and replace them with a new Su-27S. Since the new aircraft and weapon are now both part of the new DB3K_483 it will load and show the correct loadouts. Ideally, the scenario author would do this but he cannot be faulted because he would not necessarily have known of the change from SARH to TSARH. Probably the easiest solution for you is to delete and recreate all the AA-10 TSARH aircraft. Of course, don't forget to reassign them to their appropriate missions and necessary unit properties. Hope this is of help, -Wayne

quote:

I am playing the Iron Hand scenario and I am having an issue with the MiG-29S fighters.