Change language evaluation order in RTSS?

[d000hg]

http://www.ogre3d.org/forums/viewtopic. ... 28#p457014

I think trying to choose native languages first is generally better; it also means the RTSS works on iOS with Cg support enabled...

Code: Select all

	if (hmgr.isLanguageSupported("cg"))
	{
		mShaderLanguage	= "cg";
	}
	else if (hmgr.isLanguageSupported("glsl"))
	{
		mShaderLanguage	= "glsl";
	}
	else if (hmgr.isLanguageSupported("glsles"))
	{
		mShaderLanguage	= "glsles";
	}
	else if (hmgr.isLanguageSupported("hlsl"))
	{
		mShaderLanguage	= "hlsl";
	}
	else
	{...

The fact Cg is pretty much not working at all with HLSL2GLSL on iOS is another bug but regardless, using RTSS to build shaders which then have to be converted into a native format just seems ugly!

[d000hg]

There's a bug-issue for this now: http://www.ogre3d.org/mantis/view.php?id=555

In my tests, even in Ogre 1.8.2 RTSS is broken with iOS/GLES2 using the standard iOSDependencies download.

[masterfalcon]

Do keep in mind that Cg support for GLES2 is experimental in 1.8 and not guaranteed to work.

[d000hg]

Unless I have things backwards (very possible) that's kind of my point... if it chooses glsles in preference to Cg, it doesn't rely on Cg support for RTSS. As it is now, RTSS generates Cg which then gets converted using hlsl2glsl, right? Whereas in my tweak, it would generate glsles directly.

Obviously for actual Cg shaders that's a different story, but it's quite possible I'd write proper glsles shaders and still want to use RTSS for simple materials.

[masterfalcon]

Yeah I suppose so. I guess then it would basically never use Cg for GLES2. Cg would only really be supported for non-RTSS generated programs. I see that logic better now.