Jump to content

QuaxTheSnoopie

Members
  • Content Count

    53
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

10 Neutral

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

Recent Profile Visitors

606 profile views
  1. After I found that .pln files are simple xml files, I was able to do some research on the generated .pln files with Notepad++. If I add an airport as an intermediate waypoint, importing the .pln file in P2A results in an error, no matter what flight planner I used to export (loading the native P2A format .vbs works indeed). Just a sample: LFNC - LFNA (airport as intermediate waypoint) - LFNC throws error: ... <ATCWaypoint id="LFMR"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N44° 23' 14",E6° 36' 33",+003714.00</WorldPosition> <ICAO> <ICAOIdent>LFMR</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="LFNA"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N44° 27' 14",E6° 2' 12",+001966.00</WorldPosition> <ICAO> <ICAOIdent>LFNA</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="LFNC"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N44° 42' 1.99",E6° 35' 57",+002963.00</WorldPosition> <ICAO> <ICAOIdent>LFNC</ICAOIdent> </ICAO> ... LFNC - OKTET (waypoint) - LFNC works: ... <ATCWaypoint id="LFMR"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N44° 23' 14",E6° 36' 33",+003714.00</WorldPosition> <ICAO> <ICAOIdent>LFMR</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="OKTET"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N44° 29' 6",E6° 34' 10",+000000.00</WorldPosition> <ICAO> <ICAOIdent>OKTET</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="LFNC"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N44° 42' 1.99",E6° 35' 57",+002963.00</WorldPosition> <ICAO> <ICAOIdent>LFNC</ICAOIdent> </ICAO> ... I proofed this against more complex flight plans in which I replaced the intermediate airports by navaids (manually in Notepad++, afterwards in several flight planners and P2A itself), the generated .pln files are taken by P2A import as soon as the last intermediate airport is replaced by a navaid or waypoint. I remember that I was able to import such flight plans with "intermediate airports" formerly in P2A, but I don't know in what version as I didn't install every update.
  2. I used to plan my VFR flights in Plan-G, export them (.pln for FSX/P3D), then import into P2A. In 2.6.2.3 R2 this isn't possible, I get message "Unable to import flight plan. Please ensure it is the proper form". So I did some tests exporting and importing between Plan-G, Littlenavmap, P2A. While I could import anything in Plan-G and Littlenavmap (the last with warnings about "missing starting point" = runway), I could import no newer flight plans in P2A. I thought to create a topic in the Plan-G forum, but then I created a short flight plan with three points LFMR - LFNA - LFNC in P2A, exported it there as P3D .pln and did a re-export of this .pln in P2A and got the same error. In the P2A_2020_Trace files, I see entries of the same type: Error in BuildFPRoute System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource) at P2A_2020.FltPlan.BuildFPRoute(Boolean CalcTOD) Error in FltPlan ImportFromP3DFile RteType System.NullReferenceException: Object reference not set to an instance of an object. at P2A_2020.FltPlan.ImportFromP3DFile(String filePath) More strange: I can import older Plan-G flight plans into P2A So where to look what's wrong ? P2A, Plan-G, Littlenavmap ? Or a mixture of all of them as they get new functionalities with each release ? But in P3D (4.5 HF2), I can import all of my test exported .pln files. Is P2A a little bit to harsh while checking the import ? (I prefer Plan-G for VFR initial flight plan creation because of its bigger OpenTopo map).
  3. What I use for VFR: already mentioned above: https://www.timeanddate.com/weather/ to search for an appropriate month (yesterday/past weather -> select month -> somewhat below "show weather for:" to select a specific day of the month Second source https://www.wunderground.com/ "Search Locations": takes ICAO airport code ! Select tab "HISTORY" and enter a specific day derived from timeanddate. in the lower part "Daily observations" https://www.windfinder.com : nice map with clickable locations, but not all have history data and only the last week available
  4. In my environment, many airport taxiways are incomplete (missing taxiway pieces). I had these "incomplete taxiways" before, while modifying airports years ago with the ADE tool and found hints that this results from a nonstandard mesh (Pilot's Ultimate). So I have to check and optionally rework them. I take your advice not to make them pretty - eases my work. And check if they have a hold short point before every crossing of the runways. Thanks for the info.
  5. Just a question regarding the above picture: I see more than one holding point for 15R. Do I understand it right that this is not a fault and how do pilot and ATC handle these multiple holding points ? Do I have to request clearance on every holding point ? And it is not necessary to connect the taxi point on the runway entrance with a taxi point on the runway end (as I see simply the red line of the runway) ? In addition: It's stated that I shouldn't set a further taxi point between holding point and runway, but sometimes the holding position markings drawn on the ground are not straight from the runway entrance (e.g. taxiway like a "U" with holding point on the upper right side and runway entrance on the upper left side). Can I set two holding points for such an entrance, one on the drawn holding position markings, then some taxipoints, then a last holding point before the runway ? And what would ATC do ? Ignore the additional holding point ? Or request clearance on both ? Or isn't this the correct solution at all (on the photos in the user guide, the hold short points are mostly after the holding position markings, just before the runway) ?
  6. Just my experience: ADE modifications can be very difficult, as it does not only modify gates or taxiways, but the whole environment. Especially for bigger payware airports, editing with ADE is much more complicated as P2ATC taxi maintenance. And thanks for the answers above, I had the same questions...
  7. Found this thread while searching for a light vehicle to explore airports in an easy way by keyboard only, as the Bell 47 as a heli needs action on my yoke an pedals. I remembered that I bought the Franz Paramotor some years ago for FSX but didn't expect to work. Today, after reading this, saw that I could still download it from simmarket, so gave it a try - and voilà: works like a charm (Prepar3d V4.5 HF2). Installation was simple as the installer asks only for the "FSX installation directory", I selected the Prepar3d V4 main folder. Now the last hours jumped from airport to airport for short starts and circles, funny again as before in FSX 🤣 Thanks for this thread !
  8. Same question here, as I use Little Navmap for planning, P2A as ATC replacement (but for P3D). In Little Navmap, I set "Save waypoints for approaches" and "Save waypoints for SID and STARs" to load the flightplan in P3D. P2A loads the flight plan, throws some errors for Little Navmap created own user waypoints unknown to P2A (to represent SID/STAR/Intercepts) but I can file the flight plan in most cases. Although it's not easy to understand why in these 38 years after the first release of a MS Flight Simulator neither Lockheed Martin nor MS/Asobo have enhanced the old point-to-point flight plan definitions...
  9. As I read the web about P3D V5 and MSFS 2020, most discussion talks about the viewing aspect: nice sky, nice clouds, wonderfull landscapes. Comparing both sims, what about the flight engine, navigation, ATC ? Example 1: P3D V4 doesn't support ATIS over VOR frequency (comes through NAV audio), asking Skyvector: YPDN: DARWIN ATIS: 112.60 on VOR DN YMML: MELBOURNE ATIS: 114.10 on VOR ML KBWI: BALTIMORE D-ATIS: 115.1 on VORTAC BAL couldn't be used in P3D V4, possible in P3D V5 / MSFS ? Reading Flysimware Falcon manual, searching for "limitations": - Due to simulator limitations both batteries will charge/drain at all times. - MAG/TRUE swap: Due to flight sim limitations these buttons are not independent. Same for the compass card. - PITOT (Pilot and copilot pitot switches. Due to limitations both are synced together) Can I expect such limitation resolved in the newer sims ? Or runs a decade old engine under the hood that no one likes to touch - not in the past, not now and not in future ? Compared with a car getting every year a new body but runs with a twenty year old motor (=FSX) ? Helicopters: in FSX,I bought the Dodosim that gave me many helicopter-specific enhancements of the flight model. There are enhancements as HTR. Anything of this integrated into the new sims ? Integrated support for Navigraph updates ? Do I expect too much ? 38 years after FS 1.0, 14 Years after FSX ? In five years: P3D V7, MSFS 2025 - but the same old limitations ?
  10. I've learned three lessons over the years: - Never touch a running system - Don't fix it, if it ain't broken - Never be the first, let others get a bloody nose So I wouldn't recommend neither MSFS nor P3D to the thread creator, instead stay on P3D V4.5 some time until MSFS and P3D V5 are more stable. As the thread creator owns P3D V4.5, I think there's no absolute necessity to upgrade to P3D V5. And MSFS is a very new thing and may need a little more development. Just my opinion...
  11. After some research in the web, P3D V5 and MSFS seem to be the same choice regarding - stuttering - crashes - hardware problems If you find a real reason, say "a pilot's must have" for P3D V5 or MSFS, please post it. Until then, I rely on P3D V4.5 HF2 as it run solid and allows me more flying than fiddling 😁 (and all my addons are already paid 🙃)
  12. Hi, until recently, I used Plan-G, now I'm in the transition to Little Navmap and look for a function to highlight or filter my preferred airports. What I mean: In Plan-G, it's possible to create a list (.txt file) with ICAO IDs that will be marked (means: highlighted) on the map with another color as the other airports. I read the topics "Add Custom Airport?" and "Show only addons (airport)" and excluded fsAerodata, ORBX Vector and ORBX Germany North/South (otherwise every german airport is marked as "add-on"), but still see many "add-on airports" around the world that I didn't buy and would never fly to, maybe they come from some ORBX regions or whatever. Excluding the complete ORBX stuff isn't appropriate, as ORBX stores its airport BGLs (e.g. ORBX LOWI) below their top level directory. So can I mark or filter or highlight my preferred airports in Little Navmap ? Maybe I've overseen something in the manual ?
  13. Maybe useful for you: Dassault DA50 Falcon 50 Checklist and Performance
×
×
  • Create New...