slipher
slipher
> This looks more like the results I've gotten before due to GL errors. What do you mean, what kind of errors?
It's the bitness. If you run 32-bit Daemon it poisons the cache for 64-bit Daemon and vice versa. Perhaps this bug was already there but I never noticed it because...
Bitness is not the only way. I get the same thing with the following procedure on a Windows Optimus machine: 1. Delete `glsl` cache from homepath 2. Start Unvanquished 0.55.3...
The Nvidia vs. Intel issue, at least, is a regression in ab59550f23b41ea80b2443c72c9ce35fce1a7cb4. This commit comments out the driver sameness check.
References to the cvar should be removed from the preset files. It doesn't make sense to set a variable to the same value in all presets; it should just be...
> But we need to provide the user an easy way to reset it to the new default values, re-applying a preset is a good way to do that for...
As discussed in #1600, instead of just having ~no effect, SSAO with material system can also cause bad artifacts in certain configurations. With dummygame and AMD hardware I get this:...
With Mesa. With `r_ssao -1`, the SSAO lines blink on and off with varying frequency. I.e. sometimes it draws the lines, sometimes it is all white.
This is still a desirable feature. I believe the booster currently has the most oblong bounding box of those which can be built on walls. 
Can you still reproduce this? It seems implausible as the demo only writes entities that came from the network.