Hi Alessandro,
OK, this shader is a default provided to at least give something to
render. osg::DisplaySettings::ShaderHint is what controls the
addition of this fallback, in a GLES build it defaults to GLES2 or
GLES3, you can override this and switch it off via:
I did some more tests, tried to remove that 'program' from
StateSet::setGlobalDefaults () and I realised that, at last, that very program
is really not tried to be linked at all (it looks like the attached shaders are
not even compiled, but I'm not 100% sure).
So, I cannot say that the error
Hi Alessandro,
I would recommend doing the tests on a desktop system and manually
select GLES builds, this should make it easier to go through the
various possibilities.
I would also recommend use git master if you aren't already. At least
that way if you come across bugs then we can get them
Hi Robert,
and thanks again for your help and suggestions. I'm aware of the remapping done
by OSG under the hood, indeed I had no issues with this when targeting GLES 2
with version 3.4.0.
I investigated my issue further and found out that a osg::Program is added to
the scene graph by the
Hi Alessandro,
I tested the models under my GL2 build of the OSG and the dump1.osgt
worked fine for me without any errors. I don't have time to test GLES
right now.
The vertex shader doesn't provide any hint for the precision, it might
be the the GLES drivers GLSL compiler is having an issue
5 matches
Mail list logo