Vulkan status

[RCaloca]

@John_Alcatraz

Did you consider doing it like the new audio engine? So let people switch between old and compatible with everything, and new but breaking all old stuff?

Not really. The programming interface (the RHI API) is common for all the RHIs (Metal, GL, D3D, etc). So we would basically have to change the complete renderer (which is a man-years operation) and keep the new one working along the old one. So in short no Some systems have a smaller footprint such that that approach is feasible, as you noticed

@John_Alcatraz

Also, could you say if it’s making use of parallel rendering already and with what amount of draw calls you do your tests? So if you test with something like 30000 draw calls per frame, how much faster is Vulkan then compared to D3D11?

Initial parallel support is working, but not yet ready. Still got some weeks before 4.20 cut-off, so hopefully it can make it. Most of the issues are correctness issues (as in following the Vulkan spec re:transitioning resources, which work on some drivers, but there are no warranties on others).