Hi Maciej,
This is very likely to be an ATI driver bug. It may be saying that it
supports FBO's but totally screws them up.
Robert.
On Tue, Feb 10, 2009 at 10:32 AM, Maciej Krol <mack...@gmail.com> wrote:
> Hi all,
>
> I am testing trunk OSG on older devices. I've noticed that osgTerrain
> crashes on ATI 9550/X1050 Series driver version 8.561 on WinXP. To make it
> run I had to comment out geometry->setVertexBufferObjects(true) in
> osgTerrain\GeometryTechnique.cpp:668. Further investigations revealed the
> same problem when simple osg file with useVertexBufferObjects TRUE is
> loaded. The osgviewer crashes and following stack trace is generated:
>
> atioglxx.dll!691ae750()
> [Frames below may be incorrect and/or missing, no symbols loaded
> for atioglxx.dll]
> atioglxx.dll!691aec03()
>> osg55-osgd.dll!osg::DrawElementsUShort::draw(osg::State &
>> state={...}, bool useVertexBufferObjects=true) Line 184 + 0x29 bytes
>> C++
> osg55-osgd.dll!osg::Geometry::drawImplementation(osg::RenderInfo
> & renderInfo={...}) Line 1557 + 0x38 bytes C++
> osg55-osgd.dll!osg::Drawable::compileGLObjects(osg::RenderInfo &
> renderInfo={...}) Line 467 + 0x13 bytes C++
>
> osg55-osgUtild.dll!osgUtil::GLObjectsVisitor::apply(osg::Drawable &
> drawable={...}) Line 78 + 0x16 bytes C++
> osg55-osgUtild.dll!osgUtil::GLObjectsVisitor::apply(osg::Geode &
> node={...}) Line 52 C++
> osg55-osgd.dll!osg::Geode::accept(osg::NodeVisitor & nv={...})
> Line 39 + 0x41 bytes C++
> osg55-osgd.dll!osg::Group::traverse(osg::NodeVisitor &
> nv={...}) Line 62 + 0x25 bytes C++
> osg55-osgd.dll!osg::NodeVisitor::traverse(osg::Node &
> node={...}) Line 191 + 0x1c bytes C++
> osg55-osgUtild.dll!osgUtil::GLObjectsVisitor::apply(osg::Node &
> node={...}) Line 36 + 0xf bytes C++
> osg55-osgd.dll!osg::NodeVisitor::apply(osg::Group & node={...})
> Line 86 + 0x13 bytes C++
> osg55-osgd.dll!osg::Group::accept(osg::NodeVisitor & nv={...})
> Line 38 + 0x41 bytes C++
> osg55-osgViewerd.dll!osgViewer::Renderer::compile() Line 284 +
> 0x36 bytes C++
> osg55-osgViewerd.dll!osgViewer::Renderer::draw() Line 389 + 0xf
> bytes C++
>
> osg55-osgViewerd.dll!osgViewer::Renderer::operator()(osg::GraphicsContext *
> context=0x01f4f0b8) Line 693 + 0xf bytes C++
> osg55-osgd.dll!osg::GraphicsContext::runOperations() Line 688 +
> 0x33 bytes C++
>
> osg55-osgd.dll!osg::RunOperations::operator()(osg::GraphicsContext *
> context=0x01f4f0b8) Line 135 C++
> osg55-osgd.dll!osg::GraphicsOperation::operator()(osg::Object *
> object=0x01f4f0b8) Line 50 + 0x19 bytes C++
> osg55-osgd.dll!osg::OperationThread::run() Line 413 + 0x26
> bytes C++
> osg55-osgd.dll!osg::GraphicsThread::run() Line 40 C++
>
> ot11-OpenThreadsd.dll!OpenThreads::ThreadPrivateActions::StartThread(void *
> data=0x01f55e7c) Line 116 + 0xf bytes C++
> msvcr80d.dll!_callthreadstartex() Line 348 + 0xf bytes C
> msvcr80d.dll!_threadstartex(void * ptd=0x01f598c8) Line
> 331 C
> kernel32.dll!7c80b683()
>
> I suspect lack of FBO support on this particular card. I've tried to locate
> spot where FBO support is tested but didn't find anything. Has anyone had
> similar problems on older cards?
>
> Regards,
> Maciej
>
> _______________________________________________
> osg-users mailing list
> 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
