A quick post processing script to convince the outdated version of moonraker that the K1 uses that files sliced with OrcaSlicer are actually from SuperSlicer.

Simply adding the comment to your custom gcode worked for local instances of fluidd and mainsail, but not for the K1's screen and Creality Print.

Additionally, the version of moonraker that the screen uses is coupled into a binary seperate from the root filesystem of the K1, so modifications to moonraker were not immediatly available without reverse-engineering the binary.

Instead, this is a quick post processing script that can be used in OrcaSlicer directly to trick moonraker for the time being.

This change does not require the K1 to be exploited.

1. Download k1-thumbs.py from this repo and place into your root OrcaSlicer directory, next to exe file.

2. In OrcaSlicer, in Others -> Post-processing Scripts, add the following code edited depending on your system. For example, with Windows:

C:\Windows\py.exe '<path-to-orcaslicer-folder>\k1-thumbs.py'

3. GCode sent from OrcaSlicer should now show the thumbnail on the K1's screen and other applicable Creality locations.