well, the vehicels always "crash" into each other on the taxiways
They don't. Unless you confused with FSX default ground vehicles or FSX AIs. As explained many times already, GSX vehicles don't have the slightest notion of non-GSX surrounding traffic, because it would become both to complex, slow and it would create lots of traffic deadlocks.
If you saw two GSX vehicles crashing into each other, than clearly indicates a reproduction case which, as explained many times already should ALWAYS include ALL the following informations:
- The airplane used, clearly indicate which airplane is, if it's not default.
- The airport used, clearly indicate which airport is, if it's not a default one.
- The gate used.
- The GSX operation selected and possibly the order of the operations selected if multiple operations were selected.
the movement of the baggage cars is bugged
It's surely isn't. If you saw a case of a "bugged" baggage cars, clearly indicate a reproduction step, including ALL the above informations.
,the movement of the bus as well
Same as above.
the follow me sometimes just drives around the airport not on the taxiway atc has given me
Same as above, and when reporting a problem related to the follow me, include also the Runway or the place in the airport (lat/lon coordinates) of your positions when you called the Follow me, and which parking you selected as its destination.
the pushback drives through the "wingwalker" or marshall...
It surely doesn't. If you saw it on a specific place or situation, again, indicates ALL the informations we ALWAYS ask for a bug report.
thats a few problems for example, u happy now? not saying that i dont love this product, but there are still many problems..
And how are we supposed to do anything with the little information included in such kind of post ? You made it look like as if GSX had the problems you reported everywhere in any situation.
This is not the case (otherwise WE first would noticed it and of course many user would noticed too), but it's clearly something it might happened to you sometimes, so you assumed it's the "standard" behavior, but it surely isn't. GSX works with 20.000+ FSX airports, you can't obviously expect we'd test them all, we can only tweak the program to being able to consider the most wide range of possible different situations.
Note that, a big part of this, is how GSX handles mistakes in the AFCAD made by scenery developers, who liberally use AFCAD features to do something they are not intended to, like playing with parking sizes to assign AI vehicles and companies, a lot of the problems you are reporting looks like being related to a "too small" parking size problem, which of course can be fixed in GSX without having to edit the underlying AFCAD.
There IS a reason we allow customization of parking specifications and vehicle placements, what you attributed to "bugged" movement, might be a result of vehicles starting in positions too crammed together so they don't have *physical* space to maneuver, especially the baggage train, which is fairly long, requires a bit of space in the parking spot so, editing it and either enlarging the spot, or placing the vehicle in a more sensible starting position (GSX can't obviously know about the surrounding buildings, but you CAN customize this), might solve a lot of problems.
Sometimes the problem might be related to the relationship between the vehicle starting position at a gate, the airplane's doors positions AND the actual position you parked in that specific case. At some parking, there might simply not enough space to use a front baggage loader, for example. Which is why, we allow to customize that parking position to disable it.
Again, first try to learn how to use GSX properly AND, when something looks wrong, ALWAYS file a proper bug report with ALL the requested informations, so we can replicate it and eventually fix it, if it's really a program error that can't be fixed with a scenery customization.
And please, don't reply in THIS thread (which is about the "Crew salute" feature) with a bug report. Make a proper separate thread, not in the GSX Backdoor, but in the proper GSX Support area, and possibly open a different thread for every different problem report. This will make us easier to track and follow.
