-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[2.6.0 Alpha 2] Crashing Slicing at 90% #9550
Comments
Possibly same as #9470 - was OK when changing to T0 |
This is indeed the same as #9470. One thing the two issues have in common is "TIMELAPSE_TAKE_FRAME" line in custom G-Code. This line is confusing the CoolingBuffer, which mistakes it for a toolchange and crashes after failing to read the new tool number. 2.5.0 did not crash, but the CoolingBuffer was probably fooled as well. I am unable to tell if it was observable or not and how. The issue will be fixed in the next release, thanks for reporting this. |
Thanks for the feedback @lukasmatena |
I have the same issue when slicing with T1 or T2 or T3. The default print head T0 is ok. |
Same issue here! |
Please, wait until 2.6.0-alpha4 is released and retest after that. The original issue reported by @psyvision should be fixed there, if the rest of you indeed report the same problem (and not a different one that looks the same), it will be gone too. |
@psyvision and others please can you retest the issue with the new alpha? |
@kubispe1 @lukasmatena Alpha 4 has resolved the issue for me, many thanks team! |
@psyvision Thanks for the update. Closing. |
Description of the bug
When slicing a fairly simple model PrusaSlicer is crashing at 90%. I have read some other reports here which suggest it is either supports or sequential printing causing the issue. This project has neither enabled.
Project file & How to reproduce
3MF:
Enclosure - Part 18.zip
Checklist of files included above
Version of PrusaSlicer
2.6.0-alpha2-win64
Operating system
Windows 10
Printer model
RatRig VCore 3 Tool Changer
The text was updated successfully, but these errors were encountered: