!! Windows 7 no longer supported !!

As Microsoft will stop supporting Windows 7 on Jan 20th we will be unable to test any of our
products on that platform. It may work, or it may not, but no guarantees from our side. 

Jump to content

pellelil

members
  • Content Count

    117
  • 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. It turns out that the newer version of MkRwy write the elevation as a floating point where the old used integer: Version 484 write it as: <Altitude>630</Altitude> Version 4891 write it as: <Altitude>629.92</Altitude> So next release of FV will fix this issue no matter if you use 4.84 or 4.89.1 🙂
  2. I had what seamed to be a bug in FV, that I spend a large part of the day to track down. It turned out that when I used MkRwy to scan my scenery, it did not report back the correct elevation values for the airports (e.g. the elevation of UUEE was reported as 62992 ft, which resulted in the leg-search feature not working correctly). I found out returning to version 4.84 of MkRwy, the airport elevations were once again correct. So if you run into any issues, please check airport elevations.
  3. Its still WIP (Work In Progress) but I am working on the filter, and what I told would not be in version-1, will probably be in version-1 anyway 🙂 As of now I simply use an extra combo-box to test it. Here you can see I have entered the filter-text "west,provider=aig" meaning: filter the combo-box to only show flightplans with "west" in the name, where the provider is AIG (multiple filter-text can be entered, separated by comma). Beside "provider" it currently also work with "author" and "season". Plan to add "year" and "folder" also, so you would write something link: "west,folder=AIG,season=summe,year=2008" (or shorthand: "west,f=AIG,s=su,y=2008"). I guess most users will simply enter a short text such as "west" to only show flightplan with "west" in the name, but if you want to you can make it more complex: I already have the data (however currently not entered into the XML) for the DC-3, DC-6, IL-86 and L-188 so I expect these will be included in the next release along with some more.
  4. Aucery its fine you "challenge me" with your suggestions 🙂 Anyhow I don't think I would implement this feature, as I think it is not something that most users would use. This feature will only be useful for users who chose split their flightplans into many sub-folders (which I don't think many would do). Personally I only have 2 sub-folders ("Commercial" and "BizzJet"), beside some backup/test -subfolders I never enable, and I would rather want to enable/disable these folders as needed. When you disable a folder (e.g. in my case disabling "BizzJet" most of the time), it means that the flight-plans in this folder are not loaded, which results in a faster start up time, and less memory consumption. However it also means they are excluded from my search (e.g. using Leg-Search and they are not included in the traffic in/out of the airport shown in the Airport-info form). However I do realize that the combo-box at the bottom of the screen for choosing flightplans is needing a filter of some kind. As I recall the last released version came with 629 flight-plans, and you tell me that you have 1600 bgl-files (to convert to flight-plans), so finding a particular flight-plan may require some scrolling up/down. So I am thinking of adding a "filter" entry-field where you can enter a wild-card, e.g. based on your example: "AIG*Su08", which would then search for all flightplans beginning with "AIG" and ending with "SU08" (case-insensitive). This search would filter the flight-plans that are shown in the combo-box (e.g. filtering by "LUX" you would see "Cargolux" and "Luxair"). I have some idea as how to make this filter more complex in the future, where you for instance could search for flightplans in a particular sub-folder, or made by a particular provider/author, but this will not be in "version-1". Anyhow it will NOT be a "quick-fix" to implement a filter, because of the way the flight-plan combo-box is currently implemented, and it raises some questions as when the "filter" should automatically be cleared (e.g. when you import a new flightplan the filter would have to be cleared, to ensure that the newly imported flightplan should be made visible both in the combo-box and on the map). Thanks for the data on the L-1011 however I am not sure if I can add it as 3 separate aircraft, as they have the same ICAO/IATA-codes, and I am not keen on using fictitious IATA/ICAO-codes if I can avoid it. So perhaps it will be added as a single aircraft (I'll see what I can do): <AircraftInfo ICAO="L101" IATA="L10" Name="Lockheed L-1011-101/200/500 TriStar"> EDIT: It seams the 100/200 share the same IATA, but there is a separate IATA for the 500 pax and the freighter version: http://www.airlinecodes.co.uk/arctypes.asp
  5. In the Flightplan menu you find the menu-item Enable/Disable flightplans. Here you can add as many (flightplan) sub-folders as you want. The root folder is always "enabled" (meaning flightplans in the root-folder are always loaded. However each sub-folder can individually be enabled/disabled. Whenever you import flightplans they will be imported into the root folder, however then you can simply move them to the sub-folder you want to. Personally I have all my commercial (AIG) flightplans in a sub-folder called commercial, and I have all my bizz-jet flightplans in a sub-folder called "BizzJet". Normally I only have my commercial flightplans enabled, however if I want to I can enabled my BizzJet folder: If you want to, you can simply make a "Summer 2008" sub-folder and move all your "Summer 2008" flightplans into this folder. Then simply enable/disable this sub-folder as you need. Keeping the root folder empy (by having your flightplans in 1 or more sub-folders) gives an added bonus of always having the new/updated flightplans installed with the updates to the program. When you install an updated version of FV it comes with new/update flightplans that you can choose to install or not. If you choose to install these, they will install into root-folder, however they will only do so if the root folder does not already contain a flightplan with the same name. By having all your flightplans in sub-folders, this will never be the case. I suggest you have a look at this video, describing how to use the enable/disable feature:
  6. Aucery, in next version you can right-click an airport and toggle it on/off as a favorite. The check-mark shows if it currently marked as an favorite or not: In case you don't already know, in the current version you can actually toggle airports on/off as favorites from within the "Search Airport" form (CTRL+A). You simply search for something and then you can right-click the airports that are listed:
  7. The 10, 20 and 30 series are included as well. Here are the types included in the next update: Douglas DC-8-10 Douglas DC-8-20 Douglas DC-8-30 Douglas DC-8-40/43 Douglas DC-8-50/55 Douglas DC-8-50/55 Freighter Douglas DC-8-61/62/63 Douglas DC-8-61/62/63 Freighter Douglas DC-8-71/72/73 Douglas DC-8-71/72/73 Freighter I doubt it will be possible for users to add their own aircraft, as I need to control the "quality" of the data. In many cases in the software you only see IATA/ICAO-codes and names of the aircraft, but beyond this a lot of extra data are included as well. Such as various classifications need for some planed features, various performance data needed for gate/rwy-requirements, weight-constraints, cruise-speed for calculating flight-times, data used to match the name of the aircraft in the flight-plans with the types (e.g. being able to work out that a "744BCF" is actually a "747-400 F") and many more. If you or other users want to assist adding aircraft, you are more than welcome to gather all the info you can find of these aircraft to add, and post it here at the forum and I will happy add them in the next release. Here is an example of the data I today add for a single aircraft (I have removed the fields I handle myself internally). Size is in meters, weight in lbs, range in NM, alt in feet, speed in knots, gate-radius in meters, rwy requirement in feet and fuel-burn in lbs/hour: <AircraftInfo ICAO="DC81" IATA="" Name="Douglas DC-8-10"> <Wingspan>43.4</Wingspan> <Length>45.9</Length> <Height>12.92</Height> <Range>3760</Range> <MinGateRadius>22</MinGateRadius> <EmptyWeight>119797</EmptyWeight> <MaxTakeoffWeight>273000</MaxTakeoffWeight> <MaxLandingWeight>0</MaxLandingWeight> <MaxPayloadWeight>46103</MaxPayloadWeight> <MaxFuelWeight>153250</MaxFuelWeight> <MaxZeroFuelWeight>0</MaxZeroFuelWeight> <Crew>3</Crew> <MaxPassengers>177</MaxPassengers> <Performance> <MaxAlt>37000</MaxAlt> <CruiseAlt>35000</CruiseAlt> <CruiseSpeed Speed="480" Unit="TAS" /> <MaxSpeedBelow10K Speed="250" Unit="IAS" /> <MinRwyTakeoff>7200</MinRwyTakeoff> <MinRwyLanding>5300</MinRwyLanding> <FuelBurnCruise>11500</FuelBurnCruise> </Performance> </AircraftInfo> Adding a right-click menu-item to toggle airport favorite on/off would be possible (thanks for the suggestion). I doubt many users will need the options to have many "groups" for airport favorites. You can use the hint-text (in the AIrport Info view) to enter the name of the scenery-creator (e.g. Aerosoft). Then you can use the Search Airport form (CTRL+A) to find these airports. E.g. this form have a "Show" combo-box where you can set it up to show this Hint-text, and use the "Must have Hint-Text" check-box to only show airports with hint text (in the search window), and/or use the "Search in Hint-text" check-box so you for instance can search for all airports where you entered "Aerosoft" in the hint-text. Regarding the Airlines these are manually updated, and its a huge job trying to stay up to date. For each release I import the latest flightplans from AIG, and doing so I come across missing/wrong/defunct airlines that I will then add/update/mark as defunct. So don't expect to see changes to mil. airlines. Again if you or others come across data that are wrong or missing please inform me using the forum to I can correct any mistake or add missing airlines. Here is an example of the data I add for airlines (I have some extra fields for internal/future use that I have excluded): <AirlineInfo ICAO="NOA" IATA="" Name="NorOntair"> <Callsign>NORONTAIR</Callsign> <Iso3Country>CAN</Iso3Country> <CommenceDate>19710101|000000</CommenceDate> <CeaseDate>19960101|235959</CeaseDate> <LoadFactor>0.887</LoadFactor> </AirlineInfo>
  8. DC8 (pax/cargo) will be included in next release, together with better detection of non-standard Boeing names (e.g "744" in stead of "747-400", "736" in stead of "737-600" ...)
  9. A bug regarding the new "User-Airline" feature have been reported (thanks Bruce). If/When you add user airlines, the callsign you enter will be replaced by the name of the airline, when you save the new user-airline. This bug have been fixed in my current development versions of the program. However in the mean time if any of you run into this issue there is a "work-around" until the next versions will be released. When you have added the user airlines you need, shut down FV and navigate to the user folder (if you are not sure where it is, use the "Open UserData-folder" menu item, in the main-menu before shutting down FV). Here you can manually edit the UserAirlineInfo.xml file and correct the callsign. This callsign will remain until you edit this particular user-airline from within the program. If doing so the callsign will again change the callsign into the name of the airline. The bug will show its nasty face when the program validated the data entered by the user when saving a particular airline (only the edited user-airline will be affected).
  10. Hi Aucery No matter what, flight-plans have to be imported one-by-one, as you have to manually "fill in the blanks", in form of being sure the correct airline is selected (both for the entire flight-plan, and as carrier/operator for each aircraft). Also the program (at least in my own opinion) does a fairly good job detecting the correct aircraft-types based on the aircraft names, however when importing a flight-plan you should verify that aircraft-types have been correctly identified (hence another reason for it to be one file at a time). Anyhow, I don't know how to decompile the traffic bgl-files (I have never looked into this), so for the moment the only way to do this is via AIFP or AIG Traffic Tools. If either of these can decompile a BGL, being called with parameters, I would be able to execute these from within FV, but even if, it will still be a file-by-file import (hence in your case 1600 imports). Regarding the 2nd post, FV does "know" the B747F, however it currently does not catch it from the name "B744BCF". I will make sure next versions will. The DC-8 however is not included in the data-files, hence while its not being detected, I'll see if I can find all the info I need in order to add it as well.
  11. I could see the "usefullness" in a shared cockpit where you could have a virtual captain/FO sitting next to you visually performing that action performed by the person by whom you share the cockpit, but then again you don't know what the person is going to do, hence the animations would have to be delayed until that person had already performed the action, hence the "avatar" would lag behind.
  12. Mathijs, regarding visible flight-crew I find the FA on the camera in the A319-A321 bringing me my coffee is a nice touch (haven't checked if shes in the A330 as well), but I find the person on the CRJ camera a bit scarry 😉 EDIT: On a serious note - Personally I would not like to offer 5 fps on 3D flight-crew (beside the cockpit the internal of all my aircraft could be void, as it is not where I spend my time). The day we have +60 FPS everywhere, anywhere all the time, then yes. As of now I'd rather spend those 5 FPS on AI around me, 3rd party airports and what else is taxing my system.
  13. Version 1.14 have just been released, and it can be downloaded from AVSIM using this link: https://library.avsim.net/esearch.php?CatID=p3dutil&DLID=215448 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.14 have also been uploaded to YouTube and link for this video is also available via the help-menu. Here is a list of the changes in version 1.14: - Flightplan file-format was changed, to accommodate changes to the airline-data. In previous versions the airline ICAO-code had to be unique, hence not allowing old defunct airlines still remaining in the data-file when a new airline would be issued the same ICAO-code (now they can both exists, and many of the defunct have been marked as defunct). On start-up old flightplans in enabled folders will automatically be updated to the new format. If you have sub-folders containing additional flightplans, you should make sure these are enabled, in order to have these updated as well. Once they have been updated you can go ahead and disable these sub-folders again as you please. Its now possible to add user defined airlines, in case you want to add you own fictitious airlines (e.g. VA's) or you want to add airlines missing in the official data-files that I supply with the program (if this is the case, please notify me, so I can add these in the next release of the program). "Favorite aircraft" have been renamed into "Favorite aircraft-types", as it is the "types" of aircraft you mark. You don't mark a particular aircraft/cofiguration (like the PMDG B737-800 NGXu) as your favorite, but rather the "type" (B737-800). The file containing the (active) favorite aircraft-type selection was renamed as well (you don't have to do anything, the file is automatically renamed on start-up). Added a new Unit-Conversion form, letting the user convert units of: Speed, Lenght/Distance, Weight/Volume, Pressure and Temperature. The Weight/Volumne conversions is a bit special as it lets the user convert between weight (kg/lbs) and volume (liter/gal), thanks to a Fuel Density that defaults to 0.785, but can be changed by the user. All search-forms (seaching for airport, aircraft and airline) was changed to ignore whitespeaces (e.g. "airBaltic" vs. "air Baltic"), and ignore diacritics (e.g. "Aerolínea" vs. "Aerolinea"), making it more easy to find what you are searching for in one go. The airline search-form will by default exclude airlines that have been marked as defunct. However a new "Include defunct" check-box have been added to the form, allowing you to include these (who am I to say you can not still use "Air Berlin", "Monarch" or "Thomas Cook" flightplans if you want to). Added 3 new columns to the airline search form showing commence/cease-date, and wheter or not the airline is "in use" (as carrier/operator by any of the active fligthplans). State is now by default excluded when using the airport search form, which make it a lot more convenient to find airports in the city of "New York". State can still be included in the search by choosing a different search-type using the combo-box in the upper/right corner. When Flightplan Visualizer needs for perform potentially lengthy operations it will spread the workload over the available cores of the CPU. However if you want to limit which cores it uses you can now set the affinity-mask in the settings form. The splash-screen shown when the program starts, and when reloading active flightplans was prevoiusly always shown on top (top-most), but if you find this anoying it can now be disabled in settings. Fixed: Warnings/errors regarding loading flightplans were only displayed at start-up. Now they are shown whenever all active flightplans are loaded (e.g. after having enabled a sub-folder). Data: The airline-data got a major update, and a bunch of new airlines were added, and the data for MANY others were updated. It is a manual process to update these, almost as funny to do as to watch paint dry 😉 Data: A few countries had a wrong- or no sub-region code, so these were fixed/updated. As usual, if any of you spot any erros, or missing data, please use the forum to notify me. Data: Additional info added to the aircraft-data (in preparation for some future plans). Flightplans: All flightplans bundled with the installer have been updated to the new file-format. Flightplans: Thanks to Ryan Carson (RCAI) for allowing me to bundle the installer with a few of his flightplans, so the installer comes with the very first winter 2019-2020 flightplan. Flightplans: The good people over at AIG (Alpha India Group) have been VERY busy since the last release, hence the installer comes with +130 new pre-imported flightplans, bringing the total to 629. This update concludes Summer 2019, and AIG already have the first Winter 2019/2020 flight-plans in beta-test.
  14. Or simply never though about it. I have a profile with eye-candy for the very few times I do VFR, and another I use most of the time for Airliners. But I never though about using a profile for accelerated flights, but I will have one now 🙂
  15. After updating to 2.0.0.1 I tried to do a flight from ENGM to ENBR (ENGM/01L ATLAP5A ATLAP N623 PESUR PESUR3N ENBR/17) in the CRJ 900. I used the Navigraph charts many times with out any problem, but after I had landed at ENBR I tried to open the airport chart at which point I had a CTD. Here below are the 5 logged events (in order) all logged within 7 seconds (sorry its in Danish - but ask if you need a translation). Error 20:28:35: Program: Prepar3D.exe Framework-version: v4.0.30319 Beskrivelse: Denne proces blev afsluttet pga. en ubehandlet undtagelse. Undtagelsesoplysninger: undtagelseskoden c0020001, undtagelsesadressen 00007FFF1674A839 Stak: Error 20:28:36: Navn på program med fejl: Prepar3D.exe, version: 4.5.13.32097, tidsstempel: 0x5d8abf93 Navn på modul med fejl: KERNELBASE.dll, version: 10.0.18362.476, tidsstempel: 0x83c3d83a Undtagelseskode: 0xc0020001 Forskydning med fejl 0x000000000003a839 Proces-id 0x730c Programmets starttidspunkt 0x01d5aa027b0952ae Programsti: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe Modulsti: C:\WINDOWS\System32\KERNELBASE.dll Rapport-id: 9de07869-5c1c-4b65-90f7-fd865766910d Fuldt navn på program med fejl: Relativt program-id for program med fejl: Info 20:28:38: Fejlbucket 1486591396300563378, type 4 Hændelsesnavn: APPCRASH Svar: Ikke tilgængelig Cab-id: 0 Problemsignatur: P1: Prepar3D.exe P2: 4.5.13.32097 P3: 5d8abf93 P4: KERNELBASE.dll P5: 10.0.18362.476 P6: 83c3d83a P7: c0020001 P8: 000000000003a839 P9: P10: Tilknyttede filer: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA6A3.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA9F0.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAA10.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAA1E.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAA3E.tmp.txt Disse filer er muligvis tilgængelige her: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_b61cceac605ad4e6307f25302bbb9f8e47c36db_1793b743_7e591361-d0df-4c1f-b9fa-7d406fb7b609 Analysesymbol: Søger efter løsning igen: 0 Rapport-id:9de07869-5c1c-4b65-90f7-fd865766910d Rapportstatus: 268435456 Hashbucket: 14653dbb234362b0b4a16effa6a5a3b2 Cab-guide: 0 Error 20:28:40: Navn på program med fejl: Prepar3D.exe, version: 4.5.13.32097, tidsstempel: 0x5d8abf93 Navn på modul med fejl: KERNELBASE.dll, version: 10.0.18362.476, tidsstempel: 0x83c3d83a Undtagelseskode: 0xc000041d Forskydning med fejl 0x000000000003a839 Proces-id 0x730c Programmets starttidspunkt 0x01d5aa027b0952ae Programsti: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe Modulsti: C:\WINDOWS\System32\KERNELBASE.dll Rapport-id: d492298e-0109-491b-ab62-b24d0df92f6d Fuldt navn på program med fejl: Relativt program-id for program med fejl: Info 20:28:42: Fejlbucket 2153538199713445284, type 4 Hændelsesnavn: APPCRASH Svar: Ikke tilgængelig Cab-id: 0 Problemsignatur: P1: Prepar3D.exe P2: 4.5.13.32097 P3: 5d8abf93 P4: KERNELBASE.dll P5: 10.0.18362.476 P6: 83c3d83a P7: c000041d P8: 000000000003a839 P9: P10: Tilknyttede filer: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB52A.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB857.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB878.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB887.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB8A8.tmp.txt Disse filer er muligvis tilgængelige her: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_55af6bf75d1d45f6f2a6a6b05be2affe8811bf5_1793b743_6d5f1749-f4d0-413b-8949-3832088e4c7d Analysesymbol: Søger efter løsning igen: 0 Rapport-id:d492298e-0109-491b-ab62-b24d0df92f6d Rapportstatus: 268435456 Hashbucket: c9ec300a48050617fde2e7952c2775a4 Cab-guide: 0
×
×
  • Create New...