Whole timeline visible despite of single component activated?

[kristianY3VSG]

Hi,

maybe I don´t remember exactly, but as far I remember, some months ago, when I activated a component, only the timeline of this component was visible. Now I see the whole timeline, regardless of activating any of the components.  I created the components by "New component" in the right click menu while root being activated (sorry for not the best vocabulary). What am I doing wrong?

Thanks...

Kristian

[karina.harper]

Hi @kristianY3VSG 

I'm not seeing this on my side.

What OS are you on? The only thing I can think of is doing a clean uninstall.

Cheers!

Karina

[kristianY3VSG]

Hi @karina.harper ,

thanks, I´ll try this tomorrow, in Europe it´s  0:20 now 🙂

BTW: I´ve seen this recomendation at some other threads - does this mean, the automatic update performed by F360 may cause some SW mess? How can this be??? If so, you´d display a apropriate warning after updates, not only "you got the last update..." !!! May this be the origin of all problems I´m struggling with since February? Crashing Fusion while setting coincidence by dragging (even before opening CER dialogue), bodies changing to patch (237) with no chance to repair (circular dependency), bodies visibility switching while moving history marker etc.  😞

Regards...

Kristian

PS: I work on Windows 10

[karina.harper]

---

BTW: I´ve seen this recomendation at some other threads - does this mean, the automatic update performed by F360 may cause some SW mess? How can this be??? If so, you´d display a apropriate warning after updates, not only "you got the last update..." !!! May this be the origin of all problems I´m struggling with since February? Crashing Fusion while setting coincidence by dragging (even before opening CER dialogue), bodies changing to patch (237) with no chance to repair (circular dependency), bodies visibility switching while moving history marker etc.  😞

---

Hi @kristianY3VSG 

Sometimes issues come through in updates, but it's hard to say exactly what you're referring to. There are issues that may arise that we haven't anticipated. 

As for the other problems, it's hard to say. If you can share a file that you're talking about, I can try and recreate the issue and see if it's been logged with the team or not. 

Cheers,

Karina

[kristianY3VSG]

Hi @karina.harper 

before I list up all my problematic files, I have shared here during the last weeks, let´s first examine the latest problem 😉

I´ve cleaned up Fusion using the recomended exe, reinstalled it and tested it again - the result is the same (file attached). Any idea, what´s going wrong? May this be a problem of the GPU? As my NVIDIA went off while updating the BIOS of my Lenovo notebook (!!!), I can use the internal Intel GPU only :-((

Thanks and regards

Kristian

[karina.harper · Accepted solution]

Hi @kristianY3VSG 

@ryan.bales and I figured this one out - you need to turn on "hide inactive features". 

Let me know if that solves it for you!

Cheers,

Karina

[kristianY3VSG]

Hi @karina.harper ,

thanks a lot, I´ve never noticed that setting button, what a shame 😞 Earlier it worked well, then at some moment it must have changed, maybe by reinstalling F360 after the GPU crash mentioned above.

Well, this might mean, that F360 could have been OK before I reinstalled it today. Meanwhile I´ve tested some older problematic designs (which have posted here allready), they all show the same weird behavior as before.

My question now: Makes it sense to refresh my old posts somehow to get attention of the F360 team? One post resulted in a FUS, as far I remember, the others seem to be put asleep after some first responses, not beeing investigated anymore, as no clear responses came like "accidental error", "this we principially can´t find", "we´ll look at it later" or similar.

I have been programming SW almost 40 years, so I have quite an idea, how difficult it is to maintain such a colossus and find an error appearing only very rarely in a special constellation. And of course I now, that generally bug and crash reports arrive much more frequently then any team can handle, that´s why I ask. 

Cheers

Kristian

[karina.harper]

Hi @kristianY3VSG 

Which posts are you referring to? I can take a look at them if you'd like.

Karina

[kristianY3VSG]

Hi @karina.harper 

thanks for your interest and proposal!

My actual problems began when I used Insert Derive for the first time - see here my first post. Peter found, how to cure the laboratory experiment, but so far I don´t know, whether this is beeing investigated now or what. Later I had a similar problem dimensioning symmetrical lines and found, that it´s better to dimension their distance directly, not by dimensioning a perpendicular line across the symmetry line. But this still doesn´t explain the behavior of the Slave design.

The next problem (the only one resulting in a FUS) disappeared with the new sketch machine (FUS soluted?), no need to investigate anymore.

Then there was the problem with forgotten projection sources, you might remember. I´m still not sure, what the last response really means - does this work propperly or not?

The next problem was a circular dependency suddenly having appeared in a design, where I used Insert Derive earlier. I suppose, this is still beeing investigated.

The newest problem is a sketch, which worked well 2 months ago, now it´s generating warnings. I had to re-create it from scratch, the new one works well. I assume, this is the result of some changes at the new sketch machine - OK, but the idea, that any older design might be damaged just by opening it in the new SW version is quite frightening.

Well, so far a short overview of my substantial posts. I hope, it will not depress you.

Cheers

Kristian

[karina.harper]

Hi @kristianY3VSG 

That is quite a bit to look through, but here's the general answer I can give you.

Most of your posts are very geometry specific. When we create internal tickets, we are primarily looking for repeatable errors. For example, if we can re-create the error from new geometry or in our instance of Fusion then that is definitely something we create an internal ticket for. Since most of the models you have provided and questions you have asked are, while valuable, pretty specific, they have not resulted in a ticket. 

However! The person that I would have brought into a discussion like this would be Jeff Strater, who has already responded to your posts and it looks like may have created a ticket in some cases. He is the right person to be seeing this kind of behavior, as he will be able to differentiate between a one-off bug and an error that is a symptom of a larger issue.

Does that make sense? What I'm seeing in your posts is that the right eyes are on them and they have sparked valuable discussion in the support forum. We will do our best to answer your questions and log them as necessary.

Cheers,

Karina

[hank.qbgroup]

Thank you 🙂

[hank.qbgroup]

Thank You