Hi,

We just tried it on a 32 bit system and had the same incorrect results.

John

On Tue, 20 Oct 2009, Eric Sokolowsky wrote:

I tried out the file below, and I can confirm all of John's results. Since I 
use SGI's Inventor instead of Coin, it appears that the bug is in the Inventor 
plugin, and not Coin. I wonder if it's a problem with 64-bit builds? I have 
been using Centos 5.2/5.3 on a 64-bit machine for a while now, and my previous 
use of Inventor was probably on our old 32-bit machines.

-Eric

On Fri, Oct 9, 2009 at 3:12 PM, John Kelso 
<ke...@nist.gov<mailto:ke...@nist.gov>> wrote:
Hi,

We're running 2.8.2 on a 64-bit Centos system.  OSG was configured to use
Coin-3.1.1.

Not too long ago I ran an old demo using the new releases and noticed that
an Inventor file that used to load properly no longer did.  Checking around,
many others also didn't.

Here's a simple example file that demonstrates the problem:

#Inventor V2.0 ascii
Material { diffuseColor 1 0 0 }
Cone { bottomRadius 1 height 2 }

Rotation { rotation 1 0 0 3.14159 }
Material { diffuseColor 0 1 0  }
Cone { bottomRadius 1 height 2 }

If you look at this with ivview, also linked with Coin-3.1.1, you see two
intersecting cones, red on the bottom and green on the top.

If you load this same file with osgviewer you just see the red cone.

If you use osgconv to create an osg file from the iv file you see both cones
in the osg file with identical vertex data and the green one isn't rotated.
I'm surprised I don't see any z-fighting in osgviewer.

Anyway, can anyone else try loading this Inventor file and see if it works
for them?

Many thanks,

John



_______________________________________________
osg-users mailing list
osg-users@lists.openscenegraph.org<mailto:osg-users@lists.openscenegraph.org>
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


_______________________________________________
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Reply via email to