Eeproc wrote: ↑Sun Nov 22, 2020 3:29 pm
Hi Luping,
I'm assuming by that you mean manually retyping out the configuration file to make it work with 10.7.0?
I will look into doing that but it doesnt help me if to create any new profiles/commands i have to do that manual entry every time.
Is anyone aware on how to fix the issue with 3DxSmartUi not holding the correct window for selection. For example I can enter the explorer.exe and open the properties which brings up the mouse.
If I then click buttons the Button screen opens up.
This shows what program I currently have selected in this case "3DxSmartUi"
I can then click into any other program i.e. Solid edge and Solid edge will show as being selected with all the buttons changing to default solid edge buttons depending on what environment I'm in.
Now normally id click back on the buttons window and it would hold "Solid edge" as my last selected program and allow me to customize and set the buttons for what ever "environment" I was in.
But as soon as i click into the button window it selected the environment back to "3DxSmartUi" which means i can't do anything apart from manually editing the configuration file in notepad.
Has anyone else experienced this problem or have a solution?
Any help would be greatly appreciated. Thanks.
No, I mean when the 3DxWare driver v10.7.0 is installed and running while SolidEdge is running as the active application in focus, call out the 3DxWare control panel by hitting the MENU button on your SpaceMouse Enterprise hardware, actually the 3DxSmartUi.exe process.
The problem you described is what I once reported in another thread in this forum, the lack of application-specific sub-menu/sub-command list from the Buttons configuration window, in my case of testing, Siemens NX v1880, while in your case, it's Siemens SolidEdge ST9 with MP13.
Check out the screenshots below, the 3Dconnexion Viewer is detected by 3DxSmartUi.exe process and 3Dconnexion Viewer application is showed in Buttons panel commands mapping section with sub-commands for reassignment. The problem is that 3DxWare v10.7.0 is claimed to support NX v1872, v1899, v1926, but not the kind of maintenance release version between, in my test case, v1892 and another guy's v1880(all belong to v1872 major release). I believe the problem is the same one happened to your SolidEdge ST9 with maintenance pack 13, after many maintenance packs, the SolidEdge ST9 just lost the ability to be fully detected by 3DxWare v10.7.0. I suppose the initial SolidEdge ST9 with no maintenance pack should be fine with 3DxWare v10.7.0.
So far, I don't think 3Dconnexion driver developer(s) will investigate the issue what we're experiencing right now, they simple don't have enough resource to cover this specific CAD workbench/environment incompatibility issue.

- NX 2 not detected.png (72.48 KiB) Viewed 1228 times

- Viewer.png (119.6 KiB) Viewed 1228 times