Skip to content
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

Toolpath outside print area #3969

Closed
Calcousin55 opened this issue Nov 25, 2023 · 3 comments
Closed

Toolpath outside print area #3969

Calcousin55 opened this issue Nov 25, 2023 · 3 comments
Labels
bug Something isn't working as intended fixed for the next version That means that you should be able to test it in the latest nightly build

Comments

@Calcousin55
Copy link

What happened?

After slicing there can be seen a toolpath outside print area was detected in gcode preview.
image

Project file & How to reproduce

idler_bearing_cover.zip
Using the default Voron V2 300mm3 0.4mm nozzle profile with 0.10mm layer height
Using the following settings causes toolpath error
Skirt & Brim -> Draft shield -> Enable
Infill -> Sparse -> 40% Cubic

Version

2.5.59.3

Operating system

Windows 10

Printer model

Voron V2

@acorreya
Copy link

acorreya commented Dec 18, 2023

UPDATE: I can confirm that this issue happens only when the Sliced Preview tab is opened. If it is not opened, the gcode can be exported / uploaded. If the tab is opened it will create an error.

TLDR: do NOT open the Sliced Preview tab if this error occurs.

This happens for some models and it seems like the brim goes out of the print bed instead of being under the object.

A quick workaround I got is to change a brim setting to trigger slicing and then directly go to the Sliced Preview or Gcode Preview window instead of going directly to 3D View. You can export / upload now.

image

Version

2.5.59.3

Operating system type + version

Win 10

Behavior

Added above

Project File (.3MF) where problem occurs

Tube.3mf.zip

@supermerill supermerill added bug Something isn't working as intended fixed for the next version That means that you should be able to test it in the latest nightly build labels Dec 23, 2023
@supermerill
Copy link
Owner

It's because if you use complete_objects and brim_per_object, the brim needs to be shifted. But it shouldn't if no complete_objects.

@Calcousin55
Copy link
Author

acorreya's issue looks to be fixed in 2.5.59.4 but my issue still persists in 2.5.59.4 but looks like its fixed in 2.5.59.5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working as intended fixed for the next version That means that you should be able to test it in the latest nightly build
Projects
None yet
Development

No branches or pull requests

3 participants