Main > Main Forum
TurboTwist Hi-Low Spinner Backspin problem. XP 64 Poll rate, Works Now!
SavannahLion:
Hard to "genericize" a remark, so forgive me. I'm not targeting one or the other.
I understand the concept, it was merely a suggestion in order to gain greater control (or variety) over hardware/software solutions/combinations while keeping hardware costs as low as possible.
Randy and Andy both have slightly different schools of thought on how to approach certain problems. I don't claim to know how either spinner works. At this point, I have no spinner. Thereby, I really have no right to judge the er... merits of any spinner. But it seems to me, based on the numerous discussions and postings, that the different spinners have slightly different approaches. I guess my point is, whatever suggestion one make might be applicable to one, both or even none.
Different strokes, different folks. :cheers:
Derrick Renaud:
If the interface caps overflow, I think it should be mentioned is the specs. Capping limits the maximum spin. The one (and only) benefit of OS poll rate backspin is to notify the user that they need to up their OS poll rate. I suppose you could add a solder jumper tab to select the use of this feature. I do understand that there is no down side to capping if your OS poll rate is high enough, but with it capped, you have no easy way to know if you are being capped without the backspin.
Andy,
at the time I had received my Opti-Pac, I had questioned you about the poll rate and 16-bit issue. You told me that the device should be unlocked, but it turned out XP was locking it to 125Hz. That is how I searched out the USB poll rate patcher. I then asked about going to 16-bit to solve the problem and you had stated compatibility concerns on doing so in USB 1.1.
Is there any problems using 16-bit data with USB 1.1. Do all versions of Windows from 95 & up support this? Do your new interfaces support 16-bit in USB 1.1 mode.
Thanks,
D.
TPB:
I guess if we're talking about spinner product descriptions that fully disclose all compatibility issues,
Notwithstanding Bender's love of his Apache, and his disinterest in playing Arkanoid or DOH, :)
The inability of a low-res spinner (such as the Tornado or Apache) to accurately play Arkanoid or DOH on ANY Operation System, for which no patch is available (as it's a hardware limitation with the spinner itself), is something that should be disclosed.
As Bender and Frizz say, ideally all issues should be disclosed, but on the scale of things, the issues with low-res spinners (which aren't disclosed by their vendors) are far greater.
Look at the Happ website - they state "The Tornado spinner is best arcade spinning device in the market today". ::)
http://www.happcontrols.com/amusement/gameparts/95265700.htm
I can see Randy's point about confusing potential customers with too much detail on problems that will only occur for a small percentage of users (those using an uncommon 64 bit OS, WHILST ALSO vigorously spinning in games like Tempest). And in any case, a patch is available to solve the problem, which Randy would point out to anyone who emailed him with a support request.
Unnecessarily confusing potential customers with a "mountain of compatibility information" about a non-issue, will dissuade some of them from purchasing, which equals lost sales for the vendor, which affects their livelihood.
And anyone who is unnecessarily dissuaded from buying, may end up WORSE OFF, if they then go and buy an inferior low-res spinner when they read outlandish claims such as those from the Happ product description above.
P.S. There's so many spinner threads on-the-go at the moment (no less than 3), touching on this same issue, it's hard to judge in which one to post. :dizzy:
AndyWarne:
--- Quote from: Derrick Renaud on March 03, 2009, 08:23:19 am ---Andy,
at the time I had received my Opti-Pac, I had questioned you about the poll rate and 16-bit issue. You told me that the device should be unlocked, but it turned out XP was locking it to 125Hz.
--- End quote ---
Yes indeed. That was many years ago when I was still green and naive. I learned on my grandmothers knee that a USB device has its poll rate set in the device descriptor. Little did I know that Microsoft had decided to ignore this on low speed USB devices!
--- Quote from: Derrick Renaud on March 03, 2009, 08:23:19 am ---
Is there any problems using 16-bit data with USB 1.1. Do all versions of Windows from 95 & up support this? Do your new interfaces support 16-bit in USB 1.1 mode.
Thanks,
D.
--- End quote ---
Yes the new interfaces support 16 bit in USB 1.1
I must admit I have not tested this in Windows 98 or 95. I suppose I should state that the new devices are qualified as compatible with XP upwards.
Andy
Derrick Renaud:
--- Quote from: AndyWarne on March 03, 2009, 11:55:47 am ---
--- Quote from: Derrick Renaud on March 03, 2009, 08:23:19 am ---Is there any problems using 16-bit data with USB 1.1. Do all versions of Windows from 95 & up support this? Do your new interfaces support 16-bit in USB 1.1 mode.
--- End quote ---
Yes the new interfaces support 16 bit in USB 1.1
I must admit I have not tested this in Windows 98 or 95. I suppose I should state that the new devices are qualified as compatible with XP upwards.
Andy
--- End quote ---
I'm not to concerned about 95 or 98 myself. I know others use it. I was just trying to remember if that was what the concern was with 16 bit data.
It's great that 16-bit is working fine in your new products. Definitely should solve any overflow problems with a locked 125Hz system.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version