We got a new video from World of Aircraft: Glider Simulator and are asking for some alpha/beta testers! Check this post.

 

Jump to content

pellelil

members
  • Content Count

    145
  • Joined

  • Last visited

Community Reputation

23 Excellent

About pellelil

  • Rank
    Developer of Flightplan Visualizer

Contact Methods

  • Website URL
    https://forum.aerosoft.com/index.php?/forum/919-flightplan-visualizer/

Recent Profile Visitors

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

  1. Christmas comes early this year 🙂 Beside being able to reduce the with of the form in settings. I have now inserted splitters between the 3 list-views. The right part of screen is fixed (can't be made more/less narrow), however the width of the 3 list-views can be adjusted by dragging these splitters left/right.
  2. You are welcome Bernhard. I don't know if it is an issue for you (probably not as you run with 1200 pixel in height in stead of 1080), but I have reduced the initial height of the Airport-info form as well. So all form should be visible at 1920x1080 with a font-size of 125% - can't promise I can remain doing so, but I will try 😉
  3. Bernhard for now you will have to drag the form left/right to see the left/right sides, or reduce the font size in windows to 100%. However in the next version I will add a setting that allows you to specify you are using a "reduced desktop" (still guessing that the font-size scaling is the reason). Here is the form as it looks now: However when "Reduced desktop" is selected in settings (in the next version) the width of the form is reduced by "stealing" some of the width of the 3 list-views (Flightplans, Airlines and Aircraft), hence the form will look like this in stead: Remark due to scaling of the images above they appear to have the same width (until you open them), but as you can see the 3 list-views are more narrow.
  4. ... or perhaps you have setup your windows to scale the interface (e.g. running font size at 125%, 150% or higher) ?
  5. Hi Bernard It is one of the lager forms (if not the largest) however I aim for all all forms to be able to fit in a 1920x1080 desktop. The Form is only 1741 x 779 pixel so it should fit well inside your 1920x1200 desktop. Do you have any docked items/sidebars setup in windows that somehow reduces the visible area of the desktop?
  6. Up until now FV have been fully backward compatible with all previous versions, so even if you skipped a version or two you could always install the latest version of FV without fearing your personal imported flightplans, or user settings would no longer load. But with version 1.17 I will be removing some of that backward compatibility and with version 1.18 I will be removing even more. During the +2 year development cycle a lot have changed below the surface as new functionality have been added to the program and a lot of code have been added to make the program stay backward compatible with even the oldest versions (e.g. the flightplan file-format is currently in its 11th format-version). I would like to stream-line the code and remove much of this code that ensures this backward compatibility, as it has recently started to get in the way of things I want to do. As a result I urge all users who have not yet updated to version 1.16 to do so, and likewise when version 1.17 releases I urge all users to update to this version as well. Version 1.17 will forcefully update all (active) flightplan-files to ensure these are fully updated to the latest format-version. This will ensure all flightplans will load into version 1.18 and later without any issues. If you have spread your flightplans across multiple sub-folders I urge that you both in version 1.16 and 1.17 enables each of your sub-folders (only one at a time) as this will ensure ALL of your flightplans gets updated to the latest format-version, even if multiple sub-folders contains flightplans with the same name. The way you do this is to go into the "Enable/Disable flightplans" form that can be opened from the "Flightplan" main-menu item. In the top right side of the form you go through all of your sub-folders and make sure that the "Enable flightplans in this sub-folder" check-box is only checked for a single of your sub-folders. Then you click close to return to the main form, and all flightplans in that sub-folder will be reloaded and re-saved if necessary. Then again you open the "Enable/Disable-flightplans" form, disable the folder you previous enabled, and then enable the next of your sub-folders (rinse and repeat). If you have any flightplan in the [ROOT] folder you should ideally move these to a sub-folder PRIOR to performing the instructions listed before. If you are (100%) sure that you don't have same named flightplans in multiple folders you don't have to do it one at a time, and you can simply activate all sub-folders at once. Likewise if you don't import flightplans yourself, or have all your flightplans in the [ROOT]. To clarify: version 1.17 will be fully compatible with version 1.16, but not fully compatible with version 1.15 or previous (hence why I urge all to update to versions 1.16 now). Likewise version 1.18 will be fully compatible with version 1.17, but not with version 1.16 or previous (hence why I urge all to update to version 1.17 when it releases). Going forward future versions should (at least for a long time) be fully backward compatible with prevous versions back to version 1.17. So a user updating from version 1.15 (or previous) to version 1.18 (or later) here is the process to go through: Install version 1.16 (don't skip this version) Start version 1.16 and enable all flightplan sub-folders (one at a time). Install version 1.17 (don't skip this version) Start version 1.17 and enable all flightplan sub-folders (one at a time). Install version 1.18 (or later)
  7. Version 1.16 have just been released, and it can be downloaded from AVSIM using this link: https://library.avsim.net/esearch.php?CatID=p3dutil&DLID=217599 I urge to you to watch the video released with version 1.11 (available via the help-menu) as it tells you how you can manage your flightplans. A video explaining most of the changes in version 1.16 have also been uploaded to YouTube and link for this video is also available via the help-menu. Below is the entire list of all changes implemented in version 1.16, but the two major things is being able to download and install AIG flightplans directly from FV and filters and a few more criteria added to the leg search (e.g. you can now search for flights departing or arriving within a specified time-interval). List of changes: First of all a big THANK YOU to AIG (Alpha India Group) for allowing me to add features to both download their flight-plans (actually a feature suggested by Kai Kamjunke who is one of the developers of AIG AIM and other AIG tools) and access their list of defunct/renamed flightplans. While giving thanks, I also want to thank all (AI) aircraft-model creators, repainters and those who create all the flightplans ... our virtual sky would not be the same without your hard and dedicated work. Added new form to download or install AIG flightplans (downloaded directly from the AIG-servers). The form will identify all flightplans that are newer than those already installed or flightplans that are not currently installed. You can simply double-click a flightplan and it will be directly installed without the need to first download the file, and then choose to import this file. Both the new flightplan download- and the enable/disable flightplan- form contains a button which download- and show a list of defunct/renamed flightplans (obtained directly from the AIG forum). If you create a user-Airline while importing a flight-plan, when you return to the import-form you will be asked if you want to use that newly created flightplan (saves you from having to open the airline-browser and search-for/select that user-airline). Added Flightplan-, Airline- and Aircraft-filter to the top of the leg-search form to filter the items shown in the listviews. The "Select All" and "Select None" buttons now only (de)select visible items (if a filter is active there might be more items not displayed). However holding SHIFT while pressing these buttons, ALL items will be (de)selected no matter if they are shown or not. Replaced the two airport entry fields (in the leg-search form) with filter combo-boxes (MRU) so you can now enter a filter-text to filter which airports to include (the default filter is using ICAO-codes so the old functionallity is preserved). Added filters to search for legs with specific flight-numbers and/or served by aircraft with specific registrations. When setting up a filter, sub-elements of the same type can now be separated by "/" so you only have to enter the type-name once (e.g. "country=dnk/nor/swe"). The pipe-char ("|") can be uses in stead if you prefer (e.g. "country=dnk|nor|swe"). Now both "?" and "%" can be used as a single char wildcard in the filters ("?" is a DOS wildcard, whereas "%" is a SQL-wildcard). Added "#" as a wildcard for a single numeric value (0-9) in filters. Added "@" as a wildcard for a single alpha value (A-Z) in filters. Improved detection of invalid filter-text, which changes the text-color into red, to indicatet that the filter is invalid. The ISO3 country-code is now visible in the country combo-boxes in the leg-search form (these codes can be used in the airline- and airport- filters). Likewise 3-char Region- and Sub-region -codes have been added to their respective combo-boxes (these codes can also be used in the airline- and airport- filters). Saving the leg-search criteria will no longer require the input to be validated. E.g. you can now save the criteria where no aircraft have been selected. If you want to make sure that the criteria is valid for a search, please perform a search before you save the criteria. Flightplan-filter added to the "Re-process flightplans" form. Aircraft-filter added to the "Choose favorite aircraft-types" form. Also a few extra columns were added to the aicraft list-view. The Decode-METAR/TAF form now allows the user to manually enter METAR/TAF messages, and the form can now be opened directly from the main-menu (in case you optain METAR/TAF from other sources and need to decode it). Added a new button to the Randomizer form which lets you pick a random route (there is already a button to pick a random flight). The difference is the statistical chance of the chosen route. Added 2 columns to the runways listview in the Airport-info form showing head/cross-wind based on selected wind-direction/speed (automatically updated from the obtained METAR report). When accepting the result of a leg-search the previous used criteria (if different) are now archived. So you are able to load the 5 last used search criteria. The Result-viewer form now have a "Top-most" check-box. When checked that form will be shown on top of all other windows. This allows you to have this form shown on top of other forms (e.g. if you need to enter data from a metar-message into the FMC in the simulator). Many of the result-viewer forms now opens non-modal, meaning it can be displayed next to the window form where it was opened and you can switch between the two (you might need to use the new "Top-most" check-box for the best result). When closing the form from where the result-viewer was opened, the result-viewer will be closed as well. Likewise the Unit Conversion form also got the "Top-most" check-box in case you want to display this window on top of another program (e.g. if you have paper-work with weight based on kg and you need to enter the weights into a FMC/MCDU that only accepts lbs (or vice versa). The "Copy to clipboard" buttons on the METAR/TAF-decode form, and the Leg-Info form have been replaced by a "Show Report" button in stead. This new button will in stead show the text in the Result-viewer form (if you need to, it can be clipped to the clipboard from there). Below the (left/right) list-views in the "Enable/disable flightplans" form you now find a label showing two numbers. The 1st number shows the number of items (flightplans) shown in the list-view, and the 2nd number (in the parentheses) shows the number of selected items. When importing a flightplan where the aircraft-type can not be detected, the "lines" assigned to the "DUMMY AIRCRAFT" are now all automatically selected. So it is easy to just hit the "Change Aircraft type" button in case there is just a single, or multiple that should have the same type assigned. Hoovering the mouse over the gate-markers in the Airport-info form, the tool-tip now contains the GPS-position of the gate. Likewise editing the gate the caption of the edit window contains the GPS-position. Added airport size to "FS Comment" column in the "Nearby Airports" form. Added line-breaks to the METAR/TAF tool-tips displayed in the Leg-info form (line-breaks also included in the report). Fixed: There was a nasty bug in the "Legs" tab-page of the Airport-Info form where the same time-zone was used for both departure- and destination-airport when showing the departure-/destination-times as local times, even if departure- and destination-airports were in different time-zones. Fixed: The value of the "Calculated flighttime" check-box in the leg-search form was not set to the loaded value. Fixed: If one of your user-airlines had a blank callsign, it would list all airlines with a blank callsign as alternatives. Now it will only try to match non-blank callsigns. Fixed: The METAR/TAF decoder was not able to correctly detect a fraction visibility if following variable wind (e.g. "210V290 3/8SM"). Fixed: Some of the combo-boxes in the leg-search form were enabled for text-entry, where the user should only be able to pick a value. Fixed: If "[None]" was selected and you executed a leg-search the "Edit" button remained disabled when you returned to the main form. Data: While testing some of the new filters I saw a few erros in the aircraft data (e.g. a few freight aircraft had a non-zero passenger count and other minor issues like that), which were fixed. Data: Thanks to Bruce Nicholson for bringing it to my attention that DC-9-15F was not being detected in version 1.15. Now all the DC-9 sub-variants should be detected correctly (e.g. 9-11/12/13/14...51 both pax and freight). The same better sub-variant detection was added to the DC-8's and DC-10's as well. Data: Thanks to Aucery for bringing it to my attention that some of the (BizJet) aircraft were not being detected, or not being detected correctly. The King Air 250/300 should now be detected correctly as are Hawker-700/1000, Mitsubishi MU-300, IAI Astra Jet 1125, Cessna T210/T303, and Dornier 328JET/PROP. Flightplans: All new/updated flightplans have been added to the installer, and all obsolete have been removed. A total of 765 active flightplans are bundled with the installer.
  8. The video with changes in version 1.16 is now available: I still need to import new/updated flightplans and build the installer. Once build it will be uploaded to AVSIM and then it usually take a day or two before it becomes available. So if all goes well the new version should be available within a few days.
  9. In version 1.16 when you import a flightplan containing aircraft that can not be automatically detected, these will automatically be selected in the Aircraft list-view so if there is only a single, or they are all of the same type, you can simply click the "Change Aircraft type" button to assign a (substitute) airline-type (without having to manually select these):
  10. Aucery thanks for pointing out the aircraft that were not being detected (correctly). I ran through all the flightplans from the package you mentioned (just to verify aircraft-detection), and there were a few issues. In one of them "Piaggio" was misspelled as "Piaggo", so there is a good reason why that was not detected - it still won't be 🙂 The Hawker 1000 was already added to the database, however there was a bug in my aircraft-data, so it was not being detected while it should. That was fixed and the Hawker 700 was added as well. The "Mitsubishi MU-300" is now being detected as the "Hawker 400". The "King Air 200" was changed into "King Air 200/250" and the "King Air 350" was changed into "King Air 300/350", and aircraft named accordingly will now be detected as such. All variants of the King Air 90 (e.g. "E90" and "F90) were detected correctly, however to indicate this, the name was changed from "King Air (C90/B100)" into "King Air (65-A90/B90/C90/D90/E90/F90/G90/H90/A100/B100/C100)" - I know its a bit of a mouthful, but it reflects the aircraft being detected 🙂 Regarding the Cessna I came by a "T210" and "T303" that was not detected. Likewise "Dornier Do-328JET" was not being detected as "Dornier 328-300 (Jet)" (it was the "Do-" part that threw the algorithm off track). For those of you who import your own flightplans, when you have installed version 1.16 you should execute the "Re-process flightplans" menu (found in the "Flightplan" menu), and set "Aircraft redetection" to at least "Re-detect all automatically assigned". This will go through your active flightplan and redetect aircraft types once again and correct those that might have been wrongly auto-detected in the past. If you in stead choose "Re-detect all" it will also try to redetect those where you have been forced to choose a substitute aircraft because the correct aircraft was not available when you imported the flightplans (e.g. the "Mitsubishi MU-300"). If you have flightplans in sub-folders that are not activated be sure to activate these first, so the flightplans in those sub-folders gets updated as well. I will make sure that all flightplans bundled with the 1.16 installer will be updated, so no need to manually update these. Should you (or others) come across flightplans containing aircraft that are not being detected - or not being detected correctly - please put flightplans aside, so you can provide them for me to improve the aircraft detection.
  11. I am not aware of that package. When I made the BizJet package for FV I manually downloaded all the flightplans that was available via Erics website. However this website now appear discontinued. I will look into the detection of the hawkers, and the Cessna, to see if something can be done, but not sure it will be for the 1.16 release. But as you have realized since version 1.15 you can now manually pick aircraft-type if it is not automatically being detected. There are no data in the AI traffic-files that directly contain the type of aircraft in use (i.e. no IATA/ICAO-code). In stead the type have to be determined from the name given to the aircraft, and all those who make the flightplans does it differently. AIG is faily constistent, but flightplans from other creators might be more difficult. So even though FV (in my own opinion) does a good job detecting aircraft it is not perfect (the reason the before mentioned feature was added in 1.15).
  12. Regarding the year (2018) it is listed in the settings-file, so by manually altering the settings-file (there is no GUI for this value) you could download older flightplans using FV. But if you do alter the settings file for this purpose, you should know that you can then not "trust" the value displayed in the status-column. With permission from Eric Steinmetz I imported all his Bizz Jet flightplans (except a single made for a chopper) that was available at the time (as I recall it was 386 BizzJet flightplans). For a few releases these were bundled with the FV installer, but at some point I removed them from the installer and it stead made a a separate package that can be downloaded from AVSIM (using the link below). I don't know if Eric or others have released any new/updated flightplans, nor do I plan to (as I regard this as niche with few interested). So to import more/new BizzJet flightplans you are on your own ... The same goes for military flights 🙂 Link for BizzJet package for FV: https://library.avsim.net/download.php?DLID=211011
  13. The build-in download feature is limited to year 2018 and later. The reason for this is filename structure used before 2018 was less "structured", and the program needs a structured naming convention in order to be able to extract: season, year and revision (version) from the file name. It uses this information in order to populate status-column which tells if the flightplan on the server is newer/older than the one already installed. So if you need to install flightplans older than 2018 or fligthplans for other sources that AIG you are still on your own, to download these. However the pre-imported flightplans bundled with Flightplan Visualizer still contains a fair amount of flightplans from 2015(2), 2016(7) and especially 2017. Over time as AIG releases new/updated flightplans for the airlines in question these older flightplans gets replaced with newer ones. I had planed to include the defunct flightplans in the installer for 1.16 (as some people might want to fly these still), but I am in stead thinking of making these available as a separate download (as I guess only a few wants them).
  14. For those of you who download and install AIG flightplans yourself things will be a little more easy from version 1.16. It is still WIP, but the basic functionality is implemented: Top-most in the screen you select the the season to import from. It will automatically default to the latest season (hence in this example Winter 2019-2020. Looking at the values in the (right-most) status column the program will automatically detect and select flightplans you have not installed or flightplans that are availble for a new season or in a newer revision (e.g. the name is postfixed by "v2", "v3" or whatever). When you click the "Download" button you will be asked which folder to download the files to, on once you accept the selected flightplans will be downloaded.
  15. A filter have been added to the Gate tab-page of the Airport-info form. When just entering a simple filter (as in the screen-shot below) it will filter both the list-view and the map to only show gates that contains the filter-text in the name/number or list of airline-codes. The default airports in FSX/P3D don't contain an airline list for each gate, so searching for airline-codes will only work for 3rd party airports that contain this list. In this example I searched for "RYR" (ICAO-code for "RYAN AIR") to find all suitable gates at EKCH (based on the newly released FlyTampa EKCH V2): Implementation of this filter is WIP (Work-In-Progress) and currently it only works with the default filter searching within the gate-number/names and the airline-list. However I will expand this filter to also search for Category (Gate, Parking, Dock), Type (e.g. GA, RampCargo, GateSmall, GateMedium, GateHeavy), Radius of the gate (e.g. "Radius>=30") and so on.
×
×
  • Create New...