intensive use of derived parts

[Il Mauri]

Good morning to all, I would like to know what you think of from my idea of managing new projects.
I press that so far we have always worked in the classic way: molded ipts were immediately encoded and then put on the table.

my idea is to derive ipts by suppressing in connection with the basic component so I would have less heavy parts and not editable by chicchessia (not being the browser of the processing).
It is clear that by suppressing the connection the derived file is no longer up-to-date.

Do you think I'm going to encounter axiemi instability problems or something using intensely derived parts?

 

[ceschi1959]

Good morning to all, I would like to know what you think of from my idea of managing new projects.
I press that so far we have always worked in the classic way: molded ipts were immediately encoded and then put on the table.

my idea is to derive ipts by suppressing in connection with the basic component so I would have less heavy parts and not editable by chicchessia (not being the browser of the processing).
It is clear that by suppressing the connection the derived file is no longer up-to-date.

Do you think I'm going to encounter axiemi instability problems or something using intensely derived parts?

would be like importing a step, and if you have to make changes?

 

[Il Mauri]

would be like importing a step, and if you have to make changes?

changes involve a revision of the code, so I should still replace the modified part.

 

[TECNOMODEL]

I honestly don't see the slightest usefulness.

 

[Il Mauri]

I honestly don't see the slightest usefulness.

less heavy files, consider that an ipt passes me from 2563kb to 1602kb (-37%)

 

[TECNOMODEL]

and this reduction that benefits you?
open the file in 10 seconds less?
this advantage compensates for the time you lose then to make any changes?

I have parts from 8000 kb and manage them without the slightest problem with a pretty dated pc.

 

[Catafratto]

I understand derived assemblies (maybe simplifying them) to streamline things, but the individual parts... and then they would still be editable, only with extreme pastries type direct modification, move faces, etc. etc. (Just done!

 

[Il Mauri]

Well, I always start with the idea that the more files are light and the better. considering that all these files are contained in so many axioms that then I have to export them as steps (which become very heavy) to give customers I think that starting light is not wrong. I wanted to compare myself with you not to create unmanageable or unstable "masters".

 

[TECNOMODEL]

if the problem is to give a step as light as possible simplifies the assembling and export it later.
in that way your files will always be complete and avoid time loss and complications due to having to work on a treeless feature model.

 

[Il Mauri]

if the problem is to give a step as light as possible simplifies the assembling and export it later.
in that way your files will always be complete and avoid time loss and complications due to having to work on a treeless feature model.

simplify the axieme? even if I delete all internal parts and hold only the shell or external parts that serve to make the axieme coherent, transforming it into file step the file becomes very heavy (e.g. a 3300kb iam sketches at 23000kb)

 

[Zac69]

simplify the axieme? even if I delete all internal parts and hold only the shell or external parts that serve to make the axieme coherent, transforming it into file step the file becomes very heavy (e.g. a 3300kb iam sketches at 23000kb)

winrar e wetransfer.

 

[Il Mauri]

winrar e wetransfer.

Of course, but for the poor tap that receives the file and must use it once disappeared. . .