Yukari-Kuramoto commented 6 years ago

Whitelist Request

Name of the game to be whitelisted: Tokyo Xanadu eX+
Steam AppID of the game: 587260

System Information

GPU: GTX 1080
Driver/LLVM version: nvidia 396.54
Kernel version: 4.18.6
Link to full system information report as Gist
Proton version: 3.7-5 beta

I confirm:

[x] 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 the mentioned ones are necessary.

Issues

[x] 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:

kisak-valve commented 5 years ago

Proton 4.2-4 causes flickering and breaks compat with Tokyo Xanadu eX+

Issue transferred from https://github.com/ValveSoftware/Proton/issues/2692. @jcfrosty posted on 2019-05-16T02:35:38:

Compatibility Report

Name of the game with compatibility issues: Tokyo Xanadu eX+
Steam AppID of the game: 587260

System Information

GPU: Radeon VII
Driver/LLVM version: Mesa 19.0.3/LLVM 8.0.0
Kernel version:5.0.9
Link to full system information report as Gist:
Proton version: 4.2-4

I confirm:

[x] that I have found an existing compatibility report for this game. There is a whitelist request for this game. This game used to work perfectly. I've been playing it for over a month now. After recent upgrade to proton 4.2-4, its now flickering and unplayable.
[x] that I have checked whether there are updates for my system available.

steam-587260.log

Symptoms

Tokyo Xanadu eX+ has been working great for some time now. Proton 4.X has been working with no issues until recently when 4.2-4 was released. Now the game flickers a black screen on and off. Now if you have an extra wide monitor it uses a still image to fill in the gap and the still image doesn't flicker, the HUD of the game doesn't flicker, only the game play portion flickers.

Reproduction

upgrade from proton 4.2-3 to 4.2-4 and the game stops being playable.

https://gist.github.com/jcfrosty/938c89ecb73d38dfe032f2c129d4f978

Showing others have been able to play the game for quite some time now as well: https://github.com/ValveSoftware/Proton/issues/1295

jcfrosty commented 5 years ago

4.2-5 doesn't fix the issue. Still broken.

jcfrosty commented 5 years ago

4.2-7 Still Broken.

doitsujin commented 5 years ago

@jcfrosty The game works fine for me on both my RX 480 and Kaveri notebook with RADV. Maybe it's a Vega-specific driver bug?

jcfrosty commented 5 years ago

Forcing the game to use an older version of proton makes the game playable again. I'd be happy to dig further is someone can tell me exactly want they need/want.

On Tue, Jun 18, 2019, 06:22 Philip Rebohle notifications@github.com wrote:

@jcfrosty https://github.com/jcfrosty The game works fine for me on both my RX 480 and Kaveri notebook with RADV. Maybe a Vega-specific driver bug?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/1295?email_source=notifications&email_token=ADIRCGNSWAHGPHGK7WLXHZ3P3DAQPA5CNFSM4FT2GAI2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODX6B3QA#issuecomment-503061952, or mute the thread https://github.com/notifications/unsubscribe-auth/ADIRCGNPPM7EAXQQHDNQBJDP3DAQPANCNFSM4FT2GAIQ .

aqxa1 commented 5 years ago

@doitsujin I have the flicker issue with a Vega 56 and 4.2-9, so yeah, it could be Vega specific.

aqxa1 commented 5 years ago

The flickering bug looks to be an interaction between esync, DXVK, and Proton. Disabling esync works around the problem, albeit with a significant performance loss.

Esync with Wine-staging + DXVK does work (although I had a black screen at some point that may be due to missing video support). It could be that the issue was fixed with newer Wine, or the staging version of esync is different to the one that Proton uses.

Wined3d also works around the problem, and gives better performance than disabling esync.

So, in summary:

Proton 4.2-9 + DXVK (git and the provided version) + esync - flickering
Proton 4.2-9 + DXVK + no esync - no flickering, slow
Proton 4.2-9 + WineD3D + esync - no flickering
Wine-staging 4.11 + DXVK + esync - no flickering
Wine-staging 4.11 + WineD3D + esync - no flickering

So, best option if you want to use Proton is with PROTON_WINED3D=1, otherwise use ~wine-staging + DXVK~. Can't use wine-staging because videos consistently cause a black screen (everything else works but game won't advance because the video won't play). Might be possible to workaround.

It should also be noted that videos are also broken with Proton, they are just skipped over silently instead of causing a black screen.

aqxa1 commented 5 years ago

The flickering issue does also look to be Vega specific, as I tested a RX550, and the problem doesn't exist. I can't test AMDVLK since AMD they don't provide 32-bit builds (and compiling the driver is painful), and this is a 32-bit game.

aqxa1 commented 5 years ago

Interestingly, bug doesn't exist when using the new ACO shader compiler.

hakzsam commented 5 years ago

I tried to reproduce the flickering problem on my Vega 56 with Mesa 19.2.0 and LLVM 8.0.1, I didn't spot anything wrong. How do I reproduce it? Can you record a video of the problem?

aqxa1 commented 5 years ago

@hakzsam I don't currently have my Vega card plugged in, but I'll try and test it again soon. I will add that the issue doesn't seem to occur with Navi with esync or fsync, either.

It's possible it was fixed in Proton, as it was always a Proton + esync specific issue, with all other configurations working (I haven't tested fsync on Vega, though).

aqxa1 commented 5 years ago

@hakzsam I just tested with Vega and I can't trigger the bug anymore. Tested with esync/fsync with LLVM and ACO. Might have been a bug with wine/proton 4.2, since I didn't have the issue at the time with 4.11-staging.

kisak-valve commented 5 years ago

@jcfrosty, can you check how this game behaves for you and Proton 4.11 as well?

jcfrosty commented 5 years ago

I'll check today and let you know. There have also been kernel updates and Mesa updates (19.2) we'll see if it's fixed.

On Thu, Oct 10, 2019, 07:29 kisak-valve notifications@github.com wrote:

@jcfrosty https://github.com/jcfrosty, can you check how this game behaves for you and Proton 4.11 as well?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/1295?email_source=notifications&email_token=ADIRCGLQUE5WVEXBOG7LJIDQN4NY3A5CNFSM4FT2GAI2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEA4B64Q#issuecomment-540548978, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADIRCGN3FTKY5VKONZVPHXLQN4NY3ANCNFSM4FT2GAIQ .

jcfrosty commented 5 years ago

Proton 4.11-7 appears to work very well! There is one minor flaw that I can find and it seems to pertain to strange resolution monitors that require a border. A little background on the setup: I have a Samsung CHG90 that is a dual 1080P monitor (3840x1080). This game doesn't support resolutions like that so, it basically adds a background and stretches it to fill the screen so there are no black bars on each side of the gameplay "window" in fullscreen mode. I'd say about every 1-3 minutes you get a flicker, but the actual gameplay portion of the screen never flickers. Gameplay is smooth as butter. I'd rate this on protondb with GOLD. If the fickering were non-existent on the strange filler background, I'd give it a Platinum. Normal ratio monitors such as 16:9 and 16:10 will never get this issue.

trenton4k commented 4 years ago

steam-587260.log crashes on startup on proton 5.0 work on 4.11

kisak-valve commented 4 years ago

Hello @trenton4k, "Fix frequent crash introduced in Proton 5.0-1 related to video and audio playback." in Proton 5.0-2 should have helped with the regression, please retest.

jcfrosty commented 4 years ago

using 5.0-6 everything seems to be working. I'll play the game this weekend and give it a solid test and report back.

jcfrosty commented 4 years ago

Game works extremely well. Only issue is something I reported in the past. It seems like its actually better than before and border/backdrop flickers even less. For context, I'm talking about :

There is one minor flaw that I can find and it seems to pertain to strange resolution monitors that require a border. A little background on the setup: I have a Samsung CHG90 that is a dual 1080P monitor (3840x1080). This game doesn't support resolutions like that so, it basically adds a background and stretches it to fill the screen so there are no black bars on each side of the gameplay "window" in fullscreen mode. I'd say about every 1-3 minutes you get a flicker, but the actual gameplay portion of the screen never flickers. Gameplay is smooth as butter. I'd rate this on protondb with GOLD. If the fickering were non-existent on the strange filler background, I'd give it a Platinum. Normal ratio monitors such as 16:9 and 16:10 will never get this issue.

Execreed commented 4 years ago

This game turns into a blank black screen (doesn't crash completely) right after "White Shadow II" chapter. You need to find a save to progress past this chapter. No problems what-so-ever until then, or after it. I'm not sure If this only applies to me, but I tried it on multiple versions. (Used the Steam for all of them, while using most of the versions of proton up to 5.0-6) I can provide a save file for anyone who wants to try it.

jcfrosty commented 4 years ago

This game turns into a blank black screen (doesn't crash completely) right after "White Shadow II" chapter. You need to find a save to progress past this chapter. No problems what-so-ever until then, or after it. I'm not sure If this only applies to me, but I tried it on multiple versions. (Used the Steam for all of them, while using most of the versions of proton up to 5.0-6) I can provide a save file for anyone who wants to try it.

Is there a way you can zIp a save file and attach it here?

I was playing on both Linux and Windows and do recall running into this. I remember loading the save file on my windows machine just fine and skipping the cutscene and saving and then I was able to progress. This may be an issue with media loading?

lalith1996 commented 4 years ago

Just got to white shadow 2 chapter and confirm that I get the black screen and it just freezes. I have tried the proton 5.9 ge and the official and it still shows the black screen. I have asked for a save file on the discussion page. WOndering if you guys ran into a fix yet.

Execreed commented 4 years ago

Sorry I've been busy recently.. I'll just submit my whole .zip file (I know that the White Shadow 2 Chapter is somewhere in there.

https://drive.google.com/file/d/14g1EY7mTKFNBgtt5tkmTWQoowWYF_1ya/view?usp=sharing

let me know if that link works.

Execreed commented 4 years ago

My guess would be that it has something to do with loading the ev06_00_00.wmv file (inside movie or moviejp) on the screen in the town. Not sure if that is something anyone could fix.

lalith1996 commented 4 years ago

Ah thank you, I ended up watching the rest of the game on Youtube. It sucks that the game won't let that scene skipped either. I have tried skipping it and it just leads to that black screen.

Execreed commented 4 years ago

There should be a save past that portion of the game in there. If there is not, then I can prob get you one.

Here are some logs that might be helpful (not big on debugging wine/proton games)

``` **24941.663:0036:0037:warn:debugstr:OutputDebugStringA "playMovie(ev06_00_00)\n"** 24941.663:0036:0037:trace:seh:raise_exception code=40010006 flags=0 addr=0x7b43d65d ip=7b43d65d tid=0037 24941.663:0036:0037:trace:seh:raise_exception info[0]=00000017 24941.663:0036:0037:trace:seh:raise_exception info[1]=03dd6118 24941.663:0036:0037:trace:seh:raise_exception eax=7b42a451 ebx=7b640ff4 ecx=00000000 edx=0032a554 esi=0032a5f8 edi=0032a558 24941.663:0036:0037:trace:seh:raise_exception ebp=0032a5a8 esp=0032a534 cs=f7bf0023 ds=002b es=002b fs=0063 gs=006b flags=00200212 24941.663:0036:0037:trace:seh:call_vectored_handlers calling handler at 0x6a64d600 code=40010006 flags=0 24941.663:0036:0037:trace:seh:call_vectored_handlers handler at 0x6a64d600 returned 0 24941.663:0036:0037:trace:seh:call_vectored_handlers calling handler at 0x6f48afe0 code=40010006 flags=0 24941.663:0036:0037:trace:seh:call_vectored_handlers handler at 0x6f48afe0 returned 0 24941.663:0036:0037:trace:seh:call_stack_handlers calling handler at 0x7b486df0 code=40010006 flags=0 24941.663:0036:0037:trace:seh:__regs_RtlUnwind code=40010006 flags=2 24941.663:0036:0037:trace:seh:__regs_RtlUnwind eax=00000000 ebx=7b486d50 ecx=0032a540 edx=0032a5fc esi=0032a5fc edi=7b486d50 24941.663:0036:0037:trace:seh:__regs_RtlUnwind ebp=0032a118 esp=0032a0f8 eip=7b486dad cs=0023 ds=002b fs=0063 gs=006b flags=00200206 24941.663:0036:0037:trace:seh:__regs_RtlUnwind calling handler at 0x7bc85ef0 code=40010006 flags=2 24941.663:0036:0037:trace:seh:__regs_RtlUnwind handler at 0x7bc85ef0 returned 1 **24941.664:0036:0037:warn:debugstr:OutputDebugStringA "d:\\projects\\tokyoxanadu\\phyreengine\\core\\video\\win32\\./DShowCtrl.inl(821) : error: DShowCtrl::PImpl::setupFiltersAndRenderPins #1d\n"** 24941.664:0036:0037:trace:seh:raise_exception code=40010006 flags=0 addr=0x7b43d65d ip=7b43d65d tid=0037 24941.664:0036:0037:trace:seh:raise_exception info[0]=00000084 24941.664:0036:0037:trace:seh:raise_exception info[1]=03dd69a0 24941.664:0036:0037:trace:seh:raise_exception eax=7b42a451 ebx=7b640ff4 ecx=00000000 edx=00329d74 esi=00329e18 edi=00329d78 24941.664:0036:0037:trace:seh:raise_exception ebp=00329dc8 esp=00329d54 cs=f7bf0023 ds=002b es=7bd1002b fs=7bd10063 gs=006b flags=00200212 24941.664:0036:0037:trace:seh:call_vectored_handlers calling handler at 0x6a64d600 code=40010006 flags=0 24941.664:0036:0037:trace:seh:call_vectored_handlers handler at 0x6a64d600 returned 0 24941.664:0036:0037:trace:seh:call_vectored_handlers calling handler at 0x6f48afe0 code=40010006 flags=0 24941.664:0036:0037:trace:seh:call_vectored_handlers handler at 0x6f48afe0 returned 0 24941.664:0036:0037:trace:seh:call_stack_handlers calling handler at 0x7b486df0 code=40010006 flags=0 24941.664:0036:0037:trace:seh:__regs_RtlUnwind code=40010006 flags=2 24941.664:0036:0037:trace:seh:__regs_RtlUnwind eax=00000000 ebx=7b486d50 ecx=00329d60 edx=00329e1c esi=00329e1c edi=7b486d50 24941.664:0036:0037:trace:seh:__regs_RtlUnwind ebp=00329938 esp=00329918 eip=7b486dad cs=0023 ds=002b fs=0063 gs=006b flags=00200202 24941.664:0036:0037:trace:seh:__regs_RtlUnwind calling handler at 0x7bc85ef0 code=40010006 flags=2 24941.664:0036:0037:trace:seh:__regs_RtlUnwind handler at 0x7bc85ef0 returned 1 **24941.664:0036:0037:warn:debugstr:OutputDebugStringA "d:\\projects\\tokyoxanadu\\phyreengine\\core\\video\\win32\\./DShowCtrl.inl(932) : warning: DShowCtrl::PImpl::openFile #2 m\n"** 24941.664:0036:0037:trace:seh:raise_exception code=40010006 flags=0 addr=0x7b43d65d ip=7b43d65d tid=0037 24941.664:0036:0037:trace:seh:raise_exception info[0]=00000076 24941.664:0036:0037:trace:seh:raise_exception info[1]=03dd69a0 24941.664:0036:0037:trace:seh:raise_exception eax=7b42a451 ebx=7b640ff4 ecx=00000000 edx=00329db4 esi=00329e58 edi=00329db8 24941.664:0036:0037:trace:seh:raise_exception ebp=00329e08 esp=00329d94 cs=f7bf0023 ds=3dd002b es=002b fs=7bc50063 gs=32006b flags=00200212 24941.664:0036:0037:trace:seh:call_vectored_handlers calling handler at 0x6a64d600 code=40010006 flags=0 24941.664:0036:0037:trace:seh:call_vectored_handlers handler at 0x6a64d600 returned 0 24941.664:0036:0037:trace:seh:call_vectored_handlers calling handler at 0x6f48afe0 code=40010006 flags=0 24941.664:0036:0037:trace:seh:call_vectored_handlers handler at 0x6f48afe0 returned 0 24941.664:0036:0037:trace:seh:call_stack_handlers calling handler at 0x7b486df0 code=40010006 flags=0 24941.664:0036:0037:trace:seh:__regs_RtlUnwind code=40010006 flags=2 24941.664:0036:0037:trace:seh:__regs_RtlUnwind eax=00000000 ebx=7b486d50 ecx=00329da0 edx=00329e5c esi=00329e5c edi=7b486d50 24941.664:0036:0037:trace:seh:__regs_RtlUnwind ebp=00329978 esp=00329958 eip=7b486dad cs=0023 ds=002b fs=0063 gs=006b flags=00200206 24941.664:0036:0037:trace:seh:__regs_RtlUnwind calling handler at 0x7bc85ef0 code=40010006 flags=2 24941.664:0036:0037:trace:seh:__regs_RtlUnwind handler at 0x7bc85ef0 returned 1 24941.664:0036:0037:warn:debugstr:OutputDebugStringA **"d:\\projects\\tokyoxanadu\\phyreengine\\core\\video\\win32\\./DShowCtrl.inl(1054) : error: DShowCtrl::play #2\n"** 24941.664:0036:0037:trace:seh:raise_exception code=40010006 flags=0 addr=0x7b43d65d ip=7b43d65d tid=0037 24941.664:0036:0037:trace:seh:raise_exception info[0]=00000068 24941.664:0036:0037:trace:seh:raise_exception info[1]=03dd66c8 24941.664:0036:0037:trace:seh:raise_exception eax=7b42a451 ebx=7b640ff4 ecx=00000000 edx=00329df4 esi=00329e98 edi=00329df8 24941.664:0036:0037:trace:seh:raise_exception ebp=00329e48 esp=00329dd4 cs=f7bf0023 ds=3dd002b es=002b fs=7bc50063 gs=32006b flags=00200216 24941.664:0036:0037:trace:seh:call_vectored_handlers calling handler at 0x6a64d600 code=40010006 flags=0 24941.664:0036:0037:trace:seh:call_vectored_handlers handler at 0x6a64d600 returned 0 24941.664:0036:0037:trace:seh:call_vectored_handlers calling handler at 0x6f48afe0 code=40010006 flags=0 24941.664:0036:0037:trace:seh:call_vectored_handlers handler at 0x6f48afe0 returned 0 24941.664:0036:0037:trace:seh:call_stack_handlers calling handler at 0x7b486df0 code=40010006 flags=0 24941.664:0036:0037:trace:seh:__regs_RtlUnwind code=40010006 flags=2 24941.664:0036:0037:trace:seh:__regs_RtlUnwind eax=00000000 ebx=7b486d50 ecx=00329de0 edx=00329e9c esi=00329e9c edi=7b486d50 24941.664:0036:0037:trace:seh:__regs_RtlUnwind ebp=003299b8 esp=00329998 eip=7b486dad cs=0023 ds=002b fs=0063 gs=006b flags=00200206 24941.664:0036:0037:trace:seh:__regs_RtlUnwind calling handler at 0x7bc85ef0 code=40010006 flags=2 24941.664:0036:0037:trace:seh:__regs_RtlUnwind handler at 0x7bc85ef0 returned 1 **24941.665:0036:0037:warn:debugstr:OutputDebugStringA "??????????????: ev06_00_00\n"** 24941.665:0036:0037:trace:seh:raise_exception code=40010006 flags=0 addr=0x7b43d65d ip=7b43d65d tid=0037 24941.665:0036:0037:trace:seh:raise_exception info[0]=0000001c 24941.665:0036:0037:trace:seh:raise_exception info[1]=03dd68f8 24941.665:0036:0037:trace:seh:raise_exception eax=7b42a451 ebx=7b640ff4 ecx=00000000 edx=0032a554 esi=0032a5f8 edi=0032a558 24941.665:0036:0037:trace:seh:raise_exception ebp=0032a5a8 esp=0032a534 cs=f7bf0023 ds=002b es=002b fs=0063 gs=006b flags=00200212 24941.665:0036:0037:trace:seh:call_vectored_handlers calling handler at 0x6a64d600 code=40010006 flags=0 24941.665:0036:0037:trace:seh:call_vectored_handlers handler at 0x6a64d600 returned 0 24941.665:0036:0037:trace:seh:call_vectored_handlers calling handler at 0x6f48afe0 code=40010006 flags=0 24941.665:0036:0037:trace:seh:call_vectored_handlers handler at 0x6f48afe0 returned 0 24941.665:0036:0037:trace:seh:call_stack_handlers calling handler at 0x7b486df0 code=40010006 flags=0 24941.665:0036:0037:trace:seh:__regs_RtlUnwind code=40010006 flags=2 24941.665:0036:0037:trace:seh:__regs_RtlUnwind eax=00000000 ebx=7b486d50 ecx=0032a540 edx=0032a5fc esi=0032a5fc edi=7b486d50 24941.665:0036:0037:trace:seh:__regs_RtlUnwind ebp=0032a118 esp=0032a0f8 eip=7b486dad cs=0023 ds=002b fs=0063 gs=006b flags=00200206 24941.665:0036:0037:trace:seh:__regs_RtlUnwind calling handler at 0x7bc85ef0 code=40010006 flags=2 24941.665:0036:0037:trace:seh:__regs_RtlUnwind handler at 0x7bc85ef0 returned 1 24941.665:0036:0037:trace:seh:raise_exception code=40010006 flags=0 addr=0x7b43d65d ip=7b43d65d tid=0037 24941.665:0036:0037:trace:seh:raise_exception info[0]=0000001c 24941.665:0036:0037:trace:seh:raise_exception info[1]=03dd68f8 24941.665:0036:0037:trace:seh:raise_exception eax=7b42a451 ebx=7b640ff4 ecx=00000000 edx=0032a554 esi=0032a5f8 edi=0032a558 24941.665:0036:0037:trace:seh:raise_exception ebp=0032a5a8 esp=0032a534 cs=f7bf0023 ds=002b es=002b fs=0063 gs=006b flags=00200212 24941.665:0036:0037:trace:seh:call_vectored_handlers calling handler at 0x6a64d600 code=40010006 flags=0 24941.665:0036:0037:trace:seh:call_vectored_handlers handler at 0x6a64d600 returned 0 24941.665:0036:0037:trace:seh:call_vectored_handlers calling handler at 0x6f48afe0 code=40010006 flags=0 24941.665:0036:0037:trace:seh:call_vectored_handlers handler at 0x6f48afe0 returned 0 24941.665:0036:0037:trace:seh:call_stack_handlers calling handler at 0x7b486df0 code=40010006 flags=0 24941.665:0036:0037:trace:seh:__regs_RtlUnwind code=40010006 flags=2 24941.665:0036:0037:trace:seh:__regs_RtlUnwind eax=00000000 ebx=7b486d50 ecx=0032a540 edx=0032a5fc esi=0032a5fc edi=7b486d50 24941.665:0036:0037:trace:seh:__regs_RtlUnwind ebp=0032a118 esp=0032a0f8 eip=7b486dad cs=0023 ds=002b fs=0063 gs=006b flags=00200206 24941.665:0036:0037:trace:seh:__regs_RtlUnwind calling handler at 0x7bc85ef0 code=40010006 flags=2 24941.665:0036:0037:trace:seh:__regs_RtlUnwind handler at 0x7bc85ef0 returned 1 ```

Hopefully this can be useful to someone.

The following link is a save file past that point. I don't think there are any other issues from there. (I finished the game on linux after this point) You are at level 30, and you chose Asuka as a party member. https://www.mediafire.com/folder/uex088o8hbsmup3,qs5zpss3e2k3dvs/shared You'll want to put these files in your steam prefix. (Default) ~/.steam/steam/steamapps/compatdata/587260/pfx/drive_c/users/steamuser/My Documents/My Games/Aksys Games

Let me know if that link doesn't work, I'll try to pop something into ProtonDB so people can finish the game.

jcfrosty commented 3 years ago

I just tested the white shadow issue and its still present even with the latest version of proton 5.13-4. The rest of the game runs super smooth. its just this one scene that causes an ugly hang up.

aqxa1 commented 3 years ago

I'm not able to get in game for all Proton after 5.13-x (including Proton-GE), basically stuck (but not freezing/crashing) with a spinning cell phone load screen.

kisak-valve commented 3 years ago

Hello @aqxa1, please add PROTON_LOG=1 %command% to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

What's the most recent Proton version you know works with this game and your system?

aqxa1 commented 3 years ago

Steam system information steam-587260.log (log from Proton 6.3-4)

Proton 5.13-6 is the latest version that works. I'll add that it does look to be a crash, with a Tokyo Xanadu eX+ has stopped working. Crash dump has been generated message, but in the background (so I didn't initially notice it). And the game continues with the infinite loading screen unless you close the dialog.

Here's a screenshot: Crash

aqxa1 commented 3 years ago

I did a regression test and found this commit (in vanilla Wine) that causes the crash:

commit dfa4c07941322dbcad54507cd0acf271a6c719ab
Author: Zebediah Figura <z.figura12@gmail.com>
Date:   Mon Nov 2 12:25:17 2020 -0600

    quartz: Treat a filter as supporting IMediaSeeking only if it supports TIME_FORMAT_MEDIA_TIME.

    Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=48715
    Signed-off-by: Zebediah Figura <z.figura12@gmail.com>
    Signed-off-by: Alexandre Julliard <julliard@winehq.org>

 dlls/quartz/filtergraph.c         | 11 +++++++++--
 dlls/quartz/tests/filtergraph.c   | 10 +++++-----
 dlls/quartz/tests/videorenderer.c |  8 ++++----
 3 files changed, 18 insertions(+), 11 deletions(-)

However, reverting this commit only works for a few versions of wine, then some other issue breaks things with the same symptoms. I tried running a regression test with the above commit reverted, but things start breaking in the middle of the process (possibly unrelated to the bug). I'll try a bit more to narrow it down, but hopefully that's some help at least. EDIT: Up to wine-6.9 reverting the above is enough, but it breaks somewhere between there and git-master.

I get the feeling that there is supposed to be a video where the crash occurs, so the old versions of Wine/Proton are likely broken as well, just that a video not playing is less of an issue than the game not working altogether.

EDIT 2: Second regression is:

2ad44002da683634de768dbe49a0ba09c5f26f08 is the first bad commit
commit 2ad44002da683634de768dbe49a0ba09c5f26f08
Author: Anton Baskanov <baskanov@gmail.com>
Date:   Mon May 24 14:33:07 2021 +0700

    quartz: Check for IMediaPosition when counting renderers.

    The new test failures are expected since the renderers are now actually
    considered renderers by the filter graph.

    Signed-off-by: Anton Baskanov <baskanov@gmail.com>
    Signed-off-by: Zebediah Figura <zfigura@codeweavers.com>
    Signed-off-by: Alexandre Julliard <julliard@winehq.org>

 dlls/quartz/filtergraph.c         | 7 +++++++
 dlls/quartz/tests/dsoundrender.c  | 8 ++++----
 dlls/quartz/tests/filtergraph.c   | 4 ++--
 dlls/quartz/tests/videorenderer.c | 8 ++++----
 4 files changed, 17 insertions(+), 10 deletions(-)

At least this one looks like it's expected, going by the commit message. Anyway, reverting both of these commits on wine-git master, works around the problem. Reverting the first commit should be all that is needed for Wine/Proton < 6.10.

CygnusTerminal commented 3 years ago

Hello, game is crashing with Proton 6.3-5, attaching logs steam-587260.log

aqxa1 commented 2 years ago

Game looks to be fully working now with Proton 6.20-GE-1. The hang after White Shadow II no longer occurs as of Proton Experimental, and Proton GE displays the videos correctly (rather than test patterns in the case of Experimental).

ChojinDSL commented 2 years ago

Latest proton experimental doesn't play cutscenes.

BioIron commented 1 year ago

Game works almost flawlessly on experimental. Almost, because some of the cutscenes (the credits, for example) are replaced with SMPTE color bars. Proton GE can play them, but with no sound...

kisak-valve commented 1 year ago

Hello @BioIron, please add PROTON_LOG=1 %command% to the game's launch options, get the game to play one of the affected cutscenes, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.)

BioIron commented 1 year ago

Played the "True Ending" credits scene, which is one of the affected cutscenes. Also, in case it matters, i play on the Steam Deck. Also, and not less important, here is the log file: steam-587260.log Hope it helps.

Matcha-WL commented 1 year ago

Hello @BioIron, please add PROTON_LOG=1 %command% to the game's launch options, get the game to play one of the affected cutscenes, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.)

Hi @kisak-valve , I have tried to install wmp11 with GE/official, but it will skip the op video.

ValveSoftware / Proton

Tokyo Xanadu eX+ (587260) #1295

Whitelist Request

System Information

I confirm:

Issues

Compatibility Report

System Information

I confirm:

Symptoms

Reproduction