If your set is taken from a larger set, there may be common references, and so when the small set is recorded, we don't have 1 set but 2! (the small and the big together)
Have you looked at your functions which are heavy on your tree of creation
as I told you before
among other things your thin extrusions
they are or what are they based on
_les constraints, the odds are not weird
if at the base you reference
most dimensions via the point of origin (or a common ref)
you will save time to rebuild
if you constrain a piece
in one place and then you make an elevation of matter it screws up the binzzzzzz
@+ ;-)
I can't download your showcase file, is it still accessible?
Regarding the way to build the piece, I don't think there is a wolf, I have nothing wobbly and the piece is still very basic. It's the first time in more than 10 years that I've encountered this type of problem, without changing the way I work. I don't claim that it is the best, but so far it has not failed me or this kind of problem. Moreover, the reconstruction of the file from 0 was done under the same conditions, with the same references for a totally different result in terms of weight.
The file is normally always available for download.
Same impossible to download the file!
What is that your thin extrusions
Well, I'm posting the file here, I'll edit tonight to delete it.
Thin extrusions are walls for which I have only drawn a line, no thickness.
EDIT: FILE DELETED, SOLUTION SOLVED
Well, I went back to 5 MB by doing the following manipulation!
Create a new display state
Delete the old
Move the reconstruction cursor up to the beginning of the tree
Moved back down
Crtl + Q
Backup
Pkoi I don't know but in any case now the file is 5MB
3 Likes
Hi @ coyote
+ 1000................ you deserve a good point ;-)
take screenshots of the statistical tool on before and after if possible
to understand where it has m.... r
Progress in design should not be optimized
@+ ;-)
wow! super.
On the other hand (ball and chain to the end), I managed to create a new display state, but not to delete the old one. A micro tutorial, please? Thank you.
1 Like
to be sure to erase well
Give a new name to your new config
and erase the old name (delete)
@+
1 Like
Sniff, I didn't understand anything or it doesn't work for me:
- opening of the file of 195270 KB
- Creating a new display state
- Creating a new configuration
- Removal of the old configuration
- moves up the design tree
- Rolls up to the end of the tree
- CTRL Q
-backup
the new file is 195249 KB
What did I miss?
1 Like
you take your file
you make a new registration with a different name
you do the coyote procedure again
you save keeping the same name
you delete your old file
Re
I forgot something, I saw it when I started all over again!
In fact I did something more, I removed the removal of the symmetry then I put it back then CTRL + Q then save and now I'm at 6 MB!
@+
1 Like
Result of the manipulation: 190416 Kb.
There's still something wrong
Correction, I posted before coyote's last reply: with this de-deletion/re-deletion: 3740 KB!!!
Champagne!!!
You're a boss.
I'm going to test it on the 1.2 GB assembly right now.
1 Like
In a rage, I removed all the symmetries without changing the display states or saving under another name or anything, and I went down from 1.2 GB to 17 MB. Well, I have to stop the deleted symmetries (used to avoid making cross-sectional views where you lose appearances).
A big thank you to all, and especially to coyote for this winning return.
1 Like
symmetries are very good but once done you have to reconstrain them and re-dimension them
which is therefore no longer a symmetry since these refs are its own
so no search action on the part which is your basis of symmetry
@+