https://github.com/x86-39/3d_printer_configs_k1_max

PrusaSlicer configurations for the Creality K1 (Max)
https://github.com/x86-39/3d_printer_configs_k1_max

Last synced: about 4 hours ago
JSON representation

PrusaSlicer configurations for the Creality K1 (Max)

• Host: GitHub
• URL: https://github.com/x86-39/3d_printer_configs_k1_max
• Owner: x86-39
• License: unlicense
• Created: 2023-09-21T17:09:19.000Z (about 1 year ago)
• Default Branch: main
• Last Pushed: 2024-10-23T00:36:33.000Z (28 days ago)
• Last Synced: 2024-11-08T10:54:52.252Z (11 days ago)
• Language: Jinja
• Size: 112 KB
• Stars: 4
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# prusaslicer_creality_k1

PrusaSlicer configurations for the Creality K1 (Max)

## Generate PrusaSlicer print configs

I still include these in the repo bcs having an easy history of changes is nice. But you can generate them yourself if you want to change the settings.

The print configs in the PrusaSlicer folder are generated from the `generate.yml` playbook. Why Ansible? Because it's my golden hammer, next question. It takes a base config in `roles/generate_print/templates/` and generates a config for each possible permutation of variables such as speed, toughness and precision. You can then use `./copy-to-prusaslicer.sh` to copy the generated configs to your PrusaSlicer config folder.

Is this the best way to do it? No definitely not, but it works for me and I'm stubborn as fuck and will use Ansible when I can.

```

ansible-playbook generate.yml

```

Also, the playbook is a mess. I definitely could've procedurally generated it, but I was tired and just wanted it to work and don't think anyone is gonna download these anyway!