Was the new UI ever QUALITY tested by actual users?

[jimRSHFX]

This latest version is almost like an Alpha version of a new release. It is very frustrating with multiple additional keystrokes and Easter Egg hunting to find common functions.  Dropdowns are more understandable than some cryptic icon. Why are simple functions like ARC, Ellipse, buried?  My personal opinion is that the UI is NOT ready for primetime, and is counter intuitive.  If you folks were going to make such a major change, the support documentation should have been ready and updated at roll out time.  Now, it sours the taste of the product.

[jhackney1972]

When the new UI was introduced, the Fusion 360 blog released documentation as well as a video comparing the two user interfaces.  If you missed it, here it is.  The new UI was a optional preview for many months before its release which was selectable by the user.  You can still use the old UI if you like by selecting it in the preferences.  I cannot say how long this will be possible.  You must restart Fusion 360 for this to take effect.

[janus2]

Why are simple functions like ARC, Ellipse, buried?

They are not buried, they are only displayed if they can be used: If a sketch is active! Logical for me!

In the old user interface, tools were visible that could not be used at that time. Not so logical!

But I never found a complaint from you about that.

I am already 70 years old. But after one day I got used to the new UI. Tools are better grouped and more logical in their visibility. Everything's better organized. From my point of view.

Now and then learning something new is good for the brain

Jan

[g-andresen]

Hi,

For information only:
Accompanying the development of the new UI there was (and is) this forum with the possibility to express criticism and make suggestions.

günther

[HughesTooling]

The new UI was in preview for over a year and I've used it for most of that time, wouldn't go back to the old. Although I would like the Sketch tab visible at all times. As for documentation do you mean like this in the help? THe old UI is likely only be available for a mouth or so so I'd only switch back if you need to get a job finished.

Mark

[chrisplyler]

Yes. We users have been quality testing it for a while now.

[jimRSHFX]

So where is the updated documentation, etc. that was the output from the
Quality work that was done?

[jimRSHFX]

I'm thinking /meaning a complete product review that is done with any major
software release to users. Not fragmented bits and pieces of code. 'Help'
is certainly a part of a quality software package.

[jimRSHFX]

Well Jan. you are a youngster to me. Drawing an Arc or an ellipse is
certainly included in the act of sketching. Good documentation also
requires thinking, lack of it does not.

[chrisplyler]

---

@jimRSHFX wrote:
So where is the updated documentation, etc. that was the output from the
Quality work that was done?

---

There are a few bits and pieces scattered around this forum, such as this thread. We are, after all, users. We don't get paid to update documents.

[jimRSHFX]

Exactly! Tossing the support and documentation of a product to a group of
well intentioned users is something expected in the Open Source world.

[chrisplyler]

Yeah. I get it. But what do you want me to do about it? I'm just a well intentioned user.

[jimRSHFX]

Just hoping the folks at Autodesk ‘get it’. 😊 Have a great holiday!

Jim

[TrippyLighting]

---

@jimRSHFX wrote:
Just hoping the folks at Autodesk ‘get it’. 😊 Have a great holiday!

Jim

---

I doubt it. 

[johnswetz1982]

I think you are misusing the word quality when you mean preference. Saying that there was no quality control would mean that when you pressed the button for line you would be drawing an arc or that when you tried extruding something it was actually the loft command active. That would be a quality problem. Saying you dont like X or Y is your preference. Did you have an example of a button/function that does not do what it is supposed to?

[jimRSHFX]

I think you have a lack of understanding..Here is the definition of quality.

1. the standard of something as measured against other things of a
similar kind; the degree of excellence of something.

"an improvement in product quality"


synonyms:

standard, grade, class, classification, caliber, status, condition,
character, nature, constitution, makeup, form, rank, worth, value, level;
More

o



o

o

2. 2.

a distinctive attribute or characteristic possessed by someone or something.

"he shows strong leadership qualities"


Synonyms:

feature, trait, attribute, characteristic, point, aspect, facet, side,
streak, property, peculiarity, idiosyncrasy, quirk; More




Don't confuse requirements with preferences.





When you open a sketch and say draw a circle, use the push-pull and assign
it a height. That is a logical set of steps. When you decide to add another
object say a polygon on the top plane of that cylinder that you created, the
'polygon option' is no where to be found. If you selected by using 'C', the
program will ask for the plane you want to use. Without the 'Polygon' or
other drawing pre-new UI choices available, you have to GO BACK and create
another sketch. It's lame. To me, displaying constraints across the top is
a waste of real estate.

[chrisplyler]

---

@jimRSHFX wrote:
When you open a sketch and say draw a circle, use the push-pull and assign
it a height. That is a logical set of steps. When you decide to add another
object say a polygon on the top plane of that cylinder that you created, the
'polygon option' is no where to be found. If you selected by using 'C', the
program will ask for the plane you want to use. Without the 'Polygon' or
other drawing pre-new UI choices available, you have to GO BACK and create
another sketch. It's lame. To me, displaying constraints across the top is
a waste of real estate.

---

Ah. This does not seem like a UI deficiency to me. It seems more like a discrepancy between user technique discrepancy and how the software expects things.

You can't push/pull (you should use Extrude instead in the case detailed above) a Profile while still in Edit Sketch mode. When you draw the circle, and then perform a modeling action upon it, you are automatically removed from Edit Sketch mode. Either:

1. Start a new, second sketch and draw the polygon in it, or...

2. Put the polygon into the sketch with the circle before you perform any modeling action upon it, or...

3. If you forgot to do #2, go back and Edit Sketch on the one with the circle in it, add the polygon, exit the Sketch, and now Extrude the polygon.

[jimRSHFX]

This method isn't described in the 'help' documentation, and there is the
example of the missing Quality with a new release.

[johnswetz1982]

1. the standard of something as measured against other things of a similar kind; the degree of excellence of something.

So when we measure this against a similar software like Invertor, ProE, and I assume solidworks (though I have not used it) it has the same kind of sketch functionality and workflow.

The example you give just means that you are not understanding how parametric modeling and design history tends to work in this and similar softwares. That is your personal preference for how you think the workflow should work. What you describe in your example is that way because you define 2D stuff before you make it 3D stuff.   

"To me, displaying constraints across the top is a waste of real estate." That is the definition of a preference.

"This method isn't described in the 'help' documentation, and there is the example of the missing Quality with a new release." This method IS described in the help documentation.

The New Toolbar UI

Sketch Overview Sketch overview even describes the difference between the old UI and the new UI. If your going to complain about it not being documented you should at least be truthful in your criticisms. 

[Oceanconcepts]

I’m very much a fan of the UI changes. I think they tend to direct one towards best practices- which could be frustrating if you are used to doing things in another way. Giving constraints more prominence is an example of this. Sometimes you need to take a step back from expectations and look at the overarching reasons why the program operates in a given way- ask, there is almost always a good reason. 

Documentation for Fusion is I expect just going to be tough- it is a very rapidly evolving program, and has been for years now. Anything written is going to be outmoded fairly rapidly. I’ve stumbled a bit at times to find things in the new UI, but when I did, the logic was always apparent. 

The Fusion team has been very diligent and conscientious with extensive testing and previewing, but that doesn’t mean every change is going to please everyone.