Hello,
Carrying this over from the steam forum.
I have been poking around with this, far out of my league and found a log file entry that I did not see shared before, though I could be wrong.
https://pastebin.com/deKSR00hline 29 is the interesting one
System.Security.Cryptography.
CryptographicException: Padding is invalid and cannot be removed
I know you had it narrowed down to that so I figured this might help, although it seems its out of your control and in wine, and maybe its a good clue for the wine crew to see and maybe its at the heart of a larger .net bug. Ill go post it on whatever wine has for a bug tracker, after I track it down. Proton has one but its for games that are already certified or whatever verbage they use.
Thanks for all your effort on this, its really cool and exciting. I just made the switch from windows 10 and every game I have tried works in proton. Ill update this post with any news from the wine world.
Ok first I see that the 5.7 version of wine that was release on april 18th I think, updated mono from 4.9.7 (i think) to 5.0.0. So Sooner or later Glorious Egroll will probably release proton compiled against this newer version, so I am going to hold off bug reporting with wine until after that and I test it.
After tons of google, and not knowing much, and based on everything you typed
Maybe that the system.security call SHOULD be made against the standalone binary, but mono has that method and wine is calling it instead, and the mono method is assumes the wrong padding size vs the MS one?
I read you MAY be able to workaround it by explicitly stating the padding size for both decryption and encryption, but that a workaround for a "bug" in an unsupported system , and that might be total crap
I will test this as soon as i can get ahold of a test proton compiled against wine 5.7 and update this and then proceed to wine bug reporting.