CAB825

members
  • Content Count

    24
  • Joined

  • Last visited

About CAB825

  • Rank
    Flight Student - Groundwork

Recent Profile Visitors

941 profile views
  1. CAB825

    Mach Crossover Altitude

    Hi Dave, Thanks for the repose, I have just run it one more time and noticed that the switch occurs when the IAS meets the corresponding Mach. The managed speed values were 340/0.68 and as soon as the PFD Mach hit 0.68, the managed Mach kicked in. As can be seen, ISA +3 so no real issue with weather/temp. It does not seem to model the Airbus FMGC logics as below: Thanks.
  2. CAB825

    Mach Crossover Altitude

    Its occurs while in managed mode, selecting speed has no effect. It seems to occur when the cruise altitude is reached/active, even if the cruise altitude is below crossover altitude.
  3. Hi, It seems there is an error with the managed speed function. For no apparent reason, it will change from Speed to MACH at low FL's. As can be seen here, FL180 and it has switched over from Speed to MACH, while in the cruise. Regards,
  4. CAB825

    CTD A319

    I also just experienced the same issue when using the FMS to enter an alternate. Faulting application name: Prepar3D.exe, version: 4.3.29.25520, time stamp: 0x5b2c3263 Faulting module name: FMGS.dll, version: 2.64.0.47, time stamp: 0x5b957a84 Exception code: 0xc0000005 Fault offset: 0x0000000000027152 Faulting process id: 0x2644 Faulting application start time: 0x01d44d021b8c8136 Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe Faulting module path: .....Documents\Aerosoft\Aerosoft A320-A321 Professional\SimObjects\Airplanes\Aerosoft A320-A321 Professional Base\Panel_Fallback\DLLs\FMGS.dll Report Id: 5a6fe017-fdc1-4211-8fd5-9547d15c19da Faulting package full name: Faulting package-relative application ID:
  5. CAB825

    Not following flight plan

    Add one more to the list. Will not engage NAV mode correctly at T/O or when when using DIR function.
  6. Hello all, After purchasing this product today and having the same problem, i.e. MCDU Options Greyed Out and St. Elmos Fire, I have managed to rectify the problem. Firstly this was not a problem with the Aerosoft add on but with P3D updater itself. Running the 4.3.29.25520 update ‘seemed’ to work a few days ago and it did not report any problems. I thought it was strange the new C130 was not showing in the list of A/C and it turns out the updater had not worked. Check the version of P3D you are running in the about tab in P3D. If is still showing anything but 4.3.29.25520 then you can do as I did and follow the suggestion of GWI-Berlin’s post and: 1. uninstall client / install client. 2. uninstall content / install content 3. uninstall scenery / install scenery Do the uninstall using the windows add/remove function followed by running the installers individually found in the P3D install/update download. This fixed the issue and I did not need to do a clean install, ruining all my previously installed add-ons/scenery.