Author Topic: Couatl v4.8 Error  (Read 957 times)

wxman16

  • Newbie
  • *
  • Posts: 23
Couatl v4.8 Error
« on: July 30, 2024, 11:16:36 pm »
Hello,

I am having trouble when using GSX while at your KIAH airport scenery. When I am about to pushback and do Ctrl + F12, then select option 5 for pushback, I get the following error message as seen in the attached screenshot. I've noticed this error at a couple of other airports but mainly in KIAH as I fly there a lot. This only happens when I'm at the E-gates. Now, I did do some changes for the pushback to take advantage of the push and pull feature when parked at the E-gates (I've attached the kiah.ini file as well). I've spent several hours creating new pushback from those gates. When I see that error message pop-up, I take a look at the log (which is attached as well) but I'm not sure what it is saying. Hopefully you can shed some light. Everything is updated too by the way.

Using P3D v5.4
windows 11 home
« Last Edit: July 31, 2024, 01:29:11 am by wxman16 »

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51400
    • VIRTUALI Sagl
Re: Couatl v4.8 Error
« Reply #1 on: August 06, 2024, 04:12:36 pm »
Your error seems to suggest there wasn't any pushback usable for your airplane. Which one it is ?

wxman16

  • Newbie
  • *
  • Posts: 23
Re: Couatl v4.8 Error
« Reply #2 on: August 06, 2024, 10:38:19 pm »
I am using the Aerosoft A320pro

wxman16

  • Newbie
  • *
  • Posts: 23
Re: Couatl v4.8 Error
« Reply #3 on: September 05, 2024, 08:45:07 pm »
Any update status?? 3 days ago, I was updating the Drzewiecki Design KSEA scenery in P3Dv5.4 using the Aerosoft A320pro to assign gates A11-A14 as UAL handling and LGS SkyChef catering and today, I got the same couatl error message as in the screen provided in the first post when I selected the pushback option. GSX is fully updated.

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51400
    • VIRTUALI Sagl
Re: Couatl v4.8 Error
« Reply #4 on: September 28, 2024, 02:47:53 pm »
I can't reproduce the problem, so I need the complete log, the one that is Enabled in the Troubleshooting settings, because you posted the panic log, which is not detailed enough to allow me to understand what is happening.