Originally posted by zeealpal
View Post
Announcement
Collapse
No announcement yet.
Wine's Shader Compiler Now Handles... Reflections
Collapse
X
-
-
Originally posted by grantek View PostI thought the removal of Win9X tests was interesting - almost sounds like Wine 1.2 is the last version to attempt to support bug-for-bug compatibility with Win9X.
I'm sure there's a lot of people who will want to run old/archaic/bug-dependent Windows 9X software in the future (even just for retro purposes), so I thought these people will be left with maintaining the 1.2 branch until ReactOS has equivalent support. Did some googling and found this though:
http://www.mail-archive.com/wine-dev.../msg67102.html
What is the test suite used for? Why were tests marked broken for Win9x? What does that mean for Win9x compatibility?
Leave a comment:
-
I thought the removal of Win9X tests was interesting - almost sounds like Wine 1.2 is the last version to attempt to support bug-for-bug compatibility with Win9X.
I'm sure there's a lot of people who will want to run old/archaic/bug-dependent Windows 9X software in the future (even just for retro purposes), so I thought these people will be left with maintaining the 1.2 branch until ReactOS has equivalent support. Did some googling and found this though:
Right now all the test results that differ for win9x versions are marked
as broken(), i.e. Wine intentionally makes an effort to NOT replicate it.
So removing checks for (broken) results will change nothing.
Leave a comment:
-
Originally posted by droidhacker View PostAm I the only one who things that the wine developers have their priorities screwed up? How about making it actually run real useful and necessary software before messing with implementation of pointless graphical features that nobody really needs?
Ask a bunch of random people what they want from an open source project and you'll get a diverse set of opinions about what should be prioritized. But you know what? The persons submitting patches or other contributions get their itches scratched.
Leave a comment:
-
Originally posted by schmidtbag View Postwhat ever happened to that legitimate dx10 and dx11 implementation into wine? if thats still happening, the wine developers should seriously ditch the open gl conversion into dx and focus more on the functionality of wine itself. seriously, all wine needs is a REAL dx and everything should be relatively easy from there on, making small tweaks here and there for any program or game that doesn't work for reasons irrelevant to graphics.
I think that that would be the best way to go about it.
+1 To that idea
Leave a comment:
-
what ever happened to that legitimate dx10 and dx11 implementation into wine? if thats still happening, the wine developers should seriously ditch the open gl conversion into dx and focus more on the functionality of wine itself. seriously, all wine needs is a REAL dx and everything should be relatively easy from there on, making small tweaks here and there for any program or game that doesn't work for reasons irrelevant to graphics.
Leave a comment:
-
The article could only have been clearer about that if Michael had understood it correctly.
Leave a comment:
-
Looks like this is referring to "code" reflection not the graphical effect (the article could have been clearer on that...)
The Wine developers implemented methods needed for the ID3D11ShaderReflection interface, which returns information about a shader.
Leave a comment:
-
Leave a comment:
Leave a comment: