Wine 1.7.32 Updates Its Mono Engine

[phoronix]

Phoronix: Wine 1.7.32 Updates Its Mono Engine

It's time for another bi-weekly development release of Wine, but if you're looking forward to the Direct3D Command Stream work, better D3D10/D3D11 support, or any integration of Gallium3D Nine support, you'll be sadly disappointed...

http://www.phoronix.com/vr.php?view=MTg1MDM

[SpaceJunk]

Now if only fglrx would update on Ubuntu, I could try this without having a Thunderdome scene between the Windows emulator and the GPU driver.

[gutigen]

Now if only fglrx would update on Ubuntu, I could try this without having a Thunderdome scene between the Windows emulator and the GPU driver.

Why not use superior open source drivers? Get one of Mesa git PPAs like:

Bleeding edge:

https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers

Even more bleeding edge:

https://launchpad.net/~paulo-miguel-dias/+archive/ubuntu/mesa

[Xaero_Vincent]

What doesn't make a lot of sense to me is that D3D10 is 82% implemented in Wine, yet virtually no Direct3D 10 games work in Wine. Yet D3D9 is 78% implemented and the vast majority of DX9 games work at various levels of compatability.

As far as DirectX 11 and 12, I guess those haven't been much of a priority. It kind of makes sense because in order for Wine to support Direct3D 11 to OpenGL 4.x translation, it would require the actual open-source Linux video driver infrustructure and OpenGL compliance in Mesa to meet that requirement. AFAIK, only proprietary drivers support OpenGL 4.x but the open-source drivers are still at OpenGL 3.x, which can match Direct3D 10 features but not 11 or 12. Hopefully soon, enough GL 4.x extensions will be implemented to upgrade compliance status to 4.x in Mesa and the FOSS graphics driver stack so that Wine developers can begin to focus on D3D 11 and fixing D3D 10.

[pinguinpc]

In this wine version steam still working but arcania gothic 4 begins to work

https://bugs.winehq.org/show_bug.cgi?id=27282

However in cinematics only works sound

[edoantonioco]

If there is a new mono engine then it would think than some lines of the new .net code is on it. So I wonder if this means more compatibility with some software.

[pinguinpc]

If there is a new mono engine then it would think than some lines of the new .net code is on it. So I wonder if this means more compatibility with some software.

This is wine information about opensource .net

https://www.winehq.org/wwn/380#Open

We're mostly behind in higher-level class libraries like winforms, WPF, and the vb.net runtime, which afaik are still not available under a free software license.

And as of now it seems there is no plan to open source winforms, WPF and other client stacks. This and also the fact that mscoree won't be opened makes it quite unattractive for Wine.

[edoantonioco]

This is wine information about opensource .net

that makes sense, thanks for the info

[stefandoesinger]

What doesn't make a lot of sense to me is that D3D10 is 82% implemented in Wine, yet virtually no Direct3D 10 games work in Wine. Yet D3D9 is 78% implemented and the vast majority of DX9 games work at various levels of compatability.

That's because those automatically generated statistics don't make sense for the d3d libraries or any COM-based library. They look at how many calls exported by classic DLL exports have an implementation - that can be seen in the .spec file, e.g. dlls/d3d9/d3d9.spec. Most calls in d3d9.spec are just fairly simple debug functions. The only ones that are interesting are Direct3DCreate9 and Direct3DCreate9Ex. They return a COM interface that has 22 methods, whereas one of them (IDirect3D9::CreateDevice) returns yet another COM interface with dozens of methods. Those are not visible to the tool that generates the completion statistics.

D3D10 works in the same way.

What is hiding behing "Improved support for restoring display mode." is handling for alt-tab in fullscreen d3d and ddraw games. So far it is working on KDE, fvwm and OSX. Any window manager forked from Metacity currently doesn't work because they refuse to minimize windows without minimize boxes. I've reported this bug only to MATE Desktop right now, I'll push harder for a fix now that the code is available in an actual release.

[Xaero_Vincent]

That's because those automatically generated statistics don't make sense for the d3d libraries or any COM-based library. They look at how many calls exported by classic DLL exports have an implementation - that can be seen in the .spec file, e.g. dlls/d3d9/d3d9.spec. Most calls in d3d9.spec are just fairly simple debug functions. The only ones that are interesting are Direct3DCreate9 and Direct3DCreate9Ex. They return a COM interface that has 22 methods, whereas one of them (IDirect3D9::CreateDevice) returns yet another COM interface with dozens of methods. Those are not visible to the tool that generates the completion statistics.

D3D10 works in the same way.

What is hiding behing "Improved support for restoring display mode." is handling for alt-tab in fullscreen d3d and ddraw games. So far it is working on KDE, fvwm and OSX. Any window manager forked from Metacity currently doesn't work because they refuse to minimize windows without minimize boxes. I've reported this bug only to MATE Desktop right now, I'll push harder for a fix now that the code is available in an actual release.

Interesting. So how far along do you think D3D10 actually is in the current state? How close is it for something to work?

I recently came across a developer blog where someone created some patches to get some Direct3D 10 demos working with multiple versions of Wine:

http://pigflygames.com/index.php/blog

Pretty interesting stuff and maybe useful to Wine developers?