Stop Accepting Weird Workarounds as Solutions

[aleksei_ovsienko]

It's not the first time here that I'm trying to solve some problem I encountered and I stumble upon a thread many years old where this problem is solved with a weird workaround. And it's marked as "Accepted Solution". 

Would it make sense to have another status for a situation when a problem is addressed by a weird workaround? Like "Temporary solution found" or "Workaround"? So that the development team is aware the problem is actually still there.

Because I feel like these "Accepted Solutions" just get forgotten by developers and we're stuck using workarounds and bending over backwards to solve problems that really should have always had a straightforward solution. There are dozens upon dozens of such things in Fusion and boggles my mind they go unaddressed for years.

[TrippyLighting]

What is a "weird" workaround?

Could you list some?

I'll start with my favorite one, the Modify->Compute all command.

I don't recall having to do something similar ever in 15 years of SolidWorks.

In a recent larger project, I had to do this all the time, almost every time I changed a configuration properly, joined/assembled external components/assemblies popped out of place, requiring a "compute all".

[aleksei_ovsienko]

Just a few latest examples I came across: 

Point mass in Simulation can't be referenced to a point and the workaround is to create faux geometry instead:
https://forums.autodesk.com/t5/fusion-design-validate-document/simulate-assigning-a-point-mass-manua...

In Drawings one can't base a section view off of a detail view and the thread is simply marked as "Accepted solution" although there's no solution at all, they just say it's on some roadmap - https://forums.autodesk.com/t5/fusion-design-validate-document/fusion-drawing-restriction-of-section...

Drawings are full of such things. Like you can't move views between sheets, instead you have to clone the entire sheet and then drag views you don't want out of it.

To me an accepted solution is something that's been actually implemented. 

[Drewpan]

Hi,

At the time the "solution" is found it might be a workaround, and because

fusion got an update that "solution" may then have been a "temporary solution"

but how do you know at the time? While fusion is very good at doing many

things there are also other stuff it sucks at and these "solutions" end up being

the ONLY method of achieving what is needed.

If the question has been asked and the Devs have indicated it is "on the Roadmap"

they might be referred to as a "workaround" but stuff happens and some of these

promises are "superceded" by more urgent stuff. I do feel your pain and I can see why

it is annoying but honestly there is not really much that can be done. If we revise

History then we might destroy quite valid techniques. The thing is that fusion has

been designed so that there are often several ways to achieve the end result. What

might be an annoyance to you is someone else's technique of choice because it works

perfectly for them.

We all search the forums for solutions (We DO don't We?) and often some of this stuff is

dredged back up. The Devs DO follow the forum and one of the Dev Steering techniques

is to "make some noise" about a certain theme to get it bumped up the Roadmap action

list. It really comes down to if only a couple of people ask for something then it will be

bumped DOWN the Action List. If LOTS of people make noise about it then it gets bumped

UP the Action List.

Cheers

Andrew

[bhavani_sankuratri]

Hi @aleksei_ovsienko 

I wanted to check in and see if you still needed assistance, or if you found a solution to your question already? Let us know if you need further assistance by providing an update or if you have found a solution, please share it with the community so other members who may have the same question could learn from your experience.
 

[CGBenner]

@aleksei_ovsienko 

Hi, thanks for your post.  In these forums an Accepted Solution is anything that answers the question for the original poster and/or anyone who has asked a follow up question.   These may include officially posted Autodesk solutions that have been added to the Product, or it may be a quirky work around that gets the original poster where they need to go.  The key thing is that it answered the question for them, and that it does not have to be the ONLY solution.  The nice things about these forums is that a post may have multiple solutions.  Anything that the OP or others thought was helpful could be a solution.

When the product teams add new features we do not go back through the forums unmarking solutions that the new features address.  I hope this clarifies things for you.

[TrippyLighting]

---

@Drewpan wrote:

... The Devs DO follow the forum and one of the Dev Steering techniques

is to "make some noise" about a certain theme to get it bumped up the Roadmap action

list. It really comes down to if only a couple of people ask for something then it will be

bumped DOWN the Action List. If LOTS of people make noise about it then it gets bumped

UP the Action List.

...

---

Yep! It can be argued, however, that "behavior" or response to user feedback has been quite to the detriment of Fusion.

[Drewpan]

Hi,

Well said trip. I don't agree with the situation but it exists.

Cheers

Andrew