Thanks Carsten, The patch works and we're up and running again. It was a combination of the hasExtension() routine and the subject of this thread. After correcting those, we can run our applications again (albeit in limited form because of OpenAL and PhysX differences).
As for what might be happening with the hasExtension() routine, I'm wondering if the lists for various extensions are rebuilt per viewport since we only see a problem when using more than one viewport. I will try to do some more testing with this in the next couple of days to see if the current patch has any adverse effects like disabling occlusion culling. Thanks again! E. --- Eric Maslowski Research Computer Specialist University of Michigan 3D Lab Autodesk 3D Studio Max Certified Trainer email: [EMAIL PROTECTED] office: 734-615-9699 mobile: 734-730-9904 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carsten Neumann Sent: Wednesday, September 05, 2007 19:26 To: [email protected] Subject: Re: [Opensg-users] vector <x> iterator not dereferencable - OSG 1.8,VS 2005, Run-time Error Hello Eric, On Tue, 2007-09-04 at 09:35 -0400, Eric Maslowski wrote: > Hello, > Replacing the "vector<bool>" with a "vector<Uint8>" fixed that issue, but > ran into another semi-related one. (see below) First, just want to point out > that there were a few instances of vector<bool> scattered about. Some were: > vector <bool > for formatting purposes. (just in case this gets added to > the standard release) > > As for the other issue, I'm getting a vector out of range now in > RenderAction::start(id). Digging a little deeper shows that it's actually > coming from the "window->hasExtension(_arbOcclusionQuery)." inside > hasExtension(), _arbOcclusionQuery has id of 35, when total count of entries > in list (_availExtensions) is 35. Thus, causing out of range error. This > only seems to happen in a clustered application when using more than one > osg::viewport. (e.g. for stereo rendering) hm, it might be a problem with concurrent access to the extension handling, but this is just a guess. I'll take a look at the extension handling from that angle. > Unfortunately, I don't know enough about how OpenSG handles extensions to be > of much help here, but if someone has a work around/fix, I would really > appreciate it. I imagine it would be possible to paper over the problem, by either finding out how to disable the range checks in the MS STL or use the attached patch (but that might disable an extension, although it is actually available), to get things going. > OpenSG 1.8 (daily build: Sep 2, 2007) > NVIDIA Quadro 5600 (latest drivers) > WinXP 64 Thanks, Carsten ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
