I have a SPACE EXPLORER 3D Connexion mouse, that was installed some while back. I cannot recall how it was deactivated but it doesn't work at the moment.
So the IT manager downloaded and installed the latest drivers (3DxSoftware64_v3-17-8_r1730) so I could use it with SolidWorks ..... again.
The Add-In appears OK, and some of the buttons work fine. However, the controller in the middle doesn't do anything, i.e. rotate or zoom.
I'm running Windows 7, 64bit, but that's as far as my knowledge goes. So no 'geeky' answers please.
The mouse works perfectly with the trial/practice program that install with it.
When I get this working, then the next challenge will be to get it working in CATIA V5, the other program I use. There is no response at all for this yet.
3D Connexion in Solidworks
Moderator: Moderators
Re: 3D Connexion in Solidworks
Perform a clean install of the profiles.
http://www.3dconnexion.com/faq/1100
http://www.3dconnexion.com/faq/1100
Re: 3D Connexion in Solidworks
CATIA Navigation
When a 3Dconnexion device works outside of Catia - such as in the 3Dconnexion Jet demo - but not inside Catia the most likely cause is firewall software preventing Catia from seeing the device .[Start, All Programs, 3Dconnexion, Demo- Jet Demo]
Catia recognizes a USB device as a network connection.This FAQ describes the firewall exception needed http://www.3dconnexion.com/faq/4
Typically on a network an IT tech is needed to add a firewall exception. To add an exception for the Catia executable - CNEXT.EXE - the IT tech needs to determine where on your system CNEXT.exe is located. Common paths for CNEXT.exe are C:|Program Files|Dassault Systemes|B17|intel_a|code|bin|CNEXT.exe
C:|Program Files|Dassault Systemes|B17SP5PRALL|intel_a|code|bin|CNEXT.exe"
C:|Program Files|Dassault Systemes|B19|win_b64|code|bin|CNEXT.exe
To add a firewall exception for the 3Dconnexion software, add the path for 3dxsrv.exe [C:|Program Files|3Dconnexion|3Dconnexion 3DxSoftware|3DxWare|3dxsrv.exe] On a 64-bit system the 3DxWare folder is 3DxWare64.
When navigation is present in the demos but not in Catia , check whether it was working then stopped after a Catia crash. This forum thread describes a Windows7 registry key created after a Catia crash that must be removed to re-enable navigation.
viewtopic.php?t=3630
If navigation is not initally present in Catia, the USB connection is most likely being blocked by the firewall.
See http://www.3dconnexion.com/faq/4
There are two other circumstances - both fairly uncommon - that can prevent a 3D device from working in Catia. In 9 out of 10 instances, reports of no navigtion in Catia for an inital setup need the firewall exception and for an existing setup they need the 'After a Catia crash' registry fix. The 2 less common circumstances are a Catia profile mis-match and an environment variable that can disable 3D navigation.
1.There is a configuration for versions of Catia previous to V5 R15. Check the configuration in the 3Dconnexion Control Panel when Catia is open. The configuration should be "CATIA R15+" .
If one of the Catia V5 PreR15 configurations is in use , that would prevent the device from working in Catia V5 R15 and above.
If "CATIA R15+" is not listed in the configurations , check that the file "CatiaR15+.scg" can be found under the folder:
C:|Program Files|3Dconnexion|3Dconnexion 3DxSoftware|3DxWare|en_us|profiles|default
Since you have just installed the current driver , this config should be present.
2. Variable ADL_ODT_IN
http://www.3dconnexion.com/faq/3
To speed up application launch, some users define the environment variable ADL_ODT_IN. This variable is not meant for general use and, when defined, will disable the application's internal support for 3D mice
When a 3Dconnexion device works outside of Catia - such as in the 3Dconnexion Jet demo - but not inside Catia the most likely cause is firewall software preventing Catia from seeing the device .[Start, All Programs, 3Dconnexion, Demo- Jet Demo]
Catia recognizes a USB device as a network connection.This FAQ describes the firewall exception needed http://www.3dconnexion.com/faq/4
Typically on a network an IT tech is needed to add a firewall exception. To add an exception for the Catia executable - CNEXT.EXE - the IT tech needs to determine where on your system CNEXT.exe is located. Common paths for CNEXT.exe are C:|Program Files|Dassault Systemes|B17|intel_a|code|bin|CNEXT.exe
C:|Program Files|Dassault Systemes|B17SP5PRALL|intel_a|code|bin|CNEXT.exe"
C:|Program Files|Dassault Systemes|B19|win_b64|code|bin|CNEXT.exe
To add a firewall exception for the 3Dconnexion software, add the path for 3dxsrv.exe [C:|Program Files|3Dconnexion|3Dconnexion 3DxSoftware|3DxWare|3dxsrv.exe] On a 64-bit system the 3DxWare folder is 3DxWare64.
When navigation is present in the demos but not in Catia , check whether it was working then stopped after a Catia crash. This forum thread describes a Windows7 registry key created after a Catia crash that must be removed to re-enable navigation.
viewtopic.php?t=3630
If navigation is not initally present in Catia, the USB connection is most likely being blocked by the firewall.
See http://www.3dconnexion.com/faq/4
There are two other circumstances - both fairly uncommon - that can prevent a 3D device from working in Catia. In 9 out of 10 instances, reports of no navigtion in Catia for an inital setup need the firewall exception and for an existing setup they need the 'After a Catia crash' registry fix. The 2 less common circumstances are a Catia profile mis-match and an environment variable that can disable 3D navigation.
1.There is a configuration for versions of Catia previous to V5 R15. Check the configuration in the 3Dconnexion Control Panel when Catia is open. The configuration should be "CATIA R15+" .
If one of the Catia V5 PreR15 configurations is in use , that would prevent the device from working in Catia V5 R15 and above.
If "CATIA R15+" is not listed in the configurations , check that the file "CatiaR15+.scg" can be found under the folder:
C:|Program Files|3Dconnexion|3Dconnexion 3DxSoftware|3DxWare|en_us|profiles|default
Since you have just installed the current driver , this config should be present.
2. Variable ADL_ODT_IN
http://www.3dconnexion.com/faq/3
To speed up application launch, some users define the environment variable ADL_ODT_IN. This variable is not meant for general use and, when defined, will disable the application's internal support for 3D mice