-
Notifications
You must be signed in to change notification settings - Fork 336
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trying to export Gcode with Creality K1C #5557
Comments
Try change to {input_filename_base}{filament_type[0]}{print_time}.gcode |
Thx for the reply. For me, i cannot input this in BambuStudio as this data field is not present, but i can change this value in OrcaSlicer. The weird thing is that in OrcaSlicer, the value is {input_filename_base}{filament_type[initial_tool]}{print_time}.gcode and it's working! |
Try to turn on advanced view in Bambu |
Advanced view is activated, but this line does not show up like in Orca Slicer. I even tried to switch language, without result. |
@Draketornado It's on the develop mode . You can go to "preference" page to enable develop mode and then you will see the lines |
Bambu Studio Version
1.10.1.50
Where is the application from?
Bambu Lab Official website
OS version
Windows 11
Additional system information
No response
Printer
X1C
How to reproduce
My dad is owning a Creality K1C and he tryed to export a Gcode. Will not work for the K1C, but it works for other printers.
Error:
Verarbeitung der Vorlage filename_format fehlgeschlagen.
Parsing error at line 1: Not a variable name
{input_filename_base}{filament_type[initial_tool]}{print_time}.gcode
I also tryed on a 2nd computer, the result is the same.
Actual results
Error: Verarbeitung der Vorlage filename_format fehlgeschlagen.
Parsing error at line 1: Not a variable name
{input_filename_base}{filament_type[initial_tool]}{print_time}.gcode
Expected results
Should open a window to safe the gcode
Project file & Debug log uploads
Tryed with a lot of files, never worked
Checklist of files to include
The text was updated successfully, but these errors were encountered: