Different component relocation problem

[Anonymous]

Not sure if I'm missing something, but in the attached fairly simple file I cannot relocate anything.  Try creating two new empty components, and dragging to relocate one into the other, it just can't be done. The timeline appears to not be dragged to an earlier position, so I don't think that's it. 

I would greatly appreciate any insight!

Jesse

EDIT: I now attached my original model striped down to just one empty component, and its existence prevents moving anything else around in the browser tree, such as creating an additional empty component and trying to move one into the other.  Once that original empty component (which used to contain stuff) is deleted though, then new empty components can be moved inside each other.  So definitely seems like a bug, but I don't know how my model aquired this problem to begin with. 

EDIT 2: Well I found my file can be "fixed" by discontinuing capture of timeline history then reinstituting it, which causes the timeline history up until that point to be lost, but at least the file seems fixed to where components can be restructured again as subcomponents, etc.  🙂

[LMD001]

Hello Jesse,

I can reproduce this issue, loosing the TimeLine indeed fixes the file, wonder what could have caused this.

Best regards,

Ludo

[Anonymous]

Hi Ludo, yeah, I'll try recreating my model tomorrow and test the browser tree along the way to maybe identify what caused it.

Jesse

[Phil.E]

Thanks for the report and the file. I cannot reproduce it from scratch, even when I mimic your timeline. Dev is looking at this as a bug (internally reported as FUS-21212).

Sorry for the inconvenience. If you can list steps that will manually reproduce this in a new file, please do. That would help the investigation greatly.

Regards,

[Anonymous]

Hi Phil, thanks for trying, I have the same issue of being unable to reproduce it.  I'll post if it surfaces again and I can isolate the sequence, but otherwise probably better stuff for you guys to work on. 

Jesse

[Phil.E]

Jesse,

Well.. this is a concern that we will investigate. We might have enough to go on, but any new info would help. Don't worry about it, thanks for the heads up. The data is a great place to start.

Thanks,

[Phil.E]

Jesse,

Early in the design did you place a joint or joint origin and delete it? Or undo it?

Thanks,

[Anonymous]

Hi Phil, I might have created a rigid group and then deleted it.  When I get a chance will try recreating the circumstances more. 

Have a great Thanksgiving!

Jesse

[LMD001]

Hello Jesse, Hello Phil,

Could "fix" the file, like maybe 10 times, so at least this appears to be repeatable, by doing the following:

1) Move the HistoryMarker before the last Extrude (Angle#2).

2) Delete all features after the HistoryMarker, in fact the last Extrude in the TimeLine.

3) This step seems to "repair" the file.

4) Extrude Angle#2 again seems not to affect this, Components keep behaving as expected.

Deleting Angle#2, deleting the last Extrude does not have the same effect, Components keep being locked up.

Now the bigger question is: why did the components lock up and why is doing the above somehow fixes this?

Here's a little ScreenCast: http://autode.sk/1XkxZmP

Hope is of any help.

Best regards,

Ludo

[Anonymous]

Hey Ludo, I don't know how on earth you discovered that, but it's pretty interesting!  Good methodology to keep in mind if ever encounter something similar. 

Have a great day!

Jesse

[Phil.E]

The problem with the file is a bug. We are working to fix the bug. It doesn't seem like a very easy to repeat problem, with very specific steps required to encounter it.

Thanks for looking into it, but when this is fixed there should be no need for a workaround.

Regards,

[Anonymous]

It sure does seem difficult to repeat.  I'd sure dread trying to dig deep in the bowels of code to tease that one out. 

One thing that's interesting that Ludo did was show how rolling back the timeline marker and then using the delete from there option is different than just deleting from the timeline.  It appears good practice to do the roll back then delete, as I see Phil do that often too.

Jesse

[LMD001]

Hello Phil,

The repair of the file was not at all intended as a workaround, it was meant, at most, to be a possible indication for the Fusion 360 Team of where to look for a cause. I found some more ways to unlock the components but none of these where really repeatable, the one I posted was, or at least, seemed to be so.

Of course, better would be to find the exact steps needed to repeat the problem, but apart from the file Jesse provided, I could not repeat it.

Anyway good to read you are already working on this bug. Thanks for that.

Best regards,

Ludo

[Anonymous]

It looks like this bug turned up again, and this time I was able to go back using undo and find exactly what caused it to occur.  In this screencast, it's shown how creation of a joint origin did it in this case:

https://knowledge.autodesk.com/community/screencast/c40ef1df-7dcf-4405-b268-1ddda3931e0c

I've attached the f3d files of just before and just after this occurs.

Hope it helps.

Jesse

[Phil.E]

Jesse,

Looking at the After file, I can move components into other components. I just want to be sure that is the problem you are reporting, that restructure cannot be performed.

Thanks for posting more information.

Regards,

[Anonymous]

Hi Phil, yeah I must have forgotten to test the 'after' file, oops!  Like you said the restructure problem with this model is not appearing now.  Well, I'll just continue to be on the lookout for this bug 😉

Thanks,

Jesse