GCodeProcessor toolchange bug found with benchy in Feb, still around
Reporting a bug in the latest linux appimage RC3 It looks like a problem found in February slicing benchy, I'm not slicing benchy but a single filament nothing too complicated thing The first assert I've seen for years and doesn't seem to be fatal, the last two are fatal, I'm going back to beta 3, if I can find it. (prusa-slicer:16320): GLib-GObject-CRITICAL **: 23:06:59.905: g_signal_handlers_unblock_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
[2021-03-23 23:08:57.041621] [0x00007f9106ffd700] [error] GCodeProcessor encountered an invalid toolchange (Tx).
[2021-03-23 23:08:57.041733] [0x00007f9106ffd700] [error] GCodeProcessor encountered an invalid toolchange (Tc).
i965: Failed to submit batchbuffer: Input/output error
I'm on pinterest as timcor 💡
RE: GCodeProcessor toolchange bug found with benchy in Feb, still around
This is not the place to report bugs. It’s a user to user forum. To get your bug report before the eyes of the developers, you should file a bug report on Prusa’s GitHub site.