Written replies don't have any "tone". Well, not really, they DO have one, one that can easily mistaken for a "tone", because written statements tend to be more assertive than the spoken word, and that's because I try to be as accurate and precise as I can be.
Being as accurate as possible, might make the reply to sound more hard than it really is, but is in fact doing you a much better service, in the end, because while a more courteous and corporate "tone", that is designed to tell you exactly nothing, but makes you feel better (without telling anything), is what formally trained support people use, which is not what I am, I a developer, so you can be sure you'll always get the truth from me, the USEFUL truth, and sometimes the useful truth might sound more harsh than how it's intended.
BTW, I see you sent today another email saying you were never replied to. You HAVE been replied to, of course, so I sent you another copy of the email you should have received on the 10th.
Let's see all your 5 points, again:
1) You apologize for this, thank you.
2) The parking too small message.
I have tried ticking the "Ignore wingspan when parking" option. However I still get the call-out "too small for this aircraft" including when selecting a parking spot after landing, despite this option being checked. I'm expecting to be told it is just my mistake or a misunderstanding here though.
Let me clarify here:
You will STILL see the parking LABELED as being too small, even if you check the "Ignore wingspan when parking" settings. This is of course intentional, because we still want you to KNOW that, according to the data GSX has, the parking IS too small for your aircraft.
However, enabling that ignore setting, will remove the audio message you normally get when the setting is disabled, and won't show the warning when you start a flight there.
3) The menu closing after choosing an option:
Even after popping-out into it's own window for easy access next time, the window just goes black. If this is intentional then I understand but I'd add a feature request that if the user has opened in an independent window that it remain available, if for no other reason than to meet a basic expectation of UI experience.
Yes, of course it's intentional, the whole concept of a "pinned menu" simply doesn't exists in GSX, first because it's not really needed, because most of the operations are called, last for a while and during that time, you don't really need the menu to be open, that's why a pinned menu is not really useful.
But there's also a performance issue because, keeping the menu pinned, would mean it should be kept refreshed, with its entries possibly updated to reflect any changes in the operation status (changes that now are conveyed to you by using the text messages on top), and this constant refresh might affect performances for little benefit, while now the menu refreshes ONLY when you open it, so nothing is done in the background to keep up updated.
So, again, it just how the program is DESIGNED, not a bug.
4) GSX supposedly asking to stop the engines when you are still taxiing.
I was still on a taxi-way quite far away from the terminal about half-way between end of runway and the main terminal apron, and the park was far end of the terminal at a large airport. If this is a feature then I stand corrected, but I must say as far as user-experience goes, the inability to simply open the GSX Pro menu at any point can feel jarring.
So you were outside the parking spot you selected but, maybe, you were inside ANOTHER parking, so GSX was correct expecting to turn off the engines because, from its point of view, you simply decided not to use the parking you selected, and went into another one, and when you are inside a parking spot, you must turn off the engines to call GSX.
Without knowing *exactly* your position and all the data about the scenery in use, it's not possible to say more about this. It's even possible you weren't inside another parking, but from GSX point of view, you were.
This can happen if you are using a 3rd party scenery, but you forgot to Disable GSX replacement jetways for that airport, which MUST be done, as explained in the GSX Manual at Page 7, under the "IMPORTANT" heading.
Failing to do so, as the manual says, would introduce a parking position conflict, making GSX getting data about parking spot for the wrong scenery, so it's telling you are inside a parking, one that came with the scenery you were supposed to Disable.
- The volume controls for the voice announcements don't seem to have any effect. I have set both volume sliders to the lowest (just to cover all bases) and the main voice is still loud.
That is true, the audio alerts are made using a different method that is not controlled by the GSX normal Volume slider, because that only controls the sounds of the vehicles, not the aural alerts. That's not really a "bug", more like a missing feature due to the different class of those audio alerts, which would probably require a separate volume slider. However, you CAN disable those alerts, in the Settings.
I get I made some mistakes and had some misunderstandings, but I stand by the opinion that the overall experience does not justify the full price.
Even after going through your list again, we can only confirm that none of the issues your reported were really "bugs", and could be dealt with a knowledge of the product, gained by reading its manual.
The things that are common complaints but are really "features" should be communicated to the user better in-game to help mitigate perceived problems. Just my opinion.
You are free to voice your opinion, but you must be prepared to being it challenged. GSX IS a complex product, with a manual 94 pages long, and most of the things you labeled as "issues", already had an explanation in the manual and, if something is still missing, I'm not sure increasing the manual length would have helped in your case, since you clearly missed things we ARE in there.
