Not Downloaded yet
Version 1.2.1
Initial Release January 10, 2021
Last Updated February 26, 2021
File Size 492.51 KB
Downloads 795
This file has been scanned for viruses and is safe to download.
#Real-Life #4K Original #Sightseeing #Handcrafted Exclusive Drag and Drop

1 - NOTE THAT THIS IS NOT A PLANE, ONLY A FIX FOR A PAYWARE AIRCRAFT.
2 - BE AWARE THAT THIS MOD AFFECTS THE MULTIPLAYER MODEL MATCHING.
3 - 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)
4 - 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.

 

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.


Pretty empty over here.


Pretty empty over here.

  • Version 1.2.1 February 26, 2021

    "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.

  • Version 1.2 February 19, 2021

    "Aircraft.cfg" update :
    - Added hangar description for each aircraft.
    - Corrected the ICAO ATC model / type.
    - Small tweaks.

  • Version 1.1.2 February 07, 2021

    Small tweaks in the aircraft.cfg

  • Version 1.1.1 January 23, 2021

    Small tweaks in the aircraft.cfg.




Pretty empty over here.

26 Comments
  • image
    Raller
    February 20, 2021

    I noticed the following. You have the following entries in the aircraft.cfg file:
    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"

  • image
    MachGyver replied Author
    February 20, 2021
    Thank you, will look into it today !
    image
    Raller replied
    February 27, 2021
    MAKE THE ATC PRONOUNCE THE MODEL:
    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
    image
    MachGyver replied Author
    March 01, 2021
    thank you very much for this !
    image
    FlyingsCool replied
    March 04, 2021
    Yeah, I had tried this myself independently and it didn't work. The only way I got it to work was to put them in the main localization files in OneStore\fs-base
    image
    Raller replied
    March 04, 2021
    I have now also tested it and it seems that only a direct edit of the corresponding xxx.locPak file works.
    But you have to remember that after each MSFS update the entry must be repeated.
  • image
    Laffey
    February 07, 2021

    For whatever reason, I can't get this to work. I followed the instructions, but the data is still missing.

  • image
    MachGyver replied Author
    February 08, 2021
    Hi, when unzipping the folder, do you see the SimObjects folder and the layout.json file ?
    image
    Laffey replied
    February 08, 2021
    Yeah. Copied both of them to the aircraft folder, replaced the old files with the new and nothing happened. Finally got it to work after copying the cfg files to all 3 folders in the aircraft folder that had a cfg of the correct type.
    image
    MachGyver replied Author
    February 08, 2021
    Well that's weird, I tried again on a clean install and it worked for me. I'm glad it finally worked out for you !
  • image
    quelcertoleo
    January 31, 2021

    thank you very much for this, like many commented, it's really awkward that such small and simple to fix details are simply oversighted by payware developers.
    again, thank you.

  • image
    MachGyver replied Author
    February 01, 2021
    Thank you for your kind words sir !
  • image
    Flutter8
    January 22, 2021

    I don't have access to the folder. What shall i do? Thanks

  • image
    MachGyver replied Author
    January 23, 2021
    You don't have access to your piaggio folder ?
  • image
    ferruses
    January 22, 2021

    When try to copy, i have error long names

  • image
    MachGyver replied Author
    January 22, 2021
    After unzipping the file, you can't copy/replace in your piaggio folder ?
    image
    ferruses replied
    January 23, 2021
    Nop, have tris error
    image
    MachGyver replied Author
    January 23, 2021
    You need to grab the content of the folder unziped, not the whole folder, if you still have trouble, you can email me at :
    [email protected]
    with screenshots and I'll help
    image
    ferruses replied
    January 23, 2021
    Well, one archive, and other and other and no error. Now going to test.

    Perfect now. THANKS
  • image
    MrWhiteArchon
    January 11, 2021

    Great job, thank you very much!!!

    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!

  • image
    MachGyver replied Author
    January 11, 2021
    Thank you sir ! I'll try to reach up to them so they can add it to a future update of their own, once I finish some more tweaks (seems like they used some of the DR400 files for some reasons)
  • image
    Raller
    January 11, 2021

    I'll never understand that either.
    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.

  • image
    G8V8S
    January 10, 2021

    Great work. Smaller devs should look into beta tester programs within the FS community to help sort these issues before taking people's money. In return you get the aircraft for free or something?

  • image
    MachGyver replied Author
    January 10, 2021
    Thank you ! would be great ahaha ! I need to reach up to them so they can add this to an update of their own, but before I still have some tweaks to do, because for some reason the aircraft.loc file is the DR400 one (wtf) and the UI shows a cruise speed of 115 kn when in reality it is 144.
  • image
    LostPilot
    January 10, 2021

    Thanks. I love this plane but I'm tired of payware devs not even noticing this. 3 planes have completely missed or had very inaccurate data.

  • image
    MachGyver replied Author
    January 10, 2021
    Yes, it is a bit frustrating indeed. I will see if it is possible to reach up to ATSimulations so they can add this in a future update

© MachGyver - All rights reserved. Any reupload or redistribution of this file without the author's prior written consent is forbidden.
This Flight Simulator 2020 Mod was created by MachGyver and shared in Aircraft » Aircraft Additions for Microsoft Flight Simulator.

Dedicated Link Improve Report