Hi Jer,

Its really difficult to guess what might be at miss.  I doubt its
related to normal in any way, or even the 3DS plugin, this is likely
just a symptom of problems elsewhere.

As an experiement try reading the models during the update phase, i.e.
directly before or after the update() traversal, rather than in a
seperate thread.  The performance will be awful but it may well shed
some light at what is amiss, if not, it at least illiminates one of
the variables.

Robert.

On 8/6/06, J Chapman <[EMAIL PROTECTED]> wrote:

I'm using osgDB::readNodeFile() to load 3DS files, adding them to the root
Group node of my osgUtil::SceneView, and then rendering them in a 3rd party
OpenGL program.  Everything works great with the files loaded and added to
the scene graph before the first rendering pass when I call update(),
cull(), and draw().

The problem is that I also have a separate networking thread which services
requests to add new models to the scene graph.  Although the new 3DS files
seem to load correctly, they are never rendered in the scene.  The problem
appears to be related to per-vertex normal shading in lib3ds
ReaderWriter3DS.cpp.  When I build OSG with _usePerVertexNormals == false,
the new models are visible.  But with
_usePerVertexNormals == true (the default setting in the distribution), the
new models are not visible.  Models loaded before my first frame are always
visible in both cases.

I'd obviously like to use the per-vertex normal shading because it looks
better.  Any idea what's causing this or how I could work around it?

Thanks,
Jer


 ________________________________
Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great rates
starting at 1ยข/min.


_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/


_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/

Reply via email to