More usability issues.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I am now running the version with the native support for the trackpad, I haven't seen any further issues with it stopping responding, but I did have it seemingly stuck in rotate, I ended up having to quite because I couldn't release the rotation.
There are a few more things that are in the "annoyance' category. Apologies if I've missed some way or remedying these, but I've searched and I can't really find answers beyond "this is how it works".
1.) The Versioning. I've had this conversation privately with somebody in the Fusion team who agrees with me that the way it works now is not right, and it makes dealing with manufacturing files much more hassle than it really should, it essentially boils down to this.
"Saving is NOT a versioning trigger".
I don't know why Fusions :"Save" operates as a versioning trigger, it's wrong. a save is nothing more than a save, you're mid process, you go to lunch, you go home, you hit save at every opportunity because you've had 40+ years of dealing with software that crashes, so you save frequently so you don't lose anything more than a few minutes worth of work.
Versioning is completely different to versioning, versioning occurs where there's some change to a design that is going to go into production and there may be consequences for other parts which also need to be modified, a versioning should be an explicit instruction from the designer, Fusion cannot possibly know what or where a versioning operation should occur.
At the very least, allow us to disable the silly pop up window, I don't use it, I suspect there's a fair proportion of your users who simply hit "OK" without changing anything, because it's a save operation, not a versioning operation, the dialog makes sense when versioning and I'd even go as far as to say that for a versioning operation, that dialog is not very useful, if you're versioning you probably have a lot more information that might be formatted in a specific way to indicate a change order.
An analogy is me working on the code on my open-source project, I use GIT for versioning, so I work away on a feature branch, every save in my IDE doesn't perform a versioning operation, it simply saves the file, I can see in GIT what has changed since the last commit, but crucially the save does nothing.
As I work, I often will commit milestones or commit if I'm about to try something that might cause me big problems, by committing at that point I can try the code and if it doesn't work, I can just roll back.
These commits are explicit though, it's my decision on whether to commit or where to commit or how often I commit.
2.) The "Versioning" again.
And leading on from point 1 on versioning is the fact that you append this "save number" (it's not versioning!) to the manufacturing outputs, this makes it difficult to simply update say a 3D printing project because I have to change the names of the files to match the previous ones in the project so that I can simply click "Update" in my slicer (Prusa Slicer), as it stands this save number breaks that and I have on a number of occasions printed out the same model as the previous one because I forgot about the "save number", so when I hit update, the model didn't change.
3.) More "versioning" - that "note" dialog.
The note dialog on save is so annoying I'm now contemplating writing a small application that will poll in the background looking for a new window to appear in fusion with the correct title so that I can auto-dismiss that dialog, there are times I've hit save and walked away, only to come back ti be greeted by that dialog.
3.) The change of default format to 3MF.
When the changes were made recently to make the STL export appear as "Save as Mesh", the default now is :3MF and it always seems to default to "One File", these settings don't work for me, prusa slicer uses 3MF as the project format, and there are consequences regarding it importing 3MF because it will reset the settings as these are in the 3MF files that it uses and saves.
This is not a problem when using STL, and I can quite happily use an STL file without it changing any settings underneath me.
I'll concede this behaviour is in a third party program, but I'd like fusion to remember on a project by project basis to store the settings when you output a mesh, so it would remember the format and also if it's one body per file or multiple files per bodies.
I know I sound like I moan a lot, and I appreciate the way I work is going to be different to the next person, and the one after that and so on. I'm trying to be constructive, because at the heart of it, I LOVE FUSION. What I don't like is some of the idiosyncratic ways in which it works, I think there's room here to make minor changes that will actually have massive gains in how people use it.
I use it most days, but as a maker, I'm not using it for commercial purposes (although as I've mentioned previously, I pay the fee because it makes it easier for me to use with projects) and the things I mention are things that I fight with every single session, on the whole it's such a good program and I think it's pretty much a bargain at the price you can get a license for.
