Thread

IGES import problems.

About Truespace Archives

These pages are a copy of the official truespace forums prior to their removal somewhere around 2011.

They are retained here for archive purposes only.

IGES import problems. // Bugs

1  |  

Post by jamesclark // Jun 24, 2008, 11:41pm

jamesclark
Total Posts: 3
I have some IGES files that I need to import so I can do some rendering in TrueSpace.


Using the Conversion pack, and TS 7.51, I am having some problems and it looks like the importer is not working at all well. For one of the objects, I have attached two screenshots to show some of the problems.


Firstly, if I import as "original size", the object seems to split itself into two parts. One is solid, the other is wireframe! And sub-selection in one of these also selects the corresponding part in the other object... as if they are twins. (Note when importing as original size, the objects seem very small and need to be scaled x100 to be a useful size.)


Then, if I import as "scaled to screen" the object looks better with these "twins" combined. But there are still problems. Some patches are missing as can be clearly seen in the images. And there are various "construction" lines -- though these disappear when the object is moved into the workspace.


I just want to be able to import the IGES files at their original size and the object in truespace to look like they should, with no missing patches, flipped normals, etc. Is the IGES importer just not very good?

Post by TomG // Jun 25, 2008, 2:58am

TomG
Total Posts: 3397
There is a problem in the Model side with the real-time view - if you zoom in close (as you would need to do with a small object), the wireframe and the solid render become "detached". There is only one object there, and if you render using Lightworks you will see only one object, but the real-time view will show the solid view and the wireframe view in a separate location. This is a known DirectX limitation with being zoomed in (for old DirectX). This does not happen on the workspace side.


So there is nothing wrong with the IGES import there, that's just the Model side real-time view for small objects when you zoom in. You could just scale the object up and not zoom in as much, or use the workspace.


The other issue looks like normals facing the wrong way - to test, you could select the face where it appears like it is "missing" and then use a Flip Normals tool. Before doing that I would in fact try an offline render, in case the face is fine and the real-time engine is just drawing it wrong. You could also try viewing in workspace, since (as noted with the previous problem) the workspace real-time engine is much better than the Model side.


If indeed the faces do not show up, then flipping the normals for those faces will probably solve it. If not, then you may need to simply add the face in using Form Face on the workspace side, or Add Face on Model side.


HTH!

Tom

Post by jamesclark // Jun 25, 2008, 5:32am

jamesclark
Total Posts: 3
I know about the problem when you zoom in, but I don't think this is what I am describing. The screen-shot shows the object after I have scaled it x100. And you can clearly see that some wireframe is correctly positioned around the solid object, but other parts aren't!


Is it possible that because the object started off small that this DirectX issue has propagated to the object itself, not just a display issue?


The faces seem to be missing. I did try fixing the normals, but the faces don't appear to be there. They are not there when rendered in Lightworks. Nor are they in the workspace. Moreover, if I convert the object to polys (it is imported as nurbs patches), all hell breaks loose with lots of polys having incorrect normals. But even then, the original missing patches are still missing.

Post by TomG // Jun 25, 2008, 6:38am

TomG
Total Posts: 3397
With NURBS, which are mathematically generated "on the fly" it could be that whatever causes the zoom separation happens even with the scaled up object.


Unfortunately I never work with NURBS much, nor IGES at all. There may well be NURBS and import settings in tS, or export settings in the other application, that could play a role. I'd need to ask if someone with some more experience in this area could comment and advise.


HTH!

Tom
Awportals.com is a privately held community resource website dedicated to Active Worlds.
Copyright (c) Mark Randall 2006 - 2024. All Rights Reserved.
Awportals.com   ·   ProLibraries Live   ·   Twitter   ·   LinkedIn