3Dconnexion Forum

Run your program, then start our GUI. Change some button assignment on your 3D mouse.
This will generate an xml file in %appdata%\3dconnexion\3DxWare\Cfg named for your program.
PM that file to me.

The 3D mouse cap does not make a great 2D cursor mover. But we have seen reasons to use it or at least try it. You have some options. 1) You can create a cfg file for the applications you want to try this out in (e.g. a game). 2) You can edit the Desktop.xml cfg to add 2D mouse events, then switch t...

That's a good idea. But no, that is by design.

(I'm testing my memory) There were probably two places files where kept. 1) Under Program Files (this is where our installer would put them) 2) Under %appdata%/3dconnexion/something (this is where your changes are kept) Installing the old software on the new machine would take care of #1. But it is ...

Sorry. The xsi:type=... is for a default file. I should not have included that for you to put into a user file. I'll go back and edit that. There's always a problem with keyboard localization. The key that is stored isn't necessarily the key that is printed on keycap. It is really a physical key loc...

That is very old. I'd be very surprised if such an old driver build would run on a recent O/S. If this software and device worked on your old computer, there may be a .scg file for Technomatix on that old computer. Check your %appdata% directory. If you can get that old software to run on your new c...

sime,

Which driver versions are you installing? That works and doesn't work.
Which device model is this? There were a few that were white.

Also try with 3DxWare uninstalled.

What version of 3DxWare?
You should have received a notification about this conflict in the Action Center.

If you run Solidworks at a higher UAC level than the driver, the driver can't talk to it. You need to run 3DxService.exe at the same level (run as administrator). It isn't recommended.

Bug or feature, one of them. I probably add all the Macros from the Macro table into the button category. Since you are creating a Type="App", it adds it to the App category (e.g., TopSolid). If you said it was Type="Macro", it might detect the collision. I don't know if it is smart enough to choose...

Interesting. What is the serial number of your device? I'll see if there was a hardware change between mine (pre-production) and yours.

I have no idea. I assume if you unplug the SME, it goes away. Don't you have other 3D mice? Any issues with them? There are no unusual (e.g., emulated) axes on the SME. It's a very clean HID device. The only thing non-trivial about it, is that it contains groups of buttons, with breaks in the number...

Repier37,

Do you want it listed in both places?
It doesn't make a difference to me if you do (and there's no harm in having it in multiple places). You can also make your own category.
But if it is a bug, then I'd like to look at it.

Let us know what you find out. We recently had a forum user tell us about a new Microsoft O/S component that causes problems with our devices: Game Bar

I confirmed if you press certain combinations of SME hardware keys you do get an extra key presssed. In your case the SME Esc+Tab+Enter keys press those keys and also a button 1 is sent. The button 1 is the Menu key, so the driver thinks you are pressing the Menu key and toggles the GUI. The same do...