Custom G-code file extension (.hvs) in output_filename_format not maintained, replaced with .hvs.gcode

[marcoburato]

Version

1.41.0+

Operating system type + version

macOS 10.13.6

Behavior

• Describe the problem
  When the parameter output_filename_format contains a custom file extension, for instance .hvs, the "save as" dialog will still force the extension to be .gcode, resulting in a file named filename.hvs.gcode.

• Steps needed to reproduce the problem

  • In Printer Settings > Output options > Output filename format enter [input_filename_base].hvs
  • Slice a model and click Export G-code...

• Expected Results
  The dialog should use a filename like my_model.hvs.

• Actual Results
  The dialog uses a filename like my_model.hvs.gcode.
  Note: even if you delete the .gcode, it gets added again when saving the file.

Is this a new feature request?
No

[bubnikv]

What is the .hvs extension? I suppose the input field expect you to give the file name without the extension. Why do you want to change the extension?

…

On Tue, Sep 11, 2018 at 1:19 PM Zmaster ***@***.***> wrote: Version 1.41.0+ Operating system type + version macOS 10.13.6 Behavior - *Describe the problem* When the parameter output_filename_format contains a custom file extension, for instance .hvs, the "save as" dialog will still force the extension to be .gcode, resulting in a file named filename.hvs.gcode. - *Steps needed to reproduce the problem* - In *Printer Settings > Output options > Output filename format* enter [input_filename_base].hvs - Slice a model and click *Export G-code...* - *Expected Results* The dialog should use a filename like my_model.hvs. - *Actual Results* The dialog uses a filename like my_model.hvs.gcode. Note: even if you delete the .gcode, it gets added again when saving the file. *Is this a new feature request?* No — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1221>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFj5I2uaXhrtnllylqr_k2QfGAuQjoEIks5uZ5xSgaJpZM4WjGqn> .

[marcoburato]

My 3D printer, a Cubicon Style, requires files with that extension (plus some custom G-CODE), it won't see .gcode files. The .hvs extension is probably named after the manufacturer (HiVision Systems).
So, having Slic3r save the output file with the correct extension avoids having to rename the file manually.

The default value for that field is [input_filename_base].gcode, so one would expect that changing the file extension is possible.
I suppose the easy fix would be to add the hvs extension to FILE_WILDCARDS["gcode"], although this doesn't address the generic case.

[bubnikv]

The upcoming Slic3r 1.42 alpha will maintain your custom extension.
Closing.

[marcoburato]

@bubnikv This issue is now happening again on 2.6.0. Can you reopen the ticket?

[marcoburato]

Just confirming this was indeed fixed in 2.6.1. Many thanks.