Hello Crasten,
I've tried to create a log file with the required information.
https://rapidshare.com/files/2820035417/log.zip
I've added a CreateInstance comment to the log whenever we create a new instance..
7 geometries are used for each instance, the ids are:
id 831 glid 20
id 833 glid 21
id 835 glid 22
id 837 glid 23
id 841 glid 24
id 843 glid 25
id 839 glid 26
Hope this helps,
Michael
Gesendet: Donnerstag, 11. April 2013 um 23:26 Uhr
Von: "Carsten Neumann" <[email protected]>
An: [email protected]
Betreff: Re: [Opensg-users] OpenSG1.8 - Object re-initialization
Von: "Carsten Neumann" <[email protected]>
An: [email protected]
Betreff: Re: [Opensg-users] OpenSG1.8 - Object re-initialization
Hello Michael,
On 04/11/2013 04:47 AM, Michael Raab wrote:
> What I investigated is that during the problematic frame the display
> lists for the geometry cores of the created object are newly
> created/compiled. In my opinion this should not be necessary.
agreed.
> The cause
> is a "re-initialize" operation in OSGWindow::validateGLObject() line 685.
Yea, although the underlying issue is that the geometry gets marked for
re-initialization and where that comes from.
Could you send a debug log (i.e. OSG_LOG_LEVEL=DEBUG) from a run where
this happens, that way the Window reports when it updates GL objects.
If you run under a debugger you may want to set a breakpoint in
Window::reinitializeGLObject(UInt32 glId), conditional on the glId of
one of your geometries.
Cheers,
Carsten
------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
On 04/11/2013 04:47 AM, Michael Raab wrote:
> What I investigated is that during the problematic frame the display
> lists for the geometry cores of the created object are newly
> created/compiled. In my opinion this should not be necessary.
agreed.
> The cause
> is a "re-initialize" operation in OSGWindow::validateGLObject() line 685.
Yea, although the underlying issue is that the geometry gets marked for
re-initialization and where that comes from.
Could you send a debug log (i.e. OSG_LOG_LEVEL=DEBUG) from a run where
this happens, that way the Window reports when it updates GL objects.
If you run under a debugger you may want to set a breakpoint in
Window::reinitializeGLObject(UInt32 glId), conditional on the glId of
one of your geometries.
Cheers,
Carsten
------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
