Created attachment 43291 [details]
There should be roughly spherical glow around candles and fires in Unigine Sanctuary (at least that is how it looks with NVIDIA when the same settings is used), but with r300g it is distorted and displaced and can only be viewed from some angles. Also it is completely gone when RADEON_DEBUG=noopt or RADEON_NO_TCL=1 is used.
Sanctuary version: 2.3
Unigine settings: all options disabled or set to lowest possible
Created attachment 43292 [details]
output of RADEON_DEBUG=fp,vp and RADEON_DEBUG=fp,vp,noopt
Created attachment 43293 [details]
screenshot with NVIDIA driver
This is how it looks like with proprietary drivers when the same settings are used.
Is this a regression? Any chance you can bisect it?
(In reply to comment #3)
> Is this a regression? Any chance you can bisect it?
No, I don't think so, I suppose this bug is present since Sanctuary 2.3 is working (73e8a2738743035e1347571ba630747d2ec33a2d). I haven't spot this before because this distorted glow wasn't present in the 2.2 version (the glow wasn't present there at all like now when running with RADEON_DEBUG=noopt and there were some others much more visible bugs at that time).
However I'll try to manually apply 73e8a2738743035e1347571ba630747d2ec33a2d to some older mesa versions to see if it was better at some time.
I don't think it ever worked.
The distorted glow is present since "r300/compiler: use peephole and constant folding for vertex shaders too", there was no glow at all before. So I suppose this explains why there is no glow with noopt.
I think the glow is broken because the WPOS input is unassigned. Glow is a screen-space effect and as such must either use (or emulate) gl_FragCoord.
No glow at all with current mesa master and working glow with floating2 branch.
I consider this fixed.