https://bugs.winehq.org/show_bug.cgi?id=43847
Bug ID: 43847 Summary: Just Cause 2 and 3 require WINED3D_RS_MULTISAMPLEMASK 0xffff Product: Wine Version: 2.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: byi5000@gmail.com Distribution: ---
Non-breaking, but spammed a lot
fixme:d3d:state_multisampmask WINED3D_RS_MULTISAMPLEMASK 0xffff not yet implemented.
https://bugs.winehq.org/show_bug.cgi?id=43847
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |minor Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID Component|-unknown |directx-d3d
--- Comment #1 from Matteo Bruni matteo.mystral@gmail.com --- In general fixmes are not bugs: https://wiki.winehq.org/FAQ#I_get_lots_of_.22fixme:.22_messages_in_the_termi...
If there is something functionally broken in those games then yes, please do report the issue (unless there is a bug for it already, of course).
https://bugs.winehq.org/show_bug.cgi?id=43847
--- Comment #2 from BieHDC byi5000@gmail.com --- Since both of those games have other remaining graphical issues, i cant tell if this one exactly produces a visual difference. Other masks are already implemented. This one is maybe not so often used which is why it has not been added yet?
https://bugs.winehq.org/show_bug.cgi?id=43847
--- Comment #3 from Matteo Bruni matteo.mystral@gmail.com --- (In reply to BieHDC from comment #2)
Since both of those games have other remaining graphical issues, i cant tell if this one exactly produces a visual difference.
That's my point. It seems more useful to me to have a bug concerning some specific graphical issue and work from there rather than picking some fixme from the Wine log and claim that it is an actual issue for the game.
Now WRT this bug, if some developer (e.g. Józef, most likely :P) thinks that having a bug for the sample mask is useful then, of course, he can just reopen it. But they knew that already.
Other masks are already implemented. This one is maybe not so often used which is why it has not been added yet?
I think it's just that it's new to d3d10+ and nobody has yet had the need / time to implement it in wined3d.
https://bugs.winehq.org/show_bug.cgi?id=43847
--- Comment #4 from BieHDC byi5000@gmail.com --- (In reply to Matteo Bruni from comment #3)
(In reply to BieHDC from comment #2)
Since both of those games have other remaining graphical issues, i cant tell if this one exactly produces a visual difference.
That's my point. It seems more useful to me to have a bug concerning some specific graphical issue and work from there rather than picking some fixme from the Wine log and claim that it is an actual issue for the game.
You have to start somewhere ;)
https://bugs.winehq.org/show_bug.cgi?id=43847
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #5 from Matteo Bruni matteo.mystral@gmail.com --- (In reply to BieHDC from comment #4)
(In reply to Matteo Bruni from comment #3)
(In reply to BieHDC from comment #2)
Since both of those games have other remaining graphical issues, i cant tell if this one exactly produces a visual difference.
That's my point. It seems more useful to me to have a bug concerning some specific graphical issue and work from there rather than picking some fixme from the Wine log and claim that it is an actual issue for the game.
You have to start somewhere ;)
Sure, but in my opinion it's better to start from a graphical glitch in the game, explaining it clearly with the help of screenshots or even (gasp!) videos and then attaching logs as requested, that's all.