I'm using 1.41.1-5 and playing around with the new options. When I enable "Suporting dense layers" with algorithm automatic, nothing changes before a solid layer. Only "Anchored" inserts a denser infill layer. Is this a bug or a misunderstanding of it's way of working?

Screenshot of infill with "Automatic" just before the first real solid layer:

Version

Latest release... Support edition

Win64

Behavior

Can no longer drag stl file onto slic3r icon and have it get opened automatically. Have to now open slic3r first and drag stl file into slic3r window.

Last version before brim ears edition was working fine.

Version Slic3r++_1.42.0-alpha6.0_190221

Operating system type + version
Windows 10, all updates.

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

Behavior
Slic3r++ crashes while slicing.

Describe the problem
Slicing certain objects throws an "Vector too long" during slicing. Slic3r++ has to be closed and reopened to work again. Other objects work fine. Objects also slice fine in Slic3rPE.

Steps needed to reproduce the problem

I've attached three files from the same thingiverse thing: https://www.thingiverse.com/thing:3469271
The extruder parts fail to slice, throwing the error message. The carriage slices fine.

Expected Results
A complete slice.

Actual Results
Aborted slice, error message and need to close slic3r.

Screenshots from Slic3r preview are preferred

STL files and config:
files.zip
config.zip

Using 1.41.2-1 I get random places where ironing will "burn" through the top layer.
Do you have any suggestions on how to avoid it?
I changed the top solid speed from 40 to 60mms, and it improved things a bit.
I've set this print to be a bit overextruded and bumped the infill/perimeters overlap to 50% so there should be enough plastic to cover it nicely when ironed.

In Cura 60mms works fine for ironing.

Here are examples:

Hi, would you please make macOS build of your fork? it looks interesting

When slicing in vase mode, the line are not joined and too many layer are created.

Probably something related to the "last layer at exact height" function

Also, it seems this function doesn't update the flow if the height is changed (0.2mm -> 0.25 and it underextrude)

Solutions:

• short-term : deactivate it
• long-term: redo it.

Version

Slic3r++ 1.42.0-alpha3.11

Operating system type + version

Windows 10 (build 17134), 64-bit edition

Feature Request

I opened this Feature Request at Prusa Slic3r github and they are looking for volunteers. As i am not a programmer and love your improvements to Slic3rPE I was thinking maybe you will look into it if that makes sense or not and how difficult it is to implement.
Here the link to the original Feature request and feedback i got prusa3d#1282

BTW: Thanks for the great work.
My favorites at this moment (have to look for more awesome upgrades/features) are:

• Love the "Brim ears", i designed in the past my own for some potential lifting parts + ABS prints, but now no need for that anymore.
  -The Octoprint cancel-object output option you implemented.

Version

Slic3r++_1.42.0-alpha5.1_190214

Operating system type + version

Windows 10

Behavior

Trying to slice this file. Program freezes at about 20% of progress bar.

STL files.zip

STL/Config (.ZIP) where problem occurs

Upload a zipped copy of an STL and your config (File -> Export Config)

like the cura one

edit: or just try to zig-zag between 1st and 2nd perimeter, like for looping perimeters?

Version

"Boring edition ++"

Operating system type + version

Windows 10 10.0.17763 build 17763 according to System information

Behavior

When I click the "Cut" button, I can't set the cut height. Pressing numbers on the numpad rotates the view and does not insert the numbers into the textbox, the number bar numbers do nothing. Pressing delete or trying to use ctrl+v also only affects the scene, not the input texbox.

The new dense layer isn't good for the previous use-case: it create a full layer

• see why
• add option to return to the 1.40 (or wathever previous) version.

Version
1.4.20 alpha 6

Operating system type + version
Windows 10

Behavior
Slicing sequential objects skirt is generated around all objects and not around every sequential object.

Steps needed to reproduce the problem
Create a copy of the object and choose complete individual objects in sequential printing.

Expected Results
Skirt should be around every copy of the object.

Actual Results
One skirt around all sequential objects.

Version

Slic3r++ 1.42.0-alpha3.1

Operating system type + version

Win64

Behavior

Your fork seems to be ignoring sometimes the speeds I set. For example, check my settings below, I have all speeds set to 15mms and auto cooling turned off:

But you can see in the speed preview, it wants to put several things much faster than 15mms, even though I set all speeds to 15mms and even set the max printer speeds to 15mms:

Below is the same profile in Slic3r PE 1.42.0-alpha4. It's working correctly and makes whole print same speed of 15mms.

Is this a bug with your fork, or a bug with the alpha3 version and will be fixed when your fork updates to alpha4? If this was a bug in official slic3r alpha3, ignore this issue and close it. :)

Operating system type + version

Windows 10

Is this a new feature request?

Yes

Many people who do 3D design use a 3DConnextion Space Mouse. This tool works brilliant in things like Fusion360 and Blender, for navigating around a model, zooming, panning, &c.

It would be helpful to have it work in Slic3r, too. It's not a major thing, but it would mean my work-flow between the design and the slicing would be improved!

Thanks for the consideration.

Version

Slic3r++ 1.41.2-1 Win32 release

Operating system type + version

Windows 10

Behavior

Setting the attached STL to 100%, the generated preview and the print does some weird bridging moves while sanding on the same layer. Any ideas what can be done to fix this issue?

Layer that goes before ironing happens:

Layer where ironing happens:

How it looks after printing:

As you can see the weird bridge infill things are present..

STL/Config (.ZIP) where problem occurs

Config is default(prusa MK2.5) only with ironing set. Infill is set to 100%.

fans.zip

Version

1.41.2

Using PLA and my Prusa i3Mk2, my flow rate is spot on for normal printing. However when I try the Ironing feature, some parts of the top surface are smooth and others are rough like sand paper. It seems as it would need a slight increase of the flow rate for ironing, is it possible to adjust this (guess not)?

I read in the wiki that you apply 90% flow rate at first pass and 10% on the second. So it should add up to 100%, but maybe due to the double pass it fills more small gaps that would be containing air with only 1 pass between the layers resulting in a more dense layer therefore needing some % more filament..?

Hi, I am unable to build the masterPE branch, I am following the Prusa manual, I am able to build the original repo just fine, this is the error:

make[2]: *** [src/libslic3r/CMakeFiles/libslic3r.dir/pchheader.cpp.o] Error 1
make[1]: *** [src/libslic3r/CMakeFiles/libslic3r.dir/all] Error 2
make: *** [all] Error 2

Version

Version 1.42.0-alpha4.0

Operating system type + version

Windows 10 x64

Behavior

Simple box design, 0.7mm solid bottom, 2.5mm wall printed with 2 perimeters, setting the infill to 0% causes the inside wall perimeters to print in thin air above the initial solid layers. One perimeter layer is skipped or the solid infill doesn't extend out to support the first perimeter layers. "One perimeter on Top surface" doesn't seem to change the behavior. Setting even 1% infill will fix the problem, it extends the "top" layer under the first inside perimeters to support them correctly.

This can be observed in the layer preview and when printed it fails (spaghetti monster) as soon as those perimeters try to print.

STL/Config (.ZIP) where problem occurs

STL_Config.zip

I want to see what can happen if i create a little overlap with the perimeter.
Does it help/destroy the overhangs, bridges, delamination?

Not really an issue per se but can't find a way to send a message to a user on GitHub.

Just wondering if at all you could make a guide in your spare time, that shows the differences between your fork and the official slic3r PE, like what features are new, and where to find them, and what each feature does. I found a few new features, and it's nice that the tool tips have a brief description, but they don't really go in-depth to what the features really do.

I really like what you are doing, you definitely have added some things I wish Prusa would add to their fork of slic3r.

Do you think there's any way to add an option to make holes diameter bigger or smaller based on preference? My holes always come out about .30mm smaller than I design them once I print them and if there was a way to adjust that in slicing it would be immensely helpful.

Also by the way one of your options has a typo in English language, it is in as "briging" but should be "bridging" I'm not sure where it was.

Can't link the thread to the private Facebook group about this issue so I'll just post a photo of the discussion

Sorry for being annoying. I'm by no means trying to make you work hard, just throwing out ideas out there to improve the overall slic3r experience, and your fork is my favorite so far.

Something I think would be useful is a feature where you can control the Z-lift to not happen on the last layer, to help prevent blobs at the top of big flat prints.

Currently there is a setting for z-lift where you can enable it only on a Z-MM range, but it's not very intuitive because you have to change it for every part you print, and look at the part to calculate what layers correspond to the correct MM.

Far more easier would be just a setting (checkbox) where you could disable Z-lift on the first and last layers (or for each).

Version

1.42.0-alpha2

Operating system type + version

win64

Behavior

custom start gcode under printer not saving when profile is saved. It just reverts back to whatever the last input was when profile is reloaded.

This is happening in 1.42.00 alpha2 supermerill edition.

It is not happening in officla slic3rPE 1.42.00 alpha1. I have not tested official alpha2 PE yet.

1.42.0
The Slic3r 1.3.0 has a option under Layers and perimeters
Use adaptive slicing and scroll bar option under called Adaptive quality.

Would like to see these added

Version

Version of Slic3r used goes here
1.42.0.Alpha 6
Use About->About Slic3r for release versions

For -dev versions, use git describe --tag or get the hash value for the version you downloaded or git rev-parse HEAD

Operating system type + version

What OS are you using, and state any version #s
Windows 10 Home 1803 17134.590

Behavior

• Describe the problem
  When I select to use the wipe tower in a dual print it pops this error up

The Wipe Tower currently supports the non-soluble supports only if they are printed with the current extruder without triggering a tool change. (both support_material_extruder and support_material_interface_extruder need to be set to 0).

The above are already set to 0

• Steps needed to reproduce the problem

Just select use wipe tower or try to slice it.

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

It wont let me go any further than this

• Screenshots from Slic3r preview are preferred

Is this a new feature request?

STL/Config (.ZIP) where problem occurs

Upload a zipped copy of an STL and your config (File -> Export Config)

I figure I would mention this to help improve the slic3r.

I talked with you on discord, I had my infill printing very slowly, you wrote “It's possible if your filament cooling time is greater than the layer time. It will slow down the infill and try to let the perimeter at the same speed if possible.”

I was in fact playing with cooling layer times. I raised/lowered the various values to try to increase the print time, with the goal of slowing down a particular print/improving quality by increasing the amount of print time.

I’d increase the value, and slice, and look at the print time. However, my changes ended up being a ~2 hour print time difference due to slow infill speed/wait time, the slic3r only showed an increased print time of roughly 3 minutes.

So...basically the print time calculation isn’t accurate taking into account these changes. A 3 minute estimated print time increase could actually result in 2 hours longer print time on a small object. On a larger object, the time difference could be days.

Also, the speed preview doesn’t reflect the changes either, so your print speed and print time is totally in the dark/unknown.

Version
1.42.0 - alpha6.0

Operating system type + version
Windows 10 64bit

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

Behavior

Describe the problem
UI is slow when going inbetween UI elements with mouse. For example if I click on extrusion widths, they hang entire slic3r for a second or two. Especially apparent with several instances launched. Setting up a 1mm nozzle took me close to 10 minutes because of constant hanging and dialogs that ask me to make sure my nozzle is really 1mm. 😄

Steps needed to reproduce the problem
Turn on Slic3r and click around extrusion width inputs or other settings.

Expected Results
UI is as responsive as it was in Slic3rPE 1.42

Actual Results
Hanging on every input field click..

Maybe it's a debug build of the application?

1.42.0-alpha5.0+unknown
Windows 10 home version 1803

This is a feature request/continuation of the studies and changes logged on Reddit, following these successful clear prints obtained from the cura slicer:

essentially, due to the changes made to slic3r after the feature request seen on reddit, Ironed infill has been added successfully to the dev build. It works as intended in code, but does not currently produce the same results in other slicers(cura) and is therefore unfinished, for the time being, The main source of scattering within the model is the presence of microscopic bubbles, both in lines pressed between the extrusions, and caught under the extrusions due to printing on a roughly ironed surface. Here are some solid prints with clear filament. both of their top layers have been sanded to a polish for comparison:

without bubbles (cura code hand-modified with ironing every layer):

with bubbles (Slic3r code direct from program)

I'm not sure of the exact cause of the bubbles in this case, but they appear to be a combination of rough ironing and gaps between extrusions. The common solutions are: extruding more in total, extruding at 10% during ironing, ironing in smaller passes, ironing a little hotter, and selectively cooling either the ironing, first extrusion, or both.

with all these possible options, it may be prudent to add ironing as its own, advanced section in Layer Options, instead of an infill type, seeing is ironing should also apply to the shell.

Like in Cura

Version

Slic3r++_1.41.2_win32_20180926

Behavior

From #3
"as soon as there is some solid infill, all the next layers are with denser infill rate regardless of the real necessity.
The consequence for the joined case is that I have a denser density on le whole part as soon as the layer 16 (4.10mm height) due to small top solid areas (layer 19 -5.0mm height) and for all the next layers."

That issue still occurs.

Version

1.41.2 Supermerill edition

Operating system type + version

windows 10

Behavior

I can't use any support, or I get this error. It won't let me export the gcode and it also doesn't let me preview the gcode.

I don't get this error in official slic3r PE, only your fork.

Version

Slic3r++ 1.42.0-alpha3.11

Operating system type + version

Windows 10 (build 17134), 64-bit edition

Feature Request

Hi,

maybe some other MMU functions would be interesting, like the Palette 2 has:

• Gradient Mode where there is a continuous material change without purge block (maybe wipe oozing filament inside the object) https://support.mosaicmfg.com/hc/en-us/articles/360011230493-Gradient-Mode-Palette-2-
• Pattern Mode https://support.mosaicmfg.com/hc/en-us/articles/360011133574-Pattern-Mode-Palette-2-
• Random Mode https://support.mosaicmfg.com/hc/en-us/articles/360011132614-Random-Mode-Palette-2-

I really like these modes as you don't have to have multi material STL files. You just have aone STL part you want to print with bit more shine to it.

I opened a feature request on the Prusa Github, but as they are busy with lot of other things it might take some time prusa3d#1283

Don't know if that is interesting for you to have a look into it.

Version

1.42.0 alpha 3 - I THINK!

Operating system type + version

win64

Behavior

I installed the latest 1.42.0 ALPHA 3 release but it's showing up in the program as alpha 2 still? I just want confirmation if you are getting this too, or if maybe the release was compiled wrong.

Just tree supports as cura or meshmixer has, they are already there for the SL1, so why not for FDM

Version

Slic3r++_1.42.0-alpha4.0_190204

Operating system type + version

Win 10

Behavior

Just tried ironing for the first time, and I am getting odd whispy bits of filament deposited on top of the print. The fan is on 100%, so I am wondering if it's blowing some off the extruder? It's a really odd problem, which has never happened before without ironing...

Noticed some really strange edge behavior on my first try of this slic3r branch. It looks like these gaps/harsh edges in the perimeter line.

After playing a little bit, seems the issue is due to the seam alignment. For example, random or rear creates a smooth edge in the picture, whereas nearest/aligned create this very ugly edge as shown.

using this stl : prusa3d#1364
and pruse 0.35 setting

"avoid crossing perimeter" isn't good enough to avoid oozing & [something]. We need a better option.

Version
Slic3r++ 1.42.0-a6

Operating system type + version
Windows 10 64-bit

3D printer brand / version + firmware version (if known)
Prusa Mk2.5 (not relevant, this is slicing issue)

Behavior
Slicing the attached model. Prusa version of Slic3r generates solid infill around the tops and bottoms of the holes in small circles (at heights around 5.6mm). Slic3r++ generates several layers of solid infill, using top infill pattern for one of them - an octogram spiral layer buried in the middle of the print (see attached screenshots).
I tried disabling anchor size or using the default anchor size, no difference.

Slic3r++:

Prusa:

Tool stand.3mf.txt

Project File (.3MF) (or stl+config) where problem occurs

file-> save as

zip it

drag it here

Version

version_1.40.1-rc-33-g9cb144dd

Operating system type + version

Windows 10 x64 1803

Behavior

No "denser infill below top layers" when I define 2 perimeters. But there is "denser infill below top layers" when I define 3 perimeters.

STL/Config (.ZIP) where problem occurs

04513-r01f - I3D-1-20180707-174902-(P)04513-Light-MK3-(F)ColorFabb XT - chaud2-(P)PMK3-R0.8-M860-1.40.1-rc.zip.amf.zip

I use HTPLA as filament often, which requires higher temperature than normal PLA. But Slic3r don't support this filament right now.

Reason for having this as an option would be so that gcode output naming when using placeholders can be differentiated from regular PLA...

I asking you to put it in your fork, rather than in main slic3r, because Prusa never listen to any of my new feature ideas and they just close the topic.

Or better would be if user could actually type in filament name there and it would remember it. I tried typing in "HTPLA" in the box but it just revert back to PLA, because HTPLA is not an option.

Version

Slic3r++ 1.42.0-alpha3.1

Operating system type + version

Windows 10 (build 17134), 64-bit edition

Behavior

Help -> Report an issue in Slic3r++ opens a browser to "https://github.com/prusa3d/supermerill/issues/new" which can not be found.

@mperino asked for direction for a linux build:

Any tutorial for the Linux build? THe page for it is kinda empty :(
https://github.com/supermerill/Slic3r/blob/master/doc/How%20to%20build%20-%20UNIX.md

me:

I left the master branch on the last (december 2018) "stable" and used the masterPE for the new ui (and no perl, new build stack), as long as it's on alpha.

you should checkout the masterPE branch and use this : >https://github.com/supermerill/Slic3r/blob/masterPE/doc/How%20to%20build%20-%20Linux%20et%20al.md

mperino :

Thank you, That got me closer, but alas it puts me into a compile error:
^~~~
CMakeFiles/Makefile2:154: recipe for target

me:

you forgot to copy the lines before the arrow. And you should open a "compile on linux" issue, that one is for macos.

mperino:

/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/TriangleMesh.hpp:112:110:
warning:   base ‘Slic3r::Point’ [-Wreorder]
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/TriangleMesh.hpp:112:5:
warning:   when initialized here [-Wreorder]
     IntersectionPoint(const IntersectionReference &ir, const Point &pt) :
IntersectionReference(ir), Point(pt) {}
     ^~~~~~~~~~~~~~~~~
In file included from
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PerimeterGenerator.cpp:16:0:
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/SVG.hpp:
In constructor ‘Slic3r::SVG::SVG(const char*)’:
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/SVG.hpp:81:17:
warning: ‘Slic3r::SVG::filename’ will be initialized after [-Wreorder]
     std::string filename;
                 ^~~~~~~~
In file included from
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PerimeterGenerator.cpp:16:0:
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/SVG.hpp:19:10:
warning:   ‘bool Slic3r::SVG::flipY’ [-Wreorder]
     bool flipY;
          ^~~~~
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/SVG.hpp:21:5:
warning:   when initialized here [-Wreorder]
     SVG(const char* afilename) :
     ^~~
In file included from
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PerimeterGenerator.cpp:16:0:
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/SVG.hpp:
In constructor ‘Slic3r::SVG::SVG(const char*, const Slic3r::BoundingBox&,
coord_t, bool)’:
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/SVG.hpp:81:17:
warning: ‘Slic3r::SVG::filename’ will be initialized after [-Wreorder]
     std::string filename;
                 ^~~~~~~~
In file included from
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PerimeterGenerator.cpp:16:0:
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/SVG.hpp:18:11:
warning:   ‘Slic3r::Point Slic3r::SVG::origin’ [-Wreorder]
     Point origin;
           ^~~~~~
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/SVG.hpp:24:5:
warning:   when initialized here [-Wreorder]
     SVG(const char* afilename, const BoundingBox &bbox, const coord_t
bbox_offset = scale_(1.), bool aflipY = false) :
     ^~~
In file included from
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PerimeterGenerator.cpp:16:0:
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/SVG.hpp:
In constructor ‘Slic3r::SVG::SVG(const string&)’:
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/SVG.hpp:81:17:
warning: ‘Slic3r::SVG::filename’ will be initialized after [-Wreorder]
     std::string filename;
                 ^~~~~~~~
In file included from
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PerimeterGenerator.cpp:16:0:
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/SVG.hpp:19:10:
warning:   ‘bool Slic3r::SVG::flipY’ [-Wreorder]
     bool flipY;
          ^~~~~
In file included from
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PerimeterGenerator.cpp:16:0:
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/SVG.hpp:27:5:
warning:   when initialized here [-Wreorder]
     SVG(const std::string &filename) :
     ^~~
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/SVG.hpp:
In constructor ‘Slic3r::SVG::SVG(const string&, const Slic3r::BoundingBox&,
coord_t, bool)’:
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/SVG.hpp:81:17:
warning: ‘Slic3r::SVG::filename’ will be initialized after [-Wreorder]
     std::string filename;
                 ^~~~~~~~
In file included from
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PerimeterGenerator.cpp:16:0:
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/SVG.hpp:18:11:
warning:   ‘Slic3r::Point Slic3r::SVG::origin’ [-Wreorder]
     Point origin;
           ^~~~~~
In file included from
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PerimeterGenerator.cpp:16:0:
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/SVG.hpp:30:5:
warning:   when initialized here [-Wreorder]
     SVG(const std::string &filename, const BoundingBox &bbox, const
coord_t bbox_offset = scale_(1.), bool aflipY = false) :
     ^~~
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PerimeterGenerator.cpp:
In member function ‘void Slic3r::PerimeterGenerator::process()’:
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PerimeterGenerator.cpp:116:37:
warning: unused variable ‘numploy’ [-Wunused-variable]
                                 int numploy = 0;
                                     ^~~~~~~
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PerimeterGenerator.cpp:168:51:
warning: comparison between signed and unsigned integer expressions
[-Wsign-compare]
                                 for (int i = 0; i < last.size();i++) {
                                                 ~~^~~~~~~~~~~~~
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PerimeterGenerator.cpp:195:33:
warning: unused variable ‘numploy’ [-Wunused-variable]
                             int numploy = 0;
                                 ^~~~~~~
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PerimeterGenerator.cpp:425:43:
warning: comparison between signed and unsigned integer expressions
[-Wsign-compare]
                         for (int j = 0; j < contours[t].size(); ++j) {
                                         ~~^~~~~~~~~~~~~~~~~~~~
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PerimeterGenerator.cpp:
In member function ‘Slic3r::ExtrusionLoop
Slic3r::PerimeterGenerator::_extrude_and_cut_loop(const
Slic3r::PerimeterGeneratorLoop&, Slic3r::Point, const Slic3r::Line&) const’:
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PerimeterGenerator.cpp:876:45:
error: cannot bind non-const lvalue reference of type ‘Slic3r::Line&’ to an
rvalue of type ‘Slic3r::Line’
                 coord_t dot =
direction.dot(Line(direction_polyline.points.back(),
direction_polyline.points.front()));

 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/Polygon.hpp:7:0,
                 from
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/ExPolygon.hpp:5,
                 from
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/ExPolygonCollection.hpp:5,
                 from
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PerimeterGenerator.hpp:6,
                 from
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PerimeterGenerator.cpp:1:
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/Line.hpp:50:13:
note:   initializing argument 1 of ‘coord_t
Slic3r::Line::dot(Slic3r::Line&) const’
     coord_t dot(Line &l2) const;
             ^~~
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PerimeterGenerator.cpp:914:45:
error: cannot bind non-const lvalue reference of type ‘Slic3r::Line&’ to an
rvalue of type ‘Slic3r::Line’
                 coord_t dot =
direction.dot(Line(direction_polyline.points.back(),
direction_polyline.points.front()));

 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/Polygon.hpp:7:0,
                 from
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/ExPolygon.hpp:5,
                 from
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/ExPolygonCollection.hpp:5,
                 from
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PerimeterGenerator.hpp:6,
                 from
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PerimeterGenerator.cpp:1:
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/Line.hpp:50:13:
note:   initializing argument 1 of ‘coord_t
Slic3r::Line::dot(Slic3r::Line&) const’
     coord_t dot(Line &l2) const;
             ^~~
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PerimeterGenerator.cpp:
In member function ‘bool
Slic3r::PerimeterGeneratorLoop::is_internal_contour() const’:
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PerimeterGenerator.cpp:1230:5:
warning: this ‘for’ clause does not guard... [-Wmisleading-indentation]
     for (const PerimeterGeneratorLoop &loop : this->children)
     ^~~
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PerimeterGenerator.cpp:1233:9:
note: ...this statement, but the latter is misleadingly indented as if it
were guarded by the ‘for’
         return true;
         ^~~~~~
[ 90%] Building CXX object
xs/CMakeFiles/libslic3r.dir/src/libslic3r/PlaceholderParser.cpp.o
xs/CMakeFiles/libslic3r.dir/build.make:1262: recipe for target
'xs/CMakeFiles/libslic3r.dir/src/libslic3r/PerimeterGenerator.cpp.o' failed
make[2]: ***
[xs/CMakeFiles/libslic3r.dir/src/libslic3r/PerimeterGenerator.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PlaceholderParser.cpp:
In function ‘std::__cxx11::string Slic3r::process_macro(const string&,
Slic3r::client::MyContext&)’:
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PlaceholderParser.cpp:1186:10:
warning: unused variable ‘res’ [-Wunused-variable]
     bool res = phrase_parse(iter, end, macro_processor_instance(&context),
space, output);
          ^~~
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PlaceholderParser.cpp:
In instantiation of
‘Slic3r::client::macro_processor<Iterator>::macro_processor() [with
Iterator = __gnu_cxx::__normal_iterator<const char*,
std::__cxx11::basic_string<char> >]’:
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PlaceholderParser.cpp:1180:33:
 required from here
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PlaceholderParser.cpp:916:39:
warning: suggest parentheses around comparison in operand of ‘|’
[-Wparentheses]
                 (       eps(_a==true) > text_block(_r1) [_val=_1]
                         ~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PlaceholderParser.cpp:
In instantiation of ‘static void
Slic3r::client::expr<Iterator>::ternary_op(Slic3r::client::expr<Iterator>&,
Slic3r::client::expr<Iterator>&, Slic3r::client::expr<Iterator>&) [with
Iterator = __gnu_cxx::__normal_iterator<const char*,
std::__cxx11::basic_string<char> >]’:
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PlaceholderParser.cpp:982:103:
 required from
‘Slic3r::client::macro_processor<Iterator>::macro_processor() [with
Iterator = __gnu_cxx::__normal_iterator<const char*,
std::__cxx11::basic_string<char> >]’
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PlaceholderParser.cpp:1180:33:
 required from here
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PlaceholderParser.cpp:504:18:
warning: unused variable ‘value’ [-Wunused-variable]
             bool value = false;
                  ^~~~~
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PlaceholderParser.cpp:
In instantiation of ‘static void
Slic3r::client::expr<Iterator>::regex_op(Slic3r::client::expr<Iterator>&,
boost::iterator_range<IteratorT>&, char) [with Iterator =
__gnu_cxx::__normal_iterator<const char*, std::__cxx11::basic_string<char>
>]’:
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PlaceholderParser.cpp:484:106:
 required from ‘static void
Slic3r::client::expr<Iterator>::regex_matches(Slic3r::client::expr<Iterator>&,
boost::iterator_range<IteratorT>&) [with Iterator =
__gnu_cxx::__normal_iterator<const char*, std::__cxx11::basic_string<char>
>]’
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PlaceholderParser.cpp:1000:72:
 required from
‘Slic3r::client::macro_processor<Iterator>::macro_processor() [with
Iterator = __gnu_cxx::__normal_iterator<const char*,
std::__cxx11::basic_string<char> >]’
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PlaceholderParser.cpp:1180:33:
 required from here
/home/mperino/3d/Software/supermerril-slicer/Slic3r-master/xs/src/libslic3r/PlaceholderParser.cpp:462:32:
warning: unused variable ‘mask’ [-Wunused-variable]
             const std::string *mask     = nullptr;
                                ^~~~
CMakeFiles/Makefile2:154: recipe for target
'xs/CMakeFiles/libslic3r.dir/all' failed
make[1]: *** [xs/CMakeFiles/libslic3r.dir/all] Error 2
Makefile:162: recipe for target 'all' failed
make: *** [all] Error 2

like a vase mode but only for the external perimeter loop.

Version

version_1.40.1-rc-33-g9cb144dd

Operating system type + version

Windows 10 x64 1803

Behavior

Gyroid infill set as bridge feature.

STL/Config (.ZIP) where problem occurs

04513-r01f - I3D-1.zip

Are you planning to merge with the latest release of Slic3rPE again? The new support blocker system seems to be very interesting and would be fantastic to use in combination with your features

Version

Version of Slic3r used goes here
1.41.2 (1.41.0 -> your latest release)
Use About->About Slic3r for release versions

Operating system type + version

What OS are you using, and state any version #s
Win10 64bit

Behavior

Is this a new feature request?
Yes

Maybe it's already possible some how but here's my issue.

I make cookie cutters. The top most layers all all just outside perimeters. But even with "avoid crossing perimeters" setting checked, it still do cross some perimeters. And I get strings. Check below photo for example.

I wonder if it's possible to do continuous looping perimeters with ZERO travel so I never get the stringing. Maybe useful for other things too

Version
Version of Slic3r Prusa Edition used 1.42.0-alpha 6.0

Operating system windows 10

Behavior
Arrange not working properly with auto clearance setting.
Steps needed to reproduce the problem
Pressing the arrange button or the shortcut (A)
Expected Results
normal arrangement. They just do normal setting like we had not put any value in clearance.

Version

1.41.2

Operating system type + version

Windows 10 64bit

Behavior

When printing the lower part (~6mm) of a benchy with Slic3r++ I am getting some interesting gaps.

The gaps are not appearing when using Slic3r PE 1.41.2 with identical .ini files as they use the same settings folder.

This is a comparison picture:

SLic3r++ is on the right.

To reproduce it, just print the included small part of 3D benchy, it's a small print and a short one too.

I am wondering, maybe it's a settings issue? Yet disabling small gap detection and enabling thin walls did nothing.

I now have a ton of benchy bottoms trying to witch hunt this. :)

STL/Config (.ZIP) where problem occurs

bugreport.zip