Is it me - Fusion is not behaving at all any more

[garfieldQ2F8V]

Two issues, wonder if anyone has encountered in the latest updates of Fusion.

1. Joints within assemblies are not respected when that assembly is inserted into a larger assembly. Components move and cannot be fixed with edit in place - shouldn't need to be fixed in the first place.
2. Inserting an assembly triggers a non existent error - reports a fillet error that is NOT reported in the source component, attempts to remove the fillet in the source destroys 90% of the drawing so there is no fixing this - hours and hours of work wasted.

garfieldQ2F8V_0-1770389906709.pnggarfieldQ2F8V_1-1770390065203.png

1. Show referencing joints is still not reliable, joints that I know exist do not show up at all.
2. Driving joints has become really hit and miss - no option to stop an assembly snapping back to the originating position when I am validating contact / component interference in motions - if it makes contact just stop so I can see where !!.
3. Quit with that stupid 'What do you want to design' dialog everytime I open the app. If you want to do something useful open my last session and all tabs I had open.

Really starting to think hard about whether to start migrating, I am wasting way too much time chasing these little annoyances.

[mpZQ4FN]

after the update i have so many issues with especially joints, constraints and respecting those, particularily when insterting components into a new aseembly..

also getting so many "failed due to initialization error" which i have never experienced before the update. its driving me up the wall and i have a deadline closing in and a big project with thousands of parts and components are now all over the place

i cannot for the life of me find any sense in why or how this behavior occurs

mpZQ4FN_0-1770395910489.png

@mpZQ4FN - this post has been edited due to Community Rules & Etiquette violation. 

[swapnil.hamdapureDDSVZ]

@garfieldQ2F8V @mpZQ4FN Sorry to hear that you are facing issues after the January update. Is it possible for you to share the data so that we can look into what went wrong? 

[mpZQ4FN]

i have just uploaded a performance feedback through the program, Report id: 107794

[mpZQ4FN]

just trying to capture a position from a move feature is not working.

mpZQ4FN_0-1770397563224.png

moving things they are also jumping around and behaving strange... basically unusable

[andrew.giffen3052]

Yes, same thing here. joints are simply not respected after importing a sub assembly. Relieved to see this as it was totally frustrating.

[garfieldQ2F8V]

Tell me what you need, I can't delay what I am doing whilst waiting on solutions - I did look around for some sort of 'debug' log or some verbose logging but there is nothing - it would be easier if the fault was predictable, so far it isn't, I cannot attribute this behaviour to anything in the assembly / sub component that fails, seems to be how the recalculate is done when the 'import' is assimilated and recalculated into the whole - but no conflicts or issues are reported - just things aren't where they are supposed to be. 

Trying to fix this put me in the hurt locker with edit in place not cleaning house so the source component was locked in a out of date reference state that could not be resolved, I'll never use edit in place again - not that edit in place can validate the joints it won't. In order for you to experience fully I'd need to share a lot of assemblies and parts - on their own they are fine, the second they're brought together the brown stuff hits the fan - even to the point where errors are reported that don't exist - see my starting post.

Deleting a feature such as a fillet should not delete 90% of the dang drawing - something in all the calculations that create the model is busted. 

Tell me how to get a good debug log and happy to play along I'm pretty good at tearing logs apart - been at it 40 years ...

@garfieldQ2F8V - this post has been edited due to Community Rules & Etiquette violation.

[garfieldQ2F8V]

At no point did I use profanity - sort out your bots - I know another poster did but I did not - 

[garfieldQ2F8V]

Here is a classic example - this is the component, it is made of multiple parts, yes it does reference geometries that it does not contain, but that should be irrelevant - the whole benefit to Fusion has been the ability to test fit and build parts around others so that you know they will work - it is stupid to be working to dimensions all the time when where it goes can be used as a reference. The way Fusion is behaving negates the whole point of parts / components / assemblies. 

This is the component, zero issues

garfieldQ2F8V_0-1770415639716.png

Save this as a component - as in save as results in this, completely exploded and failed in so many ways - is Fusion so stupid that it can't include cached references where necessary 

garfieldQ2F8V_1-1770415787138.png

Pasting it as a new component into another drawing results in this, I mean come on - save as isn't saving references either so you end up with lots of red flags - and I don't like red flags in any of my assemblies. I also don't want to be managing large assemblies in one humungus file that becomes unmanageable.

garfieldQ2F8V_2-1770415902061.png

Utterly inconsistent behaviour - the current architecture based on my experience is not fit for purpose - and I do mean Fusions architecture - I wish it was possible to downgrade because I would do so in a heartbeat.

[TheCADWhisperer]

---

@mpZQ4FN wrote:

moving things they are also jumping around and behaving strange... basically unusable

---

@mpZQ4FN 

Are there any unresolved issues highlighted in you Timeline before attempting this Move operation?

[TheCADWhisperer]

@garfieldQ2F8V 

Can you Attach example *.f3d or *.f3z?

[TheCADWhisperer]

@garfieldQ2F8V 

Can you Attach example *.f3d or *.f3z?

Are there any unresolved issues highlighted in your Timeline?

Does Ctrl b (CMD b on Mac) return any issues?

[swapnil.hamdapureDDSVZ]

@andrew.giffen3052 @mpZQ4FN @garfieldQ2F8V We were unable to reproduce the issue on our end. Please share the data/file(*.f3d or *.f3z) to help us investigate further.

[garfieldQ2F8V]

I cannot teply via email - my system insists on TLS transmission - seems this board doesn't accept that

Tried to attach an f3z but this system stated 

garfieldQ2F8V_0-1770626616184.png

this file was created by Fusion - so something else to fix

seems happy with it as a zip and all I changed was the extension

[mpZQ4FN]

none at all

[swapnil.hamdapureDDSVZ]

We are unable to open the .f3d files in Fusion. Can you please share the .f3z file?

[garfieldQ2F8V]

Didn't read the post clearly - I did share the f3z - Autodesk system declined it .... and yet the Autodesk system created it 

[swapnil.hamdapureDDSVZ]

When I opened the files under the zip you shared, I saw all f3d files. Is it possible to provide it (f3z) under .zip file?

[garfieldQ2F8V]

Read the post I made !! - the file is an f3z, all I changed was the file extension because the Autodesk system declined it - take a look at the image I included !!

seems happy with it as a zip and all I changed was the extension

I am not in a position to export it again as I have moved on, the parts in it no longer exist, I've gone back to the old ways 

[TrippyLighting]

@garfieldQ2F8V I've downloaded the file, changed the extension, uploaded it and looked at it.

In a design like this I would not expect to see a single position capture or body-move feature.

Some other mistakes are:
This rigid group should involve the top/root level and the count should be 32, not 31:

TrippyLighting_0-1770819764470.png

The rigid group in this design is highlighted in red meaning it cannot be computed and and is non-functional.

TrippyLighting_1-1770819967379.png

This isn't a proper (sub) assembly as all components can be dragged around in the viewport, meaning they are not properly assembled in that file.

TrippyLighting_2-1770820081235.png

Same with this file:

TrippyLighting_3-1770820130650.png

And so forth...