models with unprecise dimensions. . .

[rapa]

excuse the question perhaps banal.... my fellow designers often complain about the models created by the undersigned that present different sizes with comma type 231.256890005.
I am not able to give an explanation about whether or not to yawn or intensive use of the command aligns.
Do you have any advice?
Thank you.

 

[cacciatorino]

is a common problem with this cad, especially for beginners or for those coming from other software. Unfortunately, two non-perpendicular faces are sufficient in departure and errors spread exponentially.

You should:
1) use very often the distance verification tool
2) When you load objects from the outside you always have to use the align/double controls to place them, even if they already seem aligned.
3) use a lot of construction lines

 

[reb_bl]

in addition to what has already been said as a hunter, use as little as possible the (comodissimo) alliena command, rather use 3d modification and use references (red arrow and green arrow).

 

[rapa]

Thanks for the advice?

 

[Kaji]

in the versions prior to 20 the intersections between the construction lines were not "captured" when using the free copilot, therefore to be sure of the correct path it was necessary to use the ricalca, otherwise it was risked to go very close with the click but not to center the intersection and from here measures with decimals. but beyond the decimals of the quotas, which can be erased by setting the size of the quotas in annotation, what is dangerous in the inaccuracy are the non parallel faces and the non-coaxial surfaces.

according to me the best solution, especially if you are a dozen in the office, it is to take a license for the advanced design module that with the parametrics submodule makes you set relationships to have definitely precise measurements and with the advanced assembly module allows you to mount with constraints etc, besides being able to be used for movements, animations, punctual calculation of the arms (and therefore torque moments) with logical mathematical relationships (if then else) etc etc.

 

[rapa]

in the versions prior to 20 the intersections between the construction lines were not "captured" when using the free copilot, therefore to be sure of the correct path it was necessary to use the ricalca, otherwise it was risked to go very close with the click but not to center the intersection and from here measures with decimals. but beyond the decimals of the quotas, which can be erased by setting the size of the quotas in annotation, what is dangerous in the inaccuracy are the non parallel faces and the non-coaxial surfaces.

according to me the best solution, especially if you are a dozen in the office, it is to take a license for the advanced design module that with the parametrics submodule makes you set relationships to have definitely precise measurements and with the advanced assembly module allows you to mount with constraints etc, besides being able to be used for movements, animations, punctual calculation of the arms (and therefore torque moments) with logical mathematical relationships (if then else) etc etc.View attachment 55036View attachment 55036

thanks to the tips. current we use the 17 we are going to 20 . hope in better?

 

[cacciatorino]

thanks to the tips. current we use the 17 we are going to 20 . hope in better?

The step forward is quite sensitive.

 

[Kaji]

thanks to the tips. current we use the 17 we are going to 20 . hope in better?

only fault of 20 compared to 17 is that the selection f2 key works a bit worse, so you might happen to make right button shows selector (unless you don't give different command from keyboard) and then some macros that worked with the 17 in later versions stopped working, but in most cases just add string

:toolbox-button t

under the top line of the title, for example:dialog-title "mehrfach eigenstaendig"

Finally, I do not know how the passage and scraping of permanent licenses functions as I presume were yours of the 17 to the current mandatory annual licenses, but if somehow it was possible to keep some (for example to install on laptops) I attach the lisp that allows the rescue from the versions after 17 that also works with 3d access that should also install you for free.

 

[cacciatorino]

Finally, I do not know how the passage and scraping of permanent licenses functions as I presume were yours of the 17 to the current mandatory annual licenses, but if somehow it was possible to keep some (for example to install on laptops) I attach the lisp that allows the rescue from the versions after 17 that also works with 3d access that should also install you for free.

When the v20 came out there were still permanent licenses, it's possible that they updated them for a long time.
I find the v20 much improved in the table environment and generally as a user interface even in 3d, the only annoying regression is that the command "checks distance" very often returns quite imaginative results.

 

[rapa]

When the v20 came out there were still permanent licenses, it's possible that they updated them for a long time.
I find the v20 much improved in the table environment and generally as a user interface even in 3d, the only annoying regression is that the command "checks distance" very often returns quite imaginative results.

I think update to 20.0 is annually licensed