OrcaSlicer icon indicating copy to clipboard operation
OrcaSlicer copied to clipboard

Max Build Volume Height Not Calculated Correctly After Rotating

Open niveus opened this issue 1 year ago • 1 comments

OrcaSlicer Version

1.8.1

OS version

Mac OS 14.2

Additional system information

N/A

Printer

Creality K1 Max

How to reproduce

The max printable height check doesn't recalculate after rotating an object. I created a test box with a height of 300 mm (for my K1 Max). When the object is exported from Fusion with the flat face down, Orca will allow slicing. If I export the object rotated so that the max height exceeds 300mm, but then rotate in Orca so that the face is down, Orca doesn't recalculate the max volume height and won't allow it to be sliced.

  1. Import box_300 and note that the Slice button is activated
  2. Import box_300_skew, plant the box on a small side so the height is 300mm. Note the error around max volume height
Screenshot 2023-12-13 at 8 19 32 AM

Actual results

Will not allow slicing

Expected results

Should allow slicing

Project file & Debug log uploads

I didn't include the logs since it's so easy to reproduce. LMK if you need the logs.

box_300.zip

Checklist of files to include

  • [ ] Log file
  • [ ] Project file

niveus avatar Dec 13 '23 16:12 niveus

Same problem on newest 1.9 windows 10. I was able to save project and open project in BBLS and slice just fine.

ljohnso16 avatar Jan 05 '24 23:01 ljohnso16

Same problem

lukehags007 avatar Jan 14 '24 22:01 lukehags007

Same problem also on the Windows 1.9 version. Potential fix by manually adjusting slicer max build height for printer but unclear of potential effects that could have printer side.

DrewJensen1 avatar Jan 19 '24 22:01 DrewJensen1

same isse here with BL P1S

  • object height: 245mm
  • same project possible to slice in BL Studio image

Edit 01/24: As workaround I set build volume height from 250 to 275mm and double checked last rows of GCode that Z heigt stays below 250

Hope we get a fix soon!

Aurik23 avatar Jan 22 '24 16:01 Aurik23

Same problem here.

It's noteworthy that the prime tower visualizes the issue pretty good, it seems that my ~200mm height gets calculated to around 350mm: image

Blogshot avatar Feb 01 '24 17:02 Blogshot

Orca bot: this issue is stale because it has been open for 90 days with no activity.

github-actions[bot] avatar May 02 '24 00:05 github-actions[bot]

Orca bot: This issue was closed because it has been inactive for 7 days since being marked as stale.

github-actions[bot] avatar May 09 '24 00:05 github-actions[bot]