Rpcs3: Dead Island: No longer going ingame

[Shoegzer]

Dead Island [NPUB31066] hangs shortly after the intro splash screens. The first thing you will notice is that you cannot enter any gamepad inputs to skip those screens. Eventually the game hangs on a black screen after the last one.

Bisecting shows the first bad commit is f1f5c91386e017f0a4fc1af4ba5ffeb2f575f0a9, which is from PR https://github.com/RPCS3/rpcs3/pull/7516.

Also note this should have nothing to do with (https://github.com/RPCS3/rpcs3/issues/6798), a separate issue involving graphics which renders the game essentially unplayable.

Tested on linux mint 19.3, and kernel 5.3 x64, compiled using gcc 9.2.1

Log from bad build: RPCS3.log

Update: This is "fixed" by setting Network status to "connected" and PSN status to "simulated" though it's unclear why, given that prior to the above commit the game was working with network set to "disconnected". Also, even after this "fix", the game now takes much longer to go ingame (I've clocked it at 50 seconds, whereas prior to the above commit it was going ingame in 2-5 seconds). This is possibly due to a network timeout on behalf of the game as it seeks a connection to PSN and eventually fails.

[elad335]

you really are not helping without specifying exact pull request..

[Megamouse]

tbf it's two clicks. so idk why you're upset XD

[elad335]

@Shoegzer is 54775d9 the first build not working or just the one you last tested?

[Shoegzer]

@elad335 https://github.com/RPCS3/rpcs3/commit/54775d91dc0809c0f3e9f7469f5e93ef77ca098b is the build I tested that exhibited the issue. Again it wokred with commit https://github.com/RPCS3/rpcs3/commit/c7fa4e237520b0398460417f5f015bf453b03e6a which was recent, I was hoping that would help narrow it down rather than leaving it open-ended. I can do a bisect to get the exact commit where the regression occurred if you need it, I just haven't had time to do that yet.

[elad335]

Yes, it's just a waste of developer time and money to narrow down to exact commit/build instead of user which reported the issue in the first place.

[dio-gh]

Long story short he says yes please.

[Shoegzer]

Yep, I suppose he is. To be clear I AM offering to bisect when I have some more time to do that, in case the cause of this issue wasn't immediately apparent to him. I take by his response that it is not, so I'll do that when I have time.

[Shoegzer]

This took a while, but I finally bisected, and updated the above post with the results.

My guess is that this title runs some sort of PSN check before going ingame and has some problem with this stub.

@RipleyTom any thoughts here?

[dio-gh]

Have you tested setting the PSN connection status in the Network tab to Simulated? (With the regular connection status as both Connected and Disconnected?)

[Shoegzer]

@dio-gh Thanks, I hadn't thought to try that because I assumed the previous configuration (which worked fine) was the same as "Network: disconnected" and "PSN: disconnected". However, when I changed it to "Network: connected" and "PSN: simulated", it worked. It would be interesting to know why this is suddenly required, but apparently it is.

If the consensus is that this is expected behavior, I'll close this one.

[dio-gh]

Interesting. Nothing should have changed. I'll pass it over to @RipleyTom to decide.

[Shoegzer]

I've updated the post above with the latest findings re: network settings and also indicating that the game takes much longer to go ingame than it did prior to this commit (clocked at 50 seconds vs. 2-5 seconds).

[Asinin3]

@Shoegzer Please retest. You said it was fixed by changing network settings which you didn't have to change in previous builds. And since there has been a ton of networking related changed we'd like to know if this is still a problem.

[MsDarkLow]

The game goes ingame just fine, it doesn't matter which network setting you are using.
Tested each network setting and result is always the same.
RPCN currently allows you to select the ingame's playstation network option and go ingame but the online functionality doesn't currently work.

[Shoegzer]

@Asinin3 confirmed this is no longer an issue. I was going to test it last night when checking in on another issue with this title (overbloom) but hadn't gotten to it in time. There seems to be a performance regression (used to get 30fps, now at about 15fps) but that's something different.