3dconnexion spacenavigator not working on siemens NX

[barrero]

Finally I found a solution: just has to run the file 3dxsrv.exe like administrator!!! I lost many time searching updates and reading the forum. finally the solution was simple like that.

 

[JohnRBaker]

Yes, it's best to install the Spaceball driver to start when Windows starts. Then when NX is started it will automatically connect to the already running driver task. This is also an advantage if you're ever going to be running more than one session of NX at once since if NX launces the software, when you close NX if will close the driver as well, which means that if two session of NX are running and you exit one of them the driver may no longer be active for the other NX session. Besides, there are now applications other than NX which can also take advantage of the Spaceball, such as Google Earth.

John R. Baker, P.E.
Product 'Evangelist'
Product Engineering Software
Siemens PLM Software Inc.
Industry Sector
Cypress, CA
Siemens PLM:
UG/NX Museum:

To an Engineer, the glass is twice as big as it needs to be.

 

[shags72]

This didn't work for me. Stopped the driver and restarted, run as admin and started up TC and NX and neither of the buttons will do any nx command.

 

[JohnRBaker]

When you install the driver there should be an option to launch it on Windows start-up.

John R. Baker, P.E.
Product 'Evangelist'
Product Engineering Software
Siemens PLM Software Inc.
Industry Sector
Cypress, CA
Siemens PLM:
UG/NX Museum:

To an Engineer, the glass is twice as big as it needs to be.

 

[shags72]

Had that set up but didn't think that started it as admin. Usually have to actually start things by right click and run as admin. At least that is what I thought. Correct me if I am wrong. I could have misunderstood the OP's statement but I thought he meant that he started the driver as admin and then the space puck or whatever worked. I can use the puck with NX right now but cannot assign any NX related commands to a button. I had a thread on this before and still have no luck getting this done.

 

[JohnRBaker]

I don't know what to say, but I use three different spaceballs all with the same driver and they all work just as you'd expect them to. However, I run full-time with admin privileges since I'm always installing and uninstalling versions of NX. Note that on this laptop, that I've had for about 2 years now, I've only installed the 3DConnextions driver once and haven't had any problems. The Release Version is 3.11.3 and the Driver Version is 6.11.1.

John R. Baker, P.E.
Product 'Evangelist'
Product Engineering Software
Siemens PLM Software Inc.
Industry Sector
Cypress, CA
Siemens PLM:
UG/NX Museum:

To an Engineer, the glass is twice as big as it needs to be.

 

[barrero]

What we did was, close the 3dxware program, find the 3dxsrv.exe, then right click, and in the tab compatibility mark "run as an administrator", that solved the issue. but our buttons were not gray... the buttons worked but not the device.
Maybe you can try the 3dconnexion suggestion:

"Button Mapping Editor" and "Device Settings" are grayed out in NX

The 3DConnexion Plug-in for NX requires the following System Environment Variables to be set correctly:
Rename the global system environment variable from "UGII_3DCONNEXION_LIBRARY" to "UGII_3DCONNEXION_LIBRARY_BAK"
Open the following file (e.g. for NX6): C:\Program Files\UGS\NX 6.0\UGII\ugii_env.dat
Add the following line to this file: UGII_3DCONNEXION_LIBRARY=${UGII_BASE_DIR}\UGALLIANCE\vendor\startup\3dxnx.dll

Repeat steps 2. and 3. for all NX installations.

 

[shags72]

Button Mapping Editor" and "Device Settings" are grayed out in NX

The 3DConnexion Plug-in for NX requires the following System Environment Variables to be set correctly:
Rename the global system environment variable from "UGII_3DCONNEXION_LIBRARY" to "UGII_3DCONNEXION_LIBRARY_BAK"
Open the following file (e.g. for NX6): C:\Program Files\UGS\NX 6.0\UGII\ugii_env.dat
Add the following line to this file: UGII_3DCONNEXION_LIBRARY=${UGII_BASE_DIR}\UGALLIANCE\vendor\startup\3dxnx.dll


Don't have that dll in that folder in TC or standalone NX. Could be the issue.