Prusaslicer 2.6.1 Filenaming failure, U.S. keyboard.
I want to add weight to my filename. I found the total_weight variable. I found how to add it to the Output File Name without getting an Error. The problem is the filename variables are not resolved when I save the G code. Even after reseting the Output File Name. the problem persists. It names the file as if the variables are not resolved. Is it something I am doing or a bug. Is it not setup for U.S. Keyboard? Example of the name when trying to save the G Code file.
Best Answer by vhubbard:
Follow up, working in 2.7.4 as documented.
RE: Prusaslicer 2.6.1 Filenaming failure, U.S. keyboard.
Excuse the lame question, but I‘ve searching the option for that filename pattern in the slicer for days… Where can one define that damn pattern?
RE: Prusaslicer 2.6.1 Filenaming failure, U.S. keyboard.
This is the knowledge pagefor the variables available in the slicer.
RE: Prusaslicer 2.6.1 Filenaming failure, U.S. keyboard.
Where can one define that damn pattern?
Print Settings→Output Options. You have to be in Prusaslicer's Expert mode to see it.
Formerly known on this forum as @fuchsr -- until all hell broke loose with the forum software...
RE: Prusaslicer 2.6.1 Filenaming failure, U.S. keyboard.
Print settings... OK, I wouldn't even have looked there. I assumed it would be in the preferences, which it isn't. 🙂
Thanks for the information!
RE: Prusaslicer 2.6.1 Filenaming failure, U.S. keyboard.
@vhubbard: From the screenshot it looks like you're trying to add the weight when Windows pops up the file dialog box. But Windows knows nothing about those variables. You'll have to add it to the output file name template.
Formerly known on this forum as @fuchsr -- until all hell broke loose with the forum software...
RE: Prusaslicer 2.6.1 Filenaming failure, U.S. keyboard.
I did add the variable with the template in PrusaSlicer. I did not edit the name it created. The name was created as shown in my screen capture. That is the problem. I can't figure out why it is doing this. Even the print_time, that I did not change is coming out that way. Slicer 2.6.1, windows11. U.S. keyboard
RE: Prusaslicer 2.6.1 Filenaming failure, U.S. keyboard.
Curious. The only time I see unresolved variables in the proposed file name is when I try to save before the slicer has finished slicing.
You may want to upload a 3mf project file (zipped, or the forum won't accept it) to see if anyone can replicate the issue.
Formerly known on this forum as @fuchsr -- until all hell broke loose with the forum software...
RE: Prusaslicer 2.6.1 Filenaming failure, U.S. keyboard.
Follow up, working in 2.7.4 as documented.