-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Output FileFormat #791
Comments
I just did a little testing and by changing the name, saving the print settings, and then putting it back and saving the print settings again, it appears to be working again. Until I restart the program. Once I restart the program the error returns. |
Some additional information. This seems to only be an issue if there are more than one filename tokens. If you only have 1, then restarting the application does not make the error reoccur. |
Acually looks like it might be a specific issue with [filament_preset} token. I tried a couple of different ones, like [input_filename_base][hour][minute].gcode and that works without issue as well. |
As far as my last build from master branch (version_1.40.0-alpha-285-gc6623bb2), it works like a charm now. Any confirmation? Edit -- |
I was able to reproduce it. |
Fixed with 0b4a61a |
Thanks @bubnikv, just compiled version_1.40.0-alpha1-9-g6d98c2b1 and it works as expected. |
Version
I compiled Slic3rPE v1.39 from repo (tag version_1.40.0-alpha-196-g83a2d2af)
Operating system type + version
Linux kali 4.14.0-kali3-amd64 #1 SMP Debian 4.14.17-1kali1 (2018-02-16) x86_64 GNU/Linux
Behavior
at least the following variable names can't be used in output filename forrmat [print_preset] [filament_preset] [printer_preset]
Steps needed to reproduce the problem
In print settings > Output Options > Output filename format add the following string [input_filename_base][print_preset][filament_preset]_[printer_preset].gcode
Slice your STL and export as gcode.
This will raise the following error
Any ideas about this behaviour?
The text was updated successfully, but these errors were encountered: