search

supermerill / SuperSlicer

G-code generator for 3D printers (Prusa, Voron, Creality, etc.)
4.11k stars 520 forks source link

Gcode generation problem - mesh size - suspicious result #4343

Open SimonSolar2C opened 3 months ago

SimonSolar2C commented 3 months ago

Version

Version of SuperSlicer used goes here (help->about) 2.5.60.00

Operating system type + version

What OS are you using, and state any version #s Windows 10

Behavior

Is this a new feature request? Related guides for writing feature requests: http://meta.stackexchange.com/a/259196 http://nickohrn.com/2013/09/write-great-feature-request-bug-report/ No

Project File (.3MF) where problem occurs

Upload a Project File (.3MF) Plater -> Save Project as... You have to zip it (or rename it to .zip) to be able to drag& drop it here

SimonSolar2C commented 3 months ago

Also please see my Gcode macro variables which worked in 2.5.59 image

; New method for new hotend M104 S0 ; Stops PS/SS from sending temp waits separately M140 S0 MESH_CONFIG X0={(first_layer_print_min[0]-10 <0 ? 0 : first_layer_print_min[0]-10)} Y0={ (first_layer_print_min[1]-10<0? 0 : first_layer_print_min[1]-10 )} X1={(first_layer_print_max[0]+10 >350? 350 : first_layer_print_max[0]+10 )} Y1={(first_layer_print_max[1]+10 >350? 350 : first_layer_print_max[1]+10 ) } ; PAM with my 10mm all around for better smoothing

TIMELAPSE_TAKE_FRAME SET_GCODE_OFFSET Z=0 ; coz I wonder if it messes up PRINT_START BED=[first_layer_bed_temperature] HOTEND={first_layer_temperature[initial_extruder]+extruder_temperature_offset[initial_extruder]} CHAMBER=[chamber_temperature]

supermerill commented 3 months ago

I tried with one of my project, and ican't reproduce. can you save & give me a project that shows the problem? (you dag & drop a zipped .3mf here)

btw, you can use min & max in macro: MESH_CONFIG X0={max(0, first_layer_print_min[0]-10)} Y0={max(0, first_layer_print_min[1]-10)} X1={min(350, first_layer_print_max[0]+10)} Y1={min(350, first_layer_print_max[1]+10)}

SimonSolar2C commented 3 months ago

Hi Thanks for looking:

Attached. Note this file gave ‘crash-like’ troubles with previous version. Sorry cant reproduce because I installed by overwriting into previous SuperSlicer folder.

Did you change the variable names for the print extents?

Kind regards, Simon Dyer, 2C Light Company Ltd. ph +643 981 8376 www.2CLight.com

From: Merill @.> Sent: Wednesday, July 3, 2024 8:27 PM To: supermerill/SuperSlicer @.> Cc: SimonSolar2C @.>; Author @.> Subject: Re: [supermerill/SuperSlicer] Gcode generation problem - mesh size - suspicious result (Issue #4343)

I tried with one of my project, and ican't reproduce. can you save & give me a project that shows the problem? (you dag & drop a zipped .3mf here)

btw, you can use min & max in macro: MESH_CONFIG X0={max(0, first_layer_print_min[0]-10)} Y0={max(0, first_layer_print_min[1]-10)} X1={min(350, first_layer_print_max[0]+10)} Y1={min(350, first_layer_print_max[1]+10)}

— Reply to this email directly, view it on GitHub https://github.com/supermerill/SuperSlicer/issues/4343#issuecomment-2205404457 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ADBC4VCIYJE3JO2UCRCFKPTZKOYVRAVCNFSM6AAAAABKI2UCT6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBVGQYDINBVG4 . You are receiving this because you authored the thread.Message ID: @.***>

SimonSolar2C commented 3 months ago

Just adding a further observation - it seems it has generated the output with the outer perimeter having a very low flow rate, whereas it should be similar to the inner perimeter. See pics below: image image image image

supermerill commented 3 months ago

you can't attach files by email, you need to drag & drop them here manually.

SimonSolar2C commented 2 months ago

printedPerfectWithSlower-BitsWIP-SScrashes.zip Sorry about missing the file. Here it is. I have confirmed this problem does not occur with my other files.