Prusa slicer 2.6.1 Bug  

RE: Prusa slicer 2.6.1 Bug Update

I'm using prusa slicer 2.6.1 and I've encountered a very serious problem. I set a color change with M600, then later I eliminated it from the slicer, returning to a single color, but I noticed that the printer continued to ask for a color change, so I checked the gcode with notepad and saw that in reality it didn't had deleted it, it remained in the gcode?????, I was forced to delete it manually. The BUG is serious as this problem comes back to any stl file to be processed later, once you set up an M600 even if you delete it it actually leaves it in the gcode in any subsequent file. This is a really serious problem. I uninstalled the version. 2.6.1 and reinstalled 2.6.0 and the problem disappeared, so I'll go back to the previous version, 2.6.0. And obviously I won't install the version. 2.7.0. In my opinion, we should pay attention to updates, which should improve and not worsen what was working well. I would like to have information on this matter, for possible exchanges of information. Thank you.

RE: Prusa slicer 2.6.1 Bug UPDATE 2 SORRY SORRY

Sorry for this third message but I realized that version 2.6.0 also has the problem of leaving the M600 in the gcode despite it being deleted by the slicer. I realized this problem late because I don't often make two-tone prints. I'm sorry about the previous messages, but unfortunately I wasn't able to delete them. Is it possible that I'm having a problem like this? I don't know if older versions also have this problem. I don't understand  something? Can anyone help me understand? Maybe it's me who's wrong? Thank you.

RE: Prusa slicer 2.6.1 Bug

Can you post the zip-compressed 3mf file? I've never seen this happen so I was curious but I can't replicate it. Created a project with a color change, exported GCODE. M600 in the code as expected. Then deleted the color change, exported the GCODE file again, no M600 in the code—again, as expected. 

RE:

I can't understand, now I have downloaded version 2.7.0 alpha1 and I have the same problem, with the .3mf file the M600 command remains even though I haven't set it in the slicer, I loaded another random stl file and here too even though I haven't no color change is set, M600 is present, I'm going crazy, it seems to happen after a first setting in the slicer, then even if you delete the slicer it leaves it in the gcode, I don't really understand.

RE: Prusa slicer 2.6.1 Bug

Without the 3mf file we can't do much more than guess...

RE:

I'm going crazy, I closed Prusa slicer 2.7.0 alpha1, I reopened it, took any stl file saved the gcode NO M600, OK, same file with M600 YES, OK, the problem seems to occur only with the .3mf file from me posted, but previously I also encountered the problem in other stl files, but now it seems to work fine, except for the .3mf file. With other versions, the problem arose even with different files. At this point I hope it continues to work well, and a doubt arises in my mind.....maybe when I saved the .3mf work plan was it also set to M600? 

mmmm thinking about it.... but it asks for the thread change immediately at the beginning of the print while I had set it to 2mm in height... it's a mystery...

RE: Prusa slicer 2.6.1 Bug

Change color position is set at 2mm in height....but in slicer is present at the start print. 

RE: Prusa slicer 2.6.1 Bug

Height 2mm should be here, (to see attach), M600, shouldn't it be displayed here? I apologize if I'm wrong.

RE: Prusa slicer 2.6.1 Bug

Another file stl set M600 at 2mm height and here is ok 

???????????

RE: Prusa slicer 2.6.1 Bug

And for to end....same file with NO M600 set, is OK

?????????

RE: Prusa slicer 2.6.1 Bug

I don't know. Looks like somehow a color change slipped in at the very beginning. You can see it if you set layer height and first layer height to 0.1mm. The color change now shows in the slider. How it happened, who knows, but it looks like your other files are okay now. 

RE: Prusa slicer 2.6.1 Bug

By the way, this is a really nice model. I just printed a handful myself 🙂

RE: Prusa slicer 2.6.1 Bug

True, it is a nice model but the tolerances of the lid mechanism with those of the knob are not precise, to print it well I had to make a small modification, otherwise the lid was fine but the knob was not. However, the mystery remains as to why there are sometimes problems with the M600. Thanks for the help but I hope that someone reads these messages perhaps to try to improve a program that in my opinion is among the best ever, it would be enough not to make what is already good worse. A greeting. 😊