With the recent FG, both Linux self-compiled and Jenkins for Windows, I no
longer get compilation errors from the shaders thrown to the console - badly
formed shaders just don't work without complaining. This makes developing a
bit awkward now and will make it close to impossible to trace
On 29 Apr 2013, at 07:54, Renk Thorsten thorsten.i.r...@jyu.fi wrote:
Does anyone have an idea what may have caused this, and if so would it be
easy to put the error messages back in?
When did it break?
I did some work right after 2.10 to support custom logging, and one thing I
started
If this is the cause, it's been that way since January, and I assume you
would have compiled from source since then.
I still have the funny GPU problem under Linux that the GPU refuses to go to
high performance, so I don't actually develop shader code under Linux but use
it just to
On 29 Apr 2013, at 10:09, Renk Thorsten thorsten.i.r...@jyu.fi wrote:
I still have the funny GPU problem under Linux that the GPU refuses to go to
high performance, so I don't actually develop shader code under Linux but use
it just to interface with GIT and do quick tests. I update the
4 matches
Mail list logo
