Recently we have seen a lot of codes used to unlock our products being offered for discounted prices. Almost all of them are bought using stolen credit cards. These codes will all be blocked by our systems and you will have to try to get your money back from the seller, we are unable to assist in these matters. Do be very careful when you see a deal that is almost too good to be true, it probably is too good to be true.

Jump to content

pellelil

members
  • Content Count

    78
  • Joined

  • Last visited

Community Reputation

13 Good

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. Just a quick update: Version 1.12 will be able to user FS Global Real Weather (FSGRW) as a weather provider. But it will only support METAR as FSGRW does not put any TAF data in the files it generates:
  2. I've made good progress over the weekend, and I must say I am happy with the implementation of the ”Flightplan reprocess” feature. I still need to do a little more tweaking and test, but its almost there. As posted previously the purpose of these new feature is to go through all flightplans and make them fit with YOUR (personal) installed scenery. The job is started with you opening the new “Re-process Flightplans” form where you set your criteria:] In the left side of the form you first select which of the active flightplans to re-process (by default they are all selected). In the right side of the form you have 3 combo-boxes that lets you choose how you want the selected flightplans to be re-processed. I will not go into details with these 3 combo-boxes, but they will be described in the manual and in the “whats new in version 1.12” video that I am going to record. The screen-shot above was taken while the process was running. Before it was started the "Cancel" button was replace by a “Process” button. The "Cancel" button lets you abort the operation, but the flightplans already processed will have been saved with (perhaps) updated content. When the process has finished the user will be presented with a report telling the user what was changed in the process: This report is grouped by flightplan (sorted), and for each flightplan you can see what was changed. I case of flightplans where nothing was changed, they will not be part of the report. In this screen-shot you see the reported changes for “Wizz Air” and “Wizz Air UK” along with the “result” of the report telling you how many aircraft that were redetected (in this case none – hence not written to the report), how many airports that were reverted, how many airports that vere redirected and how many flightplans that were updated (re-saved). It also tells you how long time the process took. When I started to work on this feature I was afraid it would take a lot longer to re-process 540 flightplans (considering all the work done in the background), so I am very pleased with the performance I was able to squeeze out of it (re-processing 540 flightplans in about 4 seconds).
  3. In this topic I plan to describe the features that are most likely coming in version 1.12. Some of the items are fully implemented, some will be work in progress. Everything is subject to change, and I can't offer a deadline. Feel free to comment, ask questions and suggest other features. The main theme for version 1.12 is to add the "remaining" features for each user to tailor the Flightplan data so these match his/her scenery and preferences. There are no 2 installations of P3D that are identical, so the datafiles and flightplans I bundle with the program are constructed to match a default (plain vanilla) P3D installation without any 3rd party scenery installed. So when you look at an airport in FV it will match the default P3D airport when it comes to: ICAO-code, runways, gates, frequencies and so on. However most users will be running with a few or many 3rd party airports installed. For instance I personally run with quite a few 3rd party airports (and a few ORBX regions), and on top of this I subscribe to FsAeroData (https://www.fsaerodata.com/), which is updated each 28 days, following the 28-day AIRAC cycles. Installing a 3rd airport will in most cases just update runways, gates and frequencies for that single airport, but the FsAeroData updates a lot of outdated data, so you will also notice that many wrong/outdated ICAO codes are updated as well (e.g. the ICAO code of Johannesburg, South Africa, is changed from "FAJS" into "FAOR"). So in order to have the information in FV match the installed/active scenery you have to run MakeRunways as instructed in the manual or described in this video: It's not new that you can use MakeRunways to update the info in FV to match your scenery. This feature have been in the software since its first (beta) release. But as a new feature in version 1.12 you can now in the settings form specify the path where you have the files that MakeRunways is generating. Its still a manual process to run MakeRunways - after you have installed-/updated scenery - but if you specify this path in the settings from, you don't need to copy the 3 files into your UserData folder anymore. If a valid path is specified in settings, and this path contains the 3 files (f5.csv, g5.csv and runways.xml) these will be loaded at startup; otherwise the files in the UserData folder will be used as a fall-back option. In version 1.11 I added a new form to edit the airport-redirections, where you in the past had to manually edit the "UserAirportRedirect.xml" file in the UserData-folder using a text-editor. The "redirections" in this file are used to automatic "redirect" (change) from one airport to another, when flightplans are imported. E.g. there are many flighplans that use the ICAO code "LYPR" for "Pristina International Airport". The "problem" is hovewer there are no airport in P3D with the ICAO code "LYPR", but there is one with the ICAO code "BKPR" at the same location also with the name "Pristina". The version of the redirection-file that I bundle with the installer is build with the default P3D scenery in mind, and as such - among other redirection - it contains a redirection from "LYPR" to "BKPR". But this file is just as "personal" as those files extracted by MakeRunways, so each user should define his/her own redirections to match his/her installed scenery (at least when it comes to changed/added/deleted ICAO-codes). E.g. as mentioned previously, since I run with FsAeroData I want to have a redirection from "FAJS" to "FAOR" in my personal version of the redirection-file. At the bottom of the "Edit Redirect" form I have in version 1.12 added a new button ("Generate redirection report") which lets you generate a report of pseudo-airports and active redirections. The purpose of this report is to give you all the data you need in order to determine how YOU want to setup YOUR personal redirections to match YOUR installed scenery. The manual updated for version 1.12, and the "whats new" video I will record for version 1.12 will contain a lot more description of how to use the report to setup your personal redirections. Anyway here is an example from a report, generated on my own computer based on my installed scenery: FAJS*, S26°08'01.298" E028°14'32.341", Johannesburg Intl, Johannesburg, South Africa, NON FS-Airport: with: GPS, TZ, Country, Name/City -------------------------------------------------------------------------------------------------------------------------------------------- 0,0 NM, FAOR, S26°08'01.262" E028°14'32.308", Johannesburg Intl, Johannesburg, South Africa, FS-Airport (4 runways, 81 gates, 9 frequencies) 7,1 NM, FABB, S26°14'17.001" E028°18'21.002", Benoni, Brakpan, South Africa, FS-Airport (2 runways, 2 frequencies) 8,1 NM, FAGM, S26°14'30.001" E028°09'06.001", Rand, Johannesburg, South Africa, FS-Airport (4 runways, 9 gates, 3 frequencies) 10,4 NM, FAGC, S25°59'13.437" E028°08'25.969", Grand Central, South Africa, FS-Airport (2 runways, 3 gates, 2 frequencies) 11,0 NM, FASI, S26°15'00.000" E028°24'00.000", Springs, South Africa, FS-Airport (4 runways) 18,4 NM, FAWK, S25°49'39.676" E028°13'15.211", Waterkloof AB, Waterkloof, South Africa, FS-Airport (4 runways, 6 frequencies) 19,8 NM, FASK, S25°48'41.997" E028°09'48.002", Swartkop AB, Swartkop, South Africa, FS-Airport (4 runways, 3 frequencies) 19,9 NM, FAKT, S25°51'38.973" E028°27'05.799", Kitty Hawk Aero Estate, Boschkop, South Africa, FS-Airport (2 runways, 2 gates, 2 frequencies) -------------------------------------------------------------------------------------------------------------------------------------------- FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Air Austral - Su18 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Air China - Su18 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Air France - Su18 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Air Mauritius - Su18 FAJS*, S26°08'01.200" E028°14'32.400", 0,0 NM, Air Namibia - Wi18-19 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Air Seychelles - Wi18-19 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Alitalia - Wi18-19 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Astral Aviation - Wi17-18 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Bid Air Cargo - Su18 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, British Airways - Su18 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Cargolux - Su15 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Cargolux Italia - Su15 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Cathay Pacific - Wi18-19 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Delta Air Lines - Su18 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Egypt Air - Su18 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, El Al Israel Airlines - Su18 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Emirates - Wi17-18 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Ethiopian Airlines - Su18 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Ethiopian Airlines Cargo - Su18 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Etihad Airways - Su18 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Etihad Cargo - Su18 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Fly Safair - Wi17-18 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Iberia - Su18 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Kenya Airways - Wi17-18 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, KLM - Wi18-19 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Kulula - Wi17-18 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, LATAM Airlines Brasil - Wi17-18 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Lufthansa - Su18 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Lufthansa Cargo - Su18 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Malawian Airlines - Su18 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Mango - Wi17-18 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Martinair - Wi18-19 FAJS*, S26°07'56.400" E028°14'30.600", 0,1 NM, Qantas - Su18 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Qatar Airways - Su18 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Qatar Airways Cargo - Wi17-18 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, SA Airlink - Wi17-18 FAJS*, S26°08'01.301" E028°14'32.339", 0,0 NM, Saudia - Su15 FAJS*, S26°08'01.301" E028°14'32.339", 0,0 NM, Saudia Cargo - Su15 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Singapore Airlines - Wi17-18 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Singapore Airlines Cargo - Wi17-18 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, South African Airways - Wi17-18 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, South African Airways Cargo - Wi17-18 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, South African Express - Wi17-18 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Swiss - Su18 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, TAAG Linhas Aereasde Angola - Wi18-19 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Turkish Airlines - Su18 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Turkish Airlines Cargo - Su18 FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Virgin Atlantic - Su18 The top-line for each (pseudo/redirected-airport) represent the airport that is currently used in FV. In this case the pseudo airport "FAJS" is in use. On your system (perhaps not using a 3rd party version of Johannesburg, nor FsAerodata) "FAJS" will NOT be a pseudo airport as the Johannesburg in the default P3D is indeed using the ICAO code "FAJS". But on my system (thanks to FsAerodata) "FAJS" IS a pseduo airport. Below the top-line you see that there are not less than 8 nearby (within 20 Nm) airports. The nearby airports are sorted by distance to the airport in the top-line. The very first of the nearby airports is "FAOR" and you can see its name is indeed "Johannesburg Intl". The ICAO code is not suffixed with an asterisk, and the last part of the line says "FS-Airport (4 runways, 81 gates, 9 frequencies)" to tell us that this is indeed an FS-Airport, and the data extracted tells us that MakeRunways was able to extract data regarding: 4 runways, 81 gates, and 9 frequencies. So based on this I would add a redirection from "FAJS" to "FAOR". The last many lines after the nearby airports tells us all the installed flightplans that are currently referencing the "FAJS" pseudo-airports. Lets look at another example from the same generate report on my system: BKPR, N42°34'21.997" E021°02'08.998", Pristina, Serbia and Montenegro, FS-Airport (2 runways, 6 gates, 7 frequencies) -------------------------------------------------------------------------------------------------------------------------------------------- BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, Adria Airways - Wi18-19 BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, AtlasGlobal - Su17 BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, Austrian Airlines - Su18 BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, Danish Air Transport - Su18 BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, easyJet - Su18 BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, easyJet Switzerland - Su18 BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, Edelweiss Air - Su18 BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, Eurowings - Su18 BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, Germania Flug AG - Su18 BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, Germanwings - Su17 BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, Norwegian - Su18 BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, Sun Express - Su18 BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, Sun Express Deutschland - Su18 BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, Sundair - Wi18-19 BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, Swiss - Su18 BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, Trade Air - Su18 BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, TUI fly Belgium - Su18 BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, Turkish Airlines - Su18 BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, Wizz Air - Wi18-19 BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, Wizz Air UK - Wi18-19 In this case we are not informed about any nearby airports, but in stead we can see that the airport in use in FV is "BKPR" which is not a pseudo airport (there is no asterisk after "BKPR" and it tells us that this is a FS-Airport: "FS-Airport (2 runways, 6 gates, 7 frequencies)". For each flightplan (below) we can see that they were all referencing the "LYPR" airport, however this was (based on the active redirections) reverted to the "BKPR" airport in stead ("BKPR<-LYPR**"). The direction of the arrow tells us that "LYPR" was redirected to "BKPR". The 1st asterisk after "LYPR" tells us that "LYPR" is a pseudo airport, and the 2nd asterisk tells us that there is (thanks to this redirection) no flightplan using "LYPR" (they have all been redirected to use "BKPR" in stead. Once you have setup your preferred redirections its time to process/change all installed flightplans so they comply with your chosen redirections. Changing all installed flightplans to match your preferred redirections is a 4 step process: Run MakeRunways (as instructed) to update the flight-sim data about each airport to match your installed scenery. Generate and extract the redirection report. Edit the airport-redirections based on the info in the redirection report. Use the new "Re-process airport redirects" menu-item to go through all flightplans, and update them to match our preferred airport-redirects. The behind-the-screen implementation of the "Re-process airport redirects" menu-item is still work in progress. This part is a bit "long haired" and requires a lot of testing to get it right, so more on this feature at a later time. Beside the main-theme of version 1.12 being re-processing all installed flightplans to match your scenery/preferred redirections, a handful of other small changes have been added as well: Abillity to automatic check for available program-updates at startup (can be disabled in the settings-form). The Generic Randomizer form can now be used to pick a random flight. In the "Search legs" form, you can now enter multiple ICAO-codes (separated by comma). The data-files I supply with the installer have been updated with information about a handful of military aircraft. As of now the following list of aircraft have been added: A6/AE6, A10, C5, C17, E2, E3, EF2000, F14, F15, F16, F18, F22, F35, F111, F117, JAS39, KC10, KC135, MiG 21/23/25/27/29/31, Mirage III/5/2000, Rafale, SU 17/20/22/24/25/27/30/32/34, V22. I assume most of us don't need these military aircraft, so a (default) setting have been added to the settings-form to exclude these military aircraft from being listed, unless specific requested.
  4. Great news. Looking forward to having an EFB in the busses.
  5. Version 1.11 have just been released, and its available for download from AVSIM using this link: https://library.avsim.net/esearch.php?CatID=p3dutil&DLID=211032 The file-format of the flightplans was changed and as a result the program will show a lot of warnings the first time you start version 1.11 after the upgrade (basically it just tell you that the format was changed). I've recorded a video describing what is new in version 1.11 and the start of this video tells you have to manage your flightplans. I urge to to at least watch this first part of the video: Here is a list of what have changed in version 1.11: The file-format of the Flightplan-files was changed to accommodate some planed changes. The program remains backward compatible, so "old" flightplans can still be loaded. I wanted to implement these changes BEFORE I began importing new flightplans, to ensure these new/updated flightplans are all utilizing the new format. On startup the old flightplans will automatically be converted to the new format. The new installer now comes bundled with 540 commercial flightplans (schedules:22291, legs:699158) whereas the old one "only" contained 300 commercial flighplans (schedules:16786, legs:536198). All BizJet flightplans were removed from the installer and are now available as a separate download. A new settings-form have been added to eliminate the need to manually edit the settings-file using a text-editor. A new menu-item have been added which opens an explore window browsing the content of the UserData folder. Individual (disabled) flightplan-files can now be permanently deleted via the "Enable/disable flightplans" form. Flightplan sub-folders (with exception of "Disabled") can now be marked as "enabled" (using a check-box). Meaning that the flightplans in these will be also loaded on startup (along with the files in the root-folder). Using the "Enable/disable flightplans" form you can now both move and copy flightplans (based on the value of the radio-buttons). A creator-field have been added to flightplans, which can be entered when you import/edit a flightplan. The name of the creator is displayed as a tool tip when hoovering the mouse over the combo-box in the bottom of the main-form. When importing new Flightplans the program will try to grab creator and provider from the files bundled with the flightplan. Likewise a button is added to the import-form which list the content of the text-files (e.g. "ReadMe.txt"), in case you need to manually grab the creators name from this file. Both when importing- and editing flightplans a new column have been added to the airport list-view containing comments regarding airports that have been redirected (from one ICAO to another), or airports classified as pseudo-airports (in case the airport does not exists in the flightsim). The elevation-column from previous versions was removed to make more room for the comment-column. Added a new form to edit airport-redirections (redirect from one ICAO to another on import). In the airport-info form you can now switch between showing flights for the selected flightplan/last search and all flights to/from the airport being displayed. Added a new "Nearby Airports" tab-sheet to the Airport-info form, which shows a distance-sorted list of nearby airports. In the previous versions all new aircraft were automatically added to the selection of favorite aircraft. From version 1.11 you must manually choose which are your favorites (upgrading from a previous version, your current selection of favorites will NOT be changed). First letter of decoded-metar is now changed to uppercase, and a checkbox lets you decide if you want to perserve line-breaks in the decoded text copied to the clipboard. Switched position of "Save" and "Cancel" buttons in airport-info form, to match layout of other forms. Like elsewhere in the program, the airport search-browser now lists the icao-codes with an asterisk (*) for each airport that is a pseudo airport. Greatly improved the responsiveness/performance of the browser-forms, when searching for : Airports, Airlines and Aircraft. Managed to shave off a few 10th of a second loading/processing data at startup. Added support for additional Aircraft. Many of the Airports in the supplied data-files were updated likewise some new Airlines were added as well. Made the importer stronger to import flightplans where aircraft names are not in quotes, and multiweek days are written as "1/3" in stead of "10". Fixed: When manually redirecting an airport during import, the flightplan was not visualized corretly until re-loading the flightplan (e.g. restarting the program). Fixed: Closing the Enable/Disable-flightplan using other means than the close-button would not make the program re-load active flightplans afterwards. Fixed: Several of the combo-boxes on the airport-info form allowed text being entered into them. Fixed: Corrected an issue with map-caching.
  6. Regarding DRM the sad truth is it in many cases adds more problems to the ligit users, where as those running pirated software simply install and run it. I recall years ago I bouht some software for music production I had sitting idle for 3 weeks after purchase because the developer could not process any authoring because their server was not up to par. As a developer there is little poetic justice in knowing that much pirated software/keygens comes with additional payload in form or malware 🙂 Its just sad when developers deliberately put malware on the PCs of paying costumers (no need to mention any names here). So best of both world is running legit software without DRM.
  7. No not yet. When I began working on 1.11 I just wanted to add a few features I had in my mind, and then I would update all of the flightplans with the latest released by AIG. However as of now I still haven't imported a single flightplan 🙂 Some of the features I have added will assist me when I am going to import the flightplans, and I wanted to update/change the file-format BEFORE I imported any flightplans, to ensure all new flightplans will be in the new format). Other features was added because of your comments, even though not explicit requested (e.g. being able to quickly see in-/outbound flights for a particular airport, and the new graphs showing in-/outbound traffic based on departure/arrival- airport). I still have a feature I want to add, to assist when importing airports, and then its time to first figure out which flightplans to remove because they are outdated or obsolete, which flightplans to update, and perhaps add new flightplans (in case of new/merged airlines). Planing to record a new tutorial video, with what is new in 1.11 and going into detail with the changes regarding importing flightplans. Then comes updating the installer (change regarding the new/removed flightplans), and finally "the release". I hope to be able to finish it all within the first 2 weeks of July as I will be extremely busy at the last haft of July with other tasks. So you have to be patient for a little while more 🙂
  8. As explained previously the chart tab-sheet of the Airport-info form have been extended by a combo-box that chose the "traffic" displayed on the "Legs" and "Traffic" tab-sheet (it defaults to: "Selected flightplan or last-search on main-form", but "All flights to/from this airport" can be selected in stead). On the "Traffic" tab-sheet 2 new pie-charts have been added to show "Inbound from airport" and "Outbound to airport": As visible in the screen-shot above, we here see (all) the flights into ELLX (Luxembourg) airport, sorted by departure airport. On a daily average (based on the AI-traffic installed) an average of 6.57 flights will arrive at ELLX from EDDM (Munich), 5 will arrive from EGLC (London City), 4 will arrive from EDDF (Frankfurt) and so on sorted in decreasing order. Like with all of the other graphs if you chose a specific weekday, you will see an exact number of flights for that weekday in stead of an average. In the screen-shot below "Monday" have been selected. Not only will you see an exact number of flights for each departure airport, but you will also see fewer airports. This is because it is not every day that ELLX receives traffic for all departure airports that have traffic into ELLX (e.g. there are no flights from EGBB into ELLX on a Monday): In Version 1.11 I have managed to optimize the search browsers (used when searching for airports, airlines and aircraft). Not that these were too bad before. However in version 1.11 these have become super smooth (partly thanks to better utilization of multiple cores). In version 1.10 searching for an airport by ICAO code (where you enter an ICAO code you know), it was not unsual it would perform the search before you finished entering all 4 letters (depending on how fast you typed) so when you finished entering the last letter (in which case it should re-start the search) the first search was still running so it took a small fraction of a second before you saw the result of the last search. In version 1.11 it's just so much better. The airport- and airline browsers are still by default limited to only display the first 2000 elements it finds (the aircraft-browser have no limit, but there is not even 2000 different aircraft-types in the program). Raising the "Show max" limit you can populate the search-browser with more results but it will still affect the performance if you set up the airport browser to show all 25000'ish airports. But then again why would you want to display 25000 airports and manually scroll the list, when there are so many ways to filter the result?
  9. The file format of Flightplan files have changed between version 1.10 and 1.11. In 1.11 the files have changed into a binary format with a new extension. The first time you run version 1.11 you will first be presented with this message-box: Once you click the OK button, you will be presented with the "Result Viewer" which basically informs you that each and every flightplan have been converted to the new format: If you restart the program you should not see either of these windows, as all flightplans will then at that point use the new file-format (and extension). Did a test with the new and the old file-format (based on a test with 299 commercial flightplans). The total size of these flightplans is only about 8% of the old format (a reduction from about 100 MB down to 8 MB). Likewise all the files in the Data folder have also changed to a binary format (reducing the requirement from approx 14 MB to 1.5 MB). Its not a" lot", but for those of you who want to limit the footprint on your C-drive.
  10. alpha117, Thought you would like it getting more easy 🙂
  11. In version 1.11 it will be even more easy to see the traffic going into/out-of a particular Airport. When you open the airport-info form it will default to show the traffic going into/out-of this airport based on the selected flightplan or last search performed on the main form (just as it have always done). However in version 1.11 a combo-box have been added to the Traffic tab-sheet. This combo-box lets you switch between the default value ("Selected flightplan or last-search on main form") or as shown here: "All flights to/from this airport". When you pick this value the program will find/display all flights to/from this airport.: As the eagle eyed of you might have noticed the form above have had a new tab-sheet ("Nearby Airports"). As the name denote this tab-sheet will show the airports that are nearest to the selected Airport. By default it will only show airports (sorted by distance) that are within 100 NM of the selected airport and it will only show airports classified as "Minor" or above ("Medium" and "Major"), hover using the combo-box you can both choose a greater max. distance (max 500 NM) or smaller size-classification ("Small" or "Tiny"). This feature can be used to find alternate airports, both to the used as alternates for your flights, or as redirection airports in case a flightplan reference an airport you don't have in your sim:
  12. Still trying to minimize the need to navigate to to to the UserData folder to manually edit the files there (BTW; You should remember to backup this folder along with the flightplan folder). So in version 1.11 it will be possible to edit the UserAirportRedirect.xml file directly from the program. In the past you had to close down FV, manually edit the file in a text-editor, and then reopen FV afterwards. Now you simply open this from via the menu, do your changes, and click the "OK" button: I am guessing many of you have not totally got the meaning of these redirections, but once 1.11 becomes ready for release I plan to record a video showing whats new in version 1.11 and go into detail with some of the new changes. I have some additional things I like to implement regarding the airport-redirection however I think that will be for a future version.
  13. Finally there is no longer any need to navigate to the UserData folder and manually edit the settings file in case you want to change any of the settings, as a new settings form have been added. This form is a work in progress, as I have some additional things I an considering to add. Anyway here is how currently look: If/when you click the OK button the map will be reconfigured for the changes and the flightplans will be reloaded using the new settings.
  14. Still not 100% happy about the "Enable / disable flightplans" form I changed it some more and gave it a few additional features. If you look at the previous screen-shot you will see the left side is dedicated to the "Root folder" and the right side is dedicated to the sub-folders, But then I got to think, what if you want to move a file from one sub-folder to another sub-folder? Then you have to first move it from sub-folder1 to the root and then move it again to sub-folder2. So therefore I decided to put a folder combo-box on the left-side also. The first item in this combo-box is "[ROOT]". This item is only available in the left side, and its the default item. The "Disabled" sub-folder is only available (and default) in the right-side. All other sub-folders will be available in both sides. The buttons "Add new" and "Delete" to add/delete sub-folders are only present in the right-side and it always related to 1. level sub-folders to the ROOT-folder. Likewise the "Delete selected flightplans" button is only present in the right side. Previously the form had 3 radio-buttons that let you decide what the program should do in case of duplicates when moving files. In the new updated version there are 5 radio-buttons split in 2 sections. The first section of 3 radio buttons is identical to what we had before. The 2nd section contains 2 new radio-buttons and these lets the user specify what to do in case of duplicate files when copying files.. In other words when one of the first 3 radio buttons is active files will be moved and if one of the last 2 radio buttons are active files will be copied. Last but no least the buttons to move/copy files between then 2 list-views was renamed into "To right-side >>" and "<< To left-side"
×
×
  • Create New...