News for hackers. Stuff that matters.
Re:What Valve got right and wrong with the Steam Machine by jeletonskelly on Thursday November 12, 2015 @08:17AM (#10552905)
I'm hoping someone with more knowledge about Direct3D/DirectX could clarify some things for me. Since we're seeing a lot of progress on .NET running on OSX and Linux, does this mean that at some point you'll be able to run Windows games on both OSX and Linux? If not, what are the major hurdles there?
Re:What Valve got right and wrong with the Steam Machine by voltagex_ on Thursday November 12, 2015 @08:28AM (#10552964)
I don't think there are a huge number of Steam games running on .NET, but the number might be increasing due to the rise of Unity.

Many, many games are written in C++ and require reasonable porting efforts to get to Linux support. Someone like Ryan C Gordon (icculus) is much better qualified to comment on that, though.

I doubt Microsoft would ever port DirectX to Linux, but then again I doubted they'd do that with .NET, and look where we are.

The DirectX->Wine code works pretty well, but it's always going to be behind the state of the art.

Re:What Valve got right and wrong with the Steam Machine by kbwt on Thursday November 12, 2015 @11:30PM (#10558013)
There is already a native Direct3D 9 implementation on Linux, called Gallium Nine. It works with any driver exposing the Gallium interface, such as the open source radeon driver.
Re:What Valve got right and wrong with the Steam Machine by Bouncingsoul1 on Thursday November 12, 2015 @08:31AM (#10552981)
Direct3D and DirectX have nothing to do with .Net. The port of the CLR will only allow to run .Net(core) applications on OSX or Linux . And even there DirectX seems to be a blocking factor e.g. XAML/WPF which uses DirectX for drawing won't be ported/opensourced ,IMO for this very reason.