starnet Several. All answered promptly but not related to any code changes. If something is "important" to me, that is the route I'd take (ticket plus logs). But I'm also not an advanced user and have not stumbled into a usage scenario that causes me concern, yet. And if I did, I'd absolutely do my best to provide them, and myself, a means to track the issue (ticket number) and diagnostic data to aid in debug. Plus I'd nag. But not on this forum. Privately.
For this particular issue, how would you expect them to debug this issue if they don't have potential diagnostic data of the problem? Have a development resource spend hours/days/weeks trying to reproduce it? Add to that, if I understood the problem correctly, this is an edge case (zenith). So the next question to ask is how many customers will this issue affect? Probably not many (maybe I'm wrong).
Your expectations for this product and the support behind it obviously don't meet your needs. For $500, you should have expected that. Try Celestron products instead. They charge much more, and from my experience, have a larger development group for support. Of course, you have to pay for that capability.
Have fun!