This kills the AMDrone

>Vulkan is complete and utter shit

ftfy

Can you name a single fact to back that up?

sure, why not

Attached: vulkan.png (746x474, 52K)

>86ms
Please tell me this is a joke

Attached: 1563551559441.png (670x578, 345K)

Funny, AMD cards used to be better at OpenGL. But it's a depreciated library. Use Vulkan.

Still less than most other shitty APIs
Still less than DX12
Still good enough for consolefaggots
Horrible but doesn't matter
Unreal Engine 4 has even worse input lag with DX9/11/12/etc

based

ITT: Non graphics devs circlejerking about performance without actually understanding the difference between each graphics api

Well it's sort of tangentially in AMD's favor, since vulkan allows you to run games natively in linux, and AMD cards have much better linux support and Nvidia's shit always has problems with drivers there. So there's that.

vulkan is the best and you know it
the verbosity is fucking amazing
Still don't get the point of the RAII classes in vulkan.hpp though, the only time you'll ever use them is if you're making some sort of retarded heirarchy, which will be massive
making a global context object that holds all of the state is better

>gaming in linux
No one cares. Do work on your work computer, dual boot, have two computers. Just dont game on linux

Attached: 1564191996715.jpg (1200x800, 144K)

but the reason gaming on linux isn't totally viable is because of proprietary directx bullshit. So anything that moves away from that is good in my book. Especially with MS getting worse and worse and turning their OS into ridiculously bloated mossad spyware.

Sure like i said i like vulkan. I wouldnt touch winshit if it wasnt required on a gaming pc. It is just how it is

can confirm that anything vulkan has dogshit latency
for a game like Doom to run so good yet lag so much was a real shame

No, I'll just game on Linux, thanks.

>falling for the ray tracing meme

IT JUST WERKS
THE MORE YOU BUY THE MORE YOU SAVE

Not sure if retard or just pretending...

Comparison with opengl and directX?

I'm glad I'm not autistic enough to notice this kind of input lag.

SUP Jow Forums

I want to tinker around with graphics programming, should I use OpenGL, Vulkan, or something else?

No, the real reason is the much lower playerbase on a platform with an already lower playerbase (PC). Vulkan won't make it as simple as pushing a button to make a Linux port and people aren't going to start switching to Linux en masse.

Linux is the second best operating system in history for playing video games, retard. It's not 2009 anymore.

>settling for 2nd when 1st is easily available
never settle user, else you'll never make it

Do not go into Vulkan having no knowledge of graphics coding. You'll just get lost and frustrated.

Hell, there's a good chance that you'll get lost and frustrated even with OpenGL. But it's a good place to start.

>implying it works any better on novideo

Attached: c44.png (483x701, 311K)

>you must be a fucking new type fundamental pilot to notice
You're just slow mentally.

>new type gundam pilot

>goytracing

On windows it does.

Since when do consoles use vulkan? These tests were performed on console games, so no vulkan. There's doom included, so i see how you might have been confused.

>consoles don't use vulkan
>These tests were performed on console games, so no vulkan
Maybe they were tested on the PC ports?

No PC port of Killzone exists
eurogamer.net/articles/digitalfoundry-2017-console-fps-input-lag-tested
Found the original article too, it has fuck all to do with graphics APIs and everything to do with consoles.

>raytracing is bad because... uh... it's jewish!
whatever you say poorfag

I only play retro stuff so it's not an issue for me.

That has nothing to do with tick caps.

I know, just wanted an excuse to talk about wolfenstein.

>using consoles
Lmaoing at your life.

I have a GTX 1080 Ti you nigger.

Vulkan games were laggy at first because Vulkan drivers offered no way to enter Fullscreen Exclusive
It was fixed a while ago

Meanwhile on linux it automatically disables your compositor and you can use a keybind to do it too.

Attached: 1560465822308.jpg (777x439, 99K)

I have Nvidia rtx extension for opengl under windows 7. but no support for DXR.

Vulkan runs quite well on Nvidia hardware. Better than DX12, in fact.

Attached: Screenshot_2019-08-04 Gamers Nexus(1).png (1280x720, 377K)

Vulkan trounces DirectX and also have raytracing, on ANY OS instead of just spyware 10.

But user, Linux is a kernel

I don't understand what this graph is meant to show ?
Input handling and rendering are separate things.

*Laughs in vulcan*

Attached: 1555799086525.jpg (882x758, 324K)

Attached: watchv=_Nbp9Cl96Qg-[05.45.600-06.09.150].webm (854x480, 2.67M)

Attached: watchv=_Nbp9Cl96Qg-[08.11.867-08.22.367].webm (854x480, 2.79M)

Dx12 is a failure. Half the time it performans worse than dx11 and offers nothing else except dxr, a meme. Dx12 was shills as going to inprove performance and that was not how it work out. Vulkan is based though, looks amazing and runs fast as hell

VULKAN BEST

Attached: 1556170821416.jpg (700x918, 117K)

>wangblows opengl

PS3 supports ra tracing
youtube.com/watch?v=zKqZKXwop5E

The graph is showing that rendering with Vulkan increases input lag.

Input handling is not input lag. Input lag is the total time from input to related output. The time it takes for you to click on an icon and when the machine registers the interaction caused by the click is input lag. All delays are counted, including polling rate of input devices, time spend processing, and delay caused by output devices like your monitor's response time.

I dunno if that graph is accurate cause there's no source.

The PS3 was such a beast.