protonscr

Risen 2 fails to start

protonopen appid 40390Game compatibility - Unofficial
ValveSoftware/Proton#1770 · opened 2018-10-17 by ghost · updated 2023-12-16 · 12 comments · github · game page · search this game
?ghost 2018-10-17 github

Compatibility Report

  • Name of the game with compatibility issues: Risen 2
  • Steam AppID of the game: 40390

System Information

I confirm:

  • [x] that I haven't found an existing compatibility report for this game.
  • [x] that I have checked whether there are updates for my system available.

Symptoms

Game doesn't start
steam-40390.log

Command line output has no problems shown

Need something else to go on.

It should be noted that Risen 2 might work without DXVK as noted by Wine wiki. DXVK command line args make no difference.

+all debug log may provide additional info needed; maybe could get away with less.

Reproduction

Install
Try to start

Llucifertdark 2018-10-18 github

Risen 2 includes the CEG DRM.

?ghost 2018-10-18 github

Risen 2 includes the CEG DRM.

Nothing is mentioned with drm being a problem as for as I can see on the Wine wiki: https://appdb.winehq.org/objectManager.php?sClass=application&iId=14177

Don't think its the problem, but there's still no way to know without a quality log entry or debugging [or download Wine and try it that way].

Llucifertdark 2018-10-18 github

Risen 2 includes the CEG DRM.

Nothing is mentioned with drm being a problem as for as I can see on the Wine wiki: https://appdb.winehq.org/objectManager.php?sClass=application&iId=14177

Don't think its the problem, but there's still no way to know without a quality log entry or debugging [or download Wine and try it that way].

Well not a single game that includes CEG works with Proton at the moment, Risen 2 just happens to be one of them.

?ghost 2018-10-18 github

Risen 2 includes the CEG DRM.

Nothing is mentioned with drm being a problem as for as I can see on the Wine wiki: https://appdb.winehq.org/objectManager.php?sClass=application&iId=14177
Don't think its the problem, but there's still no way to know without a quality log entry or debugging [or download Wine and try it that way].

Well not a single game that includes CEG works with Proton at the moment, Risen 2 just happens to be one of them.

Alice Madness Returns is listed as having CEG and does start and play fine, but it also has an EA activation screen.

So it depends on if the EA activation somehow passes the CEG check. If it doesn't then its not CEG, and if it does then CEG is fine (or the game actually doesn't have CEG despite being listed as having it) but Valve's servers are flagging other games as failed during start thus denying them from starting.

But it really needs some log entry or something to say that the server has rejected it to be 100% sure. Programming is a funny thing sometimes with making problems seem like one thing but coming from another.

Thanks for the input on this, it was good you knew about CEG =)

?ghost 2018-10-19 github
Llucifertdark 2018-10-21 github

I did have Risen 2 run once yesterday, played for about 5 minutes then it crashed & now refuses to start again, so you're right about it not being CEG & that something else is going on. I forgot to set up logging when it ran so I have no idea what made it work that one time.

?ghost 2018-10-28 github

I did have Risen 2 run once yesterday, played for about 5 minutes then it crashed & now refuses to start again, so you're right about it not being CEG & that something else is going on. I forgot to set up logging when it ran so I have no idea what made it work that one time.

Niiiice =)

Was looking through the log again and found 461 of not found entries:
eg 21015.809:0022:0023:trace:resource:find_entry_by_id root 0x7ff547b673e0 dir 0x7ff547b673e0 id 0018 not found

It looks like at least for me in Wine code this might refer to
https://github.com/wine-mirror/wine/blob/master/dlls/ntdll/resource.c

/**********************************************************************
 *  find_entry_by_id
 *
 * Find an entry by id in a resource directory
 */
static const IMAGE_RESOURCE_DIRECTORY *find_entry_by_id( const IMAGE_RESOURCE_DIRECTORY *dir,
                                                         WORD id, const void *root, int want_dir )
{
...
TRACE("root %p dir %p id %04x not found\n", root, dir, id );

These all come before wineserver:shutdown call and I would expect these to not be normal or at the very least these are spamming the log here. But, no idea why without building Proton myself which I won't be and I don't see them in the logs for the other games I did this with.

It took debugging using +all to get this; not found via the regular log anyway.

RRuedii 2020-04-22 github

On the one game that runs fine with CEG, the person might want to bring this up in the CEG bug.

This could be a cue to the exact issues that cause CEG games to fail right now as it will give a whitelist of some of the components of CEG that are currently working.

Like has been noted on the CEG bug, there is missing Steam Infrastructure in SteamPlay that is required for CEG. Apparently it is not required for all CEG titles, just most.

(edit: Clarity)

Mmirh 2021-10-30 github

CEG was fixed this week
And other crashes are https://bugs.winehq.org/show_bug.cgi?id=46472

Nniel 2022-01-23 github

Not sure if this is related or if I should start a new thread. I'm trying to get Risen 2 installed via Steam/Proton. After the initial download, which appears to go fine, I click Play and a dialogue opens saying that it is "Completing Installation". Eventually that fails with an error saying: "The Steam servers are too busy to handle your request for Risen 2 - Dark Water. Error Code (2)".

44164696f73 2023-09-15 github

I couldn't get Risen 2: Dark Waters (ID: 40390) to start with all possible Protons, so I'm throwing all that Proton log, system info and diagnostics in here.

Description:
The game launches the small splash art saying "Risen 2: Dark Waters", which initiates the game (classic Piranha Bytes game start), after which the game closes. I tried ALL Protons available in Steam, and took the logs from each (see gist), but all of them worked the same way.

Additional info:
I did play Risen 2 on Linux last year, though I do not remember which version of Proton it was. According to ProtonDB, the game worked on Proton 7.0-4, 3 and also on 6.3-8, which did not work for me. At that point, I was on Nvidia 750ti GPU, so there might be something related to that. Seems that people on ProtonDB mostly used Nvidia cards, and it also ran for some people on AMD (which I'm on AMD and it doesn't seem to like any of the Protons).

I'm open to try some suggestions on running the game, talking to you, Valve team. If there's any launch parameters you'd want me to try, feel free to list them so I can try them out (I'm not a very technical person, so I'd rather have some input from you than just going through the main page of this repo and trying all the launch options).

Two last files are system info and diagnostics, while all the other ones are Proton logs.
https://gist.github.com/4164696f73/71025c34175d16ce4c58eb27ea08dcee

List of Protons (not sure why I'm listing those, but whatever):

Proton3.7-8.log
Proton3.16-9.log
Proton4.2-9.log
Proton4.11-13.log
Proton5.0-10.log
Proton5.13-6.log
Proton6.3-8.log
Proton7.0-6.log
Proton8.0-3.log
ProtonExperimental.log
ProtonHotfix.log

I'm sad I can not play Risen 2... I was really hyped to play it throughout my 3 days of weekend. My dreams are ruined!

Aadiosocelote 2023-12-16 github

Something seems to be missing in the install script. After installing the game, running on Proton Experimental, game does not even load the splash screen, upon switching to 6.3-8, splash screen pops up, game launches (long launch time, though) and you can play the game. Switching back to Proton Experimental works normally, as if there was never an issue. Basically, it seems to be necessary to start on Experimental -> 6.3-8 -> Experimental (or stay on 6.3-8, up to you).

Proton versions

Upstream links