Hot on the heels of 0.3, here's 0.4! @_Ninji and @simonkosua both investigated the remaining glitch, unprompted, and found that rearranging shader code in completely meaningless ways eliminated the problem! Thank you both so much! And thanks, Intel; great drivers you've got there.