Mesa Git Should Now Work With Intel/RADV Vulkan For Doom Under Wine

[oooverclocker]

we've never landed it because we've been hoping that a game update would come out with fixed shaders.

Perfect.

we're stuck working around it. Hopefully, we can delete this code one day.

Jason, why should one switch to Linux when you introduce the same mess people are suffering on Windows in the clean new Vulkan driver code? When Bethesda is incompetent enough not to fix broken code their game simply won't work on Linux. Linus might know a shorter and more straight version how to say "hello" to this company as long as they behave that way. The open source community shouldn't be pathetic enough to support every bullshit that has been produced.

You might mean well but you are undermining Vulkan before it was helpful. You should learn to insist and fight for drivers that run every compliant game absolutely reliably. Otherwise you disadvantage developers who develop native and compliant games for Linux, you reduce the game code's quality passively and you crush the competitive long term advantage of Linux distributions over Windows.

[ramrod]

People in this thread need to calm down... Getting angry that a small workaround may temporally be in the Vulkan driver is a bit silly. In the mean time I'm going to play some DOOM with the open source driver. Thank you devs.

[Dreakon]

If the code doesn't negatively impact anything else, I don't understand why people would have such an issue with this. Sure, in a perfect world the devs would code their games properly, but in the real world, users would blame the Mess devs for stuff not working.

[LeJimster]

Well I for one am happy this has been added. I've had a copy of Doom for months that I wanted to play through wine.

[duby229]

I do agree in some sense that fixes for "non-compliancy" or whatever should be isolated. Especially if the devs are hoping it to be temporary.

[Spacefish]

This is way more generic than the fixes implemented in the nvidia / amd blobs! They replace single shader binaries with other for specific applications, so they can improve the performance.. Once the dev recompiles the game with another compiler version or changes the name of the executable, the performance drops for some unknown reason, because the driver did not detect that specific game and did not load it´s optimized replaced shader!

Common things: They exchange 32 bit float calculations with 16 bit calculations, so they have half the memory bandwidth and almost double the performance, with minor visible impact! That´s like that windows compability list which pre allocates memory for specific binaries to avoid a segfaults ^^

[dungeon]

People in this thread need to calm down... Getting angry that a small workaround may temporally be in the Vulkan driver is a bit silly. In the mean time I'm going to play some DOOM with the open source driver. Thank you devs.

Yep, people better to spend their time asking Vulkanstein 2 to be on Linux also, that seems just 4 months away

https://twitter.com/idSoftwareTiago/...87031249244160
http://steamcommunity.com/app/612880...5556479321267/

And once on Linux to fix shaders just for Mesa . And once they did this, probably something else would need fix and so on... so, people can't calm down really, but noice should really be elsewhere

Since as of this year AMD is in partnership with Bethesda it would run very likely top notch on AMD Vulkan

http://www.amd.com/en-us/press-relea...2017feb28.aspx

[oooverclocker]

Unbelievable reactions - what a punch in the face of Croteam who spent money fixing it for The Talos Principle and rich Bethesda who couldn't care less about Linux gaming get's his crappy code fixed in the chaste Vulkan drivers so people can fiddle it working with Wine. Well done!

The consequences are clear. You can now produce bullshit code for Windows an let it get fixed by driver devs. And you don't even have to support Linux natively, no - driver and Wine devs will even make people buy your Windows version... wohoo!

[notaz]

Actually it can be argued it's not even the game's fault - they just used a version of glslang (reference compiler from Khronos) that had the bug. It might even be that relevant part of the spec wasn't fully formalized at the time of DOOM was in development, there was no way for them to know their tools (actually Khronos tools) were doing something wrong.

[dungeon]

Actually it can be argued it's not even the game's fault - they just used a version of glslang (reference compiler from Khronos) that had the bug.

Achtüng! Achtüng! - "All API bugs supported" clause of blob drivers or alternative police require all people who walk to have entire law into their heads so that they actually can't walk anymore "Hey this is illegal by up to date law, so raid this now"

What, you are not up to date? Put him in prison... no, into darkest dungeon even better