DDPType Absolute Size setting not consistent between stations

DDPType Absolute Size setting not consistent between stations

murmanator
Advocate Advocate
760 Views
4 Replies
Message 1 of 5

DDPType Absolute Size setting not consistent between stations

murmanator
Advocate
Advocate

I have a drawing template with points saved in blocks and the point size is set to an absolute unit. When drawings are started from this template, some of the work stations in our office maintain the point size but others do not and show the points at an enormous size. What am I missing here, is there a preference setting or some other parameter that needs to be changed?

Thank you, Matt

0 Likes
761 Views
4 Replies
Replies (4)
Message 2 of 5

Alfred.NESWADBA
Consultant
Consultant

Hi,

 

>> When drawings are started from this template

Sounds strange, the only idea I have is to compare the settings in _OPTIONS ==> User Preferences ==> both untis settings.

That might be the source of the problem in case your blocks or your template are defined as unitless.

 

2015-12-05 12-30-40.png

 

- alfred -

------------------------------------------------------------------------------------
Alfred NESWADBA
ISH-Solutions GmbH / Ingenieur Studio HOLLAUS
www.ish-solutions.at ... blog.ish-solutions.at ... LinkedIn ... CDay 2026
------------------------------------------------------------------------------------

(not an Autodesk consultant)
0 Likes
Message 3 of 5

dbroad
Mentor
Mentor

I suggest that the only point entities that you put in blocks be on layer defpoints, where they belong.  If you want the blocks to appear to look like points, draw them that way, or use shapes that look like blocks.

 

Are the problem blocks annotative by the way?  I suspect so.

Architect, Registered NC, VA, SC, & GA.
0 Likes
Message 4 of 5

murmanator
Advocate
Advocate

Thank for your replies, guys. I checked the blocks and they are unitless and NOT annotative. I am checking all of our user preferences now...

0 Likes
Message 5 of 5

murmanator
Advocate
Advocate

Well I think we figured out a workaround. By setting up a LISP function to set the PDMODE to .1 it seems to have fixed the issue.

0 Likes