Skip to content
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

Closed
nerocide opened this issue Mar 13, 2018 · 8 comments
Closed

Output FileFormat #791

nerocide opened this issue Mar 13, 2018 · 8 comments

Comments

@nerocide
Copy link

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
image

Any ideas about this behaviour?

@jneilliii
Copy link

I can confirm I have this issue as well with latest 1.39.1 windows x64 release.

image

@jneilliii
Copy link

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.

@jneilliii
Copy link

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.

@jneilliii
Copy link

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.

@nerocide
Copy link
Author

nerocide commented Apr 7, 2018

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 --
it had work like a charm...i guess i've to test more.

@bubnikv
Copy link
Collaborator

bubnikv commented May 16, 2018

I was able to reproduce it.

bubnikv added a commit that referenced this issue May 16, 2018
The preset names have to be set at the PlaceholderParser
before querying Print for a recommended file name.
@bubnikv
Copy link
Collaborator

bubnikv commented May 16, 2018

Fixed with 0b4a61a
It will be part of the upcoming beta.
Closing, please reopen if you find out it does not work with the 1.40.0-beta. Thanks.

@bubnikv bubnikv closed this as completed May 16, 2018
@nerocide
Copy link
Author

Thanks @bubnikv, just compiled version_1.40.0-alpha1-9-g6d98c2b1 and it works as expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants