It seems users trying out SOULCALIBUR VI in Steam Play ended up with a major issues in both Linux and Windows due to a bug in Steam Play's Proton. This bug, ended up making it so SOULCALIBUR VI would not be able to use any online features after loading it up on Linux with Valve's Steam Play even once.
I held off on reporting about this previously, because many things about the problems were unclear and I didn't want to end up making anything worse. This has, thankfully, been cleared up now by Valve. Here's what Valve developer Pierre-Loup Griffais said on the bug report:
The issue with the SOULCALIBUR VI network error is now understood to be caused by a bug in the Proton Steamworks implementation of leaderboards data. The bug causes the Steam client to upload corrupt entries to the backend, which causes the game client to fail network initialization on all platforms. We will be deploying a fix in Proton as well as deleting the corrupt data for affected accounts. Due to the design of online data for that title, it also appears that affected accounts end up fixing themselves after a couple days of not attempting to log in through Steam Play. It's possible there are more network issues masked by this one, but none are known as of yet. There are also other issues affecting this title at the moment, such as missing FMVs and occasional client freezes on startup.
As with any issue specific to Steam Play, please remember to get support directly from Valve through this tracker, rather than reaching out to the original developers directly. This is especially important in this early beta stage, as these issues are largely outside their control, and developers of Windows titles are not typically equipped to deal with these issue reports.
Of course, this is a good reminder that Steam Play is still relatively new (even if Wine itself has been around a long time) and so there's probably a number of major issues like this waiting to be found and fixed. Still, it's good to know Valve are on top of things before this ended up becoming something even bigger for other titles.
It's also a good reminder to report issues to Valve not the game developer, as Valve did ask in their original Steam Play announcement which you can do so on this GitHub.
In other Steam Play related news, for those wanting to try The Vanishing of Ethan Carter Redux on AMD GPUs it looks like the next version of DXVK will spoof an NVIDIA GPU to fix it. It also seems that Quake Champions may also get a performance boost, Sword Art Online: Fatal Bullet is going to spoof an AMD GPU to improve performance and a few more little bits like that should come.
Article taken from GamingOnLinux.com.
Quoting: Purple Library GuyQuake Champions . . . for some horrible reason this sent me onto a train of thought: There should be a game, maybe a series of games, about heroic mushrooms. Quake Champignons, Eternal Champignons, Deathrace Champignons, Ultimate Arena Champignons and so forth.And all that with a glass of Dom Perignon Champagne.
Quoting: EgonautWho cares about performance improvements on Quake Champions, if that game doesn't even work because of error 103 :DIt's kinda nuts to think how far it will come in a year from now.
Proton still has a lot of bugs to fix, but it is on a good way, I'm looking forward to what games will work early next year.
Quoting: Code ArtisanIf the server accepts corrupted entries from clients, there is something wrong there too.it dont, that is why it was caught. (probably)
anyway, so... if those users are geting banned due to the netcode that means some of then were able to test the game at least offline?
i wonder if the game works already (at least offline)
valve made proton as open source, but if i fork it and end up geting banned not due to the proton code but due to some custom code that i made trying to get an game to work, how can i tell valve whats happened that i got banned?
if its their own code, its easy for then to debug and realize that i was not trying to cheat, otherwise...
Quoting: elmapulQuoting: Code ArtisanIf the server accepts corrupted entries from clients, there is something wrong there too.it dont, that is why it was caught. (probably)
anyway, so... if those users are geting banned due to the netcode that means some of then were able to test the game at least offline?
i wonder if the game works already (at least offline)
Nobody was getting banned. It was an authentication error caused by a bug in Proton.
Quoting: elmapulQuoting: Code ArtisanIf the server accepts corrupted entries from clients, there is something wrong there too.it dont, that is why it was caught. (probably)
anyway, so... if those users are geting banned due to the netcode that means some of then were able to test the game at least offline?
i wonder if the game works already (at least offline)
Quoting: aFoxNamedMorrisQuoting: elmapulQuoting: Code ArtisanIf the server accepts corrupted entries from clients, there is something wrong there too.it dont, that is why it was caught. (probably)
anyway, so... if those users are geting banned due to the netcode that means some of then were able to test the game at least offline?
i wonder if the game works already (at least offline)
Nobody was getting banned. It was an authentication error caused by a bug in Proton.
Then how come it also affected Windows?
Quoting: Code ArtisanQuoting: elmapulQuoting: Code ArtisanIf the server accepts corrupted entries from clients, there is something wrong there too.it dont, that is why it was caught. (probably)
anyway, so... if those users are geting banned due to the netcode that means some of then were able to test the game at least offline?
i wonder if the game works already (at least offline)
Quoting: aFoxNamedMorrisQuoting: elmapulQuoting: Code ArtisanIf the server accepts corrupted entries from clients, there is something wrong there too.it dont, that is why it was caught. (probably)
anyway, so... if those users are geting banned due to the netcode that means some of then were able to test the game at least offline?
i wonder if the game works already (at least offline)
Nobody was getting banned. It was an authentication error caused by a bug in Proton.
Then how come it also affected Windows?
Because the server was attempting to process invalid and corrupted data. This data is tied to the user's account. The affected accounts were fine after the server decided to purge the corrupted data, usually in a day or two.
Bans typically don't just automatically fix themselves.
Last edited by D34VA_ on 28 October 2018 at 3:36 pm UTC
Patreon
PayPal
See more from me