[r1156]Bug: HOM Heaven!

[Graf Zahl]

It just confirms that ATI's driver has a bug. One, btw, I ran into years ago in a completely different situation. Back then I also couldn't explain why a certain thing did not work.

Seems to be par for course for them though. If ATI's drivers have crippling bugs in their GL implementation it's unlikely they won't fix them. Now I have to find a way to work around this...


Can you try again with this build?

[Tiger]

Can you try again with this build?

Tested it with Catalyst 10.12 drivers, and it works for me.

[Graf Zahl]

Ok, thx.

I don't understand ATI. If something isn't anally stated in the GL specs you can be sure they implement it wrong - almost as if it is on purpose...


Here's another test.. I removed some fudging code that tried to work around the other problem I mentioned. I hope with the new information this can be addressed, too, now

[Tiger]

Here's another test.. I removed some fudging code that tried to work around the other problem I mentioned. I hope with the new information this can be addressed, too, now

So far everything is working fine on that build aswell.

[Graf Zahl]

Ok, thst means the change is working. You should have seen the problems immediately when starting a level.

[Tiger]

You should have seen the problems immediately when starting a level.

Everything seemed normal for me, and even with a fresh INI.

---

Screenshot_Doom_20110107_023752.png

[Nash]

Thanks for fixing this, Graf... so what exactly happened, if I may ask?

[Graf Zahl]

On ATI the texture matrices were not initialized to the identity matrix by default, contrary to any sane expectation (Note: Trust ATI do do the stupid thing if the GL spec is not anally clear about such issues. .) And I hijacked one of those to handle radial fog for models to eliminate some code that wouldn't have worked with voxel models due to their high vertex count. So the matrix was 0 and all geometry being multiplied by it just went into a black hole at coordinates (0,0,0)...

[Salad Viking]

Oh, good, thank you for the fix, Graf. Why does ATI seem to hate you and OpenGL so much? It's not like there's some kind of advantage to be had by not supporting it.

[Graf Zahl]

I have no idea. ATI is well known for following the GL spec to the letter, meaning if something is left undefined it really is undefined on ATI, if something is ambiguous they generally choose the wrong solution. And if something doesn't make any sense they implement that anyway, even if it only causes problems.

Which would all not be that bad if their driver wasn't also so much slower than NVidia's...