[Solved?] Slicing never finished and getting stuck

[le_avion]

Few times now I ran into an issue where S3D gets stuck at the end of preparing to print. It gets stuck displaying "Finished parsing G-Code file" and the blue bar never reaches the end. It seems to happen either having multiple copies of the objects in which case lower the number of duplicates helps or when slicing a large object. The only thing I can do is exit the program and try again but it doesn't help, it is still getting stuck at the same spot.

[mthompson239]

Wonder if while slicing, it stores temp data on the local HD tht might be near capacity...shot in the dark. I think my slicer crashed only once on me when I tried to sliced a file that was pretty much near my over all limits and at like 80% infill. #rookiemistake with one of my first designs. What are your system stats while this is slicing...cpu/memory?

[le_avion]

It's not space for sure:

Code: Select all

$ df -h /
Filesystem                   Size  Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-root  1.8T  169G  1.5T  10% /

and even though I have plenty of memory (64GB) I also had like a gazillion tabs open in chrome so it may have consumed it all.

Code: Select all

$ free 
              total        used        free      shared  buff/cache   available
Mem:       65382816     7371676    54618500      428908     3392640    56972312
Swap:      66502652           0    66502652

After restarting the computer I was able to slice the previously unslicable.

[horst.w]

It's not space for sure:
...
After restarting the computer I was able to slice the previously unslicable.

... without any changing of your settings?

Sometime this happens to me when a model ist not watertide.
And it is recommended to close the program time to time. Two weeks ago I had a situation, I could change the First Layer Width how ever I had everytime the same result. This was only to solve by restarting the computer.


horst.w, GER

[le_avion]

... without any changing of your settings?

Sometime this happens to me when a model ist not watertide.
And it is recommended to close the program time to time. Two weeks ago I had a situation, I could change the First Layer Width how ever I had everytime the same result. This was only to solve by restarting the computer.
horst.w, GER

No change in settings. I believe that the model is fine since I already sliced it and printed it at 100%. The problem started when I resized it to 200%. Also restarting the S3D didn't help but restarting the computer did and I was able to slice it.

[horst.w]

You are working in inch > mm or only mm?


It may be a problem of scaling, because a STL-File don't contain any dimension values. After having trouble you close the program with the included object, which is scaled. This will be stored when menue TOOLS> Options > Save and Restore ... is checked on.

The problem is coming up when an Inch-values is also plausible to the slicer as an applicable mm-values (e.g. 10 " are possible and 10 mm also, but 20" > 20 mm are not plausible, this makes no problems).
Have a look to your settings in TOOLS > Options > Model 1st check-box, that may be the key to your problem.

It's only an idea of mine!


H.


PS. S3D stores some files very deep in the system, even when de-installing and re-installing the program not all old settings are cleaned up. Read the How To's - clean up the computer .... Perhaps there is anything going wrong

[le_avion]

You are working in inch > mm or only mm?

Only mm.

I will look for the information on how to cleanup the installation and try a reinstall when it happens again. Since it is a Linux system and the application was installed as a user and not root, the only places S3D can store files is in my home directory in the ~/.config/Simplify3D and ~/.local/share/Simplify3D directories and I don't see anything outside the program and libraries in the installation directory.

Have a look to your settings in TOOLS > Options > Model 1st check-box, that may be the key to your problem.

Automatically scale to correct unit system without prompting is unchecked.

I still think it was a memory issue.

Avi