Can't always create groups in timline

[hoegge]

It is not always possible to create groups in the timeline. This was also reported here:

https://forums.autodesk.com/t5/fusion-360-design-validate/create-time-line-group-missing/td-p/678238...

Would be great if you could fix that. As shown in the example below, it is suddenly gone. Different selections in the timeline re-enables it but it does not seem consistent.

[Phil.E]

Hi,

Sorry to hear you are having trouble with this. Is it possible for you to share the design with me? Glad to help, but in this case the data is critical to find an answer.

Regards,

[hoegge]

@Phil.E Here is an example where timeline grouping leads to crashing (CER_172809747). When I click the - in the time line here:

Fusion crashes every time. I can share the file with you but not here (for the public).

With respect to the grouping: It seems like you cannot group operations within a component, if other operations have happened in between these operations in other components or root component. The "path" from first to last operation in a groups for some reason seems to be "un-broken". I'm not sure if that is documented anywhere? Does it make sense? Maybe - since you could be referencing items, that are created in between steps in other components, and then they would break if moving the group. That, though, I would think would normally be handled by preventing the group operation from moving.

That also leads to the idea, that it would be useful, if there in all component's timelines, was and indication between operations, where something has been done in other components, which is currently impossible to see, if you don't go back to the root component.

E.g. with an icon like this (before the fillet) on the timeline, that you could click and then jump to the next operation in another component:

[Phil.E]

@hoegge

Thanks for your CER reports! They all have comments that are very helpful.

I'll send you a PM so we can connect privately. I'm interested in two things:

1. The group problem you are describing here.

2. A sheet metal crash that you repeated. If it's at all possible I'd love to get the part from you that you mention in the reports.

Thanks,

[hoegge]

@Phil.E

With respect to the group problem, this video illustrates it (re-creating operations using redo). In the video I create one component, where I can group operations. Then I create another component and then go back to the first and add a third operation to that. Then I cannot group operations 1,2, and 3 on the first component, because operation 1,2 in component 2 is made before operation 3 in component 1:

https://autode.sk/2xSdesJ (used this link instead of inserting screen cast since it is still preparing - let me know if I should update, when it is done)

kr

Morten

[Phil.E]

@hoegge

Sorry it took a while to get back to this.

What you describe is as-design. It sort of has to be this way.

The timeline is the timeline. The events happen in that order. If you need to create a group of the Component 2 features, as shown below, with Component 1 features in between, where would you expect the Component 1 features to end up after you made the group? Before, after, or inside the Component 2 group?

Have you tried reordering the features such that C2 the features chain is not interrupted?

Thanks,

[hoegge]

Hi Phil,

That was my exact point. But I think some of the reported issues where people are not able to group is because of that, since it is not clear to a user. That is why I would suggest to put that small indicator on the time line. The menu item (create groups) should not disappear but change to “Can’t group: interleaved features” - or something shorter / smarter 🙂

Thanks

[hoegge]

The icon showing / indicating operations in other components / root component could be an in-between-items “group +” that then opens the operations done in other components with colors, just like shown in the root timeline. That would be quite useful

[Phil.E · Accepted solution]

@hoegge Thanks for the suggestions, they are now logged as improvement requests. I do think an indicator when group is not available would be a great improvement, as you point out, it can be confusing. 

Regards,