Originally posted by Ferdinand
View Post
Announcement
Collapse
No announcement yet.
Croteam Reiterates Vulkan Intentions, Shows Off Screenshot
Collapse
X
-
Ah so it was the april fools kind of humor where you lie and the joke is that somebody believes you.
Leave a comment:
-
Originally posted by Philip View PostThere are some really ugly texture mapping problems on the bridge in that screenshot, like it's a single line of texels smeared across the mesh. (It should look more like this). I assume their OpenGL renderer isn't that buggy, so that suggests it's probably an early far-from-completed Vulkan renderer.
Leave a comment:
-
Originally posted by haagch View PostStill rendered in OpenGL.
Leave a comment:
-
Originally posted by baffledmollusc View PostIt's wrong.
It was a joke - they added a "Vulcan" to their scene. Still rendered in OpenGL.
Originally posted by geearf View Postmost likely yes, it is wrong.
There'd be no way to move the engine to Vulkan in 5 minutes...
Leave a comment:
-
Maybe Michael should have posted the rest of the blog entry:
After seeing the first screenshot we weren’t quite convinced that was the support Khronos Group is looking for. We confronted Dean about it and asked him if he read the official specifications at all?
“No. Of course not! But it won’t stop me from speaking about it at this years GDC official Vulkan panel. And if you disagree, I’ll be available for questions after my lecture.”
Dean was equally straightforward about the time frame for the upcoming patch that will add Vulkan functionality:
“Soon.”
We were terrified to ask anything else. But YOU could try.
Leave a comment:
-
I can't quite tell if Michael was in on this joke when writing this or not, but it's funny either way.
Leave a comment:
Leave a comment: