I’m trying to print vase mode for the first time and I did get to print the first try, but this is happening on the bottom 4 layers. I have a 0.8 nozzle so the line width is set to 0.6 and the layer hight to 0.4. Even if I change my bottom thickness to 0.4 (1 layer) I still get this problem. Shouldn’t vase mode print without stops? I feel like I’m asking a very dumb questions but I’m missing sone importabt info here lol

  • kitnaht@lemmy.world
    link
    fedilink
    English
    arrow-up
    8
    ·
    edit-2
    3 months ago

    This is normal for vase mode, unless you have the bottom disabled. You’re doing normal, full layers there probably. What does the print look like? Is this even so much of a blemish that you should bother?

    • MissJinx@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 months ago

      I didn’t know. If I change to 1 layer it stillhas the same problem. For some reason I am not able to disable bottom

      • ShepherdPie
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 months ago

        Does your model have a bottom or is it just a hollow cylinder that’s open on both ends?

  • ROLLER@twit.social
    link
    fedilink
    arrow-up
    5
    ·
    3 months ago

    @MissJinx I’ve had issues with some slicers not coping with vase mode.

    Did you try changing the vase mode settings?

    Some models don’t work so well on vase mode. Usually with steep overhangs.

    You might try a different slicer?

  • elDalvini@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    2
    ·
    3 months ago

    This seems to be a bug in the slicer. I’m seeing the same issue in OrcaSlicer if the skirt height is set to more than one layer (even if the skirt is disabled). This makes sense if a skirt is used (can’t print a continuous spiral if you have to switch between printing the object and the skirt), but not if it’s disabled.

    What slicer are you using? If it’s a PrusaSlicer fork, this is likely the same bug.