Removing any of the Gcode tabs and/or tokens would greatly reduce the efficacy of having all kinds of automated settings for retracts, tool changes, materials, etc be able to be implemented and make multi extruder printing more difficult. I agree that some better tutorials on how to use these would make them more useful for more people. This would be detrimental to the environment I have made for myself when using Kisslicer. Admittedly, I don't have a whole lot in any of them but I do use several to change specific M settings and also trigger routines/macros in my firmware (RepRap FW on DuetWiFi). I do use several of the tabs along with FW retract and FW based scripts fairly extensively: https://www.duet3d.com/forum/thread.php?id=3121#p28273funBart wrote:Maybe I missed some, but:
...
-too much gcode tabs for printers
-unclear and not explained tokens for the gcode tabs. They are now only for the happy nerdy few. Maybe they are handy, but not without a good explanation.
-that said: all unclear and unexplained features are nice for the nerdy developer himself, but if unclear for the average user, why bother? KS shouldn't depend of nice people as Davide and Michael!...
I also wanted to note that my request to have the Destring triggers applied to G10 and G11 was not added to the list. As it is right now (when G10/1 is selected in the "Mark Path Start/Stop" dropdown), every travel movement gets a G10 and G11 (retract and unretract) even if the travel distance is tiny (which is not ideal). I want an option in the "Mark Path Start/Stop" dropdown of the "Firmware" tab to apply the "Destring" triggers (Min Jump and Trigger) to filter out unnecessary G10/G11 retracts. Could also be applied to the M101 and M103 option as well. When this option is checked, rather than writing the usual "Destring/Prime" section of the Gcode a G10 or G11 is written instead and G10 and G11 are not written at every extruder start/stop then (only the ones with significant travel following). Does that make sense? This would greatly help improve my printing efficiency and reduce the likely hood of flattening out filament or stripping it due to retracting and unretracting over the same section too many times.
One thing that I do like about Sli3r and would like to see changed here is the interface that allows you to change settings on a per mesh basis. I know we now have the option to "Lock Paths" but this is fairly limited in terms of how using different settings for different regions of the same part. It is also a bit clunky and requires a specific order of operations if you want to tweak a model that you sliced in the middle of two others. Having a menu of settings that are available to change for a mesh and then generating a list of the ones you have changed similar to Slic3r would be preferred I think. I did try using Simplify3D for some time but there were many things about it that did not jive well IMO and the multiple process approach felt like a bit too much.
I would happily pay a fee for the new version to support development and documentation/tutorials. I love this slicer and can't wait to see it grow further and more refined.