Jump to content

pellelil

Members
  • Posts

    214
  • Joined

  • Last visited

1 Follower

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.

pellelil's Achievements

Apprentice

Apprentice (3/14)

  • Reacting Well Rare
  • Conversation Starter Rare
  • Dedicated Rare
  • First Post Rare
  • Collaborator Rare

Recent Badges

58

Reputation

  1. You are welcome Bernd. One of the things that have changed in version 1.22 is that when you go into the Airport-info form it will now default to show ALL traffic into/out-off this airport, even if a flightplan have been selected in the main-form or you have performed a leg-search. So by default it will show ALL flights with no restriction (hence will also disregard the filtering by weekday. In order to ONLY see the flights of the selected flightplan or an active leg-search you need to go to the "Traffic-Charts" tab-page. Here you find the combo-box labeled "Traffic to chart" (as marked below). Here it will now in version 1.22 default to the value "All flights to/from this airport". You need to change this value to "Selected flightplan or last-search on main-form". This will both change what is charted, and the flights that are listed in the "Traffic-legs" tab-page:
  2. I noticed a small issue regarding the naming of a few older Biz-jet flightplans, that does not follow my normal naming-scheme. On my system I will fix these names, hence for a future release these will have a different name than the names of the files bundled with version 1.22. I suggest that you also rename these files on your system to prevent you potentially could have the same flightplan more than once (if you both will have it with the current/wrong name, and the changed name from a future installer). Also I've begun working on version 1.23 where I've added a new feature to try to automatic try to detect obsolete flightplans, where it will try to locate "the same filename" with different seasons (e.g. "Air Belgium - Su21.bfp" and "Air Belgium - Wi21-22.bfp"). For this feature to work, the naming of the flightplans must follow the default naming-scheme, hence another reason to rename these following files. Here below is the list of filenames to change (from/to): "Bz_Auburn University Su18.BFP" -> "Bz_Auburn University - Su18.BFP" "Bz_Baldor Electric Su18.BFP" -> "Bz_Baldor Electric - Su18.BFP" "Bz_Paramount Pictures Su18.BFP" -> "Bz_Paramount Pictures - Su18.BFP" "Bz_Philip Morris Intl.BFP" -> "Bz_Philip Morris Intl - Su18.BFP" "Bz_Textron Su18.BFP" -> "Bz_Textron - Su18.BFP" Last but not least I noticed I had two different seasons of flightplans for Tyson Foods active at the same time ("Bz_Tyson Foods - Su18.BFP" and "Bz_Tyson Foods - Su22.bfp"). I still need to check the installer if version 1.22 is bundled with both, and/or I forgot to flag the Summer-18 as obsolete. Anyway if you have both installed you should ideally remove "Bz_Tyson Foods - Su18.BFP", but for future installer I will both ensure it is not included and marked as obsolete.
  3. You need to import the zip-file into Flightplan Visualizer (don't manually unzip it). As FV is no longer able to directly download FP, I use AIG AIM to download these FP. BEFORE you install a new FP into AIG AIM you can navigate to the "Online" tab-page in the flight-plan section. Here you will both have an "Install" and "Download" button next to each (non-installed) FP. You need to download them individually, by pressing the "Download" button next to each FP you want to download. These will download as ZIP-files, and its these ZIP-files you need to import into Flightplan Visualizer. If you want to import FP into Flightplan Visualizer, that are already installed into AIG AIM, you will need to first uninstall them in AIG AIM (otherwise you will not see the download-button, which allows you to download the ZIP). Once the FP is downloaded as a ZIP to your hard-drive, you can re-install the FP into AIG AIM again. The just released version 1.22 of Flightplan Visualizer have all FP that AIG had released up til about a week ago. However having just open AIG AIM on my system I can see that AIG have been very busy since then, as it shows 3 "Not Installed" FP and 46 "Updated". If- and when you install the updated FP it will be your own responsibility to disable older versions of those FP. E,g, among my "Updated" I can see there is a "2022 Summer" FP for "AirBaltic" where there is currently bundled an "AirBaltic - Su21" with Flightplan Visualizer. So if you only want one of them active in Flightplan Visualizer you would need to remove the "AirBaltic - Su21" (can be done with the "Enable/disable flightplans" menu-item in Flightplan Visualizer.
  4. Its been more than a year since the release of version 1.21.1, however now finally version 1.22 is here, and the installer comes bundled with with 1599 pre-imported flightplans, and +300 airline logos (optional install). As usual the installer is available for download from AVSIM using this link: https://library.avsim.net/esearch.php?CatID=msfs20util&DLID=226777 If you have AIG AIM (AI Manager) installed on your computer and you have installed all/many of the trafic-files, you will have a folder on your computer containing airline logos for those files, and in settings of Flightplan Visualizer (FV) you can now specify the path to this folder (it should suggest the right path for you to pick). However if you don't have/use AIG AIM I've made a separate download containing +1400 airline logos (in a special ".CAL" format only for use with FV). This additional download is also available via AVSIM using this link: https://library.avsim.net/esearch.php?CatID=msfs20util&DLID=226778 These additional airline logos comes without an installer (its simply a .ZIP file containing these +1400 .CAL files). But before you try to put these additional logo's on your system you should first download, install and run FV version 1.22. Doing so FV will create a "LogoCache" folder where these ".CAL" files should be placed. Here below is the full path to that folder, however you should naturally replace "[User-Name]" with your actual windows user-name: C:\Users\[User-Name]\AppData\Roaming\FlightplanVisualizer\LogoCache As per usual I have recorded a video explaining the delay for the release of version 1.22, and whats new in version 1.22. To see this video you can use the link below, or you can simply access it via the "Help" menu within FV (where you find menu-item for all of the tutorial videos): Here below is a full history-list of all that have changed in this version (at least all I am prepared to share of what have changed): I had initially added a feature to download AIG airline-logos, however a later change in AIG's server setup rendered this feature useless. In stead you can now specify the local folder holding AIG's airline logo's (if/when you are using AIG AIM on your computer for AI-traffic). If specified, airline-logo's will be obtained from this folder. On the same note, I had to remove the menu-item to download AIG flightplans, as this program no longer have directly access to the AIG servers. For the same reason the menu-item to access the index with flightplans (up to summer 2021) was re-enabled. In the past when opening the Airport-Info form it defaulted to show in-/out-going traffic for the selected flightplan or active leg-search only. Now there is a new setting where you can set it up to in stead default to showing all traffic in/out of the airport (the Airport-info form still contains a combobox where you maually can choose what to see). "Owned aircraft" was renamed into "Simulator-aircraft", as these are the (flyable) aircraft you have available within your simulator of choise. When choosing to use calculated flight-times in a leg-search, you can now specify a percentage-difference (between leg-time and calculated-time). Only when the difference between leg-time and calculated-time exceeds this specified value will the calculated time be used during leg-search (e.g. "only use calc-times if diff. exceeds 50%, otherwise use leg-times"). Began using (aircraft) short-names many places where the program in the past used IATA/ICAO-code (e.g. when hovering the mouse over a route, or list of aircraft servicing specific airports when editing flightplans). Also added short-name columns to aircraft browser and when choosing favorites (these stil contains columns for IATA/ICAO-codes). Pressing the "Usage" button when editing/viewing an aircraft-type or right-clicking an aircraft-type in the browser and choosing "View usage-report..." from the context menu, you will be shown a report that inform you how that aircraft-type is used: which simulator-aircraft are based on that type, which owned aircraft that have been marked as substitute for that type, which airlines are using that type (as carrier/operator), and finally in which (active) flightplans that type is used. Items in airline-browser are now by default sorted by (airline) name, and the usage-column shows the size of the airline if its in use. If available a logo for the selected airline is displayed in the upper/right corner. Improved performance when searching for ICAO-codes in the airport-browser. Also improved priority of the default selected item, in cases when an airport had a 3 letter ICAO-code, and another was using the same 3 leters for its IATA code. When searching for ICAO/IATA-codes in the airline-browser, it will now prioritize non-defunct airlines, if multiple airlines share the same ICAO/IATA-code. When enabling/disabling flightplans, you can now select all BizJet flightplans (those prefixed with "Bz_"), all Military (prefixed with "Ml_") or all Goverment (prefixed with "Gv_"). Individual FP sub-folders can now be setup to leave (not move) defunct- and/or obsolete FP, even if the settings to automatic move these to the disabled folder is set. Performing "Search legs" you can now filter on aircrafts you are allowed to fly via type-ratings ("Must be type-rated"). Performing a substitute of a user-airline, that airline will remain selected (previously the list scrolled to the top, and selected the 1st item). Added new check-box to "Search legs" that can exclude round-trips (legs taking-off and landing at same airport). Airline/Aircraft-repaint -filter can now filter on size of airline (e.g. "size=major"). Size is determined from usage as carrier/operator in active flightplans. Airlines not in use by active flightplans are listed with a size of "unknown"). Added GPS-conversion (deg <-> deg,min,sec) to the conversion-form, as requested by a colleague. You can either manually enter lat/lon or look-up an airport to get it. There is both a primary lat/lon and a secondary, and the form will show the (GC)distance between these and the initial/final course. Added new "Max airport-distance" for airport-redirections. At the same time added new feature when importing/editing airports to permanent change an airport. If used, it is not saved/handled as a redirection (can't be restored) but rather as a perpament change. Reordered- and renamed some of the tab-pages in the Airport-info form. Reordered the length/distance-fields in the unit-conversion form. The Wind-calculator have been removed from the main-menu, in stead wind-calcuations can now be performed using the unit-conversion form. Also now the speed of the wind is always displayed as a positive value, and in stead the label will either say "Head-wind" or "Tail-wind". Added new "Country list" menu-item in the misc-menu. Will list all countries twice (sorted by names, and sorted by ISO3-codes). Showing airport-marker tool-tips on the main-map is now prioritized over showing route tool-tips. Added "Min take-off fuel ("MTFL") field to user-aircraft weight-fields. As of now its not set for any aircraft in the database, however it can be estimated as 60 minutes of flight at cruise. Moved several group-boxes of the settings-form to the 2nd tab-page, and added new fields for defalt simulator/logging-environment based on the File-prefix used when starting the program. Also now the header-names that was previous fixed to "Rank" and "Traffic-density" can be changed, so the selectable 6 values can be used for something entirely different, if anyone have the need for this. If/when changed, these new names are shown when editing an airport, or when performing a leg-search (as the leg-search can filter on these fields). MakeRunways (MkRwy) by Pete Dowson is challenged handling unicode in the scenery it scans/writes to XML. E.g. the Icelandic airport (BIFL) "Flúðir Airport" is exported by MkRwy as "Flúðir Airport". In this version FV will try to identify when this happens, and then it will fall back using the airport/city-names from the databases bundled with FV. This is not a perfect solution, but at least it improves the result. Various minor changes and tweaks to multiple forms (e.g. Unit conversion form can now be closed with ESC, renamed log-archives and so on). Fixed: If the main-form had an active flightplan filter when using the search-legs feature the flightplan combo-box still only contained the filtered context. Pressing the Clear button did not resolve the issue. Fixed: Since adding support for the AIGFP file-format, there could be flights departing from- and arriving at the same airport (e.g. helicopter flights). In previous versions the calculated flights-time would only consist of taxi-out/in times. In this version the flightplan leg-time will now also be uses for the calculated time, when the same airport is used both for departure and destination. Fixed: In some cases re-processing flightplans (resetting and performing redirection) could corrupt the flightplans and remove airport-data from the flightplans. This version will also try to add any missing airport-data to flightplans when re-processing them. Fixed: Selecting "only show favorites" in the Search aircraft-type form would filter out all aircraft (including those marked as favories). Fixed: In the leg-info form the fields to show times (Out, Off, On, In) were too narrow for multi-week flights, when showing the week-number (e.g. "TH7/14:37"). Fixed: Issues when estimating cruise/taxi fuel-burn for user-aircraft, where in some cases some fields were not saved, and wrong calcuation if setup to show weight in Kg. Fixed: In some cases wrong TimeZone was used when calculating local time for OUT, OFF, ON, IN-times. Data: The airport redirection file ("UserAirportRedirect.xml") in the UserData folder have been updated to match the latest MSFS world update. However this new file is only installed by the installer if it does not already exists (in case you made your own changes), hence you need to delete this file manually prior to running the version 1.22 installer. Data: Quite a few airports in the airport-database were updated (had wrong names due to issues with unicode-letters). Also some additional airports were added. Data: The installer comes bundled with +300 airline-logos (optional install), and a separat package of +1400 airline-logos are avilable for download from AVSIM (in both cases these are encoded into a propriotary format using the ".CAL" extension). Data: Added the P2F (Passenger-to-Freighter) versions of the Airbus A320, A321 and A330. Also added the package freighter versions of CRJ100 and CRJ200. Data: Improved detection of Boeing 737-700/800 BCF/BDSF when importing flightplans utilizing these (passenger aircraft converted into freighters). Also improved a few other freighter detections. Data: Changed a few (aircraft) short-names to either shorten them a bit, or make them "more readable". Flightplans: All new/updated flightplans have been added to the installer, and all obsolete/defunct have been marked/removed. A total of 1599 active flightplans are bundled with the installer.
  5. That feature is sadly not available any more, as AIG have moved to a new server-setup that Flightplan Visualizer (FV) cannot access. For the same reason the menu-item for downloading FP have been removed from FV 1.22. However if you have the traffic-files on your disk, they can still be imported into FV. Version 1.22 of FV comes bundled with 1599 FP (containing all AIG up to summer 2022)
  6. As written yesterday, for version 1.22 I have added code to (try to) detect when there is an issue with unicode-letters in the name-fields (typical name of airport and/or name of city). If/when this is detected FV will in stead use the name from the airport-database bundled with FV (updated for version 1.22, for the same reason). However this will NOT change the fact that illegal chars in the XML will prevent FV from reading the Runways.xml file. Running into this issue again yesterday made me rethink how I could try to handle the issue with illegal chars the name-fields of Runways.XML. In the past FV have always read the Runways.xml file, as one large (+90 MB) XML-file containing information of all +40000 airports scanned from the scenery. But as written here it meant the entire import failed if this file contained a single illegal char. As a new feature in version 1.22 FV will catch if- and when an error occur reading Runways.XML. If an error occur a new message-box (below) will appear informing the user of the issue, and it will ask the user if a new setting called "Robust 'Runways.XML' reading" should be enabled or not: If you choose "No" ("Nej" here in my Danish version) the program will work as it did in the past (not being able to read the Runways.XML file). However if you in stead chooses "Yes" ("Ja" in Danish), the Runways.XML file will be split into many small XML-sections (one for each airport), and then all of these sections are being imported in parallel. It will cost some extra CPU power, it will cost some more memory (only during import) but it will allow FV to import the file. If there is an issue with an illegal char in the XML for a single airport (as was the case with "CAN9" yesterday) it will detect this issue and it will make sure the name-fields for this one/single airport are "groomed" to remove any offending chars (data for all other airports will import without the XML needs to be "cleaned" for offending chars). So if you run MkRwy at a later time (e.g. after a future "world-update") the issue with illegal chars in the XML might have disappeared and you can try to go to settings and disable it. Worst case the issue is still there, so simply re-enable the setting on start-up. For the more nerdy users (like myself) I will probably want to "hand-edit" my XML to remove these illegal chars if/when they are being detected, but it will require you to look through the log-file to find the specification of where in the XML the issue was detected, and then you will have to manually load the XML, find the location, and edit the file. This new feature is just a matter of accepting to enable it if/when the issue is detected on start-up, and it will log the issue in a more readable fashion: 18:31:25.987|15|INFO |Load Runways.xml (MkRwy) from file: G:\FS\MakeRunways\runways.xml 18:31:26.522|15|INFO |Using normal import of MkRwy Runways.XML file 18:31:26.945|15|ERROR|An error occurred while reading Runways.xml (can happen due to illegal chars in XML generated by MkRwy). 18:32:16.109|15|INFO |User decided to enable robust-reading 18:32:16.122|15|INFO |Save App-settings(xml): C:\Users\pelle\AppData\Roaming\FlightplanVisualizer\UserData\Settings.xml 18:32:16.146|15|INFO |Using robust import of MkRwy Runways.XML file 18:32:18.704|14|WARN |Had to use robust import of MkRwy airport: CAN9 18:32:19.279|15|INFO |Airports imported (MkRwy): 41100 The log clearly states what happened, and that the user chose to enable this new setting. Also in the second last line you can see it occurred importing the XML for the "CAN9" airport, so if you want to hand-edit the XML (remove the illegal char), you in this case simply have to search for the "CAN9" airport. But the less nerdy can simply enable the feature and disregard the log, and the hand-edit part.
  7. For those of you running MkRwy to update the files you use with Flightplan Visualizer (FV) it appaers MkRwy have an issue with the latest (Canada) WU for MSFS ... at least on my system. When scanning the scenery for the airport "CAN9" ("Château Frontenac") it inserts an illegal char in the generated "runways.xml" file. This illegal char prohibits FV reading this required file, hence FV cannot start-up. If any of you runs in to this issue, you can manually edit your "runways.xml" file, however you need an editor that can load such a large file (when I generate it, I include all runways longer than 1500 feet, hence the generated file will be some +91 MB). When loaded into an editor (I use the 64 bit version of NotePad++) search for "CAN9". If you run into the same issue as me, you should see the illegal char in the "ICAOName" field (NotePad++ will show it in reversed colors). Simply paste in a new name without the illegal char "Château Frontenac"). Generally MkRwy is somewhat challenged when it comes to airport-/city-names with unicode-letters (like "â"), so even if not adding illegal chars to the XML, airport/city-names might not show correct in FV. In version 1.22 FV will try to detect these wrong names in the XML, and once detected it will try to in stead fall back and use the names from the airport-database. For the release of 1.22 I have been going through the airport-database and fixed many names that were wrong for airport/cities (also issues with unicode-letters).
  8. Since the last release (1.21.1) I've kept busy working on a brand new feature-set (to be discussed at a later time), and I've added many new features and fixed various issues I came about, and as usual I also made many updates the databases that are used by Flightplan Visualizer (FV). Once such new feature already mentions was the feature to download and display (AIG) airline-logos when browsing airlines. Also I made various changes to the feature of directly downloading AIG (AI) flightplans to be imported into FV. However all these new/updated features went out of the window the second AIG had to move to a new server-setup to cope with the increased bandwidth requirement of all the new users using AIG AIM/TC to inject AI-traffic into MSFS. For a long I was waiting to see if/when AIG was able to again offer the ability to download airline-logos and flightplans directly into FV, however sadly this is no longer an option. For quite some time Flightplan Visualizer was put on the back burner, while I weighted my options as to what to do next, and in the meantime I chose to use my spare-time on other projects that needed my involvement. For those who might be interested, one such project is a program I released last year being able to produce (audio) single-cycle waveforms that can be loaded into hardware/software synthesizers/samples. In August this year I released a new version of this program (Waveform Generator), with a new feature of being able to also generate (audio) wave-tables. If interested here at this url, you can find videos explaining how the software can be used, and you also find a download link (the software is free, but only available for Windows): http://www.infinite-noise.com/WaveformGenerator.aspx Anyhow back on track. With the update for Waveform Generator being released, I could again return my focus to Flightplan Visualizer. Sadly I've had to remove the feature to download (AIG) flightplans directly into FV, as these are no longer available to external software. Also I had to remove- or at least totally rewrite the feature to download the AIG airline-logos. In stead I now have to manually download the AI flightplans (externally, not using FV), and once these have been downloaded, I can import them into FV. I guess most users are not themselves downloading/importing flightplans, so this will only be an issue for myself and those who did download flightplans themselves. Likewise since the AIG airline-logos are no longer available for download by FV either, I've had to do the "next best thing". If you are using AIG AIM, it will download the airline-logos to a local folder for the flightplans you are using with AIG AIM/TC. So in settings of FV you can now specify the location of this folder, and FV will then use the airline-logos it finds in the folder, together with the new LogoCache folder added in version 1.22. Just last weekend I manually downloaded and imported 3-400 new/updated flightplans that have been released since FV was last able to download flightplans. Most of these are updated versions of flightplans that already are bundled with FV, but there are also many brand new flightplans, for airlines that are not available in the currently released versions of FV. While downloading all these new/updated flightplans I had an issue with about 5 of them, but I have a good idea of what went wrong, and where I have to look in the code, so I think (hope) it will be a quick fix, to import these few remaining flightplans. For a long time it was my plan to release version 1.22 with "the new feature-set" enabled. But even though I had already spend a long time working on this feature-set I still have quite a few items on my "to do list" before I am ready to release a version enabling these new features. So in stead I want to release version 1.22 with most of these new features disabled. However there will be some forms that have added fields/columns that might hint about the new feature coming later, but it will not break the software in any way. So I hope to be able to release version 1.22 (bundled with all the new/updated flightplans) within this or the next week, pending on if the last items to iron out are to be completed as I hope/plan.
  9. Thanks for the kind words Arek. Regarding import of flight-plans I can't offer batch/bulk import. The (AI) flight-plan file-format is not 100% aimed at how I use the data within Flightplan-Visualizer (FV). Hence when you import a flight-plan you might see a warning, and you are suggested to look over how it actually imported, as there might be things that needs to be fixed. For instance FV will try to detect which airline is servicing these flights. In most cases FV will detect the correct airline, but in some cases it might not (in some cases the airline might not exists within FV's internal data-base, so it has to be added first, or it might exists with another ICAO-code and/or name). Likewise it will try to detect which aircraft are servicing the flights, and it does a very good job in this aspect, but again in some cases it might not. Likewise FV will try to detect which airports are used to service the flights, and again in most cases it does a good job, but it some cases it does not get it 100%. This all comes down to the data-files AIG is using now/have used in the past, and the data-files FV is using internally. There are differences in this files (e.g. AIG might use another ICAO-code for an airport than FV does). ICAO-codes are not fixed, they do change sometime. This is the reason Flight-plans needs to be imported one at a time, and you "need to" (or at least: "you should"), look at each import to see that it imported as it should. You don't have to, but each time I import a flight-plan I pay attention to the names of the aircraft (repaints) in used by that airline. if the name of an aircraft contains "opb" or "opf" I use these information to set the carrier/operator for that airline. When the name contains "opb" it indicate the flights services by that airline is "operated by" another airline. E.g. an aircraft for a SAS (Scandinavian) flight-plan with "opb CityJet" in the name will indicate that SAS the the carrier, however CityJet is the operator. Likewise if the name in stead contains "opf" in the name it indicate that this aircraft is "operated for" the specified airline. Setting up the Carrier/Operator for the imported flight-plans is a manual process, hence another reason batch/bulk import is not possible. When it comes to the old AIG Flight-plans (dating back to 2008) you might not be able to import then all, and even if you are its more important that you look over each import and verify that it imported correctly. I don't think I tried to import anything older than 2015 myself. However in the older flight-plans AIG was less consistent in the way they made these files, than they are today. I guess thise days their internal tools for building these flightplans, assist them much more and is one of the reasons these files are more consistent. The more consistent these files are, the better FV is at detecting the correct: airlines, aircraft and airports. EDIT: Regarding the download not working in FV it is because AIG have moved their flightplans to another server setup, and as of now they can't grant access to FV being able to download these. Hence you have to download them manually (outside of FV). But once downloaded you can import them (1 at a time). AIG don't support flight-plans for ALL airlines, and they are not updated for each airline for each year. While I don't know their internal process for choosing which airlines to update each year. I guess it based on multiple factors. E.g. how easy is it to obtain the data needed to construct a flightplan, when was the last time a flightplan for this airline was made, and perhaps even personal choice of the person who generate the flightplans. Hence me as a Dane/Scandinavian I would perhaps be more interested to add a flightplan for a Danish/Scandinavian airline, or an airline with whom I had flown in real life. So I guess many factors are in play to affect for which airlines they create flightplans- and how often these gets updated. But since their flightplan are used for AI traffic, another important factor is also for which aircraft do they have (AI/3D) models, and repains. The real-lift airline might have additional flights for aircraft for which there is no AI aircraft-models available, hence either they would have to omit this data from their AI flightplans of they would have to select a substitute aircraft (model).
  10. Thanks for your kind words. AIG (Alpha India Group) have moved all their flightplans and airline logo's to a new server-setup. However due to the popular demand to use their AI traffic in MSFS, these servers are running hot (their bandwidth is somewhat in the high end). As a result they can not at this time grant me access to these data to be downloaded from Flightplan Visualizer. I am therefor at this time "in a holding pattern" and will have to wait and see if this situation are going to change in the near future. Sorry for the delay 🙂
  11. I have recently upgraded Joy2vJoy to version 1.02 and it is available from DCS World's user download (see link below). The program is no longer deployed as an installer. In stead its simple a zip, you can unzip wherever you want it, and it contains all files (the vJoy driver must be downloaded/installed separately). In the old version mentioned here at the forum, you had to cycle all buttons on the throttle at start up to have the virtual-buttons in their correct state, this is however no longer necessary. Likewise you had to manually to push the "Activate" button after starting the program. In this new version it will automatic "Activate" as soon as you run the program. The program also accepts arguments/command-line parameters, so if you add -minimize to your short-cut the program will start minimized. The enclosed manual have be updated to describe the new arguments/command-line parameters, and the download link for the vJoy driver have been updated as well. https://www.digitalcombatsimulator.com/en/files/3321311/
  12. In the post yesterday I wrote that "AIG have changed the web-content", and that I had made some changes to make it work again. It turns out that the issue is a result of the provider that AIG is using, have made some server-side changes. What I had managed to update ("fix") in my development version of the software, was it being able to download and parse HTML-content (e.g. to see the names of available flightplans and list of defunct airlines). However I had not yet made my software able to actually download flightplan-files, and I still haven't. I am not the only one affected by this issue. AIG's own software (AI-Manager) is also currently not able to download flightplans either. Hence I am not sure if I will be able to address this issue until AIG gets to a workable solution (whatever that will be). On the same note this also affects the implementation of logo's in the current development version (as it can't download logo's either). So the release of a new version, might have to be postponed until after AIG reach a workable solution - and based on what that will be, I might have some additional work to perform.
  13. First of all, I hope you all had a Merry Christmas and Happy New Year. The last released version is 6 months old, and in those 6 months I've only posted a single post regarding the addition of airline logos. However that is not the only thing I have been working on in that time (those logos are just a small part). In this time I have been working on a completely new and huge feature to be added sometime in the future. However that new feature is far from being completed, and there is still a lot of tasks on the to-do list, and a lot of testing. So until I get to check-off more of those items, I will not go deep into details with this new feature - except the blurred teaser screen-shots below, "showing" a few of the added forms (and code running behind to drive them): Teaser screenshot (work in progress) Due to the break-out of Covid-19 and what happened as a result of this, the airline-industri have taken a huge impact. Airlines east and west have been filing for bankruptcy, and many of those airlines that are still alive, are nothing but "a shadow" of what they used to be. As a result of this uncertainty, AIG (Alpha India Group) did not release many new/updated flightplan in 2020 and most of 2021. However they are now back in the saddle, both with an updated version of their AIG AIM software (with support for MSFS), and they have again begun releasing new- and updated flightplans. Within the last week or so, AIG have changed the web-content (HTML) that I scan in order to locate new/updated flightplans, so the currently released version is no longer able to download flightplans (if you manually download them, you can still import them). In the current development version, it is again able to locate/display the flightplans to download, but I still need to perform a little more testing. I had planed to postpone a release till "the new feature" would be ready for a release. However as it is still in development, and a lot of flightplans have been updated and there is the mentioned problem downloading flightplans, I am considering a release in the near future (other things have been updated/fixed in the program, and the aircraft/airline databases have been updated as well). However before being able to release an update, I first need to workout how I can disable "the new feature" (but I hope for a release within the next 1-3 weeks, pending on how things pan out).
  14. Since writing the previous post, the number of logos to be bundled with the next version of FV have grown to +260 (beside the +1250 available thanks to AIG). So by far there are now logos for most of the airlines in use (as operator or carrier) in the bundled flightplans (still a few are missing). The logos obtained from AIG and those bundled with the program are stored in the new LogoCache folder (in AppData), and these are stored in a proprietary format with the ".CAL" extension. Even though if logo-files are named "correctly" (see below) it is not trivial to always find the correct logo for the correct airline. When trying to locate the correct logo for an airline, it might look for as little as 5 different/potential logo file-names or it might look for as much as +80 different/potential logo file-names (depending on how the airline is named). This ensure that for most part it will find the logo-file if it is there, but on the other hand it might sometimes locate a "false-positive" (a logo-file it shouldn't have used). In the airline database I have added some extra "hidden fields" that assist picking the correct logo, or in some cases NOT picking the wrong logo. I have tested A LOT of different airlines/logos, but I am sure there will be logos that are not matched even though a logo might exists, and there can be cases where the wrong logo is picked (but at least none of these issues are known at this time). If you do find cases where a logo from a different airline/company is picked, or a logo is not picked when it should be, please let me know so I can fix this in future versions. Add your own/missing logos If a logo for your favorite airline is missing, you can add it yourself. You simply create and crop the graphical logo in your graphic-program of your choice. The logo-file should be constrained to a maximum size of 550x250, but it can be smaller and have a different aspect-ratio. Both the logos bundled with next version and those from AIG are transparent PNG-files, but JPG-files should work as well (however not transparent, and not tested at this time). You simply copy your own logo-files to the LogoCache folder in AppData, and restart FV (as it only looks for cached logo-files when starting up). For the program being able to detect which logo-file to use for which airline, they need to be named in a special way. The first 3 letters are the ICAO-code, then an underscore ("_"), then the name of the airline (as spelled in the airline-DB, without spaces) and finally a fixed text of "_Logo" is appended. So for example a PNG-logo for British Airways (ICAO: BAW) should be called: "BAW_BritishAirways_Logo.png". AIG already have a logo for British Airways, but in FV its cached in a proparitary file-format with the ".CAL" extension, hence the cached AIG logo would be stored as "BAW_BritishAirways_Logo.CAL". If the same filename is available in multiple formats (e.g both as ".CAL" and ".PNG") the PNG-file will have a higher priority, hence it will be the one that is used. PNG-files have the highest priority, then JPG-files and finally the CAL-files. So if for some reason you don't like a particular logo (with a ".CAL" extension) you can simply make your own PNG/JPG-file with the same filename, and then this will be the logo that will be used by the software. Don't use the ".CAL" extension for your own files, as the program will expect these to be a different format than PNG/JPG-files. The airline database bundled with FV also contains "airlines" for airlines, companies, government and military without official ICAO-codes. In the database these are all added with a fictitious ICAO "---" and the 2 letter IATA-code will either contain "BZ" (Biz-jet), "PX" (Passenger), "FR" (Freight), "GV" (Government) or "ML" (Military). Many of the AIG Biz-jet flightplans for companies without official ICAO code, AIG will in stead use a "BJO" prefix (I guess it is short for "Business Jet Operator" or something along those lines). Likewise many of the AIG logos will instead use the "MIL" prefix for military or the "GOV" prefix for government. Hence the a logo for an airline with the ICAO/IATA-codes "---/BZ" will begin with a "BJO" prefix, logos for airlines with the ICAO/IATA-codes "---/ML" will begin with a "MIL" prefix, and finally a logo for an airline with the ICAO/IATA-codes "---/GV" will begin with a "GOV" prefix. An example of each: Logo for company "[---/BZ] AbbVie" should be called "BJO_AbbVie_Logo" (with PNG/JPG-extension) Logo for government "[---/GV] Armenia Government" should be called "GOV_ArmeniaGovernment_Logo" (with PNG/JPG-extension) Logo for military "[---/ML] US Army" should be called "MIL_USArmy_Logo" (with PNG/JPG-extension) How logos are cached (disk or memory) The +260 logos bundled with the next version of FV, will (if you choose so during installation) always be installed into the new LogoCache folder, as these are not available online (hence the program cannot download these at run-time). In the first implementation of this new feature, all downloaded (AIG) logos would always be stored in the LogoCache folder, if download of these was enabled (which it is by default). Since I have added a setting that decide if these downloaded logos should be cached to disk. By default the settings dictate that logos are to be download, and they are to be cached to disk (so they only needs to be downloaded once). If you disable that these logos should be cached to disk, they are in stead cached to memory. In that case when looking at the airline-info for a particular airline (e.g. British Airways) the AIG logo is in stead downloaded to memory. To reduce the need to re-download the same logo multiple times while the program is running, these logos will remain cached in memory (for at least 15 minutes). In normal operation people will not be looking a many different airlines (hence only a few logos will be cached in memory at the same time). Unless disk-space is a big problem for you, I suggest that you cache these logos to disk, as this will will reduce the need to re-download these, and they will still be available if there is an issue connecting to the servers (don't forget you can move the physical LogoCache folder to a separate drive, simply using symbolic-links in Windows - I have previous posted another note regarding symbolic-links).
  15. For me it depends on the aircraft. For the Cesnna 152/172 its way to sensitive after SU5, but for the TBM its ok (using Thrustmaster HOTAS) EDIT: But only elevator trim. Aileron trim is fine.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use