Jump to content

XP11 Allgemeines

Allgemeine Diskussionen zu X-Plane 11

786 topics in this forum

    • 2 replies
    • 358 views
    • 8 replies
    • 734 views
    • 1 reply
    • 341 views
    • 0 replies
    • 359 views
    • 3 replies
    • 410 views
    • 14 replies
    • 1196 views
    • 4 replies
    • 387 views
    • 5 replies
    • 408 views
    • 7 replies
    • 472 views
    • 10 replies
    • 530 views
    • 7 replies
    • 461 views
    • 12 replies
    • 459 views
    • 2 replies
    • 190 views
    • 9 replies
    • 749 views
    • 2 replies
    • 257 views
    • 1 reply
    • 295 views
    • 1 reply
    • 232 views
    • 4 replies
    • 460 views
    • 7 replies
    • 657 views
    • 4 replies
    • 410 views
    • 3 replies
    • 313 views
    • 4 replies
    • 422 views
    • 8 replies
    • 518 views
    • 2 replies
    • 263 views
    • 4 replies
    • 453 views


  • Popular Topics

  • Latest Posts

    • Hi all   So in general I've been enjoying the A330 a lot, it perfectly scratches the itch I've had for ages for a long haul Airbus. However I can't but help and notice a few issues, most of those are very minor but it still would be nice to see them fixed. These are in no particular order.   ND2 draws VOR1: In VOR ROSE mode, the F/O ND shows VOR1 and the associated course, so when flying raw data (I know, Airbus, raw data VOR?!?) you can't really properly identify waypoints defined by radial crossing. ILS course marker on ND ARC mode is off: It seems that when the ND is in ARC mode the magenta cross indicating the ILS course is sometimes exactly 100° off, other times a random interval. PROG Page EPE value computed incorrectly: The EPE (Estimated Position Error) value on the PROG page currently works like the cross-track deviation figure on the ND, however its purpose is to tell the crew how "certain" the plane is about where it is, and not how far off the route it is. If you have an FCOM handy, section DSC-22-FMS-10-30 should have the info you need Vector legs make the managed descent profile kind of useless. I feel like the estimation of how long the vector leg is going to be for the purposes of descent planning is way too long so that you consistently end up way too high if you follow the descent profile without a manually inserted restriction before the vector leg. ETP Position and Crossing Time incorrect: On the Data -> Equitime Point Page there's a calculation of distance to ETP and time at ETP, on my two attempts so far distance was roughly double what it should have been and time over ETP was even after ETA at destination on every instance. (INIT) FUEL PRED Extra logic: On the INIT FUEL PRED and the regular FUEL PRED page the calculation of the Extra fuel is weird, for some reason EFOB at destination minus fuel required at destination does not equal Extra fuel, and by consequence the extra time isn't accurate either. This is a real shame since the extra time is an important part of an approach briefing. Nav Autotune makes interesting choices: This one I understand if it's basically unfixable since the bug description is so weak, however on both my flights as soon as the approach phase activates the plane tried to tune a VOR near my departure airport instead of one near my destination, i.e. on my ZRH-ORD flight it tried to tune KLO on approach to Chicago FUEL PRED preflight: While boarding the values for trip fuel calculated by the FUEL PRED pages are way too low, I assume this is because it calculates with actual plane mass instead of the entered ZFM, however I have no way to prove that RTE RSV fuel mass input highlights percentage: If you manually input a fixed route reserve fuel mass into the INIT FUEL PRED page the percentage gets turned bold instead of the mass, no functional issue there, just aesthetic RMP MIC selectors INOP: You can switch between MIC on COM1 and MIC on COM2, however only by first deactivating COM2 monitor, then activating COM1 monitor and activating COM2 monitor again. For us online pilots it would be nice to be able to switch the MIC over without having to go through that dance every time No PBD waypoints off of a runway waypoint: I can't seem to create a PBD waypoint (or a PB/PB waypoint for that matter) off of a runway waypoint, I assume this is because it expects max. 5 chars for the place identifier, whereas to my experience it should be possible to use identifiers of up to 7 chars for that (i.e. KORD28C/273/25). We'd use that format quite commonly for an EFCOP that's not in the database. HDG mode stuck in HDG hold after a RTE DISCO: When flying over a RTE DISCO the flight directors correctly revert to present heading, however it locks the guidance to present heading, changing the HDG SEL on the MCP doesn't turn the plane until you go to managed and back to selected heading. WPT sequencing after a RTE DISCO: After a RTE DISCO flight guidance sequences to the waypoint after the first one, so if you have A - DISCO - B - C ... after passing the DISCO it sequences to C. I'm not 100% sure if that's a bug or expected behaviour, I seem to remember though that our sims would sequence to B in that situation. (This one is nit-picky) Traffic selector on non ADS-B in plane: You have modelled the traffic selector dial, however it seems that you simulate a plane without ADS-B in, I don't think that combination exists IRL. APPR PERF shows TA instead of TL: On the APPR PERF page we should be able to input a transition level, not a transition altitude Transition level not honored for profile predictions on the F-PLN: The profile predictions in the F-PLN only consider the departure TA for the entire flight, even for the descent where usually the destination TL should be applicable SEC F-PLN sticks onto the ND until you select F-PLN: SEC F-PLN route drawing on the ND should only happen while any SEC page is displayed on the MCDU, and AFAIK only on the onside ND though I'd have to check that. Here it sticks around until you select (primary) F-PLN again and it draws on both the onside and offside ND.   This is about it, I hope you can take this into consideration for the next update.   Tracking info: Win 10 Professional 64bit build 19041 Prepar3D V5 Academic (5.0.31.35253) Aerosoft A330 Professional V1.0.2.0 Navigraph cycle 2010   If you need anything else let me know
    • Um das "Sommerloch" ein wenig zu füllen, habe ich ein weiteres Video erstellt, in dem ich einen Flug mit der Pilatus Porter PC6 durchführe. Es geht vom Locher Airfield zum 20 NM entfernten Landestrip Corvara in Badia. Der Anflug ist auch anspruchsvoll und es lohnt sich wirklich dort zu landen. Viel Spaß beim "Mitflug" wünsche ich!!     
    • Hi there, Thanks for your reply - yes I discovered that shortly after I posted, that was the problem! Thanks for taking the time to respond. I did note that we're currently on a single track system which makes sense given the limited air traffic.   Thanks again,   tjf
    • I see the writing, and I see the wall.   Glad there's an SDK for P3D and XP11.
    • Hi. I'm having a bit of trouble here. I can take off with a flight plan loaded (into the bigger Diamond aircraft).  I can't however, get the aircraft to follow the flight plan.  I have assumed that I have to use the heading button, and that does work, until it over-flies the NAV path, but it does not do that - it just simply flies over the NAV path and stays on the path I gave it in the Heading?   When I get close to the NAV path, should I be manually turning off the Heading switch?  Would that fix it? If not, what else should  I do to get the NAV function to work?   Gaz
  • Forum Statistics

    • Total Topics
      106038
    • Total Posts
      743771
×
×
  • Create New...