Thanks for the reply! I understand that part. Let me rephrase this; I didn't describe it clearly enough in the original post.
What appears to be the issue:
This particular marshaller closes the baton right as the nosewheel arrives at the line, so by the time the user reacts, the nosewheel has already overshot.
Why this is an issue:
The other marshallers fall into two categories. One type is where they have a continuous animation from open to fully crossed, making it possible to predict the stopping point. This marshaller keeps the batons parallel to each other for around a meter of nosewheel movement, making it impossible to predict when it'll cross. The other type allows for a bigger tolerance for the stopping position, where if I go slowly enough, I can end up stopping half a nosewheel diameter short of or past the line and still get a valid parking.
How I propose to fix it:
1. Create a bigger tolerance in stopping zone for this marshaller, where a slight overshoot won't trigger the "overshot" gesture.
OR
2. Bring a continuous transition from batons parallel to fully crossed, making it easier to predict.
I have no idea how to code, so I don't know which one is easier to do.
For anyone else reading, this is NOT what I consider a fatal flaw in GSX, I still recommend the product. There are multiple marshallers in the software, and the chances of getting this particular one is not very high; even more so considering that VDGS will be used for a lot of gates as well.
