- Messages
- 228
- Country
I've created a tool which automatically updates AI flightplans if you have a repaint installed for a specific aircraft in the flightplans.
It's just been uploaded to AVSIM and Flightsim.com and I would appreciate feedback.
Link to file: http://library.avsim.net/esearch.php?CatID=fsxutil&DLID=167343
Readme (I just noticed the readme.txt included in the file is empty, as it hadn't been saved, but same info is available in the included pdf file):
Flightplan Splitter v0.1
Flightplan Splitter (FPS) is a tool which automatically modifies AI flightplans for Microsoft Flight Simulator X, if you have a repaint for a specific aircraft. Although this has only been tested with FSX, it should work for FS2004 as well.
Requirements
FPS requires .Net Framework 4.0 or higher (not included) and Ionic.Zip.Reduced.dll (included, along with its licence).
Installation
You can run the FlightplanSplitter.exe from any location, but you have to make sure Ionic.Zip.Reduced.dll is in the same folder.
What does it do?
FPS automatically updates AI flightplans to use repaints you have for individual aircraft registrations.
Example 1, using Alpha India Group's winter 2011/12 flightplans for Croatia Airlines:
There are flightplans for five individual Dash-8 aircraft (registrations: 9A-CQB, 9A-CQC, 9A-CQD, 9A-CQE and 9A-CQF), but they are all mapped to the same repaint (Croatia Airlines Bombardier DHC-8-Q400). You will therefore only be able to use one repaint for all five aircraft, even if you have individual repaints installed.
FPS will search your installed AI aircraft for the individual repaints, and update the flightplans accordingly if repaints have been found, so you can use all repaints.
Example 2, using Alpha India Group's winter 2011/12 flightplans for Cirrus Airlines:
There are flightplans for individual Dornier 328-100 aircraft (e.g. D-COSA, D-CCIR and D-CIRC), and these aircraft have been installed in FSX, but have to be manually mapped as the aircraft titles of the installed repaints differ from the flightplans'.
FPS will update the flightplans automatically to reflect the installed aircraft titles.
Limitations – (ie features, not bugs)
FPS will select the first matching repaint, so if you have several repaints for the same individual aircraft (e.g. 9A-CQC or D-COSA), it may not chose the repaint you'd like. For this reason alone, it's highly recommended that you keep your AI Aircraft separate to your flyable aircraft.
It's only possible to mass update flightplans in either zip files, or from flightplans.txt files. FPS will not do both in the same operation.
When searching for flightplans in zip files, it will only be looking for flightplans.txt files in the root folder of the zip file and the root folder's subfolders. It will not look for flightplans.txt files in any other sub folders, nor in zip files within the zip file.
Bugs
When dragging zip files which have been modified by FPS from older versions of WinRAR to Windows Explorer, WinRAR will crash. This doesn't happen in WinRAR 4.11 64-bit, and is likely to be cause by the 3rd party compressing library.
Feedback
For any feedback, queries or requests, please email fpsplitter@gmail.com (or in this thread)
©2012, Morten Blindheim (the author)
It's just been uploaded to AVSIM and Flightsim.com and I would appreciate feedback.
Link to file: http://library.avsim.net/esearch.php?CatID=fsxutil&DLID=167343
Readme (I just noticed the readme.txt included in the file is empty, as it hadn't been saved, but same info is available in the included pdf file):
Flightplan Splitter v0.1
Flightplan Splitter (FPS) is a tool which automatically modifies AI flightplans for Microsoft Flight Simulator X, if you have a repaint for a specific aircraft. Although this has only been tested with FSX, it should work for FS2004 as well.
Requirements
FPS requires .Net Framework 4.0 or higher (not included) and Ionic.Zip.Reduced.dll (included, along with its licence).
Installation
You can run the FlightplanSplitter.exe from any location, but you have to make sure Ionic.Zip.Reduced.dll is in the same folder.
What does it do?
FPS automatically updates AI flightplans to use repaints you have for individual aircraft registrations.
Example 1, using Alpha India Group's winter 2011/12 flightplans for Croatia Airlines:
There are flightplans for five individual Dash-8 aircraft (registrations: 9A-CQB, 9A-CQC, 9A-CQD, 9A-CQE and 9A-CQF), but they are all mapped to the same repaint (Croatia Airlines Bombardier DHC-8-Q400). You will therefore only be able to use one repaint for all five aircraft, even if you have individual repaints installed.
FPS will search your installed AI aircraft for the individual repaints, and update the flightplans accordingly if repaints have been found, so you can use all repaints.
Example 2, using Alpha India Group's winter 2011/12 flightplans for Cirrus Airlines:
There are flightplans for individual Dornier 328-100 aircraft (e.g. D-COSA, D-CCIR and D-CIRC), and these aircraft have been installed in FSX, but have to be manually mapped as the aircraft titles of the installed repaints differ from the flightplans'.
FPS will update the flightplans automatically to reflect the installed aircraft titles.
Limitations – (ie features, not bugs)
FPS will select the first matching repaint, so if you have several repaints for the same individual aircraft (e.g. 9A-CQC or D-COSA), it may not chose the repaint you'd like. For this reason alone, it's highly recommended that you keep your AI Aircraft separate to your flyable aircraft.
It's only possible to mass update flightplans in either zip files, or from flightplans.txt files. FPS will not do both in the same operation.
When searching for flightplans in zip files, it will only be looking for flightplans.txt files in the root folder of the zip file and the root folder's subfolders. It will not look for flightplans.txt files in any other sub folders, nor in zip files within the zip file.
Bugs
When dragging zip files which have been modified by FPS from older versions of WinRAR to Windows Explorer, WinRAR will crash. This doesn't happen in WinRAR 4.11 64-bit, and is likely to be cause by the 3rd party compressing library.
Feedback
For any feedback, queries or requests, please email fpsplitter@gmail.com (or in this thread)
©2012, Morten Blindheim (the author)