16
Graphics / Re: Shaders available, no output error, but loading from either file or memory fails
« on: April 04, 2020, 01:12:42 am »
Thank you, yes, fixed. (the fancier original had a capital D there) 'Appreciated.
And, I agree, there should be a compilation error nestled in the build log output somewhere, but I'm not seeing it. Incidentally, another thing I tried was to insert my GLSL attempts into an online sandbox. SFML should output something if I just try and load a non-existent file or empty string, yeah?
So, if this should show me an error, clearly, I'm not looking in the right place for it.
[EDIT:] ... and watching the shader variable, tracing via breakpoints, and watching the progress logged only confirms that, yes, the previous loading operations mentioned fail without mention in (all) console logs and, yes, the data in these is left uninitialized. :\
And, I agree, there should be a compilation error nestled in the build log output somewhere, but I'm not seeing it. Incidentally, another thing I tried was to insert my GLSL attempts into an online sandbox. SFML should output something if I just try and load a non-existent file or empty string, yeah?
// TEST FORCE COMPILATION ERROR MSG
sf::Shader dummy;
dummy.loadFromMemory("", sf::Shader::Fragment);
sf::Shader dummy;
dummy.loadFromMemory("", sf::Shader::Fragment);
So, if this should show me an error, clearly, I'm not looking in the right place for it.
[EDIT:] ... and watching the shader variable, tracing via breakpoints, and watching the progress logged only confirms that, yes, the previous loading operations mentioned fail without mention in (all) console logs and, yes, the data in these is left uninitialized. :\