Bug or change Post version 2.8.1
Good Day all
Prusa has supported our printers all along however we have just discovered an issue with support for our printers post version 2.8.1
One of our printers has a bed size X 1800. We have preconfigured profiles for our printers customers can download and use. Since version 2.8.1 we are getting an error on trying to use this profile.
There is a max bed size in the X axis of 1200, When trying to modify the size to the correct size I get the error displayed in the attached picture.
The Snip of our profile that configures the bed size is below
[printer:Modix Big-180X Dual]
bed_custom_model =
bed_custom_texture =
bed_shape = 0x0,1800x0,1800x600,0x600
before_layer_gcode =
between_objects_gcode =
cooling_tube_length = 5
cooling_tube_retraction = 91.5
default_filament_profile = ""
default_print_profile =
deretract_speed = 0,0
end_gcode = M104 S0 T0 ; turn off extruder 1\nM104 S0 T1 ; turn off extruder 2\nG91 ;use relative coordinates\nG0 Z2.0; lift nozzle\nG90 ;use absolute mode\nG28 X Y;\nM84 ; disable motors
RE: Bug or change Post version 2.8.1
have you considered raising this matter on the Prusa Slicer Github, where the developers manage issues?
regards Joan
I try to make safe suggestions,You should understand the context and ensure you are happy that they are safe before attempting to apply my suggestions, what you do, is YOUR responsibility.Location Halifax UK
RE: Bug or change Post version 2.8.1
Not sure how you ever got a bed size of 1800 as theres been an open issue about the max size being limited to 1200mm since 2021. https://github.com/prusa3d/PrusaSlicer/issues/6072
That predates 2.8.1.
Given that the multiple bed stuff came in right after 2.8.1 I'd say that they started using the 1200 limit in more places.
RE: Bug or change Post version 2.8.1
thank you for your replys, I was not sure if the best way was to post it here first before going to github but I will post it over there as well.
I would tend to agree with you @neophyl, we have always used the same profile and never had an issue with it functioning.
I would guess there is some check or balance that was added that is triggering the error.
I would guess most of our customers do use Prusa mostly for the idex side of things, I am more than a little shocked we have not come across this before.