FFX ATC ID ?

[Moonwolf 0]

Is it possible to set up naming of the dispatched AI to be identical to ATC ID from aircraft.cfg and not the generic FFXAI-XX ?

Or to be named directly like in AITrackerX ?

Thanks
Michael

 

Edited October 10, 2019 by Moonwolf

[Lorby_SI 2,036]

Hello Michael,

you mean, how much would it cost to implement an input field for the AI names? Between 400 and 800€. It may take as much as a full day of effort, implementation, testing and appending three documentation files in three languages. The ATC-ID of the aircraft is used to identify them in other parts of the application, and all that would have to change too.

I'm not sure that I am prepared to do that. That kind of cost will never be recovered through sales.

Best regards

Edited October 10, 2019 by Lorby_SI
Corrected the estimate

[Moonwolf 0]

I have just purchased AITrackerX and this addon seems to use ATC ID for AI Traffic, but somehow FFX generates it's own ATC ID numberseries?
Naming via input field is only "nice to have", but it would be great if naming was the same in FFX as in AITX.
Either way i appreciate all your work and support in FFX.

 

Thanks
Michael

Edited October 10, 2019 by Moonwolf

[Lorby_SI 2,036]

39 minutes ago, Moonwolf said:

I have just purchased AITrackerX and this addon seems to use ATC ID for AI Traffic, but somehow FFX generates it's own ATC ID numberseries?
Naming via input field is only "nice to have", but it would be great if naming was the same in FFX as in AITX.
Either way i appreciate all your work and support in FFX.

 

Thanks
Michael

Hello Michael,

both applications overwrite the default ATC-ID from the aircraft.cfg (and some other fields) with new values when the AI is created. In case of AITX you can enter the text yourself, in FFX it is hard coded, to make sure that the aircraft can be identified programmatically later, for example when transmitted over the FFX netword in a multi-user setup. FFX requires the AI to have these names, that is what makes it difficult to just add a simple input field like in AITX. I would have to implement other properties, so that aircraft can still be identified as FFX AI (as opposed to simulator AI or other FFX players on the network).

Best regards

[Moonwolf 0]

Ok, i just hoped this could be solved by an ini-file option.

It's not a big problem though, as the id's can be tracked by using the scratch pad 

Thanks

Michael

Edited October 10, 2019 by Moonwolf

[Lorby_SI 2,036]

Just now, Moonwolf said:

Ok, i just hoped this could be solved by an ini-file option.

That is a small change for me, but it would only work on a single instance FFX setup. When flying with other FFX pilots, there  would be trouble.

I'm not sure that I understand the actual use case though. You could only set a new global prefix, different from "FFXAI-" - but what would that achieve or improve?

Best regards

 

[Moonwolf 0]

It would give the ability to see the type of tanker or lead at a glance on the radar as in real world.

Examples:

T72 = Tanker 72 Cal Fire

T34 = Tanker 34 Coulson C-130 (LAT)

T910 = Tanker 910 DC-10 (LAT)

T944 = Tanker 944 Boeing 747 (VLAT)

H401 = Helicopter 401 Cal Fire (Type 2)

H731 = Helicopter 731 Erickson (Type 1)

AA240 = Lead 240 Cal Fire

Each label would then give better situational awareness.

 

 

[Lorby_SI 2,036]

4 hours ago, Moonwolf said:

It would give the ability to see the type of tanker or lead at a glance on the radar as in real world.

Examples:

T72 = Tanker 72 Cal Fire

T34 = Tanker 34 Coulson C-130 (LAT)

T910 = Tanker 910 DC-10 (LAT)

T944 = Tanker 944 Boeing 747 (VLAT)

H401 = Helicopter 401 Cal Fire (Type 2)

H731 = Helicopter 731 Erickson (Type 1)

AA240 = Lead 240 Cal Fire

Each label would then give better situational awareness.

 

 

To achieve that, you would need an input field where you can set the atc-id for every single aircraft. I'm not sure that the id from the aircraft.cfg would even hold in some instances where FFX creates the AI. And that means, that I have to change the network protocol and add a special something for the AIs - back to where we started.

If you are not into networked firefighting, send me an email again, I will see if I can figure out something "small" for your use case.

Best regards

Edited October 11, 2019 by Lorby_SI