we are aware that there is a problem with the modifier keys in 3DxWare 10.6.6. We are tracking this issue with our internal bug number WIN-650. A fix will be available in our next driver release. Sorry for the inconvenience.
Thanks. But good job on fixing the flickering, crashing and disappearing objects bugs! I have not seen an issue there yet. But i am not using my Space Pilot too often, now. Because of the buttons bug.
Cheers!
TomKoe wrote: ↑Wed Apr 22, 2020 3:35 am
Thanks. But good job on fixing the flickering, crashing and disappearing objects bugs! I have not seen an issue there yet. But i am not using my Space Pilot too often, now. Because of the buttons bug.
Cheers!
hi TomKoe,
I had the same problem. (buttons bug)
solution is > open the lastest driver ver. 3DxWare64_v10-5-15.exe package > 7-zip app (https://www.7-zip.org/)
and open inside 3DxWare64.exe > subfolder components64 > 3DxWinCore > 3DxWinCore64.msi install
If you get an error just because the new version is installed > Likewise, you can get into the version 10.6.6 package with 7-zip and uninstall 3DxWincore. (current version). Then you can install the old version wincore.
I have a better workaround than using an old driver.
Workaround for the keyboard emulation problem with 3DxWare 10.6.6
Open the Device Manager. Note that you need administrator privileges to do the following.
You will not have an entry under “Human Interface Devices” named “3Dconnexion KMJ Emulator”.
Instead you will find an entry “Other devices -> Unknown device” with a little yellow exclamation mark.
Right click this entry and select “Update driver”.
Next click to “Browse my computer for driver software”.
Navigate to the path “C:\Program Files\3Dconnexion\3DxWare\3DxWinCore\Drivers\3DxKMJ”.
omerkunul wrote: ↑Wed Apr 22, 2020 5:13 pm
I had the same problem. (buttons bug)
solution is > open the lastest driver ver. 3DxWare64_v10-5-15.exe package > 7-zip app (https://www.7-zip.org/)
and open inside 3DxWare64.exe > subfolder components64 > 3DxWinCore > 3DxWinCore64.msi install
If you get an error just because the new version is installed > Likewise, you can get into the version 10.6.6 package with 7-zip and uninstall 3DxWincore. (current version). Then you can install the old version wincore.
Yay! Thank you @omerkunul! That worked. But i did then try the official and clean workaround by UtaSH:
Open the Device Manager. Note that you need administrator privileges to do the following.
You will not have an entry under “Human Interface Devices” named “3Dconnexion KMJ Emulator”.
Instead you will find an entry “Other devices -> Unknown device” with a little yellow exclamation mark.
Right click this entry and select “Update driver”.
Next click to “Browse my computer for driver software”.
Navigate to the path “C:\Program Files\3Dconnexion\3DxWare\3DxWinCore\Drivers\3DxKMJ”.
Yes, sorry. We removed 10.6.6 due to the problems with the keyboard emulation problem. We will provide a newer version very soon that has this issue fixed.
The last update work 90%% correct in MaYa.
Still some issues showing up.
Because the new driver now when I click to edit my display layer one day if goes to the really top of the screen you will never see your window display edit window again.
But now we have a huge problem than just MaYa.
After effects shows flickering as other users mentioned they have in MaYa.
Im experiencing a lot of problems using the latest drivers in many other apps.
Hope will see soon a new update, because the drivers are attacking also other Softwares which is not good at all.
Crashes when merging vertices and other various operations that perform a similar function in Maya 2020. reverted to legacy drivers and Maya2019 to test and it work fine there. We may be needing to return a lot of these SpaceMouse devices if the issue still persists with in a 30 days of this post with no driver updates to resolve the issue. Its no big deal to us to not be using them but im lazy and dont want file a return for 14 of these lol.
Equipment: SpaceMouse Compact
Software: Maya 2020.1
OS: WIndows 10
Try edit the Maya.env file and add the line: MAYA_DISABLE_OPENCL=1
I have been having time to time same behavior that you are having and for me disabling opencl helped. I am not sure if it is "correct" fix but worth trying.
I always copy my old maya preferences and plugins to new maya version and i would not bee too surprised if that is the root cause. Maybe if i have some extra time i would go do clean install and install all my scripts one by one but it would be sooo tedious job...