Cant adjust 3dconnexion properties for solidworks 2014

[tallport2]

When I initially load Solidworks, the 3connexion properties window shows the active application as "swVBAserver" and it wont let me adjust the advanced settings. If I click on a program like Chrome, the 3dconnexion properties window shows "Chrome" as the active application. If I then click back to Solidworks, it still shows Chrome as the active application.

This is frustrating because I now am not able to use the 3d mouse in Solidworks... which is really the only reason I bought it.

For reference, its a Spacenavigator mouse, windows 7 64 bit, and Solidworks 2014 SP4.0

I've tried removing and reinstalling the drivers a few times and encountered the same results every time.

Any ideas?

[UtaSH]

Hello tallport2,

that sounds as if the plugin for the 3D mouse is not available in SolidWorks. Please check at Tools -> Add-Ins if you see the entry for "3Dcontrol". Otherwise we have to find out why the plugin is not installed or loading on your machine.

[tallport2]

Got it. I forgot that I had turned that add-in off when dealing with some earlier driver update issues.

Thank you for the quick reply!

[MichalGacz]

I have the same problem but with 3ds max 2014 64bit :/

[UtaSH]

See here.
I will contact you later for a beta version of the plugin with the fix.

[tzallas]

See here.
I will contact you later for a beta version of the plugin with the fix.

Running
Solidworks 2014 SP5
SpaceMouse Pro Wireless 3DxWare 10.2.1


Still seeing the same issue as tallport2. even with 10.2.1
the 3Dcontrol Add-in would not appear in the add-ins window in solidworks
Read this thread and the link you have supplied to the 3dsMax thread above in your quote.

I had to downgrade the driver to 10.1.4 from the link you have supplied and now the problem is solved. 3Dcontrol add-in now appears as a selection

Just wanted to confirm for other users that this temp solution works for Solidworks 2014.


Hopefully 10.2.2 will fix this issue.

looking forward to confirmation of this in a reply in this thread

thank you

[tzallas]

Hopefully 10.2.2 will fix this issue.

I have just confirmed. 10.2.2 does indeed fix this issue.