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

Defect: Slicing does not seem to work with MMU, stuck in negative flow message. #639

Closed
kursatu opened this issue Nov 6, 2020 · 2 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

@kursatu
Copy link

kursatu commented Nov 6, 2020

Version

Version of SupserSlicer used goes here, Use About->About SuperSlicer
Latest release

Operating system type + version

What OS are you using (and version)
Windows

3D printer brand / version + firmware version (if known)

What 3D printer brand / version are you printing on, is it a stock model or did you modify the printer, what firmware is running on your printer, version of the firmware #s

Behavior

  • Describe the problem
    Slice the attached project file
    Observe the error
    Change one model to use the same extruder.
    The problem goes away
    All width settings are set to 0, changing them does not help to avoid the defect.
    Defect13_1

  • Steps needed to reproduce the problem

    • If this is a command-line slicing issue, include the options used
  • Expected Results

  • Actual Results

    • Screenshots from SuperSlicer preview are preferred

Project File (.3MF) where problem occurs

Upload a SuperSlicer Project File (.3MF) (File -> Save / Save Project)
Defect13.zip

@kursatu kursatu changed the title Defect: Slicing does not work, stuck in negative flow message. Defect: Slicing does not seem to work with MMU, stuck in negative flow message. Nov 6, 2020
@supermerill
Copy link
Owner

I computed the wipe tower brim in an unsafe way.
I'll fix that.
in the meantime, you can set a width for the the first layer instead of 0.

@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 Nov 6, 2020
supermerill added a commit that referenced this issue Nov 8, 2020
@kursatu
Copy link
Author

kursatu commented Nov 15, 2020

The attached .3mf file did not show the reported problem, pulled and built with the latest sources on github.

@kursatu kursatu closed this as completed Nov 15, 2020
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

2 participants