Re: [osg-users] Unable to bind a Texture2DMultisample to a StateSet

I have checked in non op getModeUsage() from Texture2DMultisample and Texture2DArray. The same applies to osg::TextureBuffer. I never use setTextureAttributeAndModes() with it. -- Paweł Księżopolski -- Read this topic online here:

Re: [osg-users] Unable to bind a Texture2DMultisample to a StateSet

HI Wojciech, Interesting observation. If GL_TEXTURE_2D_MULTISAMPLE and GL_TEXTURE_2D_ARRAY shouldn't be used with modes it's would be appropriate for us to modify the Texture2DMultisample and Texture2DArray headers to define the getModeUsage() as an empty set rather than let it default to the

Re: [osg-users] Unable to bind a Texture2DMultisample to a StateSet

Hi Robert, define the getModeUsage() as an empty set rather than let it default to the texture target as is the default with the osg::Texture subclasses. It makes sense. Cheers, Wojtek 2014/1/24 Robert Osfield robert.osfi...@gmail.com HI Wojciech, Interesting observation. If

Re: [osg-users] Unable to bind a Texture2DMultisample to a StateSet

On 24 January 2014 10:52, Wojciech Lewandowski w.p.lewandow...@gmail.comwrote: Hi Robert, define the getModeUsage() as an empty set rather than let it default to the texture target as is the default with the osg::Texture subclasses. It makes sense. I have checked in non op

Re: [osg-users] Unable to bind a Texture2DMultisample to a StateSet

HI Frank, Good detective work. GL_TEXTURE_2D_MULTISAMPLE was missing from the TextureGLModeSet singleton found in OpenSceneGraph/src/osg/Texture.cpp, it was obviously missed when Texture2DMultisample was submitted and merged. I have added this and checked it into svn/trunk and OSG-3.2 branch,

Re: [osg-users] Unable to bind a Texture2DMultisample to a StateSet

Thanks very much, Robert! -- Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=57975#57975 ___ osg-users mailing list osg-users@lists.openscenegraph.org

Re: [osg-users] Unable to bind a Texture2DMultisample to a StateSet

Hi again Robert and others, I am now getting a glError that occurs in osg::State::applyModeOnTexUnit. It is trying to pass GL_TEXTURE_2D_MULTISAMPLE TO glEnable, resulting in an invalid enum error. I'm working to track down the source of it, but this is code that I'm less-familiar with so it

Re: [osg-users] Unable to bind a Texture2DMultisample to a StateSet

Hi Frank, I believe that GL_TEXTURE_2D_MULTISAMPLE should not applied as mode. Its the same situation as with GL_TEXTURE_2D_ARRAY. These texture types are only availalble to programmable pipeline. Setup of Texture modes are neccessary for fixed pipeline. GL_TEXTURE_2D_ARRAY should be set only

Re: [osg-users] Unable to bind a Texture2DMultisample to a StateSet

Yes, Wojtek, you are correct. I habitually used setTextureAttributeAndModes. After changing it to just setTextureAttribute, the error goes away. I am getting a black screen still, but that's probably another issue, as you said. Thanks! Frank -- Read this topic online here:

Re: [osg-users] Unable to bind a Texture2DMultisample to a StateSet

Shader bug. I was using sampler2D instead of sampler2DMS. Fixed it now, and it works great! Frank -- Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=57979#57979 ___ osg-users mailing list

[osg-users] Unable to bind a Texture2DMultisample to a StateSet

Greetings, I have a multisampled texture that I've rendered my scene into, and I'd like to attach it to the StateSet of a full-screen quad so I can do some explicit multisampling. Here is the call I am making: Code: fsq-getOrCreateStateSet()-setTextureAttributeAndModes(0, inputTexture,

Re: [osg-users] Unable to bind a Texture2DMultisample to a StateSet

By the way, here is the warning message I'm receiving: Warning: non-textured mode '37120' passed to setTextureMode(unit,mode,value), assuming setMode(mode,value) instead. The value '37120' corresponds to GL_TEXTURE_2D_MULTISAMPLE . I'm not sure if setMode is the desired behavior. I'm only