Axes Not Tied to Correct Motion

[rachael7]

I can't quite seem to make this work. No matter what settings I choose in the 3DConexxion software and whichever way I toggle the extension option, the motions on the Spacemouse just don't seem to match up to the motions on screen. I use my Spacemouse in Solidworks and several other pieces of software, so I'm not a noob with it or anything; I just cant' seem to find a setup that makes it mimic the behavior it has in other applications. Any thoughts? What is your setup in the Spacemouse setup software? Thanks!

[FlyingSamson]

Could you be more specific on your setup: Which OS are you on, using which version of Cura? And what do you expect and observe?

On OSX (just tested with Cura 4.7.1 and Cura 4.8) my configuration is as straight forward as it gets: All axes are mapped to the respective movement (e.g. 3D Mouse Right to 3D Mouse Right and so forth). This then works the exact same way (i.e., object transformation rather than camera transformation) for me as in, e.g., Fusion360.

[rachael7]

Sure, I'll give you what I can. I'm running Windows 10 Pro, Cura 4.8, 3DXWare 10.7.1.3280 (latest). I expected what you describe, the same motions I would see in Fusion or Solidworks, which is what I design in. What I got, I can only describe generally, as I already uninstalled the plugin, but here is some of what I recall. Zoom was up/down, when 3DConnexion was set to forward/back. Pitch, roll, and yaw were not working correctly either, but the only one I remember for sure is that what should have produced roll (rotation about the axis perpendicular to the screen) was producing yaw (rotation about the axis perpendicular to the desk) and I couldn't seem to get roll at all. Are other people using it successfully on Windows? I could try reinstalling it to get more detailed feedback if you want - I like that your solution uses the actual drivers, rather than the other solution out there (RawMouse) which bypasses the drivers and does it's own thing - I just uninstalled it and reverted to the other, since I couldn't get this one to move the way I expected.

[FlyingSamson]

Ok, so I just tried it on Windows again. Setup is Windows 10 Pro, 3DXWare 10.6.7.3198, and Cura 4.6.1 (both a little outdated I know, since I never use the Windows machine). My configuration in 3DXWare is as follows (mine is German so pardon me if the translation don't fit 100%): Navigation on the left: Move/Zoom: check, Rotation: check, Dominant: unchecked. Zoom-direction below: Both forward/backward and up/down unchecked. Speed on the right: All active and Front/Back (2nd from top), Up/Down (3rd from top), Role (5th from top) and Pan (6th from top) are reversed the other two are not.

Maybe you could try this configuration on your system. In the meantime I will see if updating the driver and Cura makes any difference.

[rachael7]

Thanks. So here's what I got when I tried those settings. First, I had to "restore defaults" to get both forward/back and up/down both unchecked. Then I also had to reverse the up/down from what you said to get what I expected. After that, I found that no panning functions work at all and moving the cap to produce rotation around the Y axis (perpendicular to the screen) instead produces motion around the Z axis. No motion of the cap would produce rotation around the Y axis. Rotation of the cap on the spacemouse about it's vertical axis produces no change onscreen, nor do sliding the cap left/right or forward/back. The only two functions that seemed to work were rotation around the X axis and zooming.

If I set 3DConnexion to zoom on up/down, I get correct rotation around the Z axis and the X axis, and zooming on the forward/backward cap motion, but no other working functions.

If I set 3DConnexion to zoom on forward/back, I get zoom on up/down motion of the cap, correct rotation about X axis, and controller rotation about the Y axis producing screen rotation about the Z axis, with no other functions. Hope this helps!

[FlyingSamson]

I just updated both the driver to 10.7.1.3280 and Cura to 4.8 and it is still working as expected.

[rachael7]

Strange. Just not working for me at all. Oh well, I'll just stay with the other solution. Thanks for trying!

[rachael7]

So another data point. I was trying to help my dad set this up (by phone) because he's a real serious noob. It sounded like he got the whole range of motions, as best I can tell. So it might be something unique to my machine. I just don't have the faintest idea what it might be. Would the graphics card affect this? Some other driver besides the one 3DXWare installs? Any ideas for things to check?

[FlyingSamson]

This seems really odd...

Some ideas:

• Maybe there is some other Cura extension installed, which is conflicting with this one? Maybe for testing purposes it makes sense to deactivate all other extensions/plugins and try again.
• The Space Mouse Modell was the same for you and your dad?
• Are there any "unordinary" messages in the Cura log (somewhere in the AppData folder or so if I remember correctly)?
• Maybe reinstalling Cura (preferably while keeping the configurations) and/or the SpaceMouse driver might also help.
• Maybe there are traces left of the other SpaceMouse Plugin which interferes with this one?

Other then that I fear that I'm of no big help, as I am a real noob when it comes to Windows systems.

[rachael7]

It certainly struck me as odd, lol. I'll try some of your other suggestions, but in case it makes any sense to you, here is what the error log had related to the Spacemouse plugin:

2021-02-09 13:09:04,591 - DEBUG - [MainThread] SpaceMouseTool.SpaceMouseTool.debugLog [42]: Init 3DX
2021-02-09 13:09:04,627 - DEBUG - [MainThread] SpaceMouseTool.SpaceMouseTool.debugLog [42]: SiOpenWinInit: Window handle: 0000000000000000
2021-02-09 13:09:04,631 - DEBUG - [MainThread] SpaceMouseTool.SpaceMouseTool.debugLog [42]: SiOpen failed
2021-02-09 13:09:04,634 - DEBUG - [MainThread] SpaceMouseTool.SpaceMouseTool.debugLog [42]: Window handle: 000000000013102C
2021-02-09 13:09:04,635 - DEBUG - [MainThread] SpaceMouseTool.SpaceMouseTool.debugLog [42]: Init 3DX
2021-02-09 13:09:04,638 - DEBUG - [MainThread] SpaceMouseTool.SpaceMouseTool.debugLog [42]: SiOpenWinInit: Window handle: 000000000013102C
2021-02-09 13:09:04,652 - DEBUG - [MainThread] SpaceMouseTool.SpaceMouseTool.debugLog [42]: SiOpen succeeded: Device: SpaceNavigator
2021-02-09 13:09:04,653 - DEBUG - [MainThread] SpaceMouseTool.SpaceMouseTool._onEngineCreated [413]: Initialized SpaceMouseTool

Thanks for your efforts and no worries about Windows - I don't think anyone really understands this sorry excuse for an operating system!

[uChip]

Seems like what I experienced was similar to this thread so rather than filing a new issue, I will add here.
Windows 10, Cura 5.1.0, 3DWare 10.6.5

When I first used the 3D mouse in Cura some axes were swapped with others and some were reversed. Opening the 3DWare control panel showed the left side (Nav & Zoom Dir) as FlyingSamson describes above. The right side had only a couple of directions with reverse box checked. Fiddling around I tried different settings. Note that on the left the controls under Zoom Direction are radio button so really one of them should always be selected, but neither were marked. When I clicked the Up / Down radio button, the mouse connection to axes changed. They were no longer swapped. Some were still backwards, but that's correctable with the check boxes on the right. When I set the reverse checks to what FlyingSamson describes above, all axes behave as desired. But checking the reverse boxes caused the radio buttons on the left to lose their indications again (both blank).

So click the Up / Down radio button on the left first. Then click the reverse checks on the right to get the motion you want.

Also, note that the control panel reflects the settings for the app that was in front before the control panel was activated so make sure that you select Cura just before the 3DWare control panel.

[uChip]

I just updated to 3DWare 10.8.8. Everything appears to still be working correctly.