Sounds like a #humanfactors problems to me. I see that #mainsail is #opensource, maybe they would appreciate a contribution to change the default on the confirmation dialog or to change the icon?
Months ago, I saw youtubers insisting that Creality was going to start honoring open source license terms soon after actually shipping the K1 and K1 Max products to the general market. Did that ever actually happen? #3DPrinting#openSource
They took a month or so to actually post the firmware and give us rpot access to the printer. Before that, you basically had to use #CrealityPrint and their config, where they, for example, got the input shaping wrong.
They then posted the firmware, and you could easily get #Mainsail and #Fluidd. Then it happened that nozzles were crasging into beds, and they removed the firmware.
I first K1 had a problem. I rooted it, but something was wrong. So I swapped it for a new one with the supplier. Now that firmware isn't available anymore. So I had mainsail and Klipper on my first K1, but not on my second one. They are taking their sweet time to release it now as well.
So, nothing new, actually. Like the printer. Haven't had a failed print, and the quality is amazing, but the software side sucks.
That's the problem. The #Creality#K1 stock doesn't run #Klipper as we all know and love it. They run #CrealityOS. So naturally, it has no documentation, and you have no Idee what macros exist or what you can do with #Gcode.
Wirh the rooted verion, you can use #Mainsail and #Fluids, but naturally, the updates are broken, and you are dependent on Creality. But at least I have access to Klipper Macros and can also make my own. I can also correct the mistakes they made with the config.
@koz has the Qidi, and did have a better experience than me initially, but did have to change more in the Klipper config.
The fact that you paid for your 3D printer doesn't mean that any of that money reached the developers giving their time to create and maintain the software it runs.
The rule of thumb is that if you use free open-source software, please consider sponsoring the developers and maintainers of said software.
Blows my mind, that manufacturers refuse to run #KlipperScreen. All these #Klipper printers are running their own UIs.
This is just stupid. As I then can't control my entire printer as promised. I can change the config, choose between #Fluidd and #Mainsail, and have root access, but I am stuck with their bad design choices for the display.
Dear manufacturers, if you decide to re-invent the wheel. Please do so by keeping the same shape. That shit needs to be round.
I just tried #OrcaSlicer for the first time, I've just not had time to test it until now.
Because it was based on #PrusaSlicer, #SuperSlicer, and #Slic3r, I hoped that I could just import my PrusaSlicer config, but could not because it expected a .json file and PrusaSlicer outputs a .ini, but I might have done this incorrectly.
So I configure a "Generic Klipper setup" and copied the values by hand by comparing settings with my PrusaSlicer setup and a bit of experience and intuition.
My first resulting print, a custim part by me compared to the PrusaSlicer, was worlds apart. The finish was greatly improved with bridges requiring no supports, however it did print a bit slower, 28 minutes instead of 18 minutes, but this might still just be speed settings.
I like the UI, although I am more used to PrusaSlicer, and I especially love that I can access #Mainsail and #Klipper from within the app.