Skip to content
This repository

Slicing results in rectangle (of infill?) over every layer #1095

Closed
linuxlurak opened this Issue April 05, 2013 · 13 comments

7 participants

linuxlurak Alessandro Ranellucci KnechtRuprecht jeffsaha chescott dinkel Tony Olivo
linuxlurak

Hello all

Sliced a quiet simple box and got this result:
weird1_gcode

in art of illusion i can export without errors. in aoi it looks like this (upside down):
weird1_stlmodel_pic
weird1_box_texture

Nothing special there (or am i wrong?). I carved the interior out of a bigger cube.

I noticed there is no bottom when i try to print this gcode...

Using Ubuntu (3.5.0-26-generic) with aoi 2.9.2 up to date per today, Slic3r 0.9.10-dev (commit 7e51cbc, Date: Thu Apr 4 01:24:40 2013 +0200 --> up to date too), gcode displayed in repetierHost 0.85 (up to date too).

Is this a problem with Slic3r generating gcode or o problem with my technique of designing?

Thanks for your help!
Lurak

PS: is it possible to upload the stl and gcode here?

linuxlurak

I sliced some other stl files and every object has similar problems (even the 10mm calibration cube...). So probably not a problem related to designing technique or the aoi exporting function.

even with default options (nothing changed in slicer), there ist no success.

anyway my most used config file is:

generated by Slic3r 0.9.10-dev on Fri Apr 5 16:49:11 2013
avoid_crossing_perimeters = 0
bed_size = 175,145
bed_temperature = 57
bottom_solid_layers = 3
bridge_acceleration = 0
bridge_fan_speed = 100
bridge_flow_ratio = 1
bridge_speed = 60
brim_width = 0
complete_objects =
cooling = 1
default_acceleration = 0
disable_fan_first_layers = 1
duplicate = 1
duplicate_distance = 6
duplicate_grid = 1,1
end_gcode = M104 S0 ; turn off temperature\nG28 X0 ; home X axis\nG28 Y0 ; home X axis\nM84 ; disable motors\nM245\nM81
external_perimeter_speed = 50%
external_perimeters_first = 0
extra_perimeters = 1
extruder_clearance_height = 20
extruder_clearance_radius = 20
extruder_offset = 0x0
extrusion_axis = E
extrusion_multiplier = 1.0
extrusion_width = 0
fan_always_on = 1
fan_below_layer_time = 60
filament_diameter = 3
fill_angle = 45
fill_density = 0.1
fill_pattern = rectilinear
first_layer_bed_temperature = 60
first_layer_extrusion_width = 200%
first_layer_height = 100%
first_layer_speed = 50%
first_layer_temperature = 193
g0 = 0
gap_fill_speed = 20
gcode_arcs = 0
gcode_comments = 0
gcode_flavor = reprap
infill_acceleration = 0
infill_every_layers = 1
infill_extruder = 1
infill_extrusion_width = 0
infill_first = 0
infill_only_where_needed = 0
infill_speed = 100
layer_gcode =
layer_height = 0.3
max_fan_speed = 100
min_fan_speed = 75
min_print_speed = 10
min_skirt_length = 0
notes =
nozzle_diameter = 0.35
only_retract_when_crossing_perimeters = 1
output_filename_format = [input_filename_base].gcode
perimeter_acceleration = 0
perimeter_extruder = 1
perimeter_extrusion_width = 0
perimeter_speed = 100
perimeters = 3
post_process =
print_center = 87,72
raft_layers = 0
randomize_start = 0
resolution = 0
retract_before_travel = 2
retract_layer_change = 1
retract_length = 1.25
retract_length_toolchange = 10
retract_lift = 0.25
retract_restart_extra = 0
retract_restart_extra_toolchange = 0
retract_speed = 100
rotate = 0
scale = 1
skirt_distance = 6
skirt_height = 1
skirts = 1
slowdown_below_layer_time = 15
small_perimeter_speed = 75
solid_fill_pattern = rectilinear
solid_infill_below_area = 70
solid_infill_every_layers = 0
solid_infill_extrusion_width = 0
solid_infill_speed = 55
start_gcode = M80 ; atx pwr anschalten\nM190 S60 ; warten bis heizbett auf 60\nM104 S192 ; warten bis extruder auf 192\nG28 ; home all axes
support_material = 0
support_material_angle = 0
support_material_enforce_layers = 0
support_material_extruder = 1
support_material_extrusion_width = 0
support_material_interface_layers = 0
support_material_interface_spacing = 0
support_material_pattern = rectilinear
support_material_spacing = 2.5
support_material_speed = 60
support_material_threshold = 0
temperature = 187
threads = 6
toolchange_gcode =
top_infill_extrusion_width = 0
top_solid_infill_speed = 30
top_solid_layers = 3
travel_speed = 150
use_relative_e_distances =
vibration_limit = 0
wipe = 0
z_offset = 0.2

KnechtRuprecht

This is definitely a problem of Slic3r with Linux. I'm using Linux Mint Debian Edition with the latest updates (sid).

In RepetierHost 0.84 with Slicer0.9.8 I had no problems like this one. After upgrading to RepetierHost0.85b with Slic3r0.9.9 I have the same problem. The problem appears also when slicing with slic3r standalone on Linux.

Unfortunally the "old" RepetierHost with the old slicer has the same problem now (it appeared after trying to use the new versions of both).

The stl Files are O.K. because with slicer0.9.9 on Win7 they slice normally and display normally in RepetierHost0.85b on Linux.

Here is a picture of mine original part and the sliced part. The settings of slic3r are the default ones of 0.9.9.
Slic3r-linux-failure

Thanks for reading and hopefully fixing the bug.

jeffsaha

I have the same issue with MINT. Slic3r 0.9.9 and Pronterface
Screenshot - 04012013 - 10:51:24 PM

chescott

Can also confirm issue with Ubuntu 12.04 (64) / slic3r 0.9.9, seems to be adding raft at every infill, no luck in trying to roll back to 0.9.8 slic3r.

linuxlurak

Fired up virtualbox with win7 and slic3r worked. at least on windows :D. (my first aproach to run slic3r.exe with wine did fail.) remaining problem under linux confirmed too.

can someone guide me to downgrade with git under ubuntu? i did some test but im not aware of the whole git reset processes and all... did some googling and tryied half a day but those rectangle structures remain. went back to Mar 26, 2013 and commit d2b451d but problem remained.

other ways to help debugging?

dinkel

Workaround found: Problem with Boost::Geometry::Utils package

I've had the same problem on Xubuntu 12.10, 64bit. I could solve it, by downgrading the Boost::Geometry::Utils package to version 0.06 (from 0.07). I am not a cpanminus expert, but quite probably

$ sudo cpanm http://www.cpan.org/authors/id/A/AA/AAR/Boost-Geometry-Utils-0.06.tar.gz

should do.

Can anyone confirm?

So one should check what's wrong with the new version and possibly update the installation instructions.

chescott

Can confirm Dinkel's fix on Ubuntu 12.04 (64) downgraded Boost to 0.06 and no artifacts now showing in G-Code

Alessandro Ranellucci
Owner

Escalated to the upstream library maintainers: https://svn.boost.org/trac/boost/ticket/8419

Alessandro Ranellucci
Owner

Also, just released Boost::Geometry::Utils 0.08 which includes a workaround.

linuxlurak

Seems with boost geometry utils 0.08 slicing under linux works again!

Alessandro Ranellucci
Owner

Good – closing this one as Boost::Geometry::Utils now contains the relevant regression test.

Alessandro Ranellucci alexrj closed this April 08, 2013
Tony Olivo
Thav commented April 08, 2013

I might be a dummy, but

$ cpan Boost::Geometry::Utils
Reading '/home/tony/.cpan/Metadata'
    Database was generated on Mon, 08 Apr 2013 06:17:03 GMT
Boost::Geometry::Utils is up to date (0.07).

0.08 shows up at CPAN (http://search.cpan.org/~aar/Boost-Geometry-Utils-0.08/), but I can't install that version. Any thought on how to update the CPAN repo to get the latest?

EDIT:
Taking a hint from @dinkel, I solved my problem.

sudo apt-get install cpanminus
sudo cpanm http://search.cpan.org/CPAN/authors/id/A/AA/AAR/Boost-Geometry-Utils-0.08.tar.gz
Tony Olivo
Thav commented April 08, 2013

The tests of fill.t work now, but now polyclip.t fails.

t/polyclip.t ......... 1/24 
#   Failed test 'line is clipped to square with hole'
#   at t/polyclip.t line 146.
#     Structures begin differing at:
#          $got->[0][0][0] = '152.742'
#     $expected->[0][0][0] = '152'
# Looks like you failed 1 test of 24.

Since that was clip_line (https://github.com/alexrj/Slic3r/blob/master/lib/Slic3r/ExPolygon.pm#L169) which contains

Boost::Geometry::Utils::polygon_multi_linestring_intersection

could there be any relation?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.