Topic: Zoom state related error with AutoLisp Script

[septicad]

I've made the switch to AutoCAD 2015 vanilla (i run C3D as vanilla), and i tweaked my template file a bit to change default CTBs, some minor formatting the PS layout, in the process i apparently ichanged the zoom level in model space when the template is opened.

The script i have generates a drawing in model space.  But now, I'm struggling to figure out why my AutoLISP script has this funky bug that is dependent on the zoom level. 

OSNAP and ORTHO are toggle off for the entire script and then reset to what they were at the end.   The "WHEN-ZOOMED-OUT.PNG" output is generated when i'm zoomed out... but if i just delete everything, zoom in two or three times (with the mouse roller) and an rerun the script, i get the right output "WHEN ZOOMED IN.PNG".

The simple fix is to just zoom way in and resave the template, but i'm at a loss as to why this issue should be happening at all. 

Note that all of the entities are drawn using command line calls, not VLISP.

Thoughts?
Steve

[ChrisCarlson]

Don't think its related to your script or routine at all. I have the issue where circles (depending on the zoom state) appear to be pentagons or circles. What happens when you "rea" the drawing while it looks all jaggedy?

[septicad]

good idea... but regen or regen all does not help.  if i zoom waaaaaaay in or to what would be the extents of the script output then it works.

if i zoom out to like twice the extents of what the script output would be, the problem begins to occur.  as i continue to zoom out and run script at various zoom levels until the the output is essentially a point on the screen,  the output changes at different zoom levels - this is why i feel like it related to osnap or cursor related somehow?... but how is still troubling me. 

Steve

[roy_043]

@ SeptiCAD:
I think your initial analysis is correct. But without any code a definite conclusion is not possible.

[danallen]

...- this is why i feel like it related to osnap or cursor related somehow?...

check your OSNAPCOORD variable?

[septicad]

setting OSNAPCOORD to 1 fixed the problem..  didn't even know that sysvar existed.
THANK YOU! danallen
Steve