Wednesday, June 21st 2017
CryEngine to Support Vulkan Renderer in Upcoming 5.4 Update
CryEngine, the rendering prodigy responsible for some of the most visually impressive titles ever to grace our personal computing and gaming shores, is getting a Vulkan renderer. The news were broken down by the team at Crytek through a blog post, where they reaffirmed their commitment to proper GitHub support and updates for their game engine. The company puts it this way:
"Vulkan renderer
Following on from the renderer refactoring and DirectX 12 implementation, the team has been hard at work implementing a Vulkan renderer. The code can be seen in Code/RenderDll/XRenderD3D9/Vulkan/… although the feature is not functional, yet. We want to make these changes available to you for review whilst we are currently stabilizing the engine for our 5.4 release. So you can track our progress on GitHub until 5.4 is finally here by the end of July."This comes as good news for everyone, I wager, since Vulkan has been showing more promise in actual performance improvements in real world gaming scenarios than Microsoft's poster child DX12. Granted that CryEngine isn't the resource hog and graphics-card humbler that it was once before, when it birthed the famous "But can it run Crysis?" adage. It has turned from being one of the more resource intensive engines to a more streamlined, arguably better performant one. Here's hoping Crytek's upcoming Hunt: Showdown already provides support for the Vulkan renderer. A game as graphically beautiful as that one clearly deserves the performance to go with it.
Source:
Cryengine.com
"Vulkan renderer
Following on from the renderer refactoring and DirectX 12 implementation, the team has been hard at work implementing a Vulkan renderer. The code can be seen in Code/RenderDll/XRenderD3D9/Vulkan/… although the feature is not functional, yet. We want to make these changes available to you for review whilst we are currently stabilizing the engine for our 5.4 release. So you can track our progress on GitHub until 5.4 is finally here by the end of July."This comes as good news for everyone, I wager, since Vulkan has been showing more promise in actual performance improvements in real world gaming scenarios than Microsoft's poster child DX12. Granted that CryEngine isn't the resource hog and graphics-card humbler that it was once before, when it birthed the famous "But can it run Crysis?" adage. It has turned from being one of the more resource intensive engines to a more streamlined, arguably better performant one. Here's hoping Crytek's upcoming Hunt: Showdown already provides support for the Vulkan renderer. A game as graphically beautiful as that one clearly deserves the performance to go with it.
31 Comments on CryEngine to Support Vulkan Renderer in Upcoming 5.4 Update
Nope, not gonna let it go.
But don't let it go, scream and shout, fight the power! Never ever let it go.
And if anyone recalls, as soon as the new AMD cards came out with great tessellation perf, all of the sudden it wasn't overly crammed into games and wasn't important. Yeah, just a coincidence.
Short memories are for fools to folly again and again (then victim blame out of their own stupidity).
If both companies offered similar performance in games this nonsense where you can nitpick which card based off of one batch of rendering wouldn't exist. Amd needs to stop acting like a second tier company. Now mind you I flip flop between these companies like it is going out if style, but last couple of amd generations have been a let down...
Pascal wasn't that reliable either at launch. Some cards ran at 900mhz or less before BIOS updates!
For those betting on threadripper remember every single issues ryzen has will be amplified since both ccx unit have to speak across the infinity fabric. That means pcie root complex, memory for the quad channel anything the os decides to swap between cores etc. I cannot imagine the bottleneck we will see once you do something like load a game up with 2 cards in sli.
Ryzen hasn't really got issues anymore either, unless you mean the occasional driver update that makes things go wrong, but intel's driver updates aren't much better and it's mostly windows updates ruining things nowadays.
Threadripper essentially is going to use matured drivers and the extra ccx's aren't going to be an issue. Threadripper is likely going to use epyc drivers with a few tweaks here and there, so they should be stable enough and memory support is going to be great from the start since all those updates have already been implemented into motherboard BIOS's.
No, I don't own ryzen yet. Getting threadripper 16-core, though. I have done my research.