prusa3d / PrusaSlicer

G-code generator for 3D printers (RepRap, Makerbot, Ultimaker etc.)
https://www.prusa3d.com/prusaslicer/
GNU Affero General Public License v3.0
7.62k stars 1.92k forks source link

Build Plate model changes at random #5521

Open Area5142 opened 3 years ago

Area5142 commented 3 years ago

Version

PrusaSlicer version 2.3.0 rc1 g2fa582802 and RC1

Operating system type + version

Linux Mint 19.3 x64

3D printer brand / version + firmware version (if known)

Not relevant - same for all printers.

Behavior

Correctly shown build plate: Screenshot from 2020-12-19 16-55-55

Generic build plate shown: Screenshot from 2020-12-19 16-55-12

I noticed that the printer profile is different on the two screen shots but that is not important as this happens with the same profiles and different physical printers too.

Is this a new feature request? No

Project File (.3MF) where problem occurs

Not needed.

lukasmatena commented 3 years ago

I can see from the screenshots that there are at least two Printer profiles, "Original Prusa SL1" and "Original Prusa SL1 - JOH". What is the difference between them? Are you sure that both have their print bed model/texture defined?

Area5142 commented 3 years ago

The changed profile on the first screen shot was a standard profile from 2.2.0 with begin and end g-code changed to stop nagging me with newer firmware and lift the extruder to min 100 mm after a print is finished. No changes to printer bed image/model.

The missing/changed print bed also happen with the latest profiles:

Here the SL1 standard profile loaded correct with empty print bed: 1 Screenshot

Here the same profile in the same session after switching between unmodified standard Mini+/MK3+/MMU2 profiles a couple of times: 2 Screenshot

It seems to be a random error, sometimes the print bed is shown wrong when PS is just started other times it happens when I just change profile between the different printers: SL1/MK3S+/Mini/MK3S+MMU2S printer.

lukasmatena commented 3 years ago

Thanks for the clarification. I did not reproduce it on my system, though. Did you have these issues with 2.2.0 release?

Area5142 commented 3 years ago

Have not seen this problem in version 2.2.0.

Just tried to provoke the error in version 2.2.0, but can't get it to fail.