Problem in large assemblies with losing projections, components not having moved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Hello,
I am having a consistent issue with fusion losing my projections of components which do not change.
It happens both in normal assemblies, but also when using assembly context. My experience in fusion I would say is quite advanced but this problem I feel is quite basic and nobody seems to have answered this on forums before. Perhaps there is a problem with my workflow and I would love to hear from someone who would have a better approach.
Say for example that I have a sketch which contains projections of many different components. I project and intersect, lets say, around 20-30+ different parts, faces, edges, anything I need into my sketch. This is a lot and can be confusing to look at times, but can be necessary to build up the shape of certain parts.
My example is of a drone fuselage, similar shape to a normal aircraft but smaller, I trace around my components so that I can create mounting points and positions for reinforcing structure and other things. These sketches therefore become the backbone of my model.
I carry on with my model and everything is fine of course until I wish to manipulate one of the sub-parts in some way, perhaps an extrude feature I need to change, or move something a few mm left or right. Maybe the entire model of a motor we want to use is changed.
Of course, it makes sense, I just changed a part, now re-select the edges. But now I see the sketch and am faced with disaster. The entire sketch is yellow, and I am asked to re-point 20-30+ different lines, and click just for the outline to be the exact same way it was! This is not only very tedious and time consuming, but if I am not concentrating properly and select the wrong geometry, I end up making errors and changing my model without knowing.
Potentially, this happens not only when I manipulate a part, but when I add/remove one. I imagine that within the program code, each projection is assigned a line (eg. project 1, project 2,3,4 etc...) and when something is added or removed in the chain, the list shifts in name assignment and "loses" its position. This is just my hypothesis but anyway...
There must be a better way. Again perhaps my workflow needs adjusting and the answer is simple. Should I separate this process into many smaller sketches? I have read on these forums that many sketches are computationally expensive and bad practice, and if you need many sketches in one plane, it's better to use just one. Is this perhaps a case to use many sketches on one plane?
I am sorry that I cannot share my model as it is confidential and belongs to my employer. I hope that I explained myself well enough. I look forward to your answers.