FYI (SOLVED) -- blocks inserting at grossly incorrect scale
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Just a quick note. Apologies in advance if this has been discussed somewhere else... I could not find it in the forums (nor via Google).
Alternate title: Bit in the ass by 0SNAPZ (again)...
Problem description: When inserting blocks into a drawing, after snapping to a NODE location, opportunity to specify scale was not given... symbol was inserted at an ungawdly large scale.
Solution: Checked OSNAPZ setting. It was 0. Setting OSNAPZ to 1, and then inserting the block worked as expected: select location for insertion, then use mouse (or keyboard) to specify scale.
Background: I had completed most of a 3 acre topographic site plan. But needed to go back to the field and locate more trees that my client had specifically requested. Yesterday morning I spent a few hours on the drawing. I had previously shot each tree with two shots: one shot at the trunk, and a second shot at the field observed drip line. I could insert TREE3C blocks for a pine tree no problem by snapping to a survey point NODE, then pulling the mouse until the tree block drip line was roughly at the DL (dripline) observation point. All good.
Then I went to the field and shot everything the client wanted. Came back to the office and proceeded to edit that day's shots into an ASCII point file (for that day only), then import the points into the survey database just as I had done the previous three days. BUT, when I went to insert the tree blocks at my new points... the first sign of trouble was the symbol was NOT scaling uniformly -- it was scaling the X-direction first. I fought with that for a while, and finally did something (what it was, I do not know0 that got C3D from scaling X first. BUT... then when I inserted the TREE3C block at the tree location by snapping to NODE... the tree was coming in at a HUGE size. Inspecting the block properties, I noted that the X and Y scales (possibly also Z) were almost identical to the elevation. (First hint, but I didn't pick up on it.) But not identical -- they different in at least the thousandths and ten-thousandths decimal points (possibly the tenths and hundredths, but I don't recall.)
At this point I started searching Google and this forum, with no success.
I did notice that inserting a TREE3C block by just clicking on a point in the model window resulted in the block inserting as one would expect, and I could specify the block size by dragging the mouse, then clicking, then dragging to affect block rotation, then clicking.
It finally dawned on me that this *might* be OSNAPZ related. Sure enough, OSNAPZ was set to 0. Perhaps I had restarted Civil3D at some point yesterday, and OSNAPZ had defaulted to 0. I dunno.
But with OSNAPZ set to 1, I was able to insert all the TREE3C blocks I wanted by snapping to a survey point NODE and dragging the mouse to specify block size.
Hopefully this writeup helps someone in the future, and perhaps, just perhaps, saves the lives of a few keyboards.
FWIW.