Announcement
Collapse
No announcement yet.
Progress Being Made On OpenCL+OpenGL Over Direct3D 12
Collapse
X
-
Originally posted by theriddick View PostThis is true unfortunately. I was quite disappointed to see CP2077 is to have DX12 exclusivity and no Vulkan support, also no generic ray tracing support but exclusive RTX features..
Comment
-
Originally posted by kuco View Post
All of the big engines support Vulkan.
Android + iOS + Playstation + Nintendo are WAY more important than the Windows + XBox gaming market. At least internationally. The story might be different in the US since XBox is not a non-factor there.
So even if the PC Version of CP2077 is DX12 only (MS and NVidia probably paid big money), the engine still supports Vulkan.
Im pretty sure Vulkan will be the primary developement target, since only very few titles are Windows/Xbox-exklusive.
Playstation => GNM and GNMX.
iOS => Metal, Middleware engines use Metal directly, MoltenVK is a third party solution with all the caveats it entails
Android => Vulkan was introduced as optional API in Android 7, largely ignored except by Samsung and Google flagship phones, so it was made compulsory in Android 10 and given how Android updates are.....
Nintendo => NVN, there is OpenGL 4.5 and Vulkan support for porting titles. About 50% of the titles are using Unity, most first party titles use NVN.
- Likes 1
Comment
-
Originally posted by kuco View Post
It's not about FOSS, it's about the number of supported platforms.
...
The situation was different, when the Windows-gaming-market was much bigger (relatively speaking) and OpenGL sucked in comparison to DirectX (in terms of drivers and development-burden) ...
That coupled with the fact that game developers are an interesting breed of developer in that they are much more easily governed by brand names than your typical software developer (perhaps a slight inferiority complex? Perhaps a slightly more immature demographic? Perhaps lacking solid analysis skills because "code" is simply a means to an end?).
Most indies from between 2000-2014 locked themselves down to DirectX because "it is the AAA standard!(TM)", even though their graphical requirements were so simple that even an older OpenGL would have sufficed.
The whole situation was just annoying. Microsoft thrived on this. Even developing XNA as a gateway drug.
- Likes 2
Comment
-
This sounds like MS trying to keep existing DX12 investment somewhat relevant (from a technical perspective, one would think that they could just as easily have used Vulkan).
I'll keep supporting Vulkan (and not DX12) with my wallet, thank you very much.
Comment
-
Originally posted by pjmlp View Post
Maybe in an alternative reality I guess.
Playstation => GNM and GNMX.
iOS => Metal, Middleware engines use Metal directly, MoltenVK is a third party solution with all the caveats it entails
Android => Vulkan was introduced as optional API in Android 7, largely ignored except by Samsung and Google flagship phones, so it was made compulsory in Android 10 and given how Android updates are.....
Nintendo => NVN, there is OpenGL 4.5 and Vulkan support for porting titles. About 50% of the titles are using Unity, most first party titles use NVN.
DX12 is used mostly because it's mandatory on Xbox. You can't say same thing about Vulkan because there is no popular device (well, excluding Stadia now) where Vulkan would be only option. Just look how many years passed before developers stopped using DirectX 9.
- Likes 1
Comment
-
Originally posted by kpedersen View Post
Really? I thought those days of writing non-portable win-games were behind us?
Comment
Comment