Hello, there are several loadouts named the same.

Several ATA, unguided, guided, etc.

How can I change in the platform editor the names of these loadouts?
To get ATA, ATA-2, ATA-3...?

Is these loadouts related with the AI?

I thought to rename some ATA into Interceptor-4, Interceptor-5...?

Beware! as example:

- ASW and ASW-LR loadouts behave as effective ASW loadouts (patrolling, dropping sonobuoys, and so), but numbered ASW loadouts (ASW-1, ASW-2, etc) are  not effective, the airplane/helicopter simply flights at medium height without dropping sonobuoys! (This is a bug not previously commented).

Also, if you rename loadouts and after share your scenario, as the other players have not the loadouts name changes on his databases, the scenario can be unplayable at some levels (as preformed air patrols, entangled with the loadout names changed).

I understand, but this is not exactly what I mean. I want to rename the loadout itself:

ATA -> ATA

ATA -> ATA-2

ATA -> ATA-3

and I don't know how to do it.

It seems that scenario editor crashes when adding an aircraft with two or more loadouts named the same.

For example, two guided loadouts. I have missed my database work and I have to start again from zero.

On 12/30/2023 at 4:14 AM, jugasa77 said:

It seems that scenario editor crashes when adding an aircraft with two or more loadouts named the same.

For example, two guided loadouts. I have missed my database work and I have to start again from zero.

Hmm, there should not be a crash, can you zip and attach your commondb.res file and let us know which plane to use?  Then I can hopefully see why the SE is crashing and perhaps fix that.

Editing the loadout type names is a little more low level in the PE/Microsoft Access.  You open the lPlatformSubTypes table and edit the Annex 27 (loadouts).

See also 

 in case you accidentally lose the original meaning of the loadout.  No matter what you name Annex 27 ID 49, the game will treat it as ANTIRUN.

15 hours ago, TonyE said:

Hmm, there should not be a crash, can you zip and attach your commondb.res file and let us know which plane to use?  Then I can hopefully see why the SE is crashing and perhaps fix that.

Sorry, but I have deleted the corrupted files to start again. Perhaps it was the same loadout names that crashes the SE. I can remember to have renamed GP and Precis loadouts to guided loadout because I want to add a GP loadout with Mk82 GPB. So I have several guided loadouts. I'm not sure which causes the SE to crash.

15 hours ago, TonyE said:

Editing the loadout type names is a little more low level in the PE/Microsoft Access.  You open the lPlatformSubTypes table and edit the Annex 27 (loadouts).

See also 

 in case you accidentally lose the original meaning of the loadout.  No matter what you name Annex 27 ID 49, the game will treat it as ANTIRUN.

Yeah, but it seems that this chart came at pfData2005.mdb not pfBuild2005.mdb. Thanks.

4 hours ago, jugasa77 said:

Yeah, but it seems that this chart came at pfData2005.mdb not pfBuild2005.mdb. Thanks.

My screenshot is from pfBuild2005.mdb but you are correct, the actual data lives in pfData2005.mdb (indicated by the little blue arrow to the left of the table name.  that arrow means it is a linked table).  That doesn't change the task.  Is there a further question or concern I can address?  We seem to be miscommunicating on this one.

2 hours ago, TonyE said:

My screenshot is from pfBuild2005.mdb but you are correct, the actual data lives in pfData2005.mdb (indicated by the little blue arrow to the left of the table name.  that arrow means it is a linked table).  That doesn't change the task.  Is there a further question or concern I can address?  We seem to be miscommunicating on this one.

I have edited the pfData2005.mdb with new names for loadouts. They remain the same but I have added a -1, -2, -3... to difference different loadouts. Do you want me to share it? It is not a hard work: it's easy.

On 1/3/2024 at 8:07 PM, TonyE said:

Hmm, there should not be a crash, can you zip and attach your commondb.res file and let us know which plane to use?  Then I can hopefully see why the SE is crashing and perhaps fix that.

Hello, I have been editing my database but it has the same problem as before. It seems that new created loadouts cause the SCE to crash.

Take a look at Su-27SM Flanker (loadout 57299), at Su-24M2 (loadout 57300) and at Su-30M2 Flanker (loadouts 57301 and 57302).

I will try to delete these loadout and see what happens. I will tell you what happens.

MyDatabase_2022027-20240105.rar

6 minutes ago, jugasa77 said:

Hello, I have been editing my database but it has the same problem as before. It seems that new created loadouts cause the SCE to crash.

Take a look at Su-27SM Flanker (loadout 57299), at Su-24M2 (loadout 57300) and at Su-30M2 Flanker (loadouts 57301 and 57302).

I will try to delete these loadout and see what happens. I will tell you what happens.

MyDatabase_2022027-20240105.rar 15.41 MB · 0 downloads

I have deleted loadout 57299 and start SE. It is the same problem.

I have tried adding some unedited Su-27S Flanker and it is the same problem.

I don't know what happens.

52 minutes ago, jugasa77 said:

I have deleted loadout 57299 and start SE. It is the same problem.

I have tried adding some unedited Su-27S Flanker and it is the same problem.

I don't know what happens.

The message said that there is an error on loadout 56898, which is the first loadout of Su-27SM Flanker (intercept).

2 hours ago, jugasa77 said:

The message said that there is an error on loadout 56898, which is the first loadout of Su-27SM Flanker (intercept).

Hello, I have found a solution. I have got to delete the loadouts and introduce them again.

Here is the results: MyDatabase_2022027-20240105.rar.

And here is the probe scenario to probe it: OperationArkhangel-20240105.rar.

Of course, they aren't finished.

MyDatabase_2022027-20240105b.rar OperationArkhangel-20240105.rar