Export file name missing version number

[jpmcgillivray005]

Hello, first off let me apologize if this is not in the right place. First time on the forum here. 

Anyways, I opened fusion today and when I exported the file I was working on the v## was not auto populated in the file name. Usually it is "file_name v21" for example but today it's just "file_name". Saving then does try to overwrite the previous file so it's not as if it's just hidden in the UI but still saving the file with the version. I had a pending fusion update so I applied that and restarted and it is still the same. Is this a bug or perhaps a setting I somehow disabled?

I am on version 2605.1.18 on Windows 11

[lance.carocci]

Hi @jpmcgillivray005, this was removed with our November update. We've had mixed feedback over the automatic inclusion of the file version tag, in particular because it has varying degrees of significance to users receiving the file - for some it was meaningless, for others it meant a significant product revision. For this reason, Fusion files are slowly shifting away from the "version" terminology within file saving operations so that users can determine this naming themselves.

[jpmcgillivray005]

Hmm. Well at least it's not a bug then. I am definitely in the camp of wanting this feature. I make a lot of file revisions while 3d printing. Figuring out tolerances and fine tuning models takes many revisions sometimes so manually entering this while not catastrophic, is annoying. I would love this to be something that is configurable instead of just gone. A checkbox in the settings panel type thing.

[grahmart]

Wanted to say i also wish there were options to confirm it instead of just gone.  I do a lot of reverse engineering from 3d scans and the automatic version numbers help me keep track of multiple rounds of changes

[sottis]

I'm with jpmcgillivray005 - I really depend on the version names when 3d printing - how about a preference se...

[hamocean]

The automatic version naming feature was incredibly useful and a huge help with file management. It would be a shame to have to create a new version every time I export. Couldn't we go back to the old feature? It feels like losing a very intelligent assistant.

[qorwkwkd20]

I'm with jpmcgillivray005 too. Automatic version naming was very convenient. Instead of just gone, please put them in the preference, on and off. 

I thought it was bug but it was not... 

[bachofner.dom]

I Absolutely want this feature back too!

or at least make it a setting...

[lance.carocci]

To elaborate, version in Fusion currently refers to little more than how many times one has clicked save - it is not an actual reflection of version control, which is currently referred to as a milestone.

There is certainly potential for more granular control over what information is appended to exported file names in the future.

[hamocean]

This has nothing to do with version control, but even a simple countdown feature that memo how many times you've saved would be helpful for my personal file management style. If frequently export files for printing with micro edits, a simple naming feature that tells you how many times you've saved them is incredibly useful.

I hope to see the naming feature you mentioned added in the future.

[grahmart]

We know.  A search of "version control" shows no results until your own post and replies to it.  

To elaborate, I use both features.  Milestones are actual version control and anything that leaves me to go to a supplier or the floor has a milestone.  

Versions are just used to track back and forth between myself, other engineers or other software. Also the whole dismiss it as little more than a save count is looking at it from the wrong perspective.  The correct perspective is if nothing has changed, there are very few reasons to save it. So a save count is also a change count

[escalade_590]

It’s not a setting you disabled. Fusion stopped auto-appending the “v##” to exported filenames after a recent update. They changed the behaviour so the version number only shows inside Fusion’s data panel and history, but it’s no longer added to the export name by default.

Right now there’s no toggle to bring that behaviour back, so what you're seeing is normal for 2605.1.18. A few other users have mentioned the same thing, so it looks like a change on Autodesk’s side rather than anything wrong on your end.

If you need versioned export names, you’ll have to add the “v##” manually for the moment.

[infoLRDXL]

I'm also loved the feature while it is (was) very easy for versioning.
Why not a simple checkbox in somewhere so people can decide for themselves if they want the versionnumber in the export file or not?

[lance.carocci]

The file version number as you know it is slowly being replaced across the application. Some newer Fusion users are already using this system - they have no version to append already. Instead, the system differentiates changes based on date, with "Version" representing what you know currently as "Milestones."

Regardless, I understand the desire and value of file export naming conventions, but the previous system had outlived its relevance.

[Sebastian-Frankl]

Das gefällt mir nicht. Ich arbeite mit mehreren Kollegen zusammen und für uns sind die Versionsbezeichnungen sehr wichtig!

Kann man nicht eine Einstellung hinzufügen, dass man das selber aussuchen kann. Ich möchte das immer anzeigen 

[jpmcgillivray005]

I would argue it hasn't exactly outlived it's relevance when there are a bunch of people here saying otherwise. grahmart really put it best. It's incredibly useful as a detailed change log and far more than just "a save counter". I really hope we are not losing the ability to track the changes between each save.

[jm.10]

Be aware as well that the version number appended to files always had a bug where it sometimes would be wrong and not match the source file. They need to bring it back and fix that bug.

Of course we know bug fixes are minimum priority for Fusion, so if they do bring the feature back it'll still have the bug. And we also know user feedback goes nowhere around here, so my guess is that it's never coming back even if every single user demanded it.

[procratstinator]

I just got this change. 

This was a very important part of the workflow for me, very useful for rapid prototyping with a 3d printer.

Would be very nice to have this as a setting, or at least some alternative that gives unique file names for each iteration of the file on export.

[wmH8XR3]

Outlived its relevance?  Clearly not for some of us.  I ask you to please when you make a change like this, at least make it an option so those of us that depend on this "feature" can still have it.  This sort of thing feels like a slap in the face, FUsion can do whatever and the customer opinion doesn't matter.  Similar to the change with configurations.

[lance.carocci]

Outlived its relevance in the context of Fusion data management and storage for tracking file revisions. Fusion has since evolved to differentiate between incremental file changes and significant revisions or modifications to the original design. You can read more about the distinction here. Namely,

If you are not using collaborative editing, Fusion tracks iterations as milestones and versions. If you are using collaborative editing, Fusion tracks iterations as versions and changes

Collaborative editing is the standard data experience for new users, and is slowly being rolled out to existing users. What you are calling "versions" that are today represented by "v1" will be called "changes" represented by a date and time. Moving forward, there will no longer be a "v#" field in the file metadata from which to pull this value, but rather a timestamp.

In the context of bringing this back to the Export workflow, that means what used to be exported as "Model v1.f3d" would instead be something like "Model 2025-12-31.f3d" (this is just an example, as there are numerous ways users may want to represent timestamps).

This sort of thing feels like a slap in the face, FUsion can do whatever and the customer opinion doesn't matter.  Similar to the change with configurations.

Keep in mind that what may feel like an arbitrary change is generally based on customer feedback that may be of a different opinion than your own. We try to strike a balance or provide options where possible. While "versions" may not be returning to the Export dialog, that doesn't mean something else cannot take its place to serve a similar purpose.