foreachthing

Results 73 comments of foreachthing

My Dashboard is all white, well, not all of it but a whole lot: ![image](https://user-images.githubusercontent.com/10420187/66538719-dddbd600-eb25-11e9-9f6a-4b7076519c14.png)

@scott0122 I think you need to go over here: https://github.com/prusa3d/Slic3r/issues/ Also, see here: https://github.com/prusa3d/Slic3r/issues/824 And maybe this one, too: https://github.com/prusa3d/Slic3r/issues/825

@bubnikv would you be kind enough to PR your changes to Slic3r as well? Thanks!

According to @bubnikv, we're to address the Slic3r-specific issue only here. So, again, _this_ https://github.com/prusa3d/Slic3r/issues/825 issue only concerns Slic3r - not Slic3rPE.

I don't see this in version 1.3.1: (with or without loading your config) ![image](https://user-images.githubusercontent.com/10420187/66805715-fd0fa480-ef25-11e9-863e-73379e904dcc.png)

You've done nothing wrong - I just had an older version installed. I downloaded the latest build but get the same result: Everything looks just fine! ![image](https://user-images.githubusercontent.com/10420187/66978027-8e0e8900-f0a8-11e9-9be9-b3c098b0d65b.png) Are you sure...

@amsterdamman… use Blender (blender.org) and the 3D-Print addin. You can visualize the faults and also fix it.

> Minimum fan spin-up time : use a better firmware / modify it. Not the job of the slicer, imho. Also, it's impossible to know when a g-code command is...

> Quite interesting but could binaries be provided? Everyone is not a master in compilation... Right there: https://github.com/mfx-inria/curvislicer/releases/