Discord 
1 - NOTE THAT THIS IS NOT A PLANE, ONLY A FIX FOR A PAYWARE AIRCRAFT.
2 - IF YOU HAVE INSTALLED A THIRD PARTY MOD INTO YOUR COMMUNITY FOLDER FOR THIS AIRCRAFT, YOU SHOULD REPEAT THE INTRUCTIONS WITH THE MOD FOLDER TOO (Exept for the Layout.json, that you will need to update it separately with the "Layout.json Updater" available at flightsim.to)
3 - REPEAT THE PROCESS AFTER ANY UPDATE OF THE PLANE OR THIRD PARTY MOD FOR IT.
INSTRUCTIONS : just unzip and open the folder, and copy the "SimObejcts" and "Layout.json" files into your Piaggio folder. click on replace the files.
3.1 :
"Aircraft.cfg" update :
- Small tweaks.
3.0 :
"Aircraft.cfg" update :
- Corrected the ICAO ATC model / type (You can now hear the pilot say the Manufacturer and Type of aircraft when tuning in an airspace).
2.2 :
"Aircraft.cfg" update :
- Small tweaks.
2.1 :
"Aircraft.cfg" update :
- Small tweaks.
2.0 :
"Aircraft.cfg" update :
- Update of the Aircraft.cfg (To match the new update of ATSimulations).
- Changed back to original the liverie's "title" to preserve the multiplayer model matching : has no influence on the UI.
"flight_model.cfg" :
- File removed (ATSimulations corrected it in their new update).
1.2.1 :
"Aircraft.cfg" update :
- Corrected (again) the ICAO ATC model / type. (Thanks to Raller, You can now hear the manufacturer in the callsign. however, I tried everything to hear the model as well (P149), but couldn't figure it out. If you have any ideas, feel free to tell me in the comments). - Small tweaks for the manufacturer UI.
1.2 :
"Aircraft.cfg" update :
- Added hangar description for each aircraft.
- Corrected the ICAO ATC model / type.
- Small tweaks.
1.1.2 :
"Aircraft.cfg" update :
- Small tweaks.
1.1.1 :
"Aircraft.cfg" update :
- Small tweaks.
1.1 :
"Aircraft.cfg" update :
- Updated incorrect range to 590nm. (previously 680nm, this was my bad).
"flight_model.cfg" changes :
- Change of the incorrect cruise speed to 144kn in the "flight_model.cfg" file - in the "REFERENCE SPEED" paragraph - has no influence on the flight model itself, only for UI purposes. (was previously 115kn).
1.0 :
"Aircraft.cfg" changes :
- Change of the ICAO type designator to "P149". (was "P149D" but this isn't a legit ICAO code).
- Change of the ICAO manufacturer to "FOCKE-WULF". (was "Piaggio").
- Change of the ICAO model to "FWP-149". (was "2+2" ???).
- Added informative texts to display while loading.
- Change of the liveries title, manufacturer, type and variation for a better UI intergation and user experience.
- Added description for the hangar UI.
- Added UI values for : max ceiling, range, autonomy and fuel burn.
- Change of the livery order into an alphabetical order.
Thumbnails changes :
- Added "thumbnail_small" for a better UI integration.
- Change of the thumbnails to be the same size for a better user experience.
| 
Tombmaster97
MachGyver 6 month(s) ago
transbaconist
MachGyver 7 month(s) ago
transbaconist 7 month(s) ago
Raller
atc_type ="TT:ATCCOM.ATC_NAME_FOCKE-WULF.0.text"
atc_model ="TT:ATCCOM.AC_MODEL_P149.0.text"
If I take a look e.g. into the msfs original de-DE.locPak, there are no variables like this present.
IMO it should be:
atc_type ="TT:ATCCOM.ATC_NAME FOCKE WULF.0.text"
atc_model ="P1 49"
MachGyver 8 month(s) ago
Raller 8 month(s) ago
An entry for "P149" is not present in the language-packs, so we have to put one to it.
The following example is for german language:
1. Add an empty file called "de-DE.locPak" to the main folder of your mod and don't forget to call it in your layout.json file.
2. Add the following entries to the empty de-DE.locPak (this will add the two lines to the original MSFS "de-DE.locPak" file):
{
"LocalisationPackage": {
"Language": "de-DE",
"Strings": {
"ATCCOM.AC_MODEL P149.0.text": "P.149",
"ATCCOM.AC_MODEL P149.0.tts": "P149"
}
}
}
3. Now you can call up this variable in the aircraft.cfg with the following entry:
atc_model = "TT:ATCCOM.AC_MODEL P149.0.text"
DONE:
Now the model P149 is pronounced and written in radio communication (if MSFS allows it).
If this is to work for all languages in MSFS, then you have to create points 1 and 2 for all language files. en-US.locPak, fr-FR.locPak, it-IT.locPak etc. etc.
I have not tested this method as I modified the "de-DE.locPak" directly, but it should work.
Best wishes from Germany
Raller
MachGyver 8 month(s) ago
FlyingsCool 8 month(s) ago
Raller 8 month(s) ago
But you have to remember that after each MSFS update the entry must be repeated.
Laffey
MachGyver 9 month(s) ago
Laffey 9 month(s) ago
MachGyver 9 month(s) ago
quelcertoleo
again, thank you.
MachGyver 9 month(s) ago
Flutter8
MachGyver 9 month(s) ago
ferruses
MachGyver 9 month(s) ago
ferruses 9 month(s) ago
MachGyver 9 month(s) ago
[email protected]
with screenshots and I'll help
ferruses 9 month(s) ago
Perfect now. THANKS
MrWhiteArchon
But I think this and that kind of improvements have to do by the developer, because this is why we paid already to them!
For instance, I already wrote 10days ago about the missing UI data (range etc.) to the developers, but they did not do anything, but to fill out few cell for a software developer team could be not a big work!
They already get a money for a not totally finished work, and we users have to finish what they did not?! This is annoying!
Thank you very much one again!
MachGyver 10 month(s) ago
Raller
Such a great airplane, thousands of hours of development and then on the day of publication such small, elementary things are forgotten or are faulty.
G8V8S
MachGyver 10 month(s) ago
LostPilot
MachGyver 10 month(s) ago