Rampi walking path

[MaximumN2]

And here we go; two months of radio silence, and it's still not fixed. Ramp agents still don’t know where their walking path is, and wingwalkers are still walking across the engines and main landing gear.

To be honest, I’ve never seen a program with less bug-fixing ability than GSX. Such a shame.

[virtuali]

And here we go; two months of radio silence, and it's still not fixed. Ramp agents still don’t know where their walking path is, and wingwalkers are still walking across the engines and main landing gear.

What do you mean with "two months of radio silence" ? You got the proper and detailed answer why this is not as easy to "fix" (it's not even a bug) here, exactly two months ago:

https://www.fsdreamteam.com/forum/index.php/topic,33093.msg208477.html#msg208477

So, I don't know if you have missed it, or you didn't like the answer, but surely there wasn't any "radio silence".

o be honest, I’ve never seen a program with less bug-fixing ability than GSX

The changelog speaks for itself:

https://www.fsdreamteam.com/couatl_liveupdate_notes.html

Just count the words "fix" and the frequency of updates:

[MaximumN2]

For me, that's a bug. Why introduce a feature that doesn't work properly? I mean, you're creating the profile for every airplane, so you should be able to fix this.

But if I remember the last versions correctly, every "fix" has broken something else. I think at the moment it's a hot mess, which isn’t really getting better—because you're releasing features that are either incomplete or broken, and then take months to fix. Meanwhile, the core problems—like the absolutely ridiculous, unrealistic, and weird walking paths—remain untouched, with the excuse that they're "not easy to fix."

And calling the path, where the wingwalkers practically kill themselves on every pushback, not a "bug" is just ridiculous, to be honest.

[virtuali]

For me, that's a bug. Why introduce a feature that doesn't work properly?

The feature works properly, even if it's not as "perfect" as you are expecting. In addition to that, it's not even a new feature, because exactly the same issues for exactly the same reasons, happened also with the main headset operator, which also sometimes crosses the pushback towbar.

I mean, you're creating the profile for every airplane, so you should be able to fix this.

If you read what I wrote carefully, you would have known it's not as simple as that.

But if I remember the last versions correctly, every "fix" has broken something else

In the rare cases when this ever happens, it's always fixed by a later fix, when properly reported.

I think at the moment it's a hot mess

It obviously isn't. But of course, since you are nitpicking on something so minor, it's clear you'll never be ok for you.

, which isn’t really getting better—because you're releasing features that are either incomplete or broken, and then take months to fix. Meanwhile, the core problems—like the absolutely ridiculous, unrealistic, and weird walking paths—remain untouched, with the excuse that they're "not easy to fix."

I don't know what you are trying to say here, it seems you are too fixated on walking paths, that's the ones are "not easy to fix". You don't like Wingwaklers, they can be DISABLED in the airport profile.