kertus
Guest
never give reason to the machines. the man is always superior, but for working times I had to bend alas
I agree with tartufon80, to have it rigid is always better, even because it seems to me that you are doing design acrobatics, that if the program allows you, they could become dangerous to you and others. the more management is simple and the better for everyone.trouble found. this shitty rigid program more than a steel billet had troubles because of a geometric point created together and obtained from the twin present in a curved component in sheet metal. all served to have a common reference to mate this with another component. this program must die
Okay, try to cut together in cat v6, if you can do it without becoming too crazy, go change some affected component from that cut.trouble found. this shitty rigid program more than a steel billet had troubles because of a geometric point created together and obtained from the twin present in a curved component in sheet metal. all served to have a common reference to mate this with another component. this program must die
check that references you gave for the feature together, if you have copygeometry still linked to details you move, it is normal that you carry behind features tied so, in this case you have to unleash them and evaluate if really many features of together (all or some) you can not move them to its components, usually making top-down design you start with a processing idea, but then it can be simplified.otherwise explain to me why, for example (other straight arcane) if I bind one component to another that translates in one direction by means of coincidence of three planes in the three axes of space, just translating the component with the dragon I get that two of the 4 components coupled as I have just told you should turn around a perpendicular axis to the direction of translation carrying behind holes and bolts (poichè feature created in environment). I see something absurd and I don't find a logical explanation, but if you think he's right and you know how to give a reason, I'd be grateful![]()
I did not write that the machine is superior to the man. If I drive a racing car, I'll be sorry. If you drive a pilot do the numbers.never give reason to the machines. the man is always superior, but for working times I had to bend alas![]()
exactly what you say and 320i s.I agree with tartufon80, to have it rigid is always better, even because it seems to me that you are doing design acrobatics, that if the program allows you, they could become dangerous to you and others. the more management is simple and the better for everyone.
otherwise explain to me why, for example (other straight arcane) if I bind one component to another that translates in one direction by means of coincidence of three planes in the three axes of space, just translating the component with the dragon I get that two of the 4 components coupled as I have just told you should turn around a perpendicular axis to the direction of translation carrying behind holes and bolts (poichè feature created in environment). I see something absurd and I don't find a logical explanation, but if you think he's right and you know how to give a reason, I'd be grateful![]()
the answer to me is in the sentence I have highlighted!check that references you gave for the feature together, if you have copygeometry still linked to details you move, it is normal that you carry behind features tied so, in this case you have to unleash them and evaluate if really many features of together (all or some) you can not move them to its components, usually making top-down design you start with a processing idea, but then it can be simplified.
I am the first to say that I also create not perfect, but believe me that fall with higher reputation according to many "experts", they "lose in a glass of water" on management together.many times it is "colpa" of the too many possibilities to do something, that messs up everything.