Update: 14/12/21 - This has now been fixed.
Despite Valve pushing many areas of Linux gaming, including the upcoming Steam Deck handheld which will use the Arch-based SteamOS 3, they still totally break their own games.
It's pretty concerning that their absolute #1 most popular game on Steam, Counter-Strike: Global Offensive, has been thoroughly broken on Linux (and macOS) with the update that landed on Friday, December 10. First, the game wouldn't even launch at all which was thankfully fixed - but there's a pretty huge game-breaking problem still left in.
For this, I don't really need to do much explaining, I think these pictures speak for me:
You can track the open issue for it on GitHub.
It does raise an important question - are Valve even testing updates to their own games on Linux? Something like this should not have slipped through the cracks. If it does when the Steam Deck is out, what hope is there? Valve need to do better. Also, don't deploy on a Friday, you dummies.
There's probably some better news coming though, as it appears Valve are preparing Vulkan support for CS:GO with the use of DXVK-Native just like they did for Portal 2, Left 4 Dead 2 and Half-Life 2. As we posted about recently on Twitter, a new "-vulkan" string was added and you can also see DXVK libs being added too.
L4D2 native crashes a lot as well. It truly feels like a joke.
I just can't believe that they a) they didn't test b) they pushed on a Friday and then, the final nail c) they did absolutely nothing about it all weekend. IncompetentAs someone who works freelance and switches projects about 2-3 times per year, let me tell you:
I can totally believe that.
The levels of incompetence and complete breakdown of communications on multiple levels I have seen in some companies (that you'd think would be more professional given their size) would make most people revert to their pre-landfall evolutionary state just to cope if they heard it.
The longer I work in IT, the more miraculous I find it that everything around us that is software does not crash and burn 99% of the time.
This damn game has been crashing for months now, it all started with the ironic "Broken Fang" update.
L4D2 native crashes a lot as well. It truly feels like a joke.
I was about to say it. This is not the first time this happens with CS:GO on Linux.
Also L4D2 on Linux is more crashy than before, and is not only on Linux. My friends on Windows occasionally crash too, but less often than me.
I work in an IT Department, and, "Don't deploy on Friday," is probably our number one rule. If you deploy something on Friday and it causes a problem over the weekend (and you are not the one on call), you will get bawled out.
Yeah, we found out the same in the last years. :)
if it got issues with the drivers elsewhere, well, that is not an priority for then.
honestly, there is another issue here:
for how many years valve will support steam deck and the games you purchase on it?
i mean, on a console you purchase and expect it to last at least 5 years until the next generation came, but on deck, we dont know how often valve will relase new models, as soon as the competition start catch up in prices they will need to relase an "deck pro" or "deck 2", where by the pro model i imply that they will still support the base model making sure new games work on it, but on the "2" model i imply that new games may not work on the previous models...
i hope they can give some guarantee that certain games will work forever (namely those who dont receive constant updates) and the ones who do only stop working when the hardware cant run they anymore.
I just can't believe that they a) they didn't test b) they pushed on a Friday and then, the final nail c) they did absolutely nothing about it all weekend. IncompetentAs someone who works freelance and switches projects about 2-3 times per year, let me tell you:
I can totally believe that.
The levels of incompetence and complete breakdown of communications on multiple levels I have seen in some companies (that you'd think would be more professional given their size) would make most people revert to their pre-landfall evolutionary state just to cope if they heard it.
The longer I work in IT, the more miraculous I find it that everything around us that is software does not crash and burn 99% of the time.
Which is why im glad i left the I.T industry. Much less stress now & happier all round.
I'm not following those issues, but on Reddit everyone that posted was using nvidia. This is happening on Mesa too?
Yep just as broken on AMD for me.
Some day...I just can't believe that they a) they didn't test b) they pushed on a Friday and then, the final nail c) they did absolutely nothing about it all weekend. IncompetentAs someone who works freelance and switches projects about 2-3 times per year, let me tell you:
I can totally believe that.
The levels of incompetence and complete breakdown of communications on multiple levels I have seen in some companies (that you'd think would be more professional given their size) would make most people revert to their pre-landfall evolutionary state just to cope if they heard it.
The longer I work in IT, the more miraculous I find it that everything around us that is software does not crash and burn 99% of the time.
Which is why im glad i left the I.T industry. Much less stress now & happier all round.
Some day...
It was interesting to see AWP and others in scope mode was just fine.
As much as I would like to live in a perfect world where these kinds of issues don't happen, I wouldn't trade Valve style for the stick-up-the-ass passionless corpo style disguised as gaming companies and yeeted onto the stock exchange to go Neo-Harkonnen on quarterly earnings -- that is the kind of capitalism people bitch about all the time. Privately owned like Valve and bam you have literally nurtured one of the biggest multi-billion dollar entertainment industries into existence, and manage to rank as the most lucrative company per employee in the United States a few years back.
Last edited by ElectricPrism on 13 December 2021 at 7:33 pm UTC
I work in an IT Department, and, "Don't deploy on Friday," is probably our number one rule. If you deploy something on Friday and it causes a problem over the weekend (and you are not the one on call), you will get bawled out.
Yeah, we found out the same in the last years. :)
How critical the product is might have something to do with it. I can imagine that Valve has no Friday deployments policy for store, but games might not have it.
If the product is actually critical, developers might have to do some work in the weekend and that's no fun.
The longer I work in IT, the more miraculous I find it that everything around us that is software does not crash and burn 99% of the time.
We do crash 99% of the time, that's why we created watchdogs.
See more from me