Jump to content

balus

Members
  • Content Count

    293
  • Joined

  • Last visited

Community Reputation

42 Excellent

About balus

  • Rank
    Gliderpilot

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. hmmm, not doubting you Mathiijs, but this is from the PMDG forum - according to Robert the files were sent late on the night of release. A note for our Aerosoft Customers: We tried very hard to get this release done mid-week in order to give Aerosoft time to make the update live in their system for you, but unfortunately this didn't happen. We will be sending them the data that they need late tonight, but I do not know if it is reasonable to expect them to get set up for you to obtain the update during the course of the weekend. Please be kind to their support team- the release sc
  2. I understand that the download files for the PMDG 777 P3Dv5 update have been sent to Aerosoft, when will they be available to download for existing customers?
  3. And add me to the list, at FL360 enroute KSEA to RKSI al of a sudden i get a magenta 118 at the base of the speed tape and speed started to bleed off. Performance page was showing 0.78 Mach - so I pulled the speed knob and dialed it in and continued the flight.
  4. Has anyone request the new VH-ULD Qantas Freight A321? https://www.planespotters.net/photo/1109904/d-anja-qantas-airbus-a321-231p2f note that the rego in this picture has changed to VH-ULD
  5. Thanks, it is encouraging to hear that it hadn’t been put in the too hard basket as appears is the case with some other issues. If I have time today I will try another flight with all logging enabled.
  6. I'll take that as a no then, sad really, this product had such potential, back to X-plane for an A330 then.
  7. Has there been any advance on the resolution of this issue?
  8. Until the issues are sorted out From inconsistent performance in anything over a slight breeze to inconsistent altitude management at anything above 1x simulation to managed speed failures - calling for 116 kts at cruise, really? I'm sure others can add to the this list Happy to be patient, and I have been, but this far in, with this many problems, this aircraft is broken More than happy to be proven wrong, but I have experienced all of the above
  9. Hmm, not sure, I always check for discos after entering a SID and there weren't any, pretty sure it did fly the SID
  10. And I have this problem today - flew yesterday with no problems, apart from the checklist that decided to stop working, but that's common. Today I updated to 1.0.0.7 loaded a flightplan created in PFPX from ESSA to KORD, took off and at around FL180 to managed speed suddenly dropped to 116. I manually climbed to altitude and hit the SPD button to engage managed speed and 116 appeared below the speed tape and the aircraft began slowing. The CRZ page on the MCDU shows MANAGED .80, I set .80 in the SPD window and the aircraft flies normally, but not in managed speed mode.
  11. Hi Rolf, I have just let the checklist run all by itself and you are correct it does now wait until after the APU becomes available before switching on APU Bleed and disconnecting external power, this is different to what I experienced with version 1.0.0.0, which is why I was intervening. Thanks for your patience.
  12. Unfortunately that has not been my experience. The first time I let the checklist run by itself with no intervention, external power was disconnected directly after the apu start and the aircraft systems reset. It was then that I remembered that this had happened with the A32x/A31x series as well.
  13. In the updater, click on the configuration button and then select "Show available experimental updates for my products" and then click on OK
  14. It's not only bad weather, I'm on descent to YSSY with a 4 knot tailwind and the aircraft is up and down like the Assyrian Empire! A way to go yet with this flight model
  15. Yes I do batteries, EXT PWR, fuel pumps, start the APU and then IRS - a hangover from an X-plane Airbus I know in the previous versions that there wasn't enough time between starting the APU and disconnecting EXT PWR - the APU was still starting and power was disconnected which meant that the MCDU had to be reprogrammed, which is why I adopted my method - has this been fixed?
×
×
  • Create New...