Anomalous objects appear after split tool

[jgpackerRQ4HX]

In a design I used split body, then mirror. After going back and moving the splitting tool - a sketch line, extra objects are appearing in the design, which were not there before. These are visible on screen but not selectable, and seem associated to another body, so turning that body on/off also makes the ghost body disappear. I have tried re-doing the split, undoing to before the edit that caused the issue. I thought I'd resolved the issue, then a subsequent mirror body operation shows the ghost body I'd already got rid of being mirrored! Weird stuff.

Any clues?

[g-andresen]

Hi,

Please share the file.

File > export > save as f3d locally  > attach it to the next post.

günther

[jgpackerRQ4HX]

Hi, I don't want to share publicly - can I send privately?

[g-andresen]

Hi,

---

@jgpackerRQ4HX wrote:

Hi, I don't want to share publicly - can I send privately?

---

No, this is a forum in which everyone should participate.
If it helps, recreate the situation with a suitable example.

günther

[jgpackerRQ4HX]

Well that's interesting. I exported the file as an f3d, opened it in Fusion, and the anomalies have gone!

[g-andresen]

Hi

... wonderful solution!

günther

[jgpackerRQ4HX]

Unfortunately not for this - as it has assembly contexts that will be broken if I try to substitute the file... the whole assembly context thing seems near impossible to use without having endless errors when I alter parts after referencing them in assembly contexts - is there a tutorial on how to use this properly do you know? Never had an issue in Solidworks

[g-andresen]

Hi,

Please show the process in a screencast, otherwise only the crystal ball remains.

günther

[jgpackerRQ4HX]

Well I'm trying to upload a screencast for you.... but don't know the URL .... what is the screencast website that's referred to but not linked anywhere here?

https://knowledge.autodesk.com/community/screencasts/faq

[jgpackerRQ4HX]

Two towers connected with a bridge... done as separate components because in reality they are very complex. I move one tower, synchronize the assembly context, the bridge size adjusts, all good.

If I open the bridge part, make a few changes, save it, go back to the assembly, the context is now out of date. So I synchronize the assembly and all the new timeline events disappear from the bridge, it reverts to an older version!