You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ uname -a
Linux debian 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u5 (2017-09-19) x86_64 GNU/Linux
$ cat /etc/debian_version
9.2
Behavior
Slic3r's Controller Window shows multiple entries for the same device. It seems as if the entries were on a per printer basis but one printer shows up twice. On the other hand one printer I have configured does not show up at all in the controller window.
Steps needed to reproduce the problem:
Open slic3r
Load the attached configuration file
Have a look at the controller window.
Expected Results: Since one device can normally only have one printer attached to it, it would make sense to group the entries per device and let the user choose which printer should be related to this device. Also double entries of a printer (and even for one device!?) should not be allowed. Also all configured printers should show up - in my case one was missing.
Actual Results: A device can have multiple printers attached to it and one printer even shows up twice whereas one does not show up at all.
Controller is long gone, we do not currently support printing over serial line / USB in PrusaSlicer.
Closing.
If we ever impelment printing over USB / serial line, we will have a new batch of bugs.
Version
Slic3r-1.37.1-prusa3d-linux64-full-201709141215
Operating system type + version
$ uname -a
Linux debian 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u5 (2017-09-19) x86_64 GNU/Linux
$ cat /etc/debian_version
9.2
Behavior
Slic3r's Controller Window shows multiple entries for the same device. It seems as if the entries were on a per printer basis but one printer shows up twice. On the other hand one printer I have configured does not show up at all in the controller window.
Steps needed to reproduce the problem:
Slic3rControllerWindowError.zip
The text was updated successfully, but these errors were encountered: