Author Topic: After update 2.7.6 - Error on every sim start  (Read 1464 times)

disco79stu

  • Sr. Member
  • ****
  • Posts: 338
After update 2.7.6 - Error on every sim start
« on: September 28, 2023, 08:46:19 pm »
Hi,

I get this error on every sim start since I updated to 2.7.6.
When I let couatl restart, everything works fine, but the error occurs every time.
Running live update didn't solve this.
Log attached.




hammertime

  • Newbie
  • *
  • Posts: 13
Re: After update 2.7.6 - Error on every sim start
« Reply #1 on: September 28, 2023, 09:44:18 pm »
Exactly the same for me, with the exact same errors in the log file

disco79stu

  • Sr. Member
  • ****
  • Posts: 338
Re: After update 2.7.6 - Error on every sim start
« Reply #2 on: September 28, 2023, 11:33:13 pm »
So the error somehow seem to have vanished, but I'm left with the issue mentioned in the other most recent thread, where GSX is stuck at the loading wheel after start. Restarting Couatl solved this then for me.

Edit: the above error resurfaces every now and then.
« Last Edit: September 29, 2023, 08:15:57 am by disco79stu »

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51247
    • VIRTUALI Sagl
Re: After update 2.7.6 - Error on every sim start
« Reply #3 on: September 29, 2023, 09:36:20 am »
From the look of it, the error seems to be caused by some kind of timing issues, as if the sim never replied in time when connecting to it. What other add-ons you have the starts with the sim ?

disco79stu

  • Sr. Member
  • ****
  • Posts: 338
Re: After update 2.7.6 - Error on every sim start
« Reply #4 on: September 29, 2023, 11:16:19 am »
From the look of it, the error seems to be caused by some kind of timing issues, as if the sim never replied in time when connecting to it. What other add-ons you have the starts with the sim ?

These add-ons start with the sim (but never caused any issues before 2.7.6):

- FSRealsitic
- FSLTL
- AviaServer
- FSUIPC 7
- FS2Crew Command Center
- Fenix BootStrapper

-

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51247
    • VIRTUALI Sagl
Re: After update 2.7.6 - Error on every sim start
« Reply #5 on: September 29, 2023, 12:07:32 pm »
These add-ons start with the sim (but never caused any issues before 2.7.6):

Try to *temporarily* disable all of them, by setting the <Disabled>True</Disabled> line in their EXE.XML sections and see if it makes any difference.

disco79stu

  • Sr. Member
  • ****
  • Posts: 338
Re: After update 2.7.6 - Error on every sim start
« Reply #6 on: September 29, 2023, 12:23:19 pm »
These add-ons start with the sim (but never caused any issues before 2.7.6):

Try to *temporarily* disable all of them, by setting the <Disabled>True</Disabled> line in their EXE.XML sections and see if it makes any difference.

Roger, I just did and the error presented itself again, although none of the above add-ons were launched.
Log attached.


Fragtality

  • Jr. Member
  • **
  • Posts: 94
Re: After update 2.7.6 - Error on every sim start
« Reply #7 on: September 29, 2023, 02:46:13 pm »
I do not have it every Time the Sim starts, but occasionally it would crash on Start.
(When it not crashes on Sim-Start, the Menu will not work on first Use and I have to restart Couatl to make it work again)

Fragtality

  • Jr. Member
  • **
  • Posts: 94
Re: After update 2.7.6 - Error on every sim start
« Reply #8 on: September 29, 2023, 02:58:17 pm »
For completeness, the Addons in the exe.xml (same order):
- FS2Crew Command Center
- FS2Crew RAAS Pro MSFS
- Couatl
- FenixA320
- FSUIPC7

disco79stu

  • Sr. Member
  • ****
  • Posts: 338
Re: After update 2.7.6 - Error on every sim start
« Reply #9 on: October 03, 2023, 11:05:35 am »
v2.7.7, issue remains.
Using FSUIPC instead of exe.xml to start Couatl currently works best and doesn't produce the error.

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51247
    • VIRTUALI Sagl
Re: After update 2.7.6 - Error on every sim start
« Reply #10 on: October 03, 2023, 12:39:47 pm »
v2.7.7, issue remains.

I can only repeat and confirm the issue is fixed in 2.7.7, but you must run the Live Update of the updated Offline installer, it wasn't fixed in the 2.7.7 Beta.