If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

This: http://bugs.winehq.org/show_bug.cgi?id=13951
It's needed for any UnrealEds to be usable (right now they are completely useless without said patch). But apparently the patchset wasn't accepted originally, and now there is some delay due to OS X, and everyone pretty much forgot about it, it seems...

I wonder how fast you could make Wine with all that stuff that never really made it into mainline like all the D3D state tracker stuff, the command stream patch-set etc.

I think that a cartel that has restrict Linux in a bad path, will try to crash the D3D9 state tracker. I don't thing that Mesa and Wine with real D3D9 support is somewhere to be found, in any distro or repository.

tested it on TR2013

Forced TR RenderAPI to 9. enabled HKEY_CURRENT_USER/Software/Wine/Direct3D/CSMT="enabled" and run benchmark. also, both disabled GLSL, since i have NVidia 9800GT. NVidia and GLSL in wine don't really play well, halves the framerate

I think that a cartel that has restrict Linux in a bad path, will try to crash the D3D9 state tracker. I don't thing that Mesa and Wine with real D3D9 support is somewhere to be found, in any distro or repository.

Well, our (the Wine developers') and the Mesa developers' time is limited. With regards to running d3d9 applications on Mesa we have the following options:

Make Wine work better on all OpenGL implementations.

Make Mesa run all OpenGL applications better.

Write and maintain lots of special code to make Wine run better on Mesa.

Considering finite resources, we believe 1 is the way to go, and we're helping the Mesa devs with 2. You may disagree and submit code to either project to implement 3. But don't think it's a conspiracy when we disagree with you about what to do with our time.

Just dumping huge amount of code into our codebase is not how we operate. That invites technical and legal issues.

Anyone who looks at my patches on Github will see that there are numerous areas where work is needed. Anyone who then looks at wine-patches will see that I am submitting those patches, step by step. Anyone who compares this to the git commit log will see that they are getting committed. And anyone reading wine-devel will see where remaining challenges are.

It will take a while. Most likely months. I've uploaded the current hacky patches as a courtesy to Wine users. Enjoy :-)