I obviously don't have one *yet*, but I did notice Counterstrike as a listed profile in some driver screenshots.

So, how's driver support and response time in games, especially of the space variety? Any tips or tricks?
Moderator: Moderators
Is is required to stay in Test Mode for the driver to continue to work? I couldn't find abything on it. When I get out of test mode the driver has a yellow exclamation point even when I made driver signing off permanently.muddiman wrote: ↑Sun Jan 21, 2018 3:00 pm I’ve been using the RBC9 SpaceNavigator driver and program since its release in January 2007. RBC9 wrote the program and driver because of the limitations of the 3Dconnections software. Those limitations still exist today in the current 3Dconnections software. Windows XP was the operating system at the time and it worked great until Windows started releasing 64Bit operating systems. Since that time RBC9 disappeared from the scene never to be heard from again. Fortunately, he had provided the complete source code for his project. There were several updates to RBC9’s driver and software by others making it functional in Windows 7 64Bit. Michael Balieu was the last one to update the driver and software. Since that time I’ve been using Windows 7 64Bit as my gaming operating system along with Michael Balieu’s RBC9 update. I resisted to upgrading to Windows 10 because I would possibly lose the functionality of my custom controller that depended on the RBC9 software and driver. I’ve built several controllers over the years using the electronics of the SpaceNavigator and RBC9’s software.
After recently building a new Windows 10 64Bit PC I successfully installed the driver. So far I have never had the Blue Screen of Death (BSOD) using the Michael Balieu RBC9 driver. The only issue I have is the RBC9-SpaceDeviceTool may close at times but the configuration continues to work as applied.
Why I use the RBC9 software and driver.
1) It supports slices *(See note below).
2) Very easy to program.
3) The ability to bind a keyboard functions at any axis value.
4) Program keyboard bind to function with full axis. (Keyboard bind would be pressed either way the axis was moving.)
5) Program keyboard bind press to function only when the axis goes in the minus direction.
6) Program keyboard bind press to function only when the axis goes in the plus direction.
7) Provide a Dead zone for the keyboard bind press.
Program multiple keyboard key binds per axis.
9) Program keyboard bind to be pressed only.
10) Program keyboard bind to be release only.
11) Program Keyboard bind repeat rate.
12) Program Keyboard bind as a long or short press.
13) Provide any keyboard key as a bind.
*Here is a good example of programming multiple binds/Slices per axis for a FPS game.
Program at mid axis minus direction for the player to go to couch position, the couch state would remain until the axis crosses zero and into the preset positive direction. At that time, the player would return to standing position. Now add another bind beyond the couch setting near the full axis and the player would go into the prone position, the prone position state would remain until the axis crosses zero and into the preset positive direction that would return the player back to standing position and/or add an additional bind in the positive axis that would make the player jump.
Below is a link to the docs and drivers for the Windows 10 install.
https://drive.google.com/open?id=16LxFm ... pHpGOyEv8Y
Best Regards,
Don Muddiman