Vulkan/OpenGL Next Generation Initiative: unified API for mobile and non-mobile devices.

CryENGINE Is Planning To Deliver Its Vulkan Support In About Two Months

https://www.phoronix.com/scan.php?page=news_item&px=CryEngine-5.3-Vulkan-Coming

CryEngine Roadmap
https://www.cryengine.com/roadmap

 

Wow CryEngine with both DX12 and Vulkan will really open up the options for developers. I wonder how hard it would be for existing projects to shift to Vulkan.

 

A CryEngine that doesn't utterly suck (especially in terms of support, documentation, stability) is vastly more important than supporting every API under the sun IMO. There isn't a single AA/AAA game since Ryse and Everybody's Gone to Rapture using it and there's a reason behind that..it's not that good.. The new Prey doesn't look to hot but this may be because the state of engine licensed back when the deal was struck was sh@t (3 years) and Arkane is stuck with this older version ... Star Citizen is the other one but then again the Frankfurt team is for the most part composed of ex-Crytek engineers which jumped ship 2 years ago (when Tiago Sousa went th id Software).. so at least they know how to use it even thought the "game" in its current state isn't really something to brag about.... such a shame given that this engine was so advanced back then (it still is but Crytek's situation in the past 5 years really didn't help)

 

I stopped caring much about the success of cryengine by now, as the other engines have caught up for the most part. There isn't much about cryengine that puts it much ahead of its competitors now.

 

Vulkan 1.0.25 Moves To Single-Branch Model, Adds NVIDIA Extensions

http://www.phoronix.com/scan.php?page=news_item&px=Vulkan-1.0.25-Released

 

VK_NV_external_memory, VK_NV_external_memory_win32
Why they are different extensions?

 

There's one extension for the cross-platform parts of the feature, and N extensions for the platform-specific parts (e.g. Win32 HANDLEs and D3D interoperability). Currently N=1 but they could add more without duplicating the common bits.

It's similar to Vulkan's WSI, which has some common extensions plus half a dozen platform-specific ones.

 

OpenGL vs. Vulkan With AMDGPU-PRO 16.40, Compared To NVIDIA On Linux - 8 November 2016
http://www.phoronix.com/scan.php?page=news_item&px=AMDGPU-PRO-16.40-VLK-NV

 

I Was find their result strange when remember some older test from them with AMDGPUPro 16.20 http://www.phoronix.com/scan.php?page=article&item=dota2-vulkan-redux&num=3

And effectively: Update (10 November 2016): It appears the slowdowns with 16.40 may be due to running it on an unsupported (4.8) kernel. Additional tests happening now.

 

https://developer.nvidia.com/device-generated-commands-vulkan

New Vulkan extension for ExecuteIndirect like functionality.

 

This is significantly better than ExecuteIndirect. Allows changing shader per draw call. A major new feature. Other minor improvements include SoA layout for command arguments (faster access and easier to partially update) and a sequence index buffer (for sorting / culling draws easily). Command arguments also have separate frequency each (allows changing state/shader at lesser frequency = perf boost).

I hope all three PC IHVs will support feature like this soon. Current extension is limited to Nvidia hardware.

 

Yes we are getting closer to having an async GPU now.

 

Yeah, I know it said it was improved. It just came out that way.

 

So, potentially a big deal. Apparently AMD and Bethesda have inked a marketing deal where all Bethesda games in the future will be using Vulkan with AMD likely providing support in implementing Vulkan.

It makes sense considering how well Vulkan worked for the Doom re-imagining. As well as how invested AMD have been in promoting and supporting Vulkan.

Regards,
SB

 

I wasn't really paying attention to that part, anything online about it? Sounds like an awesome deal for everyone, especially for AMD though.

 

http://www.anandtech.com/show/11164...ction-for-vr-vega-gets-a-server-customer-more

 

That's just a matter of current VR leaving a lot to be desired in regards to performance. The important part of the partnership probably relates to the async reprojection abilities. It stands to reason current AMD hardware is better at that and rendering the native framerate of future HMDs likely isn't practical. Best option for testing decoupled rendering for the time being. That would affect more than just VR as well. No reason a standard game couldn't be warping the scene at 120+Hz while the game actually renders 30fps.

 

Apparently, Star Citizen will be… Vulkan only! Didn't see that coming.

http://www.fudzilla.com/news/games/43157-star-citizen-focuses-on-vulkan-api

 

Presumably that means that Lumberyard has made/is making the switch to Vulkan, since SC moved over to that version of Cryengine?