On a side note: as the executables are signed for your current installation, a verify will always re-download them.Īliens: Colonial Marines fails to start, but not the game itself, so there is a new window popping up: Steam Client Service, which closes, and then I get the message: But it seems the date(s) where it works changes, if you accidentally have overwritten the executables with a verify. When I found a date that was working, I used `faketime -f 'YYYY-MM-DD' %command%` and was able to play. Or when killing the first alien in horde mode. or when looking at the overseers in the predator campaign. when activating the first generator in the marine campaign. So it does start and you can start playing, but there are certain trigger points where it can crashed. I got it working before, by copying over the CEG signed executables from a wine Steam install on the same machine, but it was a hit or miss. Giving a few titles a run myself this morning I was able to test that Saints Row: The Third, Call of Duty: Black Ops and Call of Duty: Modern Warfare 2 seem to work well now. At least those that actually load up in some way now can see additional testing and work with Proton.Ī new black Steam client service window will pop up when Steam goes to sort the CEG, eventually that should be hidden from users - so for now it's normal. Some titles probably still won't work with other issues present but it's getting another step closer. Plenty more have CEG DRM, so it will take time for all of them to be tested and reported on.

Some of the titles that may now work include: Valve developer Pierre-Loup Griffais said on Twitter it's only 'initial' support and to post any you test on the official GitHub bug report for it. This is quite a big one actually, as it was a total showstopper for numerous games. If you have the latest version of Proton Experimental, Valve just recently put up a new Steam Client Beta ( October 28) too which allows playing Windows games on Linux that make use of their older CEG DRM.

Saints row 3 website