-
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
"Arrange" does not arrange model that appears to fit platform #285
Comments
I confirm your findings. It seems to be a problem of the way Slic3r handles the rotation / scaling internally. If you you export the rotated and scaled STL, then import and click arrange, it will work as expected. |
I having the same issue with the spit turn table parts 2 and 3 from the $30 3D Scanner (https://www.thingiverse.com/thing:1762299) after laying it flat (90° X) and rotating it 45°. |
I'm also seeing this issue, in 1.34.1.24-prusa3d. This is a regression, since it mostly works in 1.33.8-prusa3d, but seems to do literally nothing in the new version. |
I'd propose a different (additional) fix for this - make arrange non-mandatory for single parts. Sometimes you want to print something not exactly in the center of the printbed, for example when I test new filaments I'm printing to the side of the printbed as i can more easily get it off at the edge, but Slic3r wont let me put an object at the edge, only the center. Manually rearranging an object would help to work around this issue too as you could manually fix the misalignment. |
I checked 1.33.8-prusa3d and 1.35.2.4-prusa3d, and I don't have any problem moving single parts around arbitrarily on the print bed. |
You have to disable "Auto-center parts" in "File" -> "Preferences". |
Oh... never noticed that, thanks 🤣 |
Fixed with 5cae4cc |
Version
1.34.1 2017apr06-0802
Operating system type + version
Mac OS 10.12.4
Behavior
"Arrange" does not arrange model that appears to fit platform
Model centered on build platform
Model not completely on build platform
Is this a new feature request?
No
config.ini.zip
The text was updated successfully, but these errors were encountered: