Jump to content

pellelil

Members
  • Content Count

    169
  • Joined

  • Last visited

Community Reputation

34 Excellent

1 Follower

About pellelil

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. For version 1.18 of Flightplan Visualizer (FV) I had something entirely different planed, and I have been working hard on adding an entirely new set of features, where I am still a long way from being able to release anything, as it contains a lot of new data, forms, and functionality, where I also will have to do a lot of "investigation" and testing - at least I know how to spend my time throughout the long, cold, and dark winter nights 🙂 Those future plans were pushed a bit in the background (for another release), and in stead version 1.18 became all about the support for MSFS, a
  2. There was a type on the previous post. A few places I wrote "MSFS-UserAirportInfo.xml". Just to clarify it is an underscore that the program adds to the entered FilePrefix. So the correct name is "MSFS_UserAirportInfo.xml".
  3. Flightplan Visualizer (FV) have not been made to be used with multiple different simulators at the same time. However now that MSFS is here and Pete have managed to update MakeRunways (MkRwy) so it can also scan the scenery files of MSFS, I have improved how its more easy to use FV with multiple simulators. I have added a couple of command-line arguments that can be set in your short-cut icon used when starting FV. As I showed in the previous screenshot, in settings you can now quickly switch between different sets of MkRwy-files. However using the new command-line argument /MkRwy you can now
  4. In the next-version the entry-field in settings have been replaced with a combo-box, which "remembers" the last few paths you have been using, so its more convenient to switch between MkRwy -files for different sims (e.g. "P3D" and "MSFS"):
  5. Per say Flightplan Visualizer (FV) have not been made for a particular Flight Simulator. However it relies on the output from Make Runways (by Pete Dowson) which is able to scan installed FSX/P3D scenery, and extract information about Airports (including runways, gates and frequencies). Likewise the bundled (pre-imported) flight-plans are intended for AI traffic in FSX and P3D, but who are to say a person flying in MSFS cannot use these as inspiration, as they are based on real-life flight-plans. So in theory you can use FV with any sim, if you simply want to use it to find inspira
  6. Good catch 🙂 You are true. But I have seen it in the past also, so I just wanted to hear if there were something "bad" in the new versions that made users "downgrade" to previous versions. Anyhow the program is not build to allow for a downgrade. In some cases you can downgrade to a previous version without any issues. But there is no guarantee that its possible. In most cases (except for these mandatory versions) newer versions of the program are able to read old file-formats of the various data-files, however older versions are in many cases not able to read data-files using a ne
  7. Every time I have released a new version I have noticed that there are still a few download of the old one. In this case I that estimate version 1.16 have been downloaded 10-20 times since version 1.17 was released. I am guessing that most of these are people who have just come across the version 1.16 and downloading it, not knowing there is a version 1.17. Also I can be someone who want do have some of the older flightplans, that were made obsolete (hence not included) in version 1.17. Anyway I would like to hear if any of you ever have been downgrading to a previous version and i
  8. Version 1.17 have just been released, and it can be downloaded from AVSIM using this link: https://library.avsim.net/esearch.php?CatID=p3dutil&DLID=218897 Version 1.16 is a mandatory version that you must install and run prior to installing version 1.17. 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.17 have also been uploaded to YouTube and link for this video is also available via the help-menu. Below is the entire list of
  9. The video for version 1.17 was uploaded last night. I suggest that you at least have a look at the first part as it shows how to make sure all of your flightplans gets updated in case you have them in multiple sub-folders. Remember that both version 1.16 and 1.17 are considered being mandatory. So if you have not yet been enabling all of your 1.16 flightplan sub-folderes you should do so prior to installing version 1.17 (when it becomes available).
  10. If you have enough free space on your C-drive, then there is no need to read this post, as it is aimed at those who need/want -to free the space occupied by Flightplan Visualizers (FV) data-files on the C-drive. Most of these data-files does not take up that much harddisk-space, however the cached map-tiles can easily take 1-2 GB of space. This tip is not only for FV, but can be used for other programs as well. E.g. I had the same issue myself with DCS (Digital Combat Simulator), where I was able to release +200 GB on my C-Drive, simply by moving my entire DCS installation from my C-drive to a
  11. You have a plan … until you make a new one 🙂 I did initially not plan to include any of the load-sheet code that I have mentioned previously (the reason for why the form for creating an aircraft contains so many weight/load-fields). However while refactoring some code I began working on it anyway, as it allowed me to “shape that code for the future use” I had planned, and the more I wanted to test out this code, the more code was written to handle it. Its still in its early stage, and as of now only visible in the Leg-info report that can be generated from the leg-info form:
  12. Did a graph showing the difference between the real MLW (Max Landing Weight) from the aircraft-database in relation to the estimated MLW. As you can see the worst case is more than 20% "wrong" (greater than 1.2), but on average the estimated MLW is within 3% (absolute deviation) of the real MLW. As I wrote yesterday it will always be best to enter the correct weight-data (if you can obtain the data), but otherwise this estimation can be used (at least the estimated values are better than zero-values). As explained before these data are of no use at this time, but I plan to add a feature in a f
  13. We are getting closer to a release of version 1.17. Feature-wise I don't have more items planed for this version. But I still have a few more tests to carry out. Also I will have to record the video for version 1.17, and finally build the installer. So if all goes well, I hope for a release within a week or so. When you create a user aircraft you should make sure all the data including the weight-constraints are set correctly. However obtaining the correct data can be a task in itself. As a minimum you HAVE TO enter both EOW (Empty Operating Weight) and MTOW (Maximum Take-off Weigh
  14. First helicopter have been added 🙂 FV have been made with commercial (pax/freight) aircraft in mind, but during development more GA/BizJets have been added, along with various utility and military aircraft. Now the time have finally come to helicopters. In all aspect they are handled like aircraft, with the exception that the engine-category is set to "Heli", and in stead of a "Wing-span" (Dimensions) it have a "Rotor diameter".
×
×
  • Create New...