Author Topic: GSX Crash When Customizing Aircraft  (Read 2472 times)

7heAngryVe7eran

  • Jr. Member
  • **
  • Posts: 63
    • TruNorth Air
GSX Crash When Customizing Aircraft
« on: July 10, 2017, 07:00:50 pm »
After updating GSX to the newest version, I keep getting a couatl crash whenever I attempt to customize any aircraft.

Debug information...


couatl v3.2 (build 3829)
panic log started on Mon Jul 10 11:55:16 2017

problem raised by addon __init__.py
Traceback (most recent call last):
  File "couatl\GSX\__init__.py", line 738, in onSimStart
  File "couatl\GSX\assistanceServices\__init__.py", line 1852, in onSimStart
  File "couatl\GSX\assistanceServices\__init__.py", line 1928, in materializeTrafficCones
AttributeError: 'tuple' object has no attribute 'x'
{'Airport': 'KXNA', 'User Pos': (36.27618333339749, -94.29827777767393, 393.545 m, 1.26814 m, 250.0000080135488)}


Any assistance with this issue is appreciated.


virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51400
    • VIRTUALI Sagl
Re: GSX Crash When Customizing Aircraft
« Reply #1 on: July 12, 2017, 05:05:00 pm »
We cannot reproduce this. Are you sure you happens only when customizing the aircraft, and with every aircraft ?

7heAngryVe7eran

  • Jr. Member
  • **
  • Posts: 63
    • TruNorth Air
Re: GSX Crash When Customizing Aircraft
« Reply #2 on: July 13, 2017, 12:43:50 am »
We cannot reproduce this. Are you sure you happens only when customizing the aircraft, and with every aircraft ?

This is the procedure that usually results in the couatl crash.

I go to customize aircraft, use the 3D editor to set the coordinates, and go to Deboard to watch the vehicles approach the aircraft. If I need to make a change, I reset GSX with the ctrl+F12 menu. Wash and repeat. If I need to do this a few times to get the coordinates exactly where I need them, couatl will crash. I am required to restart the simulator for it to work again.

The good news is that it saves the coordinates, so I can continue to customize the aircraft until it crashes again.

I appreciate you attempting to reproduce the issue I'm having. I suppose I should've included this information from the start, as I'm sure everyone customizes their aircraft differently.