Open vladtcvs opened 8 years ago
I just played a little bit with your part and found the following effects: 1) I copied the main slicing relevant parameters into my settings (nozzle width, extrusion factors, selected options...) added the STL file and found my computer busy until slic3r crashes. 2) with my own settings I got very soon a complete layer composition. 3) just copied the basic geometry: nozzle width, fill parameter, layer height, advanced: no obvious problems. 4)activated support material: no change. 5) set support angle 70: generation of large support structures, but no change in layers. 6) switch on thin wall detection option: some silly changes in the infill, but not like yours
I have faced some problems with the thin wall detection option in another structure of mine, so this is generally off in my settings. It was messing up the infill in a similar way like you are reporting it. Please check if this has an impact on your slicing too.
I have a similar issue with a very simple model using this configuration with v1.2.9 stable on both 64-bit Arch Linux and 64-bit Windows 10. (This model is originally @PrestonStinson's.) Only the perimeter wall is generated; no filled base is generated. First layer is as follows. The brim is clipped by the screenshot but is present and correct in the GCODE.
The entire sliced model:
This example may be related: 1.3.0-dev 2017-05-09 git When printing bondi_dwarf.stl from http://www.thingiverse.com/thing:750403 The following settings print hollow (chain mail, which is a separate solid, has paths generated, but actual body, other than solid layers, does not):
Ultra Quality example:
Is this the same issue?
@expertmm Just to be sure, did Slic3r say it had to repair the model?
Additionally, we have no idea what your "Quality" settings have in them, please export a separate config.ini (File->Export Config
) for each one so that we can make sense of your report.
Thanks.
As far as I know I did not change these and they are default presets. Is that not correct?
That isn't something we ship.
You can export each config and zip them up and upload here.
Just so you know the gcodecook.py post-processing script's main purpose is to send the gcode to gpx (to convert to x3d), but doesn't modify the gcode.
The presets must have come with the prepackaged slic3r that was on my sd card that came with my FlashForge Creator Pro. Since then I had updated slic3r several times and never knew that the presets wouldn't have been there had I not used the version from FlashForge. expertmm-SlicerConfigExport.tar.gz Here are the separate ini files you asked for instead of the whole config folder.
For some models, big voids appears, some parts of a model have only perimeter.
https://vltc.net.eu.org/owncloud/public.php?service=files&t=fedcdae7216f7d281fdf840194df0110
version 1.2.9, debian. config.ini: