Jump to content


  • Posts

  • Joined

  • Last visited

1 Follower

About pellelil

Contact Methods

  • Website URL

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

pellelil's Achievements


Newbie (1/14)

  • Dedicated Rare
  • First Post Rare
  • Collaborator Rare
  • Week One Done Rare
  • One Month Later Rare

Recent Badges



  1. Version 1.21.1 have just been released, and it can be downloaded from AVSIM using this link: https://library.avsim.net/esearch.php?CatID=msfs20util&DLID=222445 As written in another post version 1.20 was skipped due to a bug introducted in version 1.19 regarding the version check. To mention a few things this version comes with A LOT more biz-jet flightsplans (692 where the previous only had about 380). This version will automatic move obsolete and defuct flightplans to the diabled sub-folder, but this can be disabled in settings. Here is a link for the video recorded for version 1.21 explaining how you can manage your flightplans (to ensure new versions are installed at each update), and what else have changed in this version: Here below is a full list of all changes in version 1.21.1 Due to a bug introduced in version 1.19 regrading the (automatic/manual) version-check, version 1.20 was skipped and this version was released as 1.21.1 (in stead of 1.21.0). Beside the season based commercial flightplans, the "Download AIG flightplans" menu-item (found in the "Flightplan" menu) is now able to download (AIG) GA- and Military-flightplans. A big thank you to AIG for granting access to these. Reorded the download-folders (in the combo-box), so the season-based AIG commercial folders are displayed in chronological order (e.g. "SUMMER_2020" is before "WINTER_2020-2021"). When scanning for/loading flightplans the program will now automatic look for flightplans marked as defunct or obsolete, and if found these will be move to the "Disabled" sub-folder. Two new settings have been added, so you can disable this feature if you want to. Aircraft-types can now be grouped in families of similar aircraft (e.g. a group containing all the Airbus A318, A319, A320 and A321). These families can be managed via the "User Aircraft" menu-item. Removed menu-item "Index of AIG flightplans" in the "Flightplan" menu, as its not needed since the "Download AIG flightplans" was added in version 1.16 (May 2020). Minor changes to the flightplan-name grooming algoritm (e.g. spaces are inserted before/after ampersand, if not already present) and prefix can be added to indicate the type of flightplan (e.g. for biz-jet, government or military flights). Detection of this prefix can be disable in settings. Dropped support for the old ".FPL" flightplan file-format. Since version 1.11 (july 2019) FV have been using the binary ".BFP" file-format in stead. Based on active flightplans, the program will try to detect primary- and secondary-hubs for each airline. An airport must have flights to atleast 10 different airports for that airline, in order to be considdered being either a primary/secondary hub for that airline. This information is displayed both in the airline edit-form and the airline usage-report. The airline usage-report will also list all destinations served by the airline (ordered by which airports are flying to most different airports). The airline usage-report will now also contain a list of the routes served by that airline (as carrier or operator). This list is sorted so the routes that are most flown (per week) comes first. Added an extra tab-page to the Airport-info form that shows which airlines have routes to/from the airport, and which airlines are using the airport as a primary or secondary hub. Added (right-click) context-menu to many aircraft/airline list-views, that lets you lookup aircraft-/airline -information. Added power-conversion to the unit-conversion form, to convert between HP (Horse-Power) and kW (kilo watt). Also added context-menu to the carrier/operator labels in the Leg-info form to show more details for the airline. Likewise the aircraft-labels have a context-menu for showing aircraft-details Removed a few columns from the form choosing favorite aircraft-types, as this info can now be obtained via the new context-menu. Added a column with engine-type/count in the aircraft browser. Minor changes to the airport redirection report (to align some values in columns, making it more easy to read the report). Added a few hard-coded names to the author-name grooming-method, to unify differnt spellings of the "same names". Also added flightplan/author-count to the "Flightplan per author" report. Swapped the operator/carrier-count showed next to size-category in the user-airline edit form (now first value is operator and 2nd is carrier). Minor change to the airline-criteria in the leg-search to simplify selection (removed options: "Carrier only" and "Operator only"). Fixed: The "Download AIG flightplans" form was not able to download flightplans with an ampersand ("&") in the name. Fixed: Once again improved importing of AIGFP flightplans where airport data is using different ICAO-codes (observed with 15 or so of the new BizJet flightplans, e.g. "ESAI_Aero-TechServices(GA-C)_Winter_2020-2021"). Fixed: Issued with the program version-check (both automatic and manual) introduced in version 1.19. Resulting in this version being released as 1.21.1. Fixed: Sometimes closing (without saving) the form for editing user-aircraft it would sometime report there were unsaved changes, even though it was not the case. Fixed: Only the active sub fp-folders were scanned for backup files. Now the main fp-folder is scanned for backups as well. Data: Some of the aircraft-types sharing the same IATA/ICAO-codes have been split into multiple new types (e.g. the Beechcrafts, Cessnas, Pipers and Learjets). This was done to better detect the specific aircraft-types in use (all bundled flightplans have been reprocessed to re-detect the specific types). Data: A few aircraft can now be detected (during flightplan import) using their millitary designation (e.g. Boeing C-22, C-32, C-40, and Gulfstream C-20 and C-37). Data: Improved detection of a few "De Havilland" aircraft. Data: Added a couple of new aircraft-types (Lockheed C-141 Starlifter, Transall C-160 and a few aircraft without official IATA/ICAO-codes, hence using "---" as the IATA-code for these). Flightplans: Thanks to the new feature to download (AIG) GA/Military-flightplans a LOT of new flightplans have been bundled with the installer (a few government and military flightplans, but mostly BizJet). The previous installer came bunled with 385 Bizjet flightplans, however in this version many of these have been updated and a lot more have been added, bringing the total count of BizJet flightplans to +690. All BizJet are prefixed by "Bz_", all Government are prefixed by "Gv_" and all military are prefixed by "Ml_", in case you want to move these to differnt sub-folders using the "enable/disable flightplans" menu-item. Flightplans: All new/updated flightplans have been added to the installer, and all obsolete/defunct have been marked/removed. A total of 1481 active flightplans are bundled with the installer (incl. all of the previous mentioned BizJet's).
  2. I found, and fixed a bug introduced in version 1.19 that results in version 1.19 not being able to detect version 1.20 as a new version (so no one would be notified when the next version is made public). So the next versions will instead be 1.21.1 which will be noticed by version 1.19 as a new version. If all goes well I hope to be able to release version 1.21.1 within the next few days, depending on how thinks pan out.
  3. KKT, you can have the program display all legs at the same time. If you use the "Search Legs" feature (CTRL+L) and do not setup any criteria (e.g. having pressed the "Reset" button) it will select ALL legs (flights). However I would advice not to do this. As the program will become slow, and the map will look like this: Here I have even removed the airport markers so you only see the routes. For the next release I have imported even more flights so the above screen-shot is the result of showing +800000 legs, utilizing no less than +46000 routes (naturally some legs are using the same routes). So in stead I would suggest that you use the the Search-leg feature and filter your search on what you want. E.g. if you only want flights inside the US, then set the criteria to only include legs (flights) with the sub-region (both inbound/outbound to "Northern America [NAM]". Likewise if you only feel for flying flights 4 hours or less, then set this as a criteria also (min/max flight-time). Also I am sure you don't have all of the aircraft as flyable aircraft in your sim, so again a good idea to filter on aircraft, to reduce the number of legs in the result.
  4. Thanks for the kind words KKT. Not sure that you mean with routes in the US? The installer for version 1.19 comes bundled with +1000 flightplans of which +380 are biz-jet flights with only routes in the US. All of these flights are based on the AI flightplans produced by AIG (Alpha India Group), and a few individualists (like all of the Biz-jet flightplans by Eric Steinmetz). The flightplans bundled with version 1.19 contains no less that 780112 different "legs" (a leg is a single flight performed by a specific aircraft). So plenty of flights all over the globe. To see flights in the states you can either choose a flightplan for an American airlines (like) "Southwest" using the drop-box in the bottom of the main-form, or press CTRL+L (or choose "Search legs" form the menu) and enter criteria of flights to search for (e.g. based on country/region/sub-region, which aircraft to include, legth/duration of flights and what not). FV will not automatic download/install new updated versions. However when I release new versions of the software you will be notified the next time you start the program. This notification will contain a link to where it can be downloaded (like this):
  5. Shaun are you asking or telling? The number of flights returned will be based on the criteria you define. The less specific you define your criteria the more flights are returned. If you perform a leg-search with less restrictive criteria you can use the Randomizer to randomly pick one of the flights, so you don't have to do this manually.
  6. Forgot to mention in the video, if you absolutely hate the connected/disconnected-sounds, you can put your own two audio-files in the UserData-folder, using the same filenames. When the program needs to play the connected/disconnected sounds, it will first try to locate these in the UserData-folder, and only it not found there, it will look for them in the Data-folder. However if you in stead replace the files in the Data-folder it will only work until you install a new version, as the installer will simply overwrite the files in the Data-folder (while it will NOT overwrite those in the UserData-folder).
  7. Hi Bernd, the release took a bit longer than anticipated as I had a few issues to iron out, but glad to hear you like it.
  8. Version 1.19 have just been released, and it can be downloaded from AVSIM using this link: https://library.avsim.net/esearch.php?CatID=msfs20util&DLID=221824 Here below is a link to the video recorded for the 1.19 release explaining what have been added and what have changed, and below that there is a full list of changes. To mention a few this version can now connect to the simulator using FSUIPC and show your location on the map. Also I have once again decided to include all of the biz-jet flights (each prefixed by "Bz_" so they are easy to identify, in case you want to put them in a separate folder). A lot of airlines have been updated/added including a lot "fictitious" (for companies without official ICAO/IATA-codes). And for you Bernd, you can now filter your Leg-searches on weekdays 🙂 Here is a full list of changes in versions 1.19: The release-version of the application is now aimed at 64-bit (granting access to more memory if needed). Enabling 64-bit adds a memory overhead of approx 50% compared to 32-bit, but its the "price to pay" to have access to more memory (for those of you with many active flightplans loaded into memory at the same time). FV can now connect to your simulator using FSUIPC (tested both with P3D and MSFS). By default you will have to manually connect/disconnect (using new menu-items in the File-menu). However in settings you can choose to do it automatic. When automatic-connection is selected the connect/disconnect menu-items becomes inactive. When connected to a sim, the location/heading of your aircraft can be displayed on the map, using an orange aircraft-marker, and hoovering the mouse over this marker will display some key data (GPS-location, altitude, heading, speed and so on). Added ability to playback audio-files. In settings you can choose which audio-device to use, and set the volume at which these files are played (defaults to 50%). If volume>0 these files will automatically be played back whenever FV connects to/disconnects from the Sim. Added additional icons that are automatically selected to indicate when the program is connected to the simulator. Hence the icon in the main-form will indicate if FV is connected to a simulator or not. In the form for editing (user)-airlines and in the form for searching airlines the context menu now have a menu-item called "Show usage". When selected, it will generate a report showing all the (active) flightplans in which the airline is used. Added a new "Manual" check-box next to the load-factor when editing user-airlines. This check-box needs to be checked if you want to manually enter a load-factor. When not checked (default) the load-factor will automatically be set to the default value of the selected country. When editing user-airlines, the airline just added/edited will be visible and selected in the list-view. Likewise when deleting an airline, the previous item will be be visible/selected (in stead of always scrolling to the top afterwards, as in previous versions). The Insert/Delete keyboard-keys can now be used as shortcuts adding/deleting user-airlines and user-aircraft (both owned and types). The gate-map context-menu (Airport Info), now allows you to re-center the map (in case your have been panning the map, and can't locate the airport again). Added a new menu-item/form to calculate head/cross-wind from manually entered flight/runway-heading and wind-direction/speed. Don't forget the runways tab-page in the Airport-info form already calculates this for each runway (and wind-direction/speed is automatically obtained from METAR). Added a new menu-item/form to convert plain-text into morse-code. There is also a button that lets you listen to the generated morse-code, so you can practice your morse-code listening skills (e.g. entering an ILS/VOR-ident, to know which morse-code to listen for in the aircraft, to verify the correct ident is received). The "Cruise speed" column have been removed from the aircraft tab-page of the Edit Flightplan form to make more room for the Carrier/Operator-columns. In the past these simply contained the ICAO for the airlines. Now it both contains: ICAO, IATA (if not blank) and Name. The criteria in the leg-search window now allows you to filter on departure/arrival week-days (e.g. only include flights departing a particular airport on a Saturday or Sunday). When using the flightplan-filter on the main-form, it will favor the current active flightplan (as in previous versions), however if not able to, it will select the first flightplan included in the filtered list (in stead of choosing "[None]"). Improved import of AIGFP-flightplans where the airport is not contained within the embedded airport.txt file and is using a different ICAO-code in route-files (observed for "AIG_UTair_Summer2018v6" and "AIG_S7Airlines_Winter2019-2020v3"). Added runway-info (for both Departure/Destination-airports) to the flightplan leg-report. For ILS-eqiupped runways its lists the ID (both as text, as morse-code), frequency and ils-slope. Morse-code also added to ILS-ID column on the "Runways" tab-page of the airport-info form. Above the list-view there is also a label showing the morse-code (using a larger font), and next to it there is a button that lets you listen to the morse-code. Traffic-pattern direction (for take-off and landing) are now displayed for each runway. These data are extracted from the scenery by MakeRunways, hence the info can't be "better" than the info in the scenery (hence most default airports simply shows 'Left'). Current/peak- memory usage is now logged at various stages while running, and when closing the program. These values can also be observed opening the about-box, which will also forcefully append these values to the log. When using MkRwy with MSFS it can't obtain the country-name, hence these are taken from the airport-database embedded with FV. However the name for USA ("United States of America") is too long to be shown together with state-name, hence code have been added it to shorten it to "United States" (which was the default country-name used in FSX/P3D). Changed font in Comments-box for user-aircraft to a fixed font, in case some users what to enter text "in columns" (e.g. if you make "tables" with speed-restrictions). Changed the color of the splitter-bars in the Airport-info and leg-search forms to a darker color, to better indicate where it is. The build-part of the version-number can now be ignored when performing the automatic version-check at start-up. This new setting is by default disabled. If enabled it will ignore changes from version 1.x.0 to 1.x.1 (e.g. an update from 1.19.0 to 1.19.1). However major/minor versions-updates (e.g. from 1.19.x to 1.20.x) will not be ignored. Fixed: Excessive logging while importing AIGFP flightplans removed (leftover from fixing a bug before the release of version 1.18). Fixed: When using kg in the leg-info report, the weight of Luggage incl. pax weight (shown in parentheses) was wrong. Fixed: Button to open filter-manual on Gate-page of the Airport-info form was not visible/position was not fixed. Fixed: The wind-speed obtained from the METAR and used to calc head/tail-wind on the Runway tab-page of the Airport-info form, did not consider the unit (e.g. Khp or meters-per-second). Data: A VERY BIG THANK YOU to Bruce Nicholson for assistance updating the Airline-database, both with new/missing entries and marking defunct airlines as such. Data: A lot of "fictions airlines" was added as well. These are used for companies without official ICAO/IATA codes. To indicate they are fictions the ICAO-code is set to "---" and the IATA-code is used to indicate the kind of traffic (e.g. the combination "---/BZ" is used for biz-jet flights). Data: Also thanks to Bruce for pointing out that a few aircraft were not being detected as they should. So this version should do a better job with Cessna T206H, Cessna Citation SII/S550 and Global 7500. Flightplans: The bundled AIG flightplans have been updated to the latests versions/revisions available from AIG (there were a few defunct that was removed, a few new versions that was added, and a lot of new revisions being updated). Flightplans: Eric Steinmetz's Bizjet (AI) flightplans that have previously been available as a separate download are once again bundled with the installer (they are only installed if you choose the option during installation). These have all been updated to use the new "---/BZ" airlines (for companies without official ICAO/IATA-codes), and the Author/Provider have been set to "Eric Steinmetz"/"ESAI" (the previous/separate download was created before adding author/provider to the software).
  9. Thank you for the file Graham, and glad you got it running in the end 🙂
  10. It appeared changing the "é" to an "e" cured your issue. If possible I would still like to have a look at the faulty Runways.xml so I can inform Peter Dowson so he (perhaps) can do something in MkRwy to handle- or at least detect this.
  11. There are multiple ways. When first installed (when nothing have changed) FV is setup to look for the 3 files it uses (Runways.xml, G5.csv, and F5.csv) in the user-data folder. However going into settings you can specify another path, and when specified the next time you start FV it will look for the 3 files in that folder. Lastly in one of the 2 last releases (forgot which one) I added an argument that can be specified in the shortcut, where this argument tells where to locate these 3 files. However I don't think your issue is finding these files. It appears that there are some "illegal" chars in your Runways.xml file. As I wrote I had this issue myself with the free Paderborn scenery in MSFS. When scanned with MkRwy the city name for Paderborn contained some weird (illegal) chars. This issue went away when Pete changed the order by which MkRwy scans "official" and 3rd party scenery (however only for MSFS). To me it appears you are using P3Dv5? These days I use mostly MSFS, however I have used P3Dv4.5 together with FV without any issues. As I wrote in the last note, please load your Runwayx.xml into a text-editor that can handle larges files (e.g. Notepad++) and have a look in the line its complaining about (1224199). In the search-menu of Notepad++ you find a menu-item called "Go to" which opens a form where you can enter the line number it should go to (be patient it takes a few seconds with such a large file. Alternative put the file somewhere (e.g. drop-box or similar) where you can share the folder so I can download it, and have a look at it
  12. Thanks for notifying med Bernd, I as afraid you had reverted back to version 1.17 🙂 I hope for a release within this or next week
  13. The issue is with your runways.xml file. If you load the runways.xml file into a text editor which can handle large files (like Notepad++) and goto line: 1224199 I am sure you will see some weird (illegal) chars or chars that are not encoded/escaped correctly (hence the xml-file is invalid). The issue I experienced, I saw "reversed chars" (black background/white text) in Notepad++ shown with hex-codes (e.g. "xA6"). Have you tried to download- and run the latest MakeRunways? It can be downloaded from via this link: http://www.fsuipc.com/ It's listed as version 5.11 (on the website) however it is in fact a newer version (you can see this when you have downloaded/extracted the file and look at properties/details it should show version as "")
  14. On 2nd thought it might an issue with your runways.xml if you made your own? (not using the one bundled with the installer). You error message report an encoding error in line 1224199 (position 33). I recently had an issue myself with MakeRunways caused by illegal chars in runways.xml. It was an issue with the free Aerosoft Paderborn scenery and the order by which MakeRunways was scanning (MSFS) official/3rd party scenery. Peter Dowson fixed this by changing the scan order, so perhaps you just need to update- and re-run MakeRunways: https://forum.simflight.com/topic/92054-illegal-char-in-runwaysxml-mkrwy-511/
  • Create New...