← All ideas
  • Published 28 Mar 2025

Save File / Output in Properties Editor: Split Name and Path Fields

In the export field (in my example for collections but this could also go for the render file name dialog) the fields should be split into two separate fields. Reasons:

  1. The file name field can get very long and you always have to scroll to the end of the line to input a new file name.
  2. If you miss the file ending, Blender assumes you wanted to use another subfolder and adds this but then also names your new files with numbering only.

Benefit: Your File Dialog is much more failsafe for filenaming. It's easier to see at a glance and could offer further enhancements like wildcards in the filename - for example a certain numbering or suffixesbased on used camera in the scene, name of the collection etc.

Example from Properties Tab > Output > Output Tab alt text

100%

Development Status: Open

Upvote 4 Downvote 0
SpookyDoom
28 Mar 2025

4 Comments

Lauloque

I don't recognize this GUI, is that from an addon?

The default FBX exporter (and AFAIK all exporters we have out of the box) just open the file dialog with two different entries for the path and name, and export options in the sidebar:

demo pic

SpookyDoom Author

That's not an addon. This is also not relevant for the export dialog . There you already have the path and filename separated by default because it's ... well it's the export dialog. The screenshot is from the collection exporter that's new to Blender. But it's also reflected in the render file output in the Properties Tab > Output > Output for example. Same thing. You have path and filename in one line.

Lauloque

It would be nice to clarify your proposal then:

  • Specifically address the Collection Exporter in the Properties editor instead of "file export dialog" which most user would interpret as what I showed above.
  • Use a screenshot that put it in its context. The Properties Editor's tabs would make it way clearer.
  • Why not enlarge the scope of the proposal to other file path inputs, such as in the render output.

The best way to maximize your chances of seeing your proposal into development is to make it as clear and comprehensive and bumpless as possible, so that any dev passing by can see and understand what it's all about and assess its feasibility with no need for extra back and forth.

SpookyDoom Author

I agree with some of your points, but I'd also apreciate if you leave an upvote as well if you agree with it.

1