VMD-L Mailing List
From: Bennion, Brian (bennion1_at_llnl.gov)
Date: Thu Aug 06 2015 - 11:36:17 CDT
- Next message: Bennion, Brian: "RE: 3dconnexion spacemouse pro and vmd on fedora 21"
- Previous message: John Stone: "Re: 3dconnexion spacemouse pro and vmd on fedora 21"
- In reply to: John Stone: "Re: 3dconnexion spacemouse pro and vmd on fedora 21"
- Next in thread: John Stone: "Re: 3dconnexion spacemouse pro and vmd on fedora 21"
- Reply: John Stone: "Re: 3dconnexion spacemouse pro and vmd on fedora 21"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Thank you for the quick reply. I have been working on this issue on and off for a couple of months.
There are no spacenavd messages in the vmd startup text.
Switching to the spacenavd drivers and getting the daemon running and confirmed as running from the spnavcfg gui is as far has I have been able to get.
Initially, I tried installing the proprietary drivers but don't know if they were even running.
Maybe having both sets of drivers is causing the trouble.
My ergonomics people are hoping that I can reduce using my mouse in my visualization work.
Brian
________________________________________
From: John Stone [johns_at_ks.uiuc.edu]
Sent: Wednesday, August 05, 2015 10:32 PM
To: Bennion, Brian
Cc: vmd-l_at_ks.uiuc.edu
Subject: Re: vmd-l: 3dconnexion spacemouse pro and vmd on fedora 21
Hi,
Assuming that the "spacenavd" daemon is running, and is
has registered and is generating standard X-Windows events
it should work fine with VMD.
The first thing to look for is whether or not VMD is detecting
that the spacenavd driver is out there. When you run VMD you
should see a message like this:
Info) X-Windows ClientMessage-based Spaceball device available.
If you see that, then VMD sees that spacenavd has registered the
special X-Windows event objects that the commercial drivers generate.
If you don't see that message when VMD starts up, then it doesn't
see those event types registered, and it can't talk to spacenavd for
some reason.
Even if VMD prints the message during startup, it won't respond to
the device unless the mouse focus is on the VMD graphics window.
So, make sure the mouse cursor is within the bounds of the VMD
graphics window, and then try moving the SpaceMouse Pro and see
if it responds.
If neither of these work correctly, then we'll need to dig further
and figure out if "spacenavd" treats the SpaceMouse Pro differently
than a SpaceNavigator, or other devices in the same hardware family,
for some reason. If you can tell me more details about the behavior
you see, it shouldn't be too hard to figure out what is working and
what isn't.
Cheers,
John Stone
vmd_at_ks.uiuc.edu
On Wed, Aug 05, 2015 at 08:02:54PM +0000, Bennion, Brian wrote:
> Hello,
>
> I am curious if any vmd user has had any luck getting vmd-1.9.2 to access
> a space mouse pro device.
>
> I have installed the spacenav drivers and the driver is running fine
> according to the spnavcfg gui.
>
> Based on the vmd website vmd1.9.2 should automatically detect usb spacenav
> devices. Perhaps I am missing something simple.
>
> Brian Bennion
-- NIH Center for Macromolecular Modeling and Bioinformatics Beckman Institute for Advanced Science and Technology University of Illinois, 405 N. Mathews Ave, Urbana, IL 61801 http://www.ks.uiuc.edu/~johns/ Phone: 217-244-3349 http://www.ks.uiuc.edu/Research/vmd/
- Next message: Bennion, Brian: "RE: 3dconnexion spacemouse pro and vmd on fedora 21"
- Previous message: John Stone: "Re: 3dconnexion spacemouse pro and vmd on fedora 21"
- In reply to: John Stone: "Re: 3dconnexion spacemouse pro and vmd on fedora 21"
- Next in thread: John Stone: "Re: 3dconnexion spacemouse pro and vmd on fedora 21"
- Reply: John Stone: "Re: 3dconnexion spacemouse pro and vmd on fedora 21"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]