Scale problem after dwg import

Daryan

I import a dwg file.
The imported model is 100 times too big, I've reduced by a factor of 100 with the scale tool.
Now i have two problem:

Texture map the model with a factor of 100. It's weird, when I measure the height of a wall it is well 2m70. But that applies to texture correctly I must give a height of 270m ....
At the display I have a bug that when I zoom a little over an area the elements gradually disappear as I approach. It is a known bug that I already had with other models, but I can not remember how I do to solve it.

Thank you very much for your help,

TIG

When you import a DWG there's an Options button click on that to change things - like the original units in the CAD file.
Unless the originator has told you you might have to guess... You already know it's 100 'wrong' so change your units from m to cm [or vice versa ?] and reimport - then there's no need to 'scale' anything...

Daryan

I totally agree with you, I would have thought. Now the problem is that I have already worked a dozen hours about this file, and I prefer not having to reimport the file and start over.

The scale of the textures is not dramatic, I can manually multiply by 100 the scale of each texture. But what bothers me most is the display bug.

TIG

The display bug is a known issue if your model is miles away from the origin.
If you imported it without changing the options it may have preserved the CAD model's origin which can be located ridiculously far from [0,0,0].
To fix it later do this...
Make sure you are in the Model context and not editing a group or component.
You will have a point in the center of the model, that you want to be at the ORIGIN.
If it is a vertex in the model remember this as the 'marker', otherwise add a temporary line as a 'marker' so its end will eventually be placed at the ORIGIN.
Tools > Axes to switch on the axes if they are not already 'on'.
Right-click over an axis line and 'reset' if the option is available [this ensures we are using the proper model-axes and not some custom-axes]
Layer Browser > switch all layers to 'visible'.
View > Hidden Geometry 'on'.
This is so we will Move everything.
Edit > Select All.
Activate the Move Tool.
Orbit until you can select the 'marker' point you chose or added earlier.
Now Move everything - either snap the selected 'marker' to the axes crossing point [0,0,0] at the ORIGIN.
OR if it's miles away an easier option might be to type [0,0,0] in the VCB + <enter> to auto-move it to that absolute position [Note: if your locale uses ',' as a decimal-separator (i.e. you'd normally enter 1,234m rather than 1.234m) then use ';' as the x/y/z separators instead... Also note that using square-brackets [x,y,z] moves to an absolute point as we want here, whereas using pointed-brackets <x,y,z> moves relative to the first picked point - and that's NOT what you want to do in this case]
De-select all.
Erase the temporary 'marker' if its no longer needed.
Check that you haven't left anything behind by using zoom extents.

Another cause of such 'clipping' issues is components which have their origin miles away from their geometry.
The DWG import might be such a component OR its sub-components might have been sloppily blocked in CAD with strange origins...
Check this too.
Model Info > Components > Show axes.
If any placed components have distant axes select them one at a time and right-click and use the 'reset axes' option, and click a new local axes point with the same red/green as before, BUT located logically 'on' the component. This should not affect any placed instances [unlike moving the contents in an edit], and any further insertions of the component will have it on the cursor using that point.

Your Model is now moved to the ORIGIN and any Component axes issues corrected, so the 'clipping issue' should be resolved too... unless this model is enormous, in which case it might reappear occasionally - then toggle perspective off/on...

Daryan

You are perfectly right ! Thank you for your help, i owe you big time !

I didn't know that each component can have his own origin. I understand now wy "explode component" solve the problem.

icepam

This is an issue that keeps appearing when importing dwgs from Autocad Architecture (need to export from Autocad Architecture as Autocad first, creating multiple components for each x-ref with often weirdly placed, yet common origin for each component).

When testing 3D models and doing come and go between Autocad and Sup, the process becomes really very very tedious.

Is there any way to make a plugin to automate your instructions TIG? in fact i am thinking this could be a simple plugin that explodes and redefines recursively each component in the file, which must exist somewhere, no?

icepam

NEVERMIND, thomthom's Axis tools solves this in an instant!
http://forums.sketchucation.com/viewtopic.php?f=323&t=30508&p=267844&hilit=%5BPlugin%5D#p267844