NavDataPro

Sign in to follow this  

NavDataPro Unterforum (nur im Zusammenhang mit X-Plane 11).

15 topics in this forum

  1. Pinned topics
    • 24 replies
    • 7650 views
  2. Topics
    • 1 reply
    • 210 views
    • 3 replies
    • 395 views
    • 1 reply
    • 459 views
    • 3 replies
    • 558 views
    • 8 replies
    • 1041 views
  3. FF A320

    • 6 replies
    • 1861 views
  4. World Traffic

    • 0 replies
    • 907 views
    • 0 replies
    • 1024 views
    • 8 replies
    • 1525 views
  5. Wohin mit Navigraph-Daten

    • 4 replies
    • 2314 views
    • 7 replies
    • 2003 views
    • 0 replies
    • 1464 views
  6. Frage zu Navdata

    • 1 reply
    • 1540 views
  7. NavDataPro

    • 6 replies
    • 1697 views
Sign in to follow this  
  • Posts

    • I'm sorry to hear this. But also sorry of the reflection this has on Aerosoft as a company, which I still hold in high regard on product quality, support and pricing.   But ... and let me stress this is assumption on my part, in Aerosoft and others I do tend to see deals with 1-2 person development team, doing the marketing and sales for their products. That also means that as soon as the product is delivered, one can count on 1 to 2 servicepacks to clear bugs, and then it stops. No more packs, no more communications, nothing. The an2, great as it is, falls in this category. More and more tend to do so too, not only marketed via Aerosoft.   I hope I'm wrong in my assumptions, as this, from my consumer's eye, reflects very poorly on the branding party, influencing my future buying choices.
    • Good morning, I have had twice this morning crahes on the ground while preparing flight from UDYZ to UUEE, everythime while manipilating MCDU. Error message is:
      Faulting application name: Prepar3D.exe, version: 4.4.16.27077, time stamp: 0x5bfdbb35
      Faulting module name: FMGS.dll, version: 2.64.0.94, time stamp: 0x5c5dbc2a
      Exception code: 0xc0000005
      Fault offset: 0x0000000000009230
      Faulting process id: 0x31c0
      Faulting application start time: 0x01d4ca8215c62c9b
      Faulting application path: E:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe
      Faulting module path: E:\Program Files\Lockheed Martin\Prepar3D v4\Ecosystem\Aerosoft\Aerosoft A320-A321 Professional\SimObjects\Airplanes\Aerosoft A320-A321 Professional Base\Panel_Fallback\DLLs\FMGS.dll
      Report Id: 04ef132a-7713-4982-b8b7-5d30eb364e34
      Faulting package full name: 
      Faulting package-relative application ID:    Additional info from aerosoft updater; Regular as well as experimental updates are available for installation
      Prepar3D 4.x found: (E:\Program Files\Lockheed Martin\Prepar3D v4\) Product Name: Aerosoft A320-A321 Professional for Prepar3D v4.x Add-on Path: E:\Program Files\Lockheed Martin\Prepar3D v4\Ecosystem\Aerosoft\Aerosoft A320-A321 Professional
      Installed version: 1.2.3.1
      No updates available for this product!   Also ysterday I have flown from LFPG to UDYZ with the A320, and noticed a couple of things.   While on the ground after start up at CDG, I was going through the flight control check and noticed that all were operative except for full up and down. the elevators were stuck in the non feeding position (LIKE IF IT WAS NON ELECTRICALY ACTIVATED). I have checked all but did not find any specific miss operating system untill my eyes looked at the engine mode selector who stayed on the start position. As soon as I set it up on NORMAL position, I had my elevators operating again. This was double checked from the cokpit and from outside in visual.   During the cruise I have had twice an autopilot runaway, which resulted in an pitch up moment that put me above REC MAX. after recovery Ii reengaged the automation and it did work again.   Last point, 10 minutes after reaching cruise level, and for I do not know which reason, the MANAGED system triggered a MANAGED speed of 135kt.... I switched from MANAGED to SELECTED speed and of course to MACH. The only cure was to reset in flight ATHR, AP1 and FDs. I went raw data and s everything one after one, starting with FD, and all went fine till the AP runaway.   The version that I have is the experimental version correcting the MANAGED VERTICAL profile problem.   Cyrille
    • +1 for a selection box into the AS configuration that allows using this or not
    • Hi, both the A318/319 and the A320/321 are already in their "final" state for a long time. Final state means release state here. Both products still have some (same for both products) bugs and fixing them is an ongoing process. You can expect the same experience with both products so if you already fly the A318/319 you will see the same features and bugs with the A320/321. Make sure you download the latest versions from your shop account!    
    • Hello Harry,   David's files are cumulative so you only need install the latest.   From cycle 1901 PFPXv2 is required.