You could obfuscate and minify your shader:
https://github.com/laurentlb/Shader_Minifier
Or hire a demoscene person to mangle it. ;)
On Thu, Jan 31, 2019 at 11:43 AM Werner Modenbach
wrote:
> Hi Michael and all other people responding to my request,
>
> first of all thank you very much!
>
>
Hi Michael and all other people responding to my request,
first of all thank you very much!
@Michael: What you suggest is something like asking Zuckerberg to
publish his algorithms.
And belief me, Chinese don't care at all about patents
or other rules we usually accept here.
I'm
Hi.
You may have a look at the problem from a different angle. If someone
is stealing from you that means they need it. If you cannot stop it
(or it costs much more than simply let them have it), then you should
lead it. Instead of hiding your great shaders you can publish them
yourself (don't
Hi,
I don't know what the OSG solution to this would be.
You could obfuscate the shader code. Though to be honest this would only
slow someone down not stop them from obtaining the shader source.
In addition to obfusication put the shader source into the DLL/exe and
potentially hide the strings
Hi Werner,
You can compile shaders into source, the osgText, osgVolume and
osgParticle NodeKits all have local shaders directories i.e
src/osgText/shaders. The .cpp files found in these shaders directory
are generated from shaders found in OpenSceneGraph-Data/shaders, and
converted to ,cpp's
Dear Robert, dear community,
I use OSG since many years now with great success. But being honest I
usually just use the osg api and direct gl calls are very rare in our code.
That's the reason why I ask people with more gl experience here.
I'm working in a commercial environment. Unfortunately we
6 matches
Mail list logo
