Tree Inserting

[Rich Rosemann]

A little while ago I inserted a few nXt trees into my model.  They all came in one or two feet high.  I had to scale them 20 times or so to get them to a reasonable height.  I checked my units (insunits - 1) and insert scale (inches).  Am I missing another scale variable that controls the tree insert?  I don't remember having to re-scale all trees I inserted before.  The trees are about 1000 feet from the 0,0.  Is this too far?

Latest nXt version.

 

RIch

 

[Roy Hirshkowitz]

It's definitely a sign that something is wrong.  Try setting INSUNITS to 2 and back to 1 to see if it makes a difference.

[Rich Rosemann]

I'll try that, Roy.  I should have thought of that after reading the earlier reply on scale problems.

 

Rich

[Rich Rosemann]

Hi Roy

 

I was able to get back to the tree problem. again.  i started a new drawing with the insunits set to 2, my normal scale units.  I inserted a few trees with the same result.  The tallest tree came in at about 3 feet high.  These are from the nXt std. tree library.   They look very good except for the face that they are Japanese dwarfs.  If you are having no problems there, I have to be setting a variable wrong.

 

Rich

[Roy Hirshkowitz]

They seem to be working fine here-- with INSUNITS = 2 the Blue Spruce from the nXt lib, for example, is about 31 units high.  

Send a simple drawing illustrating the problem-- I'll take a look.  Even the example above is probably sufficient.

[Rich Rosemann]

I'll send the above drawing Monday morning.  Thanks

 

Rich

 

[Rich Rosemann]

Good morning, Roy

 

I have uploaded the test drawing with the Nxt trees inserting small.

Where am I going wrong.

 

Rich

 

 

[Roy Hirshkowitz]

The INSUNITS are 1 for this drawing.

As suspected-- with nXt loaded-- change INSUNITS to 2 then back to 1.  It should work from then on.  This is very likely due to legacy information (perhaps in the template drawing) that differs from your INSUNITS.

[Rich Rosemann]

Hummmm.  Just when you think you have everything covered.

I think this is likely due to user error, as almost always. 

One more thing to double check.

Thanks, Roy.

 

Rich