Well, I did further tests and I see the problem even if virtually all my
code is commented out (leaving only the VRJuggler kernel and the OSG
rendering alive). Since I run in "simulator" mode with VRJ, it normally
displays the green wand icon. Well, when the problem happens, it doesn't
render either, that tells me that VRJ own OGL rendering is not happening
either. This being said, it doesn't stop the normal flow inside the
application as I can break in my update routines. So it still goes
through all the normal flow of events but something really bad happens
at the rendering stage. This would let us think that OSG is probably
involved in the problem as it does most of the OGL rendering tasks, or
does it? It is also a strange coincidence that an OSG version change
(where lib3DS has been modified) causes this bug to appear. So far, the
bug is only contained within 3DS file loading, not FLT files. Could it
be that the resulting internal format of the loaded vertices has become
incompatible with VRJuggler OGL rendering routine formats? Could we try
to link the old lib3DS code within the new OSG 1.2 code? Would it be
compatible?
I had been thinking about a possible interaction with VRJuggler as I add
seen a few others complain about JPG textures loading problem if I
recall correctly. These problems appearance coincided with the OSG 1.1
release as well. It seems to me that there is a definite interaction
between the new 3DS handling in the OSG code with VRJ. When it starts
endlessly looping, if I break, I am always in VRJ code. Is there a race
condition or something having to do with VRJ and OSG threads fighting
over each other, I don't know. By the way, I think I noted some code
change in OSG about mutexes… can that be related to a VRJ render thread
being paralyzed by something from OSG?
VRJuggler alone works. OSG alone works. Who is doing something wrong,
hard to say...
Let us know if you people out there find other clues into this. I'll
post new findings as I make progress. This is definitely a show stopper
for me as I rely heavily on the 3DS format and need new functionalities
of OSG 1.1+ at the same time. I do not know if this is a rare occurring
bug as few seems to have seen it, but I feel the more we let it go, the
more it becomes a time bomb monster that will get worse in time.
Thanks Frédéric and the others.
--
=====================================
Marc Bernatchez
Candidat au Ph.D.
Ecole Polytechnique de Montreal
Montreal, QC, CANADA
=====================================
Virtual Reality web site, VResources:
http://vresources.org
=====================================
Date: Tue, 26 Sep 2006 13:03:09 -0400
From: "Drolet, Frederic (LTI)" <[EMAIL PROTECTED]>
Subject: RE: [osg-users] Problems loading 3DS files since OSG 1.1
To: osg users <[email protected]>
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain
Hello Marc,
I have the same problem here. I didn't test OSG 1.2 however since I kept the
1.0 version because of this bug. I tested it on Windows XP with VR Juggler
2.0.1 and OSG 1.1. Like you, it doesn't work with VR Juggler but it works
with OSG viewer. What I think is that OSG changed since version 1.0 and that
VR Juggler is doing something incompatible with the new code. Even if there
is a new version of VR Juggler, it doesn't seem to resolve the problem.
I already posted a message in the VR Juggler community about this but you
should do it too.
See ya!
Fred
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
