Author Topic: GSX fatal Error after update  (Read 2093 times)

ronprice46

  • Newbie
  • *
  • Posts: 29
GSX fatal Error after update
« on: November 29, 2019, 02:19:04 pm »
Attached is log file and not sure what possible fix i could do. This happens after i updated GSX with the updater as i usually run it everyday in case i miss an update/ Attached is the log file

Framsen

  • Newbie
  • *
  • Posts: 37
Re: GSX fatal Error after update
« Reply #1 on: November 29, 2019, 04:07:00 pm »
Updated GSX 10 minutes ago and still have error:

couatl v3.2 (build 4278)
panic log started on Fri Nov 29 16:05:46 2019

problem raised by addon <unknown>
Taking vehicle.cruiseSpeed: 13.4112Traceback (most recent call last):
  File ".\common\fsm.py", line 73, in executeDoFuncToCompletion
  File ".\GSX\assistanceServices\baseAssistanceVehicle.py", line 418, in do
  File ".\GSX\assistanceServices\passengerBus.py", line 190, in getLeaveRoute
IndexError: list index out of range
{'Airport': 'LHBP', 'Requested assistance services at': 'Gate R 273', 'User Pos': (47.43543270426085, 19.265075043574537, 155.31 m, 4.43013 m, 222.00001435148778)}

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51400
    • VIRTUALI Sagl
Re: GSX fatal Error after update
« Reply #2 on: November 29, 2019, 06:38:52 pm »
Attached is log file and not sure what possible fix i could do. This happens after i updated GSX with the updater as i usually run it everyday in case i miss an update/ Attached is the log file

Your error has been already fixed early today.

ronprice46

  • Newbie
  • *
  • Posts: 29
Re: GSX fatal Error after update
« Reply #3 on: November 30, 2019, 07:12:08 am »
ok so just run the updater and it would be fixed?

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51400
    • VIRTUALI Sagl
Re: GSX fatal Error after update
« Reply #4 on: November 30, 2019, 01:53:10 pm »
ok so just run the updater and it would be fixed?

Of course. Note that, the fixed error is the one you posted in your log.

The one posted by Framsen is an entirely different issue, which is likely caused by a problem in the scenery AFCAD, like orhpaned/missing/overlapped nodes, and doesn't have anything to do with the update or this thread subject.