Prusa Slicer 2.5.2 and SpaceMouse  

RE: Prusa Slicer 2.5.2 and SpaceMouse

In Linux, there are *ini files.  On my machine, they are in ~/.config/apps/PrusaSlicer but I don't see anything similar to the Windows thing.  Since the post you linked states that it is an issue with the mouse driver, I would check the configuration files for the mouse to see if you can tell it to look at the Prusa software.

Looks like the configuration files for the Spacemouse are in /etc/3DWare directory.  You may have to copy a config file and modify it there.  I don't have the Spacemouse to check.

I found information on this for Ubuntu from 2020 and how to get it to work with 360 Fusion under Wine.  I also found that there is a configuration program spnavcfg that you may have used.  This link is for the Linux tools and may be available in your distributions programs.

Spacenav on Linux

RE:

Hey, thank you for this tip! 🙂 Until now I have always booted my laptop with Win10 for this. Would be great to get Fusion 360 and the SpaceMouse working on Linux. I will certainly try this!

RE:

Posted by: @robin_13

In Linux, there are *ini files.  On my machine, they are in ~/.config/apps/PrusaSlicer but I don't see anything similar to the Windows thing.  Since the post you linked states that it is an issue with the mouse driver, I would check the configuration files for the mouse to see if you can tell it to look at the Prusa software.

Looks like the configuration files for the Spacemouse are in /etc/3DWare directory.  You may have to copy a config file and modify it there.  I don't have the Spacemouse to check.

I found information on this for Ubuntu from 2020 and how to get it to work with 360 Fusion under Wine.  I also found that there is a configuration program spnavcfg that you may have used.  This link is for the Linux tools and may be available in your distributions programs.

Spacenav on Linux

 

 

Unfortunately, none of that is applicable.  You are talking about two different offerings there... There is no /etc/3Dware directory on my system... in fact, there is no "3Dware" anywhere on my system.  The drivers come from Spacenavd, not from proprietary sources.  Spacenavd is an opensource project.  I know it works, because as I stated, they work in FreeCAD, and I've been using it for years.  In my experience, 3Dconnexion could not be counted on to keep their linux ports up to date and functional.  Spacenavd has been much more reliable.

The location for prusaslicer settings is in ~/.config/PrusaSlicer (there is no "apps" directory in .config).  The only ini file I find in ~/.config/PrusaSlicer is the PrusaSlicer.ini file.  I find no mention of the spacemouse, 3dconnexion or spacenavd anywhere under ~/.config/PrusaSlicer.

While it is possible that PrusaSlicer relies upon the proprietary drivers, I'd like to think it does not, as they are always a pain in the rear to maintain... they get bugs, they fall out of sync with the rest of the system... and then it becomes a federal production to get things working again.  Proprietary software developers rarely prioritize issues/bugs on the Linux platform. Spacenavd updates with the system, and is always consistent, and in several years of usage, has never once done me wrong.

Again. My spacemouse works -- I use it in FreeCAD all the time.  I don't need help with drivers, I need help getting it running in PrusaSlicer.

So, does anyone know if the spacemouse can be brought to work on PrusaSlicer, in Linux, using spacenavd?  And if so, can you share how this is done?

Thanks.

RE: Prusa Slicer 2.5.2 and SpaceMouse

From what I remember from the various posts on github regarding the spacemouse PS uses the official drivers.  As such I suspect you are stuck with the how did you put it, 'proprietary drivers'.

RE: Prusa Slicer 2.5.2 and SpaceMouse

As I said, I don't have the mouse and don't use spacenvd and I was reading what I found on the net as a pointer.  The Ubuntu page on the mouse pointed to the /etc directory.  It may have been related to the original drivers then.

My system has ~/.config/apps directory which is what I referred to.  At least the system I was using at the time.   Maybe there is something in the log files that point to the issue or this thread may help you.

https://forum.prusa3d.com/forum/prusaslicer/need-help-enabling-a-3dconnexion-device-in-prusa-slicer-2-2/

RE:

Posted by: @neophyl

From what I remember from the various posts on github regarding the spacemouse PS uses the official drivers.  As such I suspect you are stuck with the how did you put it, 'proprietary drivers'.

If that is true, it is unfortunate.  I'm not going back down that road... not even for prusa slicer... it would nice to have this functionality, but I want to spend my time designing and printing... not fussing with proprietary drivers, biting my  nails every time there is a system update.

Posted by: @robin_13

As I said, I don't have the mouse and don't use spacenvd and I was reading what I found on the net as a pointer.  The Ubuntu page on the mouse pointed to the /etc directory.  It may have been related to the original drivers then.

My system has ~/.config/apps directory which is what I referred to.  At least the system I was using at the time.   Maybe there is something in the log files that point to the issue or this thread may help you.

https://forum.prusa3d.com/forum/prusaslicer/need-help-enabling-a-3dconnexion-device-in-prusa-slicer-2-2/

Yes, I've seen this stuff.  It is all so very old, and seems to point to using the proprietary driver... which doesn't make much sense to me.  I don't know of any distros that have the 3dconnexion drivers in their repos... the EULA of 3Dconnexion probably does not allow for that.... so every update you do risks breaking things when you use things like that out of  the repo, and maybe 3Dconnexion might get to a fix before hell freezes over... maybe not... int he meant time you are stuck, and NONE of your applications will work with the spacemouse.  I know that FreeCAD works great with it Spacenav, so I don't see why I would give up something I know works, for something I know has a history of not working well...  I had hoped that this aspect of PrusaSlicer  received further development since PS 2.2.0, and they embraced spacenavd, but it doesn't sound like it. 

Just out of curiosity... what distro do you use?

RE: Prusa Slicer 2.5.2 and SpaceMouse

Okay, it is an issue with prusa-slicer.  Took me some time to find the location for the configuration files for your device.  Or at least where they should be. 

I have been busy but an issue with configuration files and another appimage pointed me to the location to look.  As the slicer is an appimage, the configuration files may be stored in a tmp directory and only there when you run the file.  It may change every time you run it.

On my linux box, this time while running the Prusa slicer, I have a directory created with /tmp/.mount_Prusa_3RRs84.  In this directory there are sub directories for the appimage.  I think what you are looking for is usr/bin/resources/udev/ and there is a 90-3dconnexion.rules file in it.   If the mouse worked in a previous version, try to run that and see what the file is and if it is different.  I don't know how udev devices work across appimages.     There doesn't look to be a change in the udev rule for 2.5.1 and 2.5.2  I don't know how spacenav handles udev rules from appimages.

This is what is in the 90-3dconnexion.rules file on my machine.

# See src/slic3r/GUI/Mouse3DController.cpp for the list of devices

# Logitech vendor devices
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c603", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c605", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c606", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c621", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c623", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c625", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c626", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c627", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c628", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c629", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c62b", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c62e", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c62f", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c631", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c632", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c633", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c635", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c636", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c640", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c652", MODE="0666"

# 3D Connexion vendor devices
KERNEL=="hidraw*", ATTRS{idVendor}=="256f", ATTRS{idProduct}=="c603", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="256f", ATTRS{idProduct}=="c605", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="256f", ATTRS{idProduct}=="c606", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="256f", ATTRS{idProduct}=="c621", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="256f", ATTRS{idProduct}=="c623", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="256f", ATTRS{idProduct}=="c625", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="256f", ATTRS{idProduct}=="c626", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="256f", ATTRS{idProduct}=="c627", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="256f", ATTRS{idProduct}=="c628", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="256f", ATTRS{idProduct}=="c629", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="256f", ATTRS{idProduct}=="c62b", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="256f", ATTRS{idProduct}=="c62e", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="256f", ATTRS{idProduct}=="c62f", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="256f", ATTRS{idProduct}=="c631", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="256f", ATTRS{idProduct}=="c632", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="256f", ATTRS{idProduct}=="c633", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="256f", ATTRS{idProduct}=="c635", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="256f", ATTRS{idProduct}=="c636", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="256f", ATTRS{idProduct}=="c640", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="256f", ATTRS{idProduct}=="c652", MODE="0666"

RE: Prusa Slicer 2.5.2 and SpaceMouse

Just thought of it.  For FreeCAD, do you use a native app or the appimage?  If you use a native app, you may want to test with an appimage and see if your mouse still works there.

RE: Prusa Slicer 2.5.2 and SpaceMouse

Hi Robin.

Thanks for that.  I'll take a look when I get a moment.

Yes -- I do use the appimage for FreeCAD.  That seems the best way to go with it, honestly.  It seems like everything else (the .deb, the snap, the flatpak -- they are all either missing something crucial, or flat out broken.  The appimage never lets me down 🙂 ).

I probably won't get time to play with this until the weekend.  I'll post what I find.  Thanks again.