bug? ghost body after parameter change

[relopesfusion0]

Hello All and thanks for the help and apologies if this is a dumb question but I am fairly new to Fusion and new to the forums.
I have been playing with a more advanced (for me) use of parametric design. The idea being that I can change basic dimensions and 90% of if is recalculated and ready (barring some move and extrude commands which do not keep their parameter references).
I am attaching two images, one of the project (a desk) before parameter change and another after the parameter change. I am highlighting what is the selectable body on both, as well as showing the sketch. Both seem to recalculate correctly but the old body is there, non selectable as far as I can tell.
Thanks for any help and go easy on me 🙂

Renatoafter parameter change

before

[g-andresen]

Hi,

please share the file for investigation

File > export >save as f3d on local device > attach to post

günther

[relopesfusion0]

thanks günther!
attached is the F3d. timeline marker is already at the right element point(drawer top). Parameters succesfully affect the sketch but the resulting body is both the new and old body(ies) (?)!

[g-andresen]

Hi,

At which parameter changes does the effect occur?
I cannot reproduce the behaviour with changed widths.

Günther

[relopesfusion0]

sorry forgot to point that out.

It is deskWidth. This drives the top surfaces width. Its sketch is projected on the drawer top component sketch and "should" in turn affect the drawer box body.

In time, i should mention that similar issue was happening with the desktop component (the main one affected by deskWidth). I managed to work around it by rolling the timeline back to when that component's sketch is extruded and then changing the parameter.

Hope that helps.

[g-andresen]

Hi,

that´s what I see

günther

[relopesfusion0 · Accepted solution]

Hey Gunther,
After your reply I was v happy to see it working on someone´s screen - that narrowed it down to a problem with my Fusion/machine.
I had been running it for a few days and it seems that all that it needed was a fresh restart and it now shows up correctly.

Apologies, It did not occur to me that this could be the problem but now I know better 🙂

Thanks for your prompt attention on this!

Renato

[relopesfusion0]

stopping here to credit @g-andresen for walking through troubleshooting with me. I´ve chosen my own answer as the correct (as it explains the solution) but his help was key to isolating the problem.
Cheers  Guenther!