Hi Jason,
Good to hear you've tracked down the problem. W.r.t the crash, I
think we need to start drawing up extension disable lists for
different hardware/drivers profiles, and have some formal system for
it so we can better cope with hardware claming to support
extensions/OGL features but
Hi Jason,
It does sounds like you are hitting problems with texture download.
When using osgTerrain the texturing should be the same as when using
just osg::Geometry/osg::StateSet based paged databases. The only
difference I can spot would be the setting of anisotropic filtering on
the textures,
Hi Robert,
I noticed that anisotropy setting as well and tried commenting it out and it
didn't have any affect. Still large hiccups when downloading textures using
--terrain. Looking at the memory usage of my app in the Intel driver's
control panel says that it has a max of 128 mb of memory,
Hi Jason,
It would be worth bringing up the viewer stats to look at the update,
cull, draw dispatch times. My expectation is that its draw dispatch
is stalling due to the graphics driver, but it would still be worth
checking.
Another thing you could try would be to rebuild a osg --terrain
Hi Robert,
I finally figured out the issue I was having. I was passing in
--no-mip-mapping to osgdem to compensate for the ATI compressed textures
issue that existed before their drivers got updated. Removing the
--no-mip-mapping argument caused the performance to be great on the
machine. I
Hi all,
More integrated graphics woes for me today. I'm working with an Intel 945GM
graphics card and trying to load a terrain database generated with
--terrain. Robert, your suggestion of disabling VBO programatically worked
great for getting the machine to stop crashing. For some reason, the
6 matches
Mail list logo
