Jump to content


  • Posts

  • Joined

  • Last visited

About gollum65

gollum65's Achievements


Newbie (1/14)

  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare
  • Week One Done
  • One Month Later

Recent Badges



  1. This may have been caused by either Coutl (GSX) or Enhanced Atmospherics. I've been running EA ever since P3D 5.2 came out and have not had any problems with it. And regarding Couatl, there was an update this morning that broke Coutl (even if the dev says it didn't). So now Coutl is off, and I turned off EA, and now I can load into EDDM in a pyaware plane. P3D is SO picky sometimes!!!!
  2. Just purchased Sim Wings Pro Mega Airport EDDM for P3D v5. I can't be near (or at) the airport in any payware aircraft (PMDG NGXu, 777, 747, or FSLabs Airbus) without getting a DGXI Device Hung error. My specs: AMD Ryzen 9 5900X 32 GB RAM AMD RX 6800 (16 GB of VRAM) NOTE: I CAN be at EDDM in the default F-35 that P3D loads into if I let it, but if I try to load any payware aircraft listed above, I get the error and have to quit P3D. I can also load any aircraft up at any other payware, freeware, or default airport without issue. NOTE 2: There are NO errors showing in Windows Event Viewer, so I can't tell you if there was a P3D crash or if it's not related to P3D? NOTE 3: After installing Sim Wings EDDM I did run the Aerosoft Updater and it did update EDDM Steps I've taken: 1: Used Disk Cleanup to delete the DirectX Shader Cache, and also found and deleted the P3D Shaders from ..\user\App Data\Local\Lockheed Martin\Shaders folder 2: Uninstalled EDDM and installed it into a new folder (c:\Aerosoft EDDM Install instead of the default....old Windows support trick). I disabled my antivirus (Kaspersky Security Cloud Free...which never objected to the EDDM install in the first place, but I turned it off anyway) Other than trying to reinstall my GPU drivers, I don't know what elxe to do? And since all aircraft work perfectly at all other P3D airports, and all other software on my PC works fine, I can't see how the driver/GPU would be an issue.
  3. Any plans to update Mega Airport Prague for P3D v5? The installer won't even run. kernelbase.dll error immediately when I try to start it, so it doesn't even know what P3D I have yet?
  4. As I indicated in my OP the traffic cones were not being removed and removing them myself did not initiate the pushback. But this morning I've fixed it! I completely uninstalled the Aerosoft Bus and GSX/GSX2 including removing their folders and doing a registry clean. After reboot I installed the Aerosoft Bus and verified it was completely up to date and working in P3D. I then reinstalled GSX/GSX2 and verified that it was completely up to date. After another reboot I went through the whole boarding/loading process and then asked for pushback. Here's what I believe was the problem: After installing in the MCDU3 Ground Services menu GSX services were turned off. Once I turned them back on pushback worked as expected, including the traffic cones being removed. I don't know if that's what the original issue was but it might be a good idea to verify whether GSX Services get turned off when upgrading from to Thanks for everyone's responses.
  5. Not sure and I don't remember. I never got to even taxi from the ramp. After pushback the plane just wouldn't move. I uninstalled and installed and now the plane will move again. I don't know if GSX is going to work again as I didn't try it?
  6. Yes, I agree that I don't know if this is a problem with the Bus or with GSX? Regardless, I uninstalled and reinstalled after a reboot. Now I have to see if it all works correctly?
  7. Yes, that's correct. Never had an issue until the update last week. Now I ran into an even stranger problem. I just setup a flight, went through the checklists using the automatic copilot, pushed back using the built in pushback feature in the Aerosoft bus, and once it was completed I went through the after start checklist with no problem, got to the point where I was supposed to start to taxi and the aircraft refused to move. It was like it was stuck in concrete. Even with the engines at max throttle the aircraft wouldn't budge. This was at Aerosoft Frankfurt. I slewed to another location thinking maybe I had found a spot on the airport where there was a clipping problem (though I've used that gate dozens of times without issue). After slewing to somewhere else on the airport the aircraft still refused to move an inch. I ended up quitting out of P3D as there was no way to get the plane to move at all. All this is very frustrating. I guess I can uninstall the Aerosoft bus and reinstall using the older version, if I still have that installer? I'll have to search for it.
  8. I use the automated copilot and checklists, so they are supposed to be removed automatically,
  9. In the last week I updated the Aerosoft baby bus (A320/321...I don't own the 318/319 or 330) to version 1.3.0,.0 and also it seems like GSX 2 is always updating itself. Now the last few days when I call GSX for push back it starts but never pushes back. I get de-iced if needed, the PB truck connects, the FO goes thru the checklist, and that's it. It just sits there and does not initiate the push back. It never asks for parking brakes released or gives me any message to release them. One thing I noticed in MCDU3 is that the parking cones are never removed, but even if I remove them GSX still never pushes back. I then have to use the built in PB system that is independent of GSX 2. Any help would be appreciated.
  10. 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.
  11. 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.
  12. 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:
  • Create New...