Author Topic: Stuttering animation in GSX  (Read 1398 times)

airbadger

  • Sr. Member
  • ****
  • Posts: 342
Stuttering animation in GSX
« on: March 05, 2022, 01:43:20 pm »
In the current verison of GSX, I observed this regular stuttering in all of the objects/people associated with GSX. The rest of the sim is running smooth, it's just GSX in this instance. I'm only seeing this at MK Studio's Vagar/EKVG with the FSL 320 so far, but I've seen it twice.

https://streamable.com/69atex

EDIT: one other note - when I pushback, the stuttering of the tug affects the plane as well during pushback
« Last Edit: March 05, 2022, 01:53:15 pm by airbadger »

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 50710
    • VIRTUALI Sagl
Re: Stuttering animation in GSX
« Reply #1 on: March 05, 2022, 02:07:14 pm »
The stuttering is not obviously caused by GSX but, instead, GSX is the victim of a stuttering induced by another addon that use Simconnect and it's likely sending too many commands in a short period of time.

The stuttering seems to be regular at 1 seconds intervals, further proving GSX is not the cause, because its own animations are otherwise smooth, which wouldn't be the case if the stuttering *originated* by GSX and yes, 1 second is a commonly used update frequency to communicate with Simconnect, but that alone is not saying much, without knowing how much data is being transferred every second.

Since you said it only happens on that airport, this confirms it cannot possibly be caused GSX, since nothing in any of its animations handling has any knowledge of the airport

Quote
when I pushback, the stuttering of the tug affects the plane as well during pushback

That's not an indication the stuttering originates by GSX either. It the sim ( using Simconnect ) doesn't call GSX back at the normal frame rate interval because it's overwhelmed with traffic generated by something else, GSX won't update its calculations to move the plane during the lost frames, so it's entirely expected you'll see a stutter because the position wasn't updated for a few frames.