Re: [osg-users] Falling off the NVidia fast path

Hi Chris, I just wanted to follow up and note that GL_RGBA16 seems to have been the culprit. GL_RGBA16F_ARB performs fine. Have a look at this. It's an older version of the NVidia GPU programming guide, but it (and the newer version at the following link) has lots of good info. http://d

Re: [osg-users] Falling off the NVidia fast path

I just wanted to follow up and note that GL_RGBA16 seems to have been the culprit. GL_RGBA16F_ARB performs fine. I don't get what's so unsupported about basic GL_RGBA16, but OSG dislikes it AND Nvidia Quadros dislike it. -- Chris 'Xenon' Hanson, omo sanza lettere. xe...@alphapixel.com http:/

Re: [osg-users] Falling off the NVidia fast path

Hi May be using some specific blendfunc\op or logic op can cause this. Some glsl code on older hardware (f.e. indexing into array with non-constant index)You can try to strip your shaders to basic ones to check if they cause problems, and turn off rasterization specific state one by one Cheers 22.0

[osg-users] Falling off the NVidia fast path

I'm doing my 16-bit RTT work with GL_RGBA16 successfully now, though osg::Image doesn't like it much (I avoided the problem). However, recently, I've made some change that knocked me off the fast path onto software rendering(!) on some older hardware. My GTX 560M is just fine, but a Quadro FX 270