I certainly am patient enough to wait for a solution, provided that I receive some feedback at a reasonable time interval, to prevent the costumer feeling that nothing is being done.
I already replied to you in this thread with a "we'll check this". And no, I don't find "unreasonable" taking 3 days to check a bug, because (as you can clearly see), there are OTHER bugs and other customers that are being followed constantly. Again, just check my forum post count, it speaks for itself.
Here I cannot agree with you. I purchased the MJCQ400 on the 7th of June 2013 and it is the only airplane I have been flying with since then. I purchased GSX on the 20th of September 2013 and it worked fine. As you can see there is no chance that I didn't notice the catering vehicles issue before (with older GSX versions).
You haven't noticed it because, most likely, the configuration for the Q400 that comes with GSX has changed between releases, either because there was no catering service on the front door, or because the door's height was moved just a little bit that made a different catering to appear. If there's just one catering, or if there are two vehicles with full animations (with the service crew and the platform), the problem doesn't appear. It ONLY appears when one of the vehicles has a crew and the other doesn't, and this depends how the front door is configured, but nothing in the GSX catering code has ever changed, not from many months, and surely well before you purchased it.
You can get an easy proof of this quite easily: just change the Q400 config with the GSX airplane configuration editor and remove the front catering door, the bug will disappear ( select "restart Couatl" before trying the new config )
I asked for an older GSX version for two reasons, to fully profit from the good software product I purchased and somehow to help FSDT to troubleshoot the catering vehicles bug.
An older version won't change anything in this regard,
If the issue is known by FSDT and you are working on solution for that, why didn't you mention it since my very first post???
This issue has been found only AFTER your report. When I've said "we'll check it", I MEAN IT. To be precise, I've confirmed the bug yesterday very late in the night, and since today I was out of office the whole day, I couldn't get a chance to reply it before you posted your complaint about the supposed lack of a reply.