I know this issue is well known as I see on flight simmer streams and I think it’s just an MSFS issue, and maybe specifically GSX users, but is there any fix on the horizon for these wonky pushbacks where the other users have their nose or tail at 45 degrees in the air, or even vertical?
I don’t remember ever seeing this in P3D with GSX. If it’s some kind of data issue couldn’t some code be added to block erroneous pitch data during Ground manoeuvres say under 100kts?
Thanks
David
I also see this very often. Would love a fix for this!
I came here to ask the same thing. Here’s Spirit pushing back at KBOS the other day. Kinda ruins the immersion lol.
Yep it’s a shame it doesn’t seem to be getting any attention as it’s been an issue for months. I had two aircraft pushing back in front of me the other day and one 767 was perfectly on the ground, and a 737 in front of him had his nosewheel 10ft off the ground.
I would suggest that, if you don’t like the behavior exhibited due to the failure of a developer’s software, you contact the developer to investigate, find the root cause of the problem and solve the problem. You can get sympathy here, but you should push for the root cause to be solved with the developer.
That was precisely the reason for posting, I was hoping vPilot could be coded to solve the problem, maybe some kind of rule which won’t change pitch of AI models under 30kts ground speed for example. But maybe an expert on the forum knows the root cause (something to do with the traffic models? Or is a GSX issue?)
Others may know better – I’m only going off what I vaguely remember – but I think it’s a GSX issue. Anyone can feel free to correct me if that’s not right.
Hi,
The GSX developer has given thoughts here, and believes it to be an issue that needs to be resolved in vpilot:
This reached new levels of crazy for me yesterday. The amount of smoke that gets generated from the crazy pitch dropped my framerate to single digits until the other guys pushback finished!
What would be great is if there was some way to flag this in VPilot or XPilot, so they could take a look at the data from a log file and figure out what was happening. Do the VATSIM clients need to be updated to better understand what GSX is doing? Or does GSX need to change how their pushback is being transmitted?
There’s a good explanation (or theory) on the GSX forum link posted above. It seems MSFS changed the way certain variables work versus how they worked in FSX, P3D etc and unless the relevant client takes account of this you could get erroneous data and therefore incorrect pitch values being assigned to AI traffic models. I think we need the vPilot Dev to give a view.
I wonder if this is something that might see some attention now that CRC is released
