For my project i have a clean timeline no errors no warnings.
After i changed something in the past history all looks great no warnings and errors in the timeline.
But if i run "Compute all" i get this warning.
But i am sure that this joint is deleted and can't exist anymore.
I searched the timeline for a yellow market joint feature, but can't find one.
The timeline has no error or warning signed features.
So how can i fixe that?
Here is the file for testing: http://a360.co/2dZhCwi
Hi @macmanpb,
Thanks for the file! I was able to reproduce this issue on my end, so it's not just you! Unfortunately though, I am uncertain how to go about fixing the warning. However, I am actively looking a solution and will circle back here once I have something to share!
Cheers,
Hi @macmanpb,
Thanks for the nudge! I was hoping to have some better news to share at this point.
I was able to find that during your design process you may have inadvertently deleted an edge that was associated with a joint. However, the associated joint should be highlighted in the timeline, but for some reason it is not. After a search through our bug tracking system, I was able to find that another user was having this same issue. I have added your details and design to the bug report for the development team to review (FUS-19808 for your reference).
Also, I found some other strange behavior with your design. While investigating your timeline to try and figure out what exactly was causing the issue, I had rolled the timeline marker all the way to the beginning and was progressing through it, feature by feature until I hit the feature that caused the warning to appear. I noticed that it appeared shortly after you created the component "Zahnriemenrad_HTD_60_25_17246000 v2". It was at this point that I discovered that there was a "ghost" sketch appearing in your design as shown below. The strange part is that the sketch should be suppressed because it was created after the timeline marker. For this reason, I have logged a new bug (FUS-28132 for your reference) for our development team to review.
I am sorry that I do not have better news to share! I will keep you updated as the bug reports are updated!
I have looked that the same problem as reported in this thread. My design has a spiffy clean timeline 400 components and only these implicit joint warnings are creating a problem.
My suspicion is that Fusion 360 has problems when joining external components.
I happen to be German and that Zahnriemen_Rad_HDT 60 is from https://www.contitech.de/ and also likely imported geometry starting with a base feature.
That is the same in my case (Screws and Washers from McMaster Carr in STEP format).
Here is a little screencast looking at some of this.
That "ghost image" is not a problem, really. Component highlight in Fusion shows sketches owned by the component, even if they are hidden. The weird part is that this is true even if the sketch does not yet exist (that is, if the history marker is rolled back before the sketch's creation). You could argue that this is a bug, and we'll look into fixing it, but it does not indicate any sort of data corruption in this model, and seems unrelated to the implicit joint warning. Here is a view of that sketch when it does come into existence:
If you are curious to see this behavior in a simpler model, check out this screencast: http://autode.sk/2ftkTUD
Now, back to the original problem. I continue to look into it, but have not tracked down the actual cause. If you are correct, @macmanpb, that this is from a joint that no longer exists, then we do have a bug.
It's probably worth a little explanation of what these "implicit joint origin" things are. When Fusion first was released, you had to create explicit Joint Origin features in order to create a Joint. We realized that this was cumbersome. But, we needed the joint origins in the data model. So, now, when you create a Joint, we implicitly create joint origin objects for the geometry that you pick for the joint. We do not show these in the browser or timeline, because you didn't create them yourself. So, when one goes bad, it becomes a bit of a challenge to find these guys and fix them.
We'll keep you informed of our progress on this error.
Jeff
Thank you, @macmanpb,
Great detective work! That looks like it will give us a great clue about where to look for this bug.
Jeff
Briliant detective work!
This also provides a very good guideline on how to avoid it.
Good news! This issue will be fixed in the up-coming Jan update!
Fusion
