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

long time to slice thing:23517 #390

Closed
simcop2387 opened this issue May 28, 2012 · 4 comments
Closed

long time to slice thing:23517 #390

simcop2387 opened this issue May 28, 2012 · 4 comments

Comments

@simcop2387
Copy link
Contributor

I've been trying to slice http://www.thingiverse.com/thing:23517 using latest git. It'll run for hours and hours without finishing and ended up using 10GB of ram before I killed it.

I'm using the config at https://gist.github.com/2819160 to do the slicing, along with the command there: ./slic3r.pl --load config_bulldog.ini --scale 150 --rotate 45 ../stl/BulldogwithPlatform_fixed.stl

I've tried running it through netfabb without any difference in the result. It just sits there processing the mesh without going any further. I've also tried 1 thread through 8 threads (max number of processors I have) without any change except in how quickly it starts to take up ram.

Telling it to not rotate and scale it allows it to succeed but I'd like to be able to rotate it so that I can make the largest copy of the model possible.

@simcop2387
Copy link
Contributor Author

Watching that last commit you just did for memory savings for hi-res input files, I'll give that new change a try later tonight to see if it helps. I did some more testing and the rotation wasn't the cause, but the scaling so I'm hoping this will improve the results.

@alranel
Copy link
Member

alranel commented May 29, 2012

--scale 150 ?!? What's your printer size?
Are you sure you want to print a 1.2 meters tall object??

I'm not surprised Slic3r is consuming so much memory... at 0.2mm it's going to draw over 60.000 layers...

@alranel
Copy link
Member

alranel commented May 29, 2012

Your bed_size is set to 140mm x 140mm though...

@simcop2387
Copy link
Contributor Author

Ok that is definitely where the problem was... I had assumed it would be a percentage like it is in the plating gui. much nicer at --scale 1.5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants