flybywiresim - Facebook schrieb:Alles anzeigen
This is a heads-up that in approximately four hours from now, we will begin packaging and distributing the A32NX as a separate aircraft from the default Asobo A320neo. This has been planned for several months now and is a necessary step to reduce compatibility issues as well as make the A32NX available through the in-game MSFS marketplace in the near future (of course, still remaining freeware).
This package separation, or "fork", will only affect new versions of the development and experimental branches (a 0.6.0 stable release with the fork will come within the week).
One of the main things to be aware of is that liveries made for the default A320neo will no longer function in the new FlyByWire package. Liveries will need to be converted by their respective authors.
Additionally, a simple livery conversion tool will be available in our next installer version, which will be released approximately a week from now (subject to change). This utility will be opt-in and will require the users' discretion to make sure the livery's license allows such modification. External programs which identify individual aircraft may need to be updated to recognize the new FlyByWire A32NX package.
While this might represent an inconvenience for a short amount of time, we are sure that 3rd party content authors will be quick to provide you with updated liveries and programs. If you wish to avoid this, we advise that you remain on your currently installed development/experimental versions for now.
Ab Version 0.6.0 wird Der Flybywire Neo ein eigenständiges Flugzeug sein. Damit wird der Neo auch über den Marktplatz erhältlich.
Alle Liveries werden nicht mehr am flybywire Neo funktionieren. Die Autoren der Bemalung müssen dementsprechend ihre Arbeit umgestalten und neu zum Download anbieten.
Sie werden außerdem ein Konversations Tool in der nächsten Version bereit stellen.