3Dconnexion Forum

An additional note on this: It appears that this issue is not isolated to R17 on Windows7. Today, a co-worker running CATIA R18 (with Win7) had a crash that caused his spacemouse to stop functioning. The reg hack listed below was used to get the spacemouse functional again without having to uninstal...

Hi Nuno, We are aware that R17 is not supported on Windows 7, but the use of R17 is required by one of our customers. Rather than working with dual boot computers, we just run it in Win7. I have been chasing this issue for a little while now, and was able to finally narrow it down to that specific r...

Re-visiting this issue: We have had several instances where, following a CATIA R17 crash, the spacemouse stops working in R17. It continues to work fine in other applications (SolidWorks, 3dx Demos, etc) and even in other releases of CATIA. The problem seems to be related to a registry entry that Wi...

Solved the problem by fully uninstalling all versions of CATIA and 3d Connexion. Deleted the relative installation folders from Program Files. Went through the registry and removed entries pertaining to Dassault Systemes and 3d Connexion. Re-installed software. I suspect the issue was that CATIA R18...

A couple of other things I probably should have included.... I did check to see that the environment variable ADL_ODT_IN was not being used. Additionally, the other 2 computers that the 3d Navigator functions correctly are using the same CATIA environment as the computer that the Navigator will not ...

Strange behavior with the 3d Navigator.

It functions fine in CATIA R18, but does not work in R17.

OS: Windows 7 64 bit
3Dx driver: 3.10.1

However, a co-worker using the same OS and driver does not have the problem I do.

Demos function fine.