[quote=“Sauron|EFG”]
“In high dynamic range rendering (HDR) applications, it is used when the necessary brightness exceeds the contrast ratio that a computer monitor can display.”
I’m well aware that I don’t know what I’m talking about. ;)[/quote]
Please don’t quote wikipedia as an authority on a technical topic, since more often then not, it’s written by laymens or very poorly worded.
Bloom isn’t used because the monitors lack ability to bleed colors. (They all do, and it’s a bad thing.)
Again, might be a bit dumb yet basic question but I’ll ask it anyway. Isn’t HDR DirectX thing? I mean, it mostly requires Shader Model 3.0 which is a feature of DX9? Or is it? (I know it has to be supported by the graphics card also.) And ETQW uses OpenGL, not DX. Not to say it’d be impossible to use HDR with OpenGL, just a bit… strange? I mean, it hasn’t yet been done?
Just a thought…
Anyway, I don’t care whether there’s HDR in the game or not. I care about the graphics overall. (Not to forget gameplay either.)
DirectX and openGL are just APIs. They don’t determine what the hardware is capable of.
OpenGL 2.0 and it’s Shader Language actually provides features that DirectX 10 doesn’t provide (and that actually no hardvare provides yet), especially via it’s extension mechanism, just as DirectX 10 provides some features OpenGL doesn’t provide. For 99% the feature set is identical though. Just the programming model is different. The all deciding question is though, what do the available drivers of the hardware provide for each api? Because in the Gaming market, DirectX drivers often have precedence, whereas in the highend market the openGL drivers have the precedence. So which features become practically available for each api merely depends on where the chip builder wants to put the development ressources. Of course it helps that Microsoft often helps with the funding of DirectX support.
HDR is a pretty basic shader feature though, so both shader languages are capable of expressing it.