slic3r / Slic3r

Open Source toolpath generator for 3D printers
https://slic3r.org/
GNU Affero General Public License v3.0
3.34k stars 1.29k forks source link

Part offset in z axis doesn't work. #4895

Open DocTrucker opened 4 years ago

DocTrucker commented 4 years ago

Describe the bug Part offset in z axis doesn't work.

To Reproduce "File" menu > "Preferences" > Deselect "Auto-centre parts (x,y):" & "Auto-align parts (z=0):"

191125_Preferences

Click ok to clear popup. Load benchy Left click to select, right click to raise menu. > "Cut" Keep upper and lower part.

191125_CutWindow

Click perform cut

191125_CutResult

Parts have been moved unexpectedly. (see other bug) Left click select top part of model. Right click to raise menu. > "Settings" Click "#3DBency.stl" in tree window. Type "24" into "Z:" text entry box in the "Move" section of the popup window.

191125_SettingsPopup

Press ok. Popup window goes, part hasn't moved as expected. Ctrl + 8 for front view.

191125_Result2_Ctrl8

Top section still on z=0 plane. Ctrl + 0 for diagonal view. Left click select top part of model. Right click to raise menu. > "Settings" Click "#3DBency.stl" in tree window. Type "24" into "Z:" text entry box in the "Move" section of the popup window. Press enter key. Top section still on z=0 plane.

Expected behavior Top part should have been offset to z=24 level.

Screenshots See screenshots.

Desktop (please complete the following information): Slic3r Version: 1.3.1-dev Slic3r Build Commit: 4f5b935 Ubuntu 18.04.

Additional context N/A

191125_Slic3r_Bug4.zip

supermerill commented 4 years ago

warning: i can't see the screenshot so maybe i'm wrong.

I think that cut create 2 pieces not 1 piece with 2 parts. If you save the top part as stl, remove it from slic3r, then go to settings of the bottom part, then add part and select the saved stl, then you should be able to move it.

DocTrucker commented 4 years ago

Screenshot should be in the zip file, let me check.

supermerill commented 4 years ago

you can drag-drop them

DocTrucker commented 4 years ago

I'll bear that in mind for future bug reports/feature requests. Just running through your suggestions.

Edit: Have now added screenshots

DocTrucker commented 4 years ago

Ok i have removed the previous work flow from cutting. try the following.

Describe the bug Part offset in z axis doesn't work.

To Reproduce "File" menu > "Preferences" > Deselect "Auto-centre parts (x,y):" & "Auto-align parts (z=0):"

191125_d2_00_Settings

Click ok to clear popup. Press "Add" toolbar button, select box, press open. Press "Add" toolbar button, select box, press open. Left click to select a box. Right click for pop-up menu and select settings. Type "10" into "Z:" text entry box in the "Move" section of the popup window.

191125_d2_01_OffsetToZ10

Press ok. Ctrl + 8 for front view.

191125_d2_02_FrontView

Both boxes still on z=0 plane.

Expected behaviour Top part should have been offset to z=10 level. Front view should show rectangular object.

Screenshots Screenshots also in zip file.

Desktop (please complete the following information): Slic3r Version: 1.3.1-dev Slic3r Build Commit: 4f5b935 Ubuntu 18.04.

Additional context N/A

191125_Slic3r_bug4b.zip

lordofhyphens commented 4 years ago

Gotta offset relative to something else

On Mon, Nov 25, 2019, 8:51 AM DocTrucker notifications@github.com wrote:

Ok i have removed the previous work flow from cutting. try the following.

Describe the bug Part offset in z axis doesn't work.

To Reproduce "File" menu > "Preferences" > Deselect "Auto-centre parts (x,y):" & "Auto-align parts (z=0):"

[image: 191125_d2_00_Settings] https://user-images.githubusercontent.com/30924036/69550408-dddb4c80-0f92-11ea-94cb-79404e43656f.png

Click ok to clear popup. Press "Add" toolbar button, select box, press open. Press "Add" toolbar button, select box, press open. Left click to select a box. Right click for pop-up menu and select settings. Type "10" into "Z:" text entry box in the "Move" section of the popup window.

[image: 191125_d2_01_OffsetToZ10] https://user-images.githubusercontent.com/30924036/69550443-ed5a9580-0f92-11ea-9d3f-557d73b6fb8a.png

Press ok. Ctrl + 8 for front view.

[image: 191125_d2_02_FrontView] https://user-images.githubusercontent.com/30924036/69550478-f8adc100-0f92-11ea-8df1-3a8cd294cf7f.png

Both boxes still on z=0 plane.

Expected behaviour Top part should have been offset to z=10 level. Front view should show rectangular object.

Screenshots Screenshots also in zip file.

Desktop (please complete the following information): Slic3r Version: 1.3.1-dev Slic3r Build Commit: 4f5b935 https://github.com/slic3r/Slic3r/commit/4f5b935ecf1335755d607ec38395bd94106daa7f Ubuntu 18.04.

Additional context N/A

191125_Slic3r_bug4b.zip https://github.com/slic3r/Slic3r/files/3887159/191125_Slic3r_bug4b.zip

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/slic3r/Slic3r/issues/4895?email_source=notifications&email_token=AAAHYCRNKCMJT7X77ZVRDJDQVPRARA5CNFSM4JRJUDUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFCU2BY#issuecomment-558189831, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAHYCRKXL6E4H6IMXYHSCLQVPRARANCNFSM4JRJUDUA .

DocTrucker commented 4 years ago

That doesn't make sense to me. I want to offset relative to world/machine co-ordinates, can you explain or point to how to move a part to z=[a specific value] in the manual?

Why does the preview show it working ok, but then the result fail? What am I doing wrong?

DocTrucker commented 4 years ago

Here's more context. I found this bug when trying to resolve the other bug about cutting shifting parts back down to z=0 despite all auto align features being disabled.

Thingiverse file: https://www.thingiverse.com/thing:3029305

Model: 191125_d3_00_Model

Cut window: 191125_d3_00_Cut

Cur result: 191125_d3_01_CutResult

Manual xy alignment (bad, but alignement data has been lost): 191125_d3_01_PartsAlignedIsh

Attempt to move upper part back up by 2.2 (not as bad as the 2.2 was explicitly specified before, but still extra unneeded workflow): 191125_d3_03_MoveSpecified

Result of no move, feet still below base level: 191125_d3_04_NotMoved

Please be aware this bug report is only relating to the failure of the move part to z=2.2 rather than the auto align of the cut parts.

foreachthing commented 4 years ago

If you want to split parts (i.e. for multi-color printing) you'll need to "add" to an existing part!

  1. Perform cut
  2. EXPORT model (i.e. TOP cut) as stl (or something else)
  3. Double-click the BASE and Load Part...
  4. Select and ok TOP part
  5. Position TOP part in xyz (and maybe the BASE as well.
  6. And then it should look like this: image

Sliced: image

DocTrucker commented 4 years ago

Not multicoloured (or multi material) printing, but may as well be. Makes little odds.

Odd workflow. In that case shouldn't the controls to offset the part be hidden when it clearly can't be achieved with a single part in an object? And final question why can't it work? I have clearly set the preferences to not align to z=0 so forcing it here seems odd and counter intuitive. It doesn't appear to align relative to another part in the object, merely the parts are aligned relative to the objects co-ordinate system rather than the world/machine's co-ordinate system.

I'll discuss the issues relating to the auto align applied after the cut operation on that bug report ( https://github.com/slic3r/Slic3r/issues/4894 ) rather than here.

foreachthing commented 4 years ago

@DocTrucker, yes! I, too, find it odd but got used to it. I think it's a good thing, objects drop to the plate. If you miss something and your print starts 0.5 mm in the air .... You could add a cube (make it really tiny) and add your object to the cube. Then z-offset it as desired.

DocTrucker commented 4 years ago

Yeah the work around for offsetting is possible just more work than it needs to be for the users.

It's also not consistant. Load an STL that is floating (my two half box example) and it respects the don't align to z=0 option.

I would hope that I have demonstrated that it would make sense for all opperations to respect the prefference settings and if people are still concerned that the end user doesn't know what they are doing they can add a warning on gcode export if an object was floating above z=0.