search

prusa3d / PrusaSlicer

G-code generator for 3D printers (RepRap, Makerbot, Ultimaker etc.)
https://www.prusa3d.com/prusaslicer/
GNU Affero General Public License v3.0
7.71k stars 1.93k forks source link

2.3.0 Has broken support for my (SpacePilot) 3DMouse #4899

Closed jweaver100 closed 3 years ago

jweaver100 commented 4 years ago

Version

2.3.0-alpha1+win64

Operating system type + version

Windows 10

3D printer brand / version + firmware version (if known)

Prusa Mk3 and Mini

Behavior

I was thrilled with the introduction of 3DMouse support in 2.2.0 and I was one of the people with ZERO issues.

But I know a lot of people didn't like how it was implimented and wanted support usign the 3DConnexion drivers/config and I just had a feeling this would be a problem.

Just got to play with 2.3.0-Alpha1 today and the first thing I noticed was that the 3DMouse movement was unbearably slow.. I hit CTL+M to bring up the config and nothing happened.. Then I remembered that config is now down via the 3DConnexcion config tool.. So I loaded it up and started to tweek but it has NO effect on my mouse...

I suspect the reason is that I am uising 3DxWare which is old.. But thats the last release that supports my "SpacePilot"

So I now can't change the speed of movement and 2.3.0 is now a downgrade to 2.2.0.. I would be more than happy with the old config (CTL+M) back..

Please do something to help people who do not.. not cannot have the lateast 3DxWare drivers.

jweaver100 commented 4 years ago

Just been reading the release log and it talks about 3DConnexion support.. And I am a bit lost..

It says that the XML should be created in "c:\Program Files\3Dconnexion\3DxWare\3DxWinCore64\Cfg\prusa-slicer.xml", but I don't have this XML (the directoy is full of files for other apps, but not Prusa).

It goes on to say that the prusa-slicer.xml and prusa-gcodeviewer.xml can be copied into this directory, but where do I get them as they arnt' there by default?

dahuafschmied commented 4 years ago

Duplicate of #4892

jweaver100 commented 4 years ago

I am still not sure my issue is a duplicate.. The other issue was fixed by editing the PrusaSlicer.ini.. For me, none of those changes worked.

I just fear I am going to miss out on 3DMouse support in 2.3.0 as I have an old mouse with obsolete drivers and where as 2.2.0 worked perfectly for me, 2.3.0 does not allow me to change the config.

bubnikv commented 3 years ago

We have brought the Ctrl-M dialog back in PrusaSlicer 2.3.0-beta1. You have to enable "Legacy 3DConnexion" in the preferences dialog first. Closing.