-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
3DConnexion Space Mouse is ignored in 2.2.0 - Windows #3937
Comments
We are accessing the 3D mouse directly. It may be, that we are not
interpreting the data from this particular model correctly. We tested 3
different types, it may be that yours is 4rth. Hard to know.
pá 27. 3. 2020 v 20:32 odesílatel rosscadguy <[email protected]>
napsal:
… Version
2.2.0 Win64
Operating system type + version
Windows 10 Home - 64 bit
Version 1903
OS Build 18362.720
3D printer brand / version + firmware version (if known)
Prusa MK3S/MMU2S
Behavior
-
*Describe the problem*
3DConnexion Space Mouse is ignored
SpaceMouse Wireless PN: 3DX-600044
-
*Steps needed to reproduce the problem*
Launch PrusaSlicer / Manipulate the puck
-
*Expected Results*
Scene should rotate/pan/zoom according to puck inputs.
-
*Actual Results*
The only inputs from the puck that are reflected on the PrusaSlicer
scene are:
• TILT FORWARD (away from user) ► the scene zooms in.
• TILT BACKWARD (towards user) ► the scene zooms out.
No other puck input results in any scene manipulation.
*Is this a new feature request?*
No.
I have searched the forums and see no repeated reference to the SpaceMouse
not working in version 2.2.0.
I have tried every combination of turning the Space Mouse on and off.
Unplugging and Plugging the USB dongle, plugging the SpaceMouse in directly
with a USB cable, restarting PrusaSlicer, Rebooting Windows. I have
uninstalled and reinstalled PrusaSlicer 2.2.0. To no avail. Behavior is
unchanged.
The Space Mouse works properly in Fusion 360 and in other CAD applications.
Thanks for your help
◄ RB ►
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#3937>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABMPSI6FDDRMXJSWJ3BLS5TRJT5MDANCNFSM4LVHVWCQ>
.
|
You can verify the models that you have tested by looking at the bottom of the SpaceMouse.
The only two part numbers I can find on the web for this version of the SpaceMouse Wireless are: 3DX-600044, and 3DX-700066. Both units look exactly the same. So I believe the one you’ve tested is one of these. Can you verify? (I have attached two photos of mine.)
I have also verified that I am running the current drivers from 3DConnexion: 3DXWare v10.6.5
Thanks,
RB
From: Vojtěch Bubník <[email protected]>
Sent: Friday, March 27, 2020 12:55 PM
To: prusa3d/PrusaSlicer <[email protected]>
Cc: rosscadguy <[email protected]>; Author <[email protected]>
Subject: Re: [prusa3d/PrusaSlicer] 3DConnexion Space Mouse is ignored in 2.2.0 - Windows (#3937)
We are accessing the 3D mouse directly. It may be, that we are not
interpreting the data from this particular model correctly. We tested 3
different types, it may be that yours is 4rth. Hard to know.
pá 27. 3. 2020 v 20:32 odesílatel rosscadguy <[email protected] <mailto:[email protected]> >
napsal:
Version
2.2.0 Win64
Operating system type + version
Windows 10 Home - 64 bit
Version 1903
OS Build 18362.720
3D printer brand / version + firmware version (if known)
Prusa MK3S/MMU2S
Behavior
-
*Describe the problem*
3DConnexion Space Mouse is ignored
SpaceMouse Wireless PN: 3DX-600044
-
*Steps needed to reproduce the problem*
Launch PrusaSlicer / Manipulate the puck
-
*Expected Results*
Scene should rotate/pan/zoom according to puck inputs.
-
*Actual Results*
The only inputs from the puck that are reflected on the PrusaSlicer
scene are:
• TILT FORWARD (away from user) ► the scene zooms in.
• TILT BACKWARD (towards user) ► the scene zooms out.
No other puck input results in any scene manipulation.
*Is this a new feature request?*
No.
I have searched the forums and see no repeated reference to the SpaceMouse
not working in version 2.2.0.
I have tried every combination of turning the Space Mouse on and off.
Unplugging and Plugging the USB dongle, plugging the SpaceMouse in directly
with a USB cable, restarting PrusaSlicer, Rebooting Windows. I have
uninstalled and reinstalled PrusaSlicer 2.2.0. To no avail. Behavior is
unchanged.
The Space Mouse works properly in Fusion 360 and in other CAD applications.
Thanks for your help
◄ RB ►
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#3937>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABMPSI6FDDRMXJSWJ3BLS5TRJT5MDANCNFSM4LVHVWCQ>
.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#3937 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJKSJHUTJTXZZGVQYFPIG4TRJUABTANCNFSM4LVHVWCQ> . <https://github.com/notifications/beacon/AJKSJHQBOHZVDKVAOS637V3RJUABTA5CNFSM4LVHVWC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEQJ7OWI.gif>
|
3DX-600047 does work fine without issues. |
I have two instances of 3DX-600044. One at home and one at the office. (So two different computers, both running Windows 10.) Neither one operates correctly on PrusaSlicer v2.2.0.
I don’t know what the difference is between 0044 and 0047. It’s hard to imagine that anything that would work on one wouldn’t work on the other. Especially just the basic functions of pan, zoom, and rotate. Should be straight-forward?
Thanks for the help.
◄ RB ►
From: MorroWeb <[email protected]>
Sent: Friday, March 27, 2020 5:12 PM
To: prusa3d/PrusaSlicer <[email protected]>
Cc: rosscadguy <[email protected]>; Author <[email protected]>
Subject: Re: [prusa3d/PrusaSlicer] 3DConnexion Space Mouse is ignored in 2.2.0 - Windows (#3937)
3DX-600047 does work fine without issues.
What models were tested?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#3937 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJKSJHTPSIA7RUNGWYTJ2EDRJU6DVANCNFSM4LVHVWCQ> . <https://github.com/notifications/beacon/AJKSJHSIIKDD4X5QQNIJD4LRJU6DVA5CNFSM4LVHVWC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEQKR63I.gif>
|
I don't know what is going on. PrusaSlicer connects to the hardware
directly, so your version of the driver is only relevant if it interferes
with PrusaSlicer, while it should not. I wonder what would happen if you
deinstall the driver and test PrusaSlicer?
so 28. 3. 2020 v 4:07 odesílatel rosscadguy <[email protected]>
napsal:
… I have two instances of 3DX-600044. One at home and one at the office. (So
two different computers, both running Windows 10.) Neither one operates
correctly on PrusaSlicer v2.2.0.
I don’t know what the difference is between 0044 and 0047. It’s hard to
imagine that anything that would work on one wouldn’t work on the other.
Especially just the basic functions of pan, zoom, and rotate. Should be
straight-forward?
Thanks for the help.
◄ RB ►
From: MorroWeb ***@***.***>
Sent: Friday, March 27, 2020 5:12 PM
To: prusa3d/PrusaSlicer ***@***.***>
Cc: rosscadguy ***@***.***>; Author <
***@***.***>
Subject: Re: [prusa3d/PrusaSlicer] 3DConnexion Space Mouse is ignored in
2.2.0 - Windows (#3937)
3DX-600047 does work fine without issues.
What models were tested?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <
#3937 (comment)>
, or unsubscribe <
https://github.com/notifications/unsubscribe-auth/AJKSJHTPSIA7RUNGWYTJ2EDRJU6DVANCNFSM4LVHVWCQ>
. <
https://github.com/notifications/beacon/AJKSJHSIIKDD4X5QQNIJD4LRJU6DVA5CNFSM4LVHVWC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEQKR63I.gif>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3937 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABMPSI5VWCHA4A2DBL3RYELRJVSYDANCNFSM4LVHVWCQ>
.
|
I have just tested on mine, it is 3DX-600044. I have tested with PrusaSlicer 2.2.0 final release. Wired connection works just fine, wireless as well. Now I am totally confused. |
Hello. I have the same problem where the Space Mouse does not function in PrusaSlicer. I have done all updates (Windows 10, PrusaSlicer 2.2 and 3Dconnexion 10.6.5) and rebooted. My Space Mouse version is 3DX-600044. Control-M settings which didn’t work either. Any ideas? |
I had a really interesting discovery and a potential fix. @bubnikv, hopefully this can help you understand what is happening, I don't know enough about device management. Troubleshooting I have a second unused 3Dconnexion universal USB receiver because I have a Space Mouse and CADMouse. I removed the 3Dconnexion receiver from the USB port. Summary of what I'm seeing Fix Cheers! |
@rosscadguy @xxxTark77xxx |
If the wireless Space Mouse is plugged in through USB (like when charging), it always works in PrusaSlicer. To get the wireless Space Mouse to work repeatedly in PrusaSlicer wirelessly, I needed to delete all HID-compliant mice in Device Manager > Other Pointing Devices. Then I needed to pair the Space Mouse to the 3Dconnexion receiver. |
Thanks. I will check Blender implementation. The issue with PrusaSlicer and 3DConnexion driver may be, that PrusaSlicer is open source. I will have to talk to the 3DConnexion company. Without the 3DConnexion driver, we would likely have to open all the USB subports of a dongle, for which some device is paired and expect data to be received from there. |
The driver software for the 3DConnexion Space Mouse Wireless (and probably all their products) is 3DxWare. It is what empowers the functions of all the extra “function buttons” on the devices.
I uninstalled 3DxWare and found that ALL response to the SpaceMouse in PrusaSlicer went away. (It used to at least zoom in and out before – but that’s all.) All the “function buttons” went dead too. I also confirmed that Fusion360 gets no response from the SpaceMouse with 3DxWare uninstalled.
I also have the 3DConnexion CAD Mouse Wireless. The mouse function operates the same even if 3DxWare is uninstalled. Though its “function buttons” are dead in this case.
I reinstalled 3DxWare, and the limited zoom response reappeared in PrusaSlicer, and all normal response returned to Fusion360. The “function buttons” on both devices returned to normal.
I also discovered that in the START menu, there is of course a 3DConnexion list item. In its submenu there are two options (which I never noticed before) that offer “Stop 3DxWare”, and “Start 3DxWare”. I invoked those and they cause the same behavior as if the “3DxWare” driver had been completely uninstalled and reinstalled. If I picked, “Stop 3DxWare”, then all responsiveness in all apps, and all “function buttons” would go away. (But again the mouse worked normally.) If I picked, “Start 3DxWare”, then all previous behaviors would return.
So it does not appear that uninstalling or disabling 3DxWare opens up any gateways that allow the SpaceMouse Wireless to operate properly in PrusaSlicer. I’m glad for any further ideas you may have.
Thanks for the ongoing interaction and help.
Cheers,
◄ RB ►
From: Vojtěch Bubník <[email protected]>
Sent: Saturday, March 28, 2020 2:09 AM
To: prusa3d/PrusaSlicer <[email protected]>
Cc: rosscadguy <[email protected]>; Author <[email protected]>
Subject: Re: [prusa3d/PrusaSlicer] 3DConnexion Space Mouse is ignored in 2.2.0 - Windows (#3937)
I don't know what is going on. PrusaSlicer connects to the hardware
directly, so your version of the driver is only relevant if it interferes
with PrusaSlicer, while it should not. I wonder what would happen if you
deinstall the driver and test PrusaSlicer?
so 28. 3. 2020 v 4:07 odesílatel rosscadguy <[email protected]>
napsal:
I have two instances of 3DX-600044. One at home and one at the office. (So
two different computers, both running Windows 10.) Neither one operates
correctly on PrusaSlicer v2.2.0.
I don’t know what the difference is between 0044 and 0047. It’s hard to
imagine that anything that would work on one wouldn’t work on the other.
Especially just the basic functions of pan, zoom, and rotate. Should be
straight-forward?
Thanks for the help.
◄ RB ►
From: MorroWeb ***@***.***>
Sent: Friday, March 27, 2020 5:12 PM
To: prusa3d/PrusaSlicer ***@***.***>
Cc: rosscadguy ***@***.***>; Author <
***@***.***>
Subject: Re: [prusa3d/PrusaSlicer] 3DConnexion Space Mouse is ignored in
2.2.0 - Windows (#3937)
3DX-600047 does work fine without issues.
What models were tested?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <
#3937 (comment)>
, or unsubscribe <
https://github.com/notifications/unsubscribe-auth/AJKSJHTPSIA7RUNGWYTJ2EDRJU6DVANCNFSM4LVHVWCQ>
. <
https://github.com/notifications/beacon/AJKSJHSIIKDD4X5QQNIJD4LRJU6DVA5CNFSM4LVHVWC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEQKR63I.gif>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3937 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABMPSI5VWCHA4A2DBL3RYELRJVSYDANCNFSM4LVHVWCQ>
.
—
You are receiving this because you authored the thread.
Reply to this email directly, <#3937 (comment)> view it on GitHub, or <https://github.com/notifications/unsubscribe-auth/AJKSJHS6XNXCF4DUBUEH3DLRJW5BPANCNFSM4LVHVWCQ> unsubscribe.
|
Using the ideas from Tark77, I simply tried changing the port of the wireless receiver. Up to now, I’ve been plugged into one of the ports of a USB_3.0 hub.
For the test, I moved the wireless receiver to one of the ports directly on my laptop (of which there are only two – hence the hub). PrusaSlicer now reacts to the SpaceMouse Wireless correctly.
I moved the wireless receiver back to the hub, and the proper functionality went away.
I moved the wireless receiver back to the on-board USB hub and the puck works correctly again.
I could never get any “direct connect” situation to work. I plugged a USB cable into the puck, and then tried both the hub location and the on-board location and neither case would work.
So as long as my wireless receiver Is connected to a USB port directly on the laptop, I’m golden.
Cheers,
◄ RB ►
From: Vojtěch Bubník <[email protected]>
Sent: Monday, March 30, 2020 5:22 AM
To: prusa3d/PrusaSlicer <[email protected]>
Cc: rosscadguy <[email protected]>; Mention <[email protected]>
Subject: Re: [prusa3d/PrusaSlicer] 3DConnexion Space Mouse is ignored in 2.2.0 - Windows (#3937)
@xxxTark77xxx <https://github.com/xxxTark77xxx>
Thanks. I will check Blender implementation. The issue with PrusaSlicer and 3DConnexion driver may be, that PrusaSlicer is open source. I will have to talk to the 3DConnexion company.
Without the 3DConnexion driver, we would likely have to open all the USB subports of a dongle, for which some device is paired and expect data to be received from there.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#3937 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJKSJHQWO3V5DVRIAXV4NMTRKCFEZANCNFSM4LVHVWCQ> .
|
As commented here https://forum.prusaprinters.org/forum/prusaslicer/spacemouse-on-prusaslicer-2-2-0/paged/2/#post-203555 The good news is that we have a Windows specific prototype of 3DConnexion support in PrusaSlicer inspired by Blender, which seems to work with the driver (you can swap axes as you wish), if a configuration file is dropped to c:\Program Files\3Dconnexion\3DxWare\3DxWinCore64\Cfg\ We are negotiating with a 3DConnexion representative, hopefully a config for PrusaSlicer will be added into the next 3DConnexion driver package. That should conclude the 3DConnexion integration. |
Thanks for the further info.
As I mentioned in a previous post, I have two computers. A Laptop at work, and a desktop at home.
I got the laptop working yesterday by making sure the wireless receiver is plugged into an on-board USB slot, not into a USB hub. 3DxWare remained installed.
At home on my desktop (a Dell Optiplex 7070) I do not have a hub since there are 5 USB ports on-board. So the wireless receiver is plugged into the motherboard, and yet, the SpaceMouse Wireless does not work correctly with PrusaSlicer.
Using one of your suggestions, I uninstalled the 3DConnexion driver (3DxWare) and discovered that this was enough to get the puck working correctly with PrusaSlicer. (This did not work on my laptop.)
So it seems that there are varying conditions that allow the puck to work correctly on different machines, and the right combination of elements has to be discovered in each case.
We wish you luck and thank you for your efforts in untangling all this.
Cheers,
RB
From: Vojtěch Bubník <[email protected]>
Sent: Monday, March 30, 2020 11:09 PM
To: prusa3d/PrusaSlicer <[email protected]>
Cc: rosscadguy <[email protected]>; Mention <[email protected]>
Subject: Re: [prusa3d/PrusaSlicer] 3DConnexion Space Mouse is ignored in 2.2.0 - Windows (#3937)
As commented here https://forum.prusaprinters.org/forum/prusaslicer/spacemouse-on-prusaslicer-2-2-0/paged/2/#post-203555
The good news is that we have a Windows specific prototype of 3DConnexion support in PrusaSlicer inspired by Blender, which seems to work with the driver (you can swap axes as you wish), if a configuration file is dropped to
c:\Program Files\3Dconnexion\3DxWare\3DxWinCore64\Cfg\
We are negotiating with a 3DConnexion representative, hopefully a config for PrusaSlicer will be added into the next 3DConnexion driver package. That should conclude the 3DConnexion integration.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#3937 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJKSJHVUIWALWL32QZF2U53RKGCI3ANCNFSM4LVHVWCQ> . <https://github.com/notifications/beacon/AJKSJHXBZI7CLCB42D2UV4TRKGCI3A5CNFSM4LVHVWC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEQST6SY.gif>
|
I have just tried switching the USB port and got the mouse to work in PS; but it's slow and nothing I do will increase the speed, so it's still not really usable for me in PS as there is nothing more frustrating than waiting for an expected response from an input. |
PrusaSlicer newly communicates with the 3DConnexion devices using the 3DConnexion driver, thus it is possible to configure 3DConnexion for PrusaSlicer in the driver. For the 3DConnexion driver to recognize PrusaSlicer, the user has to copy PrusaSlicer.xml into c:\Program Files\3Dconnexion\3DxWare\3DxWinCore64\Cfg\ . We are actively communicating with 3DConnexion to add our configuration file into their installer It will be part of the upcoming PrusaSlicer 2.3.0-alpha1. Closing. |
Thanks for your continued work on this @bubnikv, it's appreciated. Where can I find the file PrusaSlicer.xml? |
Version
2.2.0 Win64
Operating system type + version
Windows 10 Home - 64 bit
Version 1903
OS Build 18362.720
3D printer brand / version + firmware version (if known)
Prusa MK3S/MMU2S
Behavior
Describe the problem
3DConnexion Space Mouse is ignored
SpaceMouse Wireless PN: 3DX-600044
Steps needed to reproduce the problem
Launch PrusaSlicer / Manipulate the puck
Expected Results
Scene should rotate/pan/zoom according to puck inputs.
Actual Results
The only inputs from the puck that are reflected on the PrusaSlicer scene are:
• TILT FORWARD (away from user) ► the scene zooms in.
• TILT BACKWARD (towards user) ► the scene zooms out.
No other puck input results in any scene manipulation.
Is this a new feature request?
No.
I have searched the forums and see no repeated reference to the SpaceMouse not working in version 2.2.0.
I have tried every combination of turning the Space Mouse on and off. Unplugging and Plugging the USB dongle, plugging the SpaceMouse in directly with a USB cable, restarting PrusaSlicer, Rebooting Windows. I have uninstalled and reinstalled PrusaSlicer 2.2.0. To no avail. Behavior is unchanged.
The Space Mouse works properly in Fusion 360 and in other CAD applications.
Thanks for your help
◄ RB ►
The text was updated successfully, but these errors were encountered: