Slic3r v 1.2.4. Test Trial Report
Slic3r is one of the free applications available for generating G-code for 3D printers. It can be used both directly, with a graphical interface, and from the command line, including within other applications.
At present, “stable” is version 1.1.7, and “experimental” version 1.2.4 supports, according to the developer, compared to the stable version, incremental real-time slicing, a window for viewing the model in 3D, a window with a preview of the head trace , filling the internal parts of the three-dimensional honeycomb structure, etc.
Appearance of the program in version 1.2.x
')
The most valuable improvement, from my point of view, is the possibility of layer-by-layer preview of the results of the program. In previous versions, it was necessary to use third-party, relatively slow G-code visualizers. And without the use of a visualizer, unpleasant program or model errors are often found already at the cultivation stage. And the greater the volume of the model, the more expensive such errors.
I tried to evaluate the performance of the latest version of Slic3R and its suitability for use on real tasks based on 22 stl files.
The following results were obtained (for the 64-bit version for Windows)
In six cases, the program fell almost immediately.
In four cases, the disappearance of the internal shading on the layer was detected in the preview window. For example, this is what a normal layer looks like.
And so - with the missing shading
In this case, in three cases, the hatching disappeared on one layer, and in one case - on three.
Large files are loaded relatively slower than in version 1.1.7 - probably due to the fact that simultaneously with the download, the construction of the 3D view and the generation of the preview (G-code in the internal representation) begins.
For a file of 57 MB in size, reading and processing took about 16 minutes (for comparison, in version 1.1.7, reading takes about a minute, and 3D rendering takes about half an hour). At the same time, RAM required 2.3 GB.
When deleting a file (Delete button), the memory is not returned to the system /
For a simple model in the form of an exact hollow cylinder, the program generated some unexpected trajectories on some layers.
At present, “stable” is version 1.1.7, and “experimental” version 1.2.4 supports, according to the developer, compared to the stable version, incremental real-time slicing, a window for viewing the model in 3D, a window with a preview of the head trace , filling the internal parts of the three-dimensional honeycomb structure, etc.
Appearance of the program in version 1.2.x
')
The most valuable improvement, from my point of view, is the possibility of layer-by-layer preview of the results of the program. In previous versions, it was necessary to use third-party, relatively slow G-code visualizers. And without the use of a visualizer, unpleasant program or model errors are often found already at the cultivation stage. And the greater the volume of the model, the more expensive such errors.
I tried to evaluate the performance of the latest version of Slic3R and its suitability for use on real tasks based on 22 stl files.
The following results were obtained (for the 64-bit version for Windows)
In six cases, the program fell almost immediately.
In four cases, the disappearance of the internal shading on the layer was detected in the preview window. For example, this is what a normal layer looks like.
And so - with the missing shading
In this case, in three cases, the hatching disappeared on one layer, and in one case - on three.
Large files are loaded relatively slower than in version 1.1.7 - probably due to the fact that simultaneously with the download, the construction of the 3D view and the generation of the preview (G-code in the internal representation) begins.
For a file of 57 MB in size, reading and processing took about 16 minutes (for comparison, in version 1.1.7, reading takes about a minute, and 3D rendering takes about half an hour). At the same time, RAM required 2.3 GB.
When deleting a file (Delete button), the memory is not returned to the system /
For a simple model in the form of an exact hollow cylinder, the program generated some unexpected trajectories on some layers.
Source: https://habr.com/ru/post/375183/
All Articles