Recently we have seen a lot of codes used to unlock our products being offered for discounted prices. Almost all of them are bought using stolen credit cards. These codes will all be blocked by our systems and you will have to try to get your money back from the seller, we are unable to assist in these matters. Do be very careful when you see a deal that is almost too good to be true, it probably is too good to be true.

Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About gollum65

  • Rank
    Flight Student - Groundwork
  1. Yes, will do. Flying it right now on a long hop from London to Cyprus. No issues so far and I'm about 80% completed.
  2. Hello, I had this happen today. While enroute from EGKK to LIRN, approximately 40 minutes after takeoff from Gatwick the entire aircraft powered down without warning. My specs: AMD Ryzen 2600 @ 3.4 GHZ 32 GB DDR 4 @ 3000 MHZ NVidia GTX 1660 w/ 6 GB 250 GB SSD with P3D v. 4.5 with hotfix 1TB HD Windows 10 Pro Version 10.0.18362 Build 18362 Aerosoft A320/A321 v (Updated to this version on July 31, 2019 Chaseplane version 1.0.43 Experimental (I've been using this version a few weeks and haven't had problems with P3D or the Aerosoft Airbus) Activesky for P3Dv4 version 7070 REX Sky Force 3D (Not sure what version it is? It's set to auto update, and has not done so for a while) Swift Pilot Client version 0.9.1905161012 British Airways Virtual Merlin ACARS version At the time the aircraft powered down I had just opened Google Chrome Version 76.0.3809.100 , maybe 90 seconds earlier? I usually have at least one browser tab open while I fly, if not more for charts, so it's not unusual for me to have Chrome open. As I stated above, I was flying from EGKK to LIRN. I had left Gatwick 40 minutes earlier and was flying on VATSIM at FL310 under the control of EuroControl West. I wasn't even in the P3D window as I was using my browser to search for scenery. But I had my headphones on and I heard the aircraft power down. The checklist and copilot system did not react in any way to the aircraft losing power. I looked at the overhead panel and saw that nothing was illuminated except for the battery indicators, which both showed 28.0 volts, but of course as I tried to repower the aircraft the voltages started decreasing. My first thought was to turn the batteries off and on, then see if I could start the APU. That didn't work. I tried shutting both engine toggles, turning the engine master to start and seeing if the engines would restart, which they did not. I then tried the old Ctrl++Shift+F4 then Ctrl+E to see if the engines would start? They did not. About 1 minute after the aircraft powered down, I did get an audible warning, which I assume was because the aircraft was losing speed and altitude. While there was no caution or warning light visible on the main panel, I knew where the button was and hit it, and the sound stopped. I wanted to see if any other systems worked, so I lowered the landing gear. It lowered just fine, then went back up on my command. But I couldn't think of any other way to power up the aircraft, so I just quit out of P3D. As I wrote in another post, I had never had this happen before. I do not remember if I had loaded the load sheet before starting the checklists? I think I did, but I am not positive. I wondered in the other post if I had run out of fuel and was asking what fuel load the aircraft would have if I had not loaded the load sheet? I thought perhaps it only had the fuel remaining from my previous flight? I did observe a few things that seemed unusual about this flight before the power failure. 1: On takeoff the aircraft seemed to accelerate abnormally fast. It reached V1 and VR about halfway down the runway, which felt early to me. 2: After takeoff, both while I was flying the aircraft and after I turned on the autopilot, it seemed to accelerate very quickly. Within maybe 5 seconds of liftoff I was already hitting the flaps 0 overspeed indicator, which happened so quickly that the copilot/checklist didn't even have a chance to react. Then after I switched on the autopilot the aircraft seemed to climb abnormally fast. It exceeded 6000 FPM at one point, and through most of the climbout it was over 4k/m. 3: The aircraft reached the cruising altitude of FL310 very quickly. I don't even think I had crossed the channel yet. At the time I didn't think much of these issues. I had expected to be almost max weight, but I just assumed that maybe it wasn't as heavy as I thought? Thinking back, perhaps I didn't loadsheet and instead the aircraft was almost empty? I don't know? I've since reloaded the aircraft and everything seems normal, including the fact that it has payload and fuel on board without any input from me. I have not tried to fly it again yet, though I'm going to in a few minutes.
  3. I've been flying the Aerosoft Bus Pro for months and this is the first time I've seen this happen. I was cruising along at FL310, about halfway between Gatwick and Naples, and all of a sudden the aircraft had a complete power failure. The batteries on the overhead indicated 28 volts each, but the APU wouldn't start and I had no way to power the aircraft back up. What I THINK happened is that during pre-flight I may have forgotten to initialize the load sheet? I don't remember for sure. So my guess is, if I didn't load the load sheet that I must have run out of fuel? Can anyone advise what fuel load the plane loads at by default? If it's the fuel and payload from the beginning of the last flight, the last time I loaded the load sheet, it would have had more than enough fuel as that was a 4 hour flight. Is it possible the aircraft loaded with the fuel that remained after that flight? That would certainly make sense. If I didn't run out of fuel, any ideas on what could have happened?
  4. Hello. Could someone please do repaints of the A320 and A321 Professional in Alitalia colors? I'd really appreciate it. Thanks in advance. Here are photos: A320: A321:
  5. No sir, I just started a brand new flight. It was the same aircraft, departure airport, and gate, but I did not load from a saved flight. About to start another flight now. I'll post again if I still have the problem.
  6. One last update, since I'm not sure if I'll get a response from Aerosoft. Upon landing at Heathrow yesterday in the flight mentioned in my last post, after I got to the gate and the aircraft stopped, I got the completion of the pushback dialogs, up until the "Wait" portion, which never happened and the checklists never continued after that. Curiously though, when I landed, the copilot, who I thought was stuck, began shutting lights and doing other post-flight tasks, without the checklists. Anyway, I decided to reinstall the aircraft over itself, without even uninstalling it. My suspicion is that on Saturday afternoon I was working through the checklists, and just as I pushed back from the gate something came up at home and I had to quit my flight. Since I closed P3D without finishing the entire flight, I think the checklists got "stuck" at the point where I closed P3d. In a future update maybe the devs can add some sort of function that resets the checklists back to the start when the sim closes, or at least an option for the pilot to manually reset the checklists somehow? I haven't tested since I reinstalled to make sure everything is working? I'm going to do a flight in a couple of hours.
  7. This morning I again attempted the flight I wanted to make. The checklist/copilot again got stuck at "Starting Engine 2". I never got the "Engine 2 is stabilized" callout. So, not wanting to mess with it anymore I decided to continue my flight anyway, hoping that the aircraft would fly normally. Both engines started, I taxied out and took off, and climbed to my cruise altitude of FL340. A few seconds after reaching FL340 I hear the callout "Engine 2 is stabilized", followed by the "checklist beep", and then a few seconds later "Engine 1 is stabilized". But that's as far as it's gotten so far. MCDU3 is still showing "Start Push" but nothing has progressed from there. If it progresses any further during this flight I'll post an update.
  8. By the way, I don't have GSX. This issue is happening with the pushback and startup procedure that's built into the Aerosoft Bus.
  9. I've been flying the Aerosoft Airbus A320/321 almost daily for a few months now, and I almost always use the checklists and copilot. Because I'm lazy and like to let the plane fly itself. LOL Anyway, today I completed a flight without incident, shut down the computer and went about my day. This evening I booted up with the intention of doing my return flight. I get into the checklists. I get to the pushback option. I call for pushback. The pushback starts and ground tells me I'm cleared to start engines. I switch on the engine mode selector to IGN/START and flip engine 2 switch. The checklist says "Starting engine 2". Engine 2 starts. That's as far as it gets. I never get the "Engine 2 is stablized" callout. So I figured ok, I'll move on. I flip up engine 1. Checklist says "Starting engine 1". Engine 1 starts, but that's as far as anything gets. I again don't get the "Engine 1 is stablized". I set the parking brake, but I never get "pushback complete". The after start checklist never begins. It's just stuck on the pushback checklist. So I figured I must have done something wrong that I wasn't thinking of. I quit everything, shut the computer, went to have dinner, and then came back to try again. Booted up the PC, started P3D, ran though all the normal procedures. Again the checklist/copilot gets stuck at the exact same place, "Starting Engine 2". I'm going to try again tomorrow. I've literally completed probably 40 flights with this aircraft and I've never had this problem. We'll see if it happens again. But in the meantime, any ideas or suggestions of what could be wrong? Thanks.
  10. Ok thanks. That's what I figured. I'll just have to make sure I don't forget that checklist.
  11. I have a bad habit of forgetting to run the before takeoff checklist. So once I set takeoff thrust, the checklists and copilot basically shut down because I missed that checklist. Is there any way to force the sim to move on to the next checklist? I've tried turning off both checklists and copilot, but that doesn't seem to do it.
  12. Since everyone seems to be using this as a bug report thread for the new version I'll add to it. Let me know if you want me to post separately? This is a new install of of the A320/A321 product into a new install of P3D v4.5 on a brand new computer running Win10Pro. It's all less than a week old. Today I flew my first flight using the Aerosoft Airbus, in this case the A321 with UAE engines. I ran into 2 issues with the checklist, one of which was posted above in the 1st or 2nd post.... 1) After passing the transition altitude and the copilot setting both altimeters to STD, I started getting the "Altimeter Setting" callout a few minutes later. This was resolved by pulling out the altimeter knobs and pushing them back in. So this wasn't a big issue. 2) What WAS a big issue was that on final approach, when the "pilot" called out for "Exterior Lights", the copilot didn't change them and the "pilot" got stuck in an infinite loop of saying "Exterior Lights". There was no way to shut her up and it didn't matter what I did to the exterior lights, the loop continued. Thanks in advance. I'm loving this plane so far (other than these issues).
  13. Ok, I think I get it now. Thanks. I'll try again.
  • Create New...