From: John Stone (
Date: Thu Oct 03 2013 - 09:15:06 CDT

  Can you try the non-CUDA version of 1.9.1 quickly and verify
that it sees your SpaceNavigator? If it does not, then that would
indicate that the problem is caused by something other than VMD, and
would be an indication that they've changed the communication protocol
or something else and made it incompatible with the original drivers.
I just want to verify that your problem is indeed a VMD issue and not
something else.


On Thu, Oct 03, 2013 at 10:35:00AM +0200, FX wrote:
> > Which VMD binary are you running? There was a bug in
> > the 1.9.1 release that prevented Spacenavigator from working
> > with the CUDA-enabled VMD binary.
> Well, I was running that one, as I saw no mention of it in the release notes.
> > Try running the non-CUDA version
> I need CUDA.
> > or try one of the more recent Windows test versions of VMD and it should cure the problem. I can do a new test
> > build of VMD 1.9.2 if necessary to solve your problem.
> I've tried 192a13 (which seems to be the most recent Win32 CUDA build on BioCore), but it does not work. I'd appreciate if you could spin a recent build at some point.
> Cheers,
> FX

NIH Center for Macromolecular Modeling and Bioinformatics
Beckman Institute for Advanced Science and Technology
University of Illinois, 405 N. Mathews Ave, Urbana, IL 61801           Phone: 217-244-3349