GOD EATER 2 Rage Burst (438490)

[Seizz]

Whitelist Request

• GOD EATER 2 Rage Burst
• 438490

System Information

• GPU: Geforce GT 820M
• Driver/LLVM version: nvidia-340 (dunno srsly it's linux one... tbh 100% honest, I play via integrated HD Graphics 3000 still, because last update for nvidia-340 drivers written bad and does not let me continue booting after loading accounts)
• Distro version: Ubuntu 19.04
• https://gist.github.com/Seizz/f663a129f80044afd1f0cd5a7752d048
• Proton version: Latest Proton 4.2

I confirm:

• [+] that pressing the Play button in the Steam client is sufficient.
• [+] that runtime config options are necessary to run the game.
• [+] that no workarounds other than PROTON_* env variables are necessary.

Issues

• [ ] I haven't experienced any issues.
• [ ] There are no issues left open for this game.
• [+] Although I consider the gaming experience equal to Windows there are remaining issues:

[Seizz]

Tired of seeing that the game launches and then just report window appear instead of game.

[Seizz]

God, seriously it is unfair as hell. Why would Dark Souls launch well with Proton then? The count of libraries to run Dark Souls is higher and include those that GOD EATER uses. https://appdb.winehq.org/objectManager.php?sClass=version&iId=34449&iTestingId=95773

[kisak-valve]

Hello @Seizz, please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

[ghost]

@kisak-valve I took the freedom and grabbed a log for of the said game. Its basically the same problem with God Eater Ressurrection and God Eater 2, so this maybe can fix the first one too. Here is the log for God Eater 2 Rage Burst: steam-438490.log

[Seizz]

Hello @kisak-valve, Sorry was sick for a while. Here is full... Proton log: steam-438490.log Nothing good just same as @stefan240 mentioned.

[Seizz]

@kisak-valve, What a twist even https://github.com/popsUlfr/Proton/releases/tag/proton-3.16-6-gne-0.3.0 this thing does not help. :( steam-438490.log

[ghost]

The first game (which is forcibly bundled with this and shares same store ID) now works for me with latest wine-staging.

I am not sure if Proton just needs updated Wine, or it needs staging patches.

Edit: I believe it requires some staging patch, as the game still does not work with proton-ge 4.11

[soredake]

Still not working with latest proton or proton-tkg

[soredake]

Game does start now with proton 5.0-2, sound is crackling (pulseaudio with tsched=0)

With gamepad connected game freezes on startup: steam-438490.log

[basxto]

On 5.0-2 I managed to get to selecting a savegame, but it hung there then. steam-438490.log

I got that far on the 10th try or so. At first it hung during the loading screen. It might make a difference if the window has focus all the time.

[soredake]

God eater 1 shows only black screen on start. steam-460870.log

https://gist.github.com/soredake/ed1fa30f885371dda5f331815920a3ae

[basxto]

God eater 1 460870

This is the wrong issue for that game

[rednaxela600]

With PROTON_NO_ESYNC and experimental or GE the game runs, but poorly. Other than cutscenes working in ge all other behavior is the same between them. The loading screens are still a little long and very choppy, which would be tolerable on its own. The main problem is the loading hitches in game menus like mission selection and much worse in combat. Frame rate hits single digits when shooting enemies. Outside of menus and combat, fps is solid 60. I don't think it's related to d3d emulation since dxvk and wined3d have the exact same results.

I see a lot of entries for GMOTextureManager and god_npc_tuning.cpp not finding files, but the game still runs and textures don't appear missing. Maybe it's losing time making multiple attempts, or loading the file with a fallback slower method?

System Info: systeminfo.txt Proton Log: steam-438490.log

[ipr]

Black screen on starting. Kernel 5.14.14, Mesa 21.2.4, AMD Vega 10 XL/XT [Radeon RX Vega 56/64]

steam-438490.log

[kisak-valve]

Hello @ipr, I'm not seeing a failure in your log. If you give the game excessive time to ponder its own existence (up to 20 minutes?), does it get further? You might have luck setting the game's launch options to PROTON_NO_ESYNC=1 %command%.

[ipr]

Hello @ipr, I'm not seeing a failure in your log. If you give the game excessive time to ponder its own existence (up to 20 minutes?), does it get further? You might have luck setting the game's launch options to PROTON_NO_ESYNC=1 %command%.

Hi, I ran some upgrades, switched to experimental version and waited. This time I got progress and eventually got into main menu as well. It is possible I did not wait long enough as symptoms looked similar to some other games.