The second problem is, I only have mentioned 2 variables here. ![]() ![]() The most problem is => you don't see it as long as you don't interchange data with other drawings. That also might not seem to be that much, but at least all you draw based on that wrong ANGBASE will not fit into other drawings (not as exact as CAD has to work). If you have set ANGBASE to 90° (so having the north-direction as angle=0) the SYSVDLG exports this value in radiant (with a lot of decimal places that is 1,5707963.), limiting that now to 2 decimalplaces and reimporting that in another drawing makes the "0°-base" not any more at 90°, but at 89.95°. With double values of any length-options the error is not as big as if you export angular-values. If you import now this SVF-file into another drawing this value ( 0.63) is imported, so it's different/wrong in the destination drawing. ![]() Importing that truncated values then is risky!Īs an example: if the variable DIMEXO is set to 0.625 (what it is by default for metric AutoCAD templates), and your precision is set to 2 decimal places the export writes DIMEXO 0.63. I'm also interesting what sysvar did this solve/was the problem (and what settings), butĪTTENTION:exporting sysvars (using command SYSVDLG) exports double values only with that number of decimal-places defined in the _UNITS dialog => precision.
0 Comments
Leave a Reply. |