[4/5] d3d9: Accept the d3d10 fog+sRGB behavior as broken

Stefan Dösinger stefan at codeweavers.com
Tue Jul 6 10:41:09 CDT 2010

Am Dienstag 06 Juli 2010 17:02:23 schrieb Henri Verbeet:
> > I haven't seen any game that depends on the new behavior. Since the
> > Source 2003 engine is pretty popular it would be a lot of pain to try to
> > adopt the dx10 fog-sRGB behavior with no gain.
> We may want to use the framebuffer_sRGB extension in the future.
In which case we'll have to fall back to the shader sRGB correction if fog is 
used with sRGB writing.
> > It's not the only case where we declare "new" behavior as broken. E.g.
> > the error returned due to bad buffer lock flags happens to break games,
> > even though the new behavior is saner than the old one.
> Sure, I just don't think either behaviour should be considered broken
> at this point.
Do you think we should just accept both behaviors as OK?

More information about the wine-devel mailing list