neat, I see we're at the extend part again. Can't wait for what comes next.
Announcement
Collapse
No announcement yet.
"Dozen" Merged Into Mesa For Implementing Vulkan On Direct3D 12
Collapse
X
-
Originally posted by Linuxxx View Post
Serious question:
Do you honestly think this is going to be used to provide Vulkan support on the Xbox of all of Microsoft's platforms?
For reference:
Nintendo's Switch actually has official Vulkan support, yet, AFAIK, not a single commercial game is making use of it.
(Probably because it has a nVidia Maxwell GPU, which is badly suited for running Vulkan loads in the first place.)
And to others, think of that library and WINE (or winelib) itself as an option for developers, so they can port their (originally Windows) games more easily. Similarly like you can download a Microsoft's solution to Visual Studio containing a template and their fork of the ANGLE library, so your game can use OpenGL ES, despite the target platform (Windows UWP/Store, Windows on ARM, Xbox, ...) has only DirectX 12. You simply bundle the library with your app, so no support in the OS is needed. The same exists also for DirectX 12 on Windows 7 (used by Cyberpunk 2077 and some Blizzard games) - you bundle DX12 with your game, so no DX12 is needed on Win7 (but you needed MS to create the Win7 libraries).
Comment
-
Originally posted by dragorth View PostAlso, this kinda makes MESA a truly agnostic graphics driver layer, which can be used by hardware manufacturers to jumpstart and test against known good implementations, doesn't it?
Comment
-
Originally posted by Linuxxx View Post
Serious question:
Do you honestly think this is going to be used to provide Vulkan support on the Xbox of all of Microsoft's platforms?
The problem with Vulkan is that it had a difficult and too late arrival... Metal was ready since 2013, DirectX 12 since 2015 and Vulkan.... 2016.
Furthermore its complexity (not kidding, over 6000 lines of code just to draw a freaking triangle) turns every graphics dev off, regardless of its advantages.
On the other hand OpenGL enjoyed lots of success because it arrived earlier than DirectX despite its "state machine" model not being so ideal...Last edited by tildearrow; 25 March 2022, 09:59 PM.
Comment
-
Originally posted by Danny3 View PostWhy the fuck this is needed when Vulkan already works on all OSes?
Makes no sense to me why would anyone need another abstraction layer that slowes things down and consumes extra CPU cycles, hence also more electrical power.
Comment
-
Originally posted by peterdk View PostWonder what the use as reference documentation is for the DXVK/VKD3D?
Originally posted by Danny3 View PostWhy the fuck this is needed when Vulkan already works on all OSes?
Makes no sense to me why would anyone need another abstraction layer that slowes things down and consumes extra CPU cycles, hence also more electrical power.
Originally posted by SWY1985 View PostI recently needed a Windows VM. The whole experience was a complete disaster...
Either the Windows experience has taken a nosedive, or I just don't remember what it was like to use an animated advertisement billboard as a UI.
- Likes 1
Comment
-
Originally posted by tildearrow View Post
That's something I am doubting since most game devs just use the platform-specific graphics API or just a graphics engine...
The problem with Vulkan is that it had a difficult and too late arrival... Metal was ready since 2013, DirectX 12 since 2015 and Vulkan.... 2016.
Furthermore its complexity (not kidding, over 6000 lines of code just to draw a freaking triangle) turns every graphics dev off, regardless of its advantages.
On the other hand OpenGL enjoyed lots of success because it arrived earlier than DirectX despite its "state machine" model not being so ideal...
Comment
-
I wonder whats the value of a vulkan to D3D12 layer if, if there is no D3D12 implementation in Mesa. I mean even for testing it's kind of pointless, isn't it? Can the Mesa people even test if this thing works? How does CI look like? How to be sure that a change in Mesa doesn't kill the layer? I'm not sure if this platform specific "module" wouldn't be better off out of tree.
I'm not saying it's bad or that Microsoft should stay away from Mesa, I just cant see the benefit and on the other hand I can see this to be a major roadblock because of testing / test integration in the future.
- Likes 1
Comment
-
Originally posted by SWY1985 View PostI recently needed a Windows VM. The whole experience was a complete disaster...
Either the Windows experience has taken a nosedive, or I just don't remember what it was like to use an animated advertisement billboard as a UI.
I love that Microsoft has added a Linux environment to their OS. Now they just need to take down the rest of Windows around it and start working on a decent user experience.
Or, you know... just release their own Linux distro.
- Likes 1
Comment
Comment