Tomorrow is the Khronos UK 'Vulkanised!' talk about Vulkan from developers like Feral Interactive, Croteam and others. You will be able to watch it online.
The two most interesting talks (for Linux gamers) are listed below:
I assume the times are BST, since the UK is currently is summer time, but the events page doesn't actually say.
Watch online: http://khr.io/vulkanised
You can see details of the event here.
It's going to be fun to listen to, so hopefully the livestream works well enough. While I doubt we will learn any secrets, it's going to be interesting to hear directly from the developers working with Vulkan what it's really like.
The two most interesting talks (for Linux gamers) are listed below:
- At 10:15 BST (9:15 UTC) Alex Smith & Marc Di Luzio from Feral Interactive will be doing a talk about bringing Mad Max to Vulkan.
- At 13:30 BST (12:30 UTC) Dean Sekulić from Croteam will do a talk about Serious Sam and Vulkan.
I assume the times are BST, since the UK is currently is summer time, but the events page doesn't actually say.
Watch online: http://khr.io/vulkanised
You can see details of the event here.
It's going to be fun to listen to, so hopefully the livestream works well enough. While I doubt we will learn any secrets, it's going to be interesting to hear directly from the developers working with Vulkan what it's really like.
Some you may have missed, popular articles from the last month:
If anyone isn't at the event but is nearby Cambridge then feel free to come to the beer festival afterwards and say hi :)
4 Likes, Who?
Looking forward to this! Wonder if Deus Ex: Mankind Divided will get the Vulkan treatment. I need to grab and play some of the DLC.
1 Likes, Who?
Looking forward most to Worst Practices talk. Vulkan leaves a lot of room for screw ups and I'm eager to see just how bad it can get.
1 Likes, Who?
I look forward to these talks. I'm assuming that it'll be on YouTube at some point in the near future, so I'm going to wait for that :)
2 Likes, Who?
Quoting: mdiluzIf anyone isn't at the event but is nearby Cambridge then feel free to come to the beer festival afterwards and say hi :)
There's an idea.
We should have a GOL get-together.
I am nowhere near Cambridge though :(
Last edited by razing32 on 24 May 2017 at 6:53 pm UTC
1 Likes, Who?
Quoting: AnxiousInfusionLooking forward most to Worst Practices talk. Vulkan leaves a lot of room for screw ups and I'm eager to see just how bad it can get.
It does, but also leaves a lot of room for great performance increases to squeeze most out of the availible hardware power. Now devs will show not only their story ideas but also their programming and coding skills and true optimizations, because when games are poor optimized people won't blame Nvidia and MS's dx and Khronos's Vulkan, but rather will blame the poor optimization from developer's side which in my opinion is very healthy for developers to take care about, so Nvidia/AMD can take more time developing best possible Vulkan drivers and less time optimizing and fixing poor developers' faults in their titles...
Last edited by MaCroX95 on 24 May 2017 at 9:37 pm UTC
2 Likes, Who?
Quoting: MaCroX95Quoting: AnxiousInfusionLooking forward most to Worst Practices talk. Vulkan leaves a lot of room for screw ups and I'm eager to see just how bad it can get.
It does, but also leaves a lot of room for great performance increases to squeeze most out of the availible hardware power. Now devs will show not only their story ideas but also their programming and coding skills and true optimizations, because when games are poor optimized people won't blame Nvidia and MS's dx and Khronos's Vulkan, but rather will blame the poor optimization from developer's side which in my opinion is very healthy for developers to take care about, so Nvidia/AMD can take more time developing best possible Vulkan drivers and less time optimizing and fixing poor developers' faults in their titles...
I'm in two minds about this. Would the low level graphics API devs not be best placed to squeeze the best performance out of the API rather than the game developers that I would expect would be more proficient in graphics, gameplay and storytelling? I think one of the reasons that DX12 seems to have stalled with so few games is that it seems to have moved some of the effort and costs onto the game developers rather than the OS/API/low level graphics developers that would have the in-house experience with low level API coding. Those guys don't come cheap.
0 Likes
I'm a Yank so I'll have to watch it on youtube, but much love to my fellow Penguins across the pond! I hope you all have a blast and some interesting things are revealed. Cheers!
0 Likes
Hmmm... so no iD "Doom" Vulkan at the event. I'd venture that their code is well optimised.
0 Likes
Quoting: MintedGamerQuoting: MaCroX95Quoting: AnxiousInfusionLooking forward most to Worst Practices talk. Vulkan leaves a lot of room for screw ups and I'm eager to see just how bad it can get.
It does, but also leaves a lot of room for great performance increases to squeeze most out of the availible hardware power. Now devs will show not only their story ideas but also their programming and coding skills and true optimizations, because when games are poor optimized people won't blame Nvidia and MS's dx and Khronos's Vulkan, but rather will blame the poor optimization from developer's side which in my opinion is very healthy for developers to take care about, so Nvidia/AMD can take more time developing best possible Vulkan drivers and less time optimizing and fixing poor developers' faults in their titles...
I'm in two minds about this. Would the low level graphics API devs not be best placed to squeeze the best performance out of the API rather than the game developers that I would expect would be more proficient in graphics, gameplay and storytelling? I think one of the reasons that DX12 seems to have stalled with so few games is that it seems to have moved some of the effort and costs onto the game developers rather than the OS/API/low level graphics developers that would have the in-house experience with low level API coding. Those guys don't come cheap.
Maybe, but I suspect the main reason is that there are still so many people on Windows versions that don't run DX12, so you either have to do both DX12 and (either DX11 or OpenGL or Vulkan), or you have to drop half your customers. But if you're going to do (DX11 or OpenGL or Vulkan) anyway, why bother doing DX12 on top of that? As MS manage to drag their customer base to Windows 10 over the next couple-few years, this will become less of an issue, but now today it still is one. I think MS, in trying to use DX12 as a pull factor to yank people onto the latest versions, accidentally messed it up bad and may well end up surrendering what could have been a strong lead over Vulkan. If they hadn't been so dead set on end-of-lifing old Windows versions and had made DX12 available across their ecosystem it might have been dominant by now. Overconfidence.
1 Likes, Who?
See more from me