disable unit scaling

[Anonymous]

I've checked and tried suggestions for disabling unit scaling the database - but inconsistent results. I've wasted hours trying to get my template drawings which have worked for years into my drawing session at 1:1, but being scaled to something I don't want. I've set target and destination units in preferences, insunits to 0 in all drawings, measurement and measureinit to 0. suggestions much appreciated.

[Anonymous]

Hey JR;

You've been into the Projects>Drawing Setup>Scale tab by this time correct?

I didn't see it listed in the post, is why I ask.

It will also help to know the version of LDT you're using.

--
Don Reichle
"King Of Work-Arounds"
"The only thing worse
than training your staff,
and having them leave is -
not training your staff,
and having them stay."
Courtesy Graphics Solution Providers
--------------------------------------
LDT3/CD3
IntelP4-2.4
1GB RAM
Nvidia GeForce2 MX 32MB
Western Digital Raptor 10K-rpm HD


wrote in message news:4917702@discussion.autodesk.com...
I've checked and tried suggestions for disabling unit scaling the database -
but inconsistent results. I've wasted hours trying to get my template
drawings which have worked for years into my drawing session at 1:1, but
being scaled to something I don't want. I've set target and destination
units in preferences, insunits to 0 in all drawings, measurement and
measureinit to 0. suggestions much appreciated.

[Anonymous]

LDT Acad 2004 - yes, I've run the Projects>Drawing Setup>Scale. I did not have this problem when we first went to 2004, it just cropped up about a month ago and I've been struggling with it since. The unit scaling screws up my template block drawings and I want it gone.

[Anonymous]

It's even unit-scaling my Block=Block when I update unit block definitions - why would AutoDesk do that? This is a major hassle.

[Anonymous]

Because they can.

Have you done a Search of the Knowledge Base on this issue?

I've seen far more grousing about this issue in 2K6, than was ever mentioned
in 2K4.

Have you considered a Reair? Especially when you relate that it was fine for
awhile, and then went belly-up on you lately.

--
Don Reichle
"King Of Work-Arounds"
"The only thing worse
than training your staff,
and having them leave is -
not training your staff,
and having them stay."
Courtesy Graphics Solution Providers
--------------------------------------
LDT3/CD3
IntelP4-2.4
1GB RAM
Nvidia GeForce2 MX 32MB
Western Digital Raptor 10K-rpm HD


wrote in message news:4918103@discussion.autodesk.com...
It's even unit-scaling my Block=Block when I update unit block definitions -
why would AutoDesk do that? This is a major hassle.

[Anonymous]

I've searched far and wide and implemented the INSUNITS, INSUNITSDEFSOURCE, INSUNITSTARGET* = 0 through our MNL file. Everything appears unitless. The problem is we run on a licence server and I don't have the ready ability to do a repair - the software is not inhouse. Most CAD managers have evaluated 2005 but not installed it across their department, as repair disks are constantly being sent from the corporate manager. I just don't have time for that and am waiting till we are forced to upgrade - perhaps with 2006. I get the impression it sounds like a bigger problem in 2006 - oh joy.

[Anonymous]

The advantage in 2K6 is that there have been successful fixes discovered
already for this issue.

Maybe you do a Search on the WebBrowser side on "block insert" in the 2K6
discussion group?

What they found to work for them, may be applicable to your situation also.

Just a thought.

--
Don Reichle
"King Of Work-Arounds"
"The only thing worse
than training your staff,
and having them leave is -
not training your staff,
and having them stay."
Courtesy Graphics Solution Providers
--------------------------------------
LDT3/CD3
IntelP4-2.4
1GB RAM
Nvidia GeForce2 MX 32MB
Western Digital Raptor 10K-rpm HD


wrote in message news:4918597@discussion.autodesk.com...
I've searched far and wide and implemented the INSUNITS, INSUNITSDEFSOURCE,
INSUNITSTARGET* = 0 through our MNL file. Everything appears unitless. The
problem is we run on a licence server and I don't have the ready ability to
do a repair - the software is not inhouse. Most CAD managers have evaluated
2005 but not installed it across their department, as repair disks are
constantly being sent from the corporate manager. I just don't have time
for that and am waiting till we are forced to upgrade - perhaps with 2006.
I get the impression it sounds like a bigger problem in 2006 - oh joy.

[Anonymous]

Running the Audit command may have fixed the drawing where the settings did not seem to take effect (insunit, target, and source); I did play around with some other settings in the source drawings so I'm not sure, but works for now - otherwise the other drawings I've opened since work as expected with unitless settings.