Quote:
Originally posted by gonk:
I looked back at the post in question . It was in response to a post that suggested that Outlaw was doing nothing about the issue, even though someone had reported just a few posts earlier that they'd been helping Outlaw test updated firmware designed to fix the problem.
We also have comments in this thread that say Outlaw doesn't consider this an issue but more of a "feature". It would be nice to know really what they think and what (if anything) they are doing about it.

The bottom line is that the issue was raised almost a year ago, and the way Outlaw has dealt with it has only frustrated customers. If they don't feel this is an issue then say so. If they can't fix it, say so. If they consider this an issue and are planning on fixing it then say so and give an estimate of when. At least we would know what to expect.

Quote:
Originally posted by gonk:

...so all I can do is make note of what I've seen transpire in the past.
Thank you for sharing your experience - it is appreciated. Given what you've seen in the past, is this type of response to an issue typical of Outlaw?