I just ran memtest86+. Fortunately there weren't any errors. The thing I try to print is complex but not that complex (
http://www.thingiverse.com/thing:19104
) the same thing happens with the terminator skull. (Not scaled 0.1mm layer height)
I just ran memtest86+. Fortunately there weren't any errors. The thing I try to print is complex but not that complex (
http://www.thingiverse.com/thing:19104
) the same thing happens with the terminator skull. (Not scaled 0.1mm layer height)
At 0.2mm layers the cellularThing_optimizedForMakerbot.stl seems to slice, but it is using a huge amount of memory, like 800MB. With thinner layers that would get even worse. Slic3r or Kisslicer might do a better job at these models.
It's a known problem, and solving it would mean moving to another slicer (Cura is Skeinforge based), but that's no an easy change to make.
Yeah but I don't want to use a different slicer, since cura gave me excellent results - way better than netfabb.
Instead I try to run linux in a virtual box and slice it there with cura. Hope that works...
Quick update: I installed Ubuntu in a virtual box and installed Cura there (which wasn't that easy but finally I managed to do it). Everything works just fine now.
Recommended Posts
Daid 304
The 32 bit pypy implementation can only use 2GB of memory under windows. So even if you have 10GB of free ram, it will still bug out after using 2GB. Which is a bit of a shame, as the slicing process is currently quite memory hungry.
I've never had a model so complex that it would bug out like this, but other people have had the same problem.
However, a memory error could also indicate a problem with your RAM. I highly recommend running memtest:
http://www.memtest.org/
to be sure that is not it.
(This problem is limited to Windows, Mac is always 64 bit, and for linux there is a 64bit pypy to use)
Link to post
Share on other sites