MShadowy
Published
It would actually be totally fine, but it's obnoxious to get things done given the regularity with which the game faceplants.
Proton-5.21-GE-1 GloriousEggroll
Some issues with a sluggish framerate and a general lagginess to the inputs; not a lot, but noticeable
Crashes with predictable regularity after about 20-25 minutes of play time; running with PROTON_LOG=1 %command% leaves the following near the end of the log file:
eventfd: Too many open files
Protocol error: process 00fc: sendmsg: Bad file descriptor
...
wine: Unhandled page fault on execute access to 00007F2A30946F45 at address 00007F2A30946F45 (thread 00a0), starting debugger...
Runs but does not start under GE-Proton 8-16 ; black screen on default settings
Tried Proton GE 8.16 as well
Seems like it might be a Media Foundation issue?
While GE hangs during module loading for some reason, running it under the default 8.0-3 gets past the initial loading stage; unfortunately, that's where it stops, with the game stopping on a black screen I can't get past. Looking at the logs with PROTON_LOG=1 %command% returns:
12870.411:0130:024c:err:combase:RoGetActivationFactory Failed to find library for L"Windows.System.DispatcherQueue"
12870.419:0130:02d4:fixme:combase:RoGetActivationFactory (L"Windows.System.DispatcherQueue", {00000035-0000-0000-c000-000000000046}, 0000000164E7F9F0): semi-stub
From what I know this characteristic of something we'd previously fix with mf-install, but I have no idea why it's occurring here. This is an oddly anachronistic error at this point.
Forces offline mode with the message "Inappropriate activity detected. Starting in offline mode." presumably due to EAC.
The game does not work at all without Glorious Eggroll, freezing on a white screen at startup. I'm not really sure why it seems to have worked for me and not anyone else, especially since many of them have used the same version of GE that I did. Even so, the asynchronous multiplayer aspects I feel would be sorely missed for any play through.
Additionally, for whatever reason, some dialogue audio files do not play, though I haven't tried overriding xaudio2_7 yet.
Hangs trying to start mission one with both 5.13-4 and Glorious Eggroll 5.21-GE-1
Not much else to add, really; it's the same problem everyone else has reported in previous versions or Proton. Disabling ESync does reduce frame hiccups significantly, however, and basically halves CPU usage.
I set up a logfile but I'm sure how useful it is; there is a repeating error while the game is starting where it can't find a rendering module for an overlay, but it seems doubtful that this would cause the infinite loading error people have been reporting.
However, there is also an unmarked error later on which might be more fruitful, as this reports creating a minidump:
Unable to read VR Path Registry from C:\users\steamuser\Local Settings\Application Data\openvr\openvrpaths.vrpath Setting breakpad minidump AppID = 899440 Steam_SetMinidumpSteamID: Caching Steam ID: 76561198005614259 [API loaded no]
Black screen; Checking the logs indicates quartz failing to initialize the MPEG/ACMWrapper
Tried protontricks 992300 ffdshow
Getting the program log with PROTON_LOG=1 %command% results in the following:
2032699.189:0031:0032:err:quartz:CheckCircularConnection Checking filtergraph returned 80040231, something's not right! 2032699.198:0031:0032:fixme:quartz:ACMWrapper_SetMediaType acmStreamOpen returned 512 2032699.208:0031:0032:fixme:quartz:MPEGSplitter_query_accept {00000000-0000-0000-0000-000000000000} 2032699.208:0031:0032:fixme:quartz:MPEGSplitter_query_accept {00000000-0000-0000-0000-000000000000}
Further above in the log we get: 2032699.108:0031:0032:err:ole:CoGetClassObject class {1643e180-90f5-11ce-97d5-00aa0055595a} not registered 2032699.108:0031:0032:err:ole:CoGetClassObject no class object {1643e180-90f5-11ce-97d5-00aa0055595a} could be created for context 0x1
Followed shortly by: 2032699.085:0031:0032:err:quartz:GetClassMediaFile Media class not found
Unfortunately I'm not entirely sure why this has started failing; from earlier reports the video format appears to be h.264, which ffdshow should support.
