Think I saw that one around, but just was thinking making it a nice report.
Looks like with quite a few shaders we can end up with nil techniques(specially when moving around renderers). All compiled properly, just a red nil technique enum.
It looks like to happen a bit random (never the same one getting red).
It’s definitely not related to gfx memory (had it with like 5-6 texturefx, which is nowhere near 1gb on my graphics card). Moving renderer across screen make it easier to happen tho (but even without still does).
Quite hard to reproduce as well, but a few texture fx generally does the job.
Quite a pretty annoying bug (quite a show killer sometimes really), so would be good to have that one sorted.