Does anyone know IF and when the next slic3r version will come out? Really a long time ago since the last update 
+Peter van der Walt thx. Already knew that 
but thats not really stable. Didnt find any clue when it will come out. No real updates on the site 
just thought somebody knew
+Peter van der Walt thx. Well seems thats rather far away lol
+Peter van der Walt already donated several times and sometimes on github helping sorting out bullshit (like wrong handling rather than an issue-stuff). But its more for fun.
+Peter van der Walt well i think slic3r may not be the slicer with most options or best gui. But its simple and versatile at once and its free. Supporting such a software/developer especially if you can make it better is my payment to it/him.
It’s such a pain to run from source on windows. Wish there were debug builds. The newer slic3r versions fix some outstanding bugs with thin walls.
I’m using Slic3r too and as you, I’m really expecting a new release even an alpha one as I haven’t achieved to compile the github stuff on Windows…
@Josef_Prusa seems to be compiling his own version of Slic3r for the i3 MK2 software package from newer sources with a bunch of bugfixes and improvements - maybe that would be a more reasonable version instead of the ancient official builds?
@Stephanie_A just switch to Gnu/Linux? /s
Lol thanks @Thomas_Sanladerer , I would if I could. It’s not so easy.
I just wish that they had a buildscript or something. These mixed development environments with c, c++, perl, and python are so messy. Throw in a couple hundred dependencies then it’s not worth it.
@Stephanie_A there are weekly builds generated here - https://bintray.com/lordofhyphens/Slic3r/slic3r_dev/view if i’m not mistaken they are win32 builds (which would work on windows).
i don’t have a windows box to check on ATM so i can’t be 100% sure…
@Tom_Keidar awesome, those do seem to work! They are not “compiled” .exe files, but instead interpreted (?) from the Perl source. No idea how much compiling Perl does while you run programs, but it feels plenty fast, on my PC at least.
@Thomas_Sanladerer good to know it works, thanks.
as a software engineer/architect i use compiled/built interchangeably when i don’t know if my target audience knows the difference (because to most people it all just means “magically turning code into something that works on my computer”).
a more accurate description of these packages are builds. since IIRC slic3r uses a c++ for the core api (math, geometry, data structures, etc…) which has to be compiled into a library which is then wrapped by a perl gui (maybe with some higher level processes for abstraction of the c++ api) which is probably packed by app::packer or something similar. so while the gui runs on interpreted perl, the main core (where all the hard work occurs) is compiled c++ which is probably why you don’t notice any lag.
if you are interested you can read more on perl “packing” - in this app:packer example - http://www.perlmonks.org/bare/index.pl/?node_id=215299