BlazBlue: Calamity Trigger (263300)

[unit73e]

Compatibility Report

• Name of the game with compatibility issues: BlazBlue: Calamity Trigger
• Steam AppID of the game: 263300

System Information

• GPU: R9 380
• Driver/LLVM version: Mesa 18.3.1
• Kernel version: 4.19.12
• Link to full system information report as Gist: https://gist.github.com/unit73e/24ef938c170ac7d9bdb14a5150b5c45a
• Proton version: 3.16-6 Beta

I confirm:

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

steam-263300.log

Symptoms

The game starts but crashes immediately.

Reproduction

Start the game.

Other

WineHQ have an opened bug for this game (thanks to Iglu47 for finding that out):
https://bugs.winehq.org/show_bug.cgi?id=48684

Update

Works with Proton GE but has the following bugs

• No sound in videos. Issue: https://bugs.winehq.org/show_bug.cgi?id=48836#c5
• Crashes or freezes after some time.
• Sound does not play correctly when you win.
• In Arcade when players are talking the text is skipped at full-speed.

[flibitijibibo]

This line is interesting:

411.574:0008:002c:err:d3d:wined3d_debug_callback 0x216380: "GL_INVALID_OPERATION in glBlitFramebuffer(bad src/dst multisample region sizes)".

Is there a way to disable multisampling via config files? If so, disabling it will most likely fix the problem.

[unit73e]

Is there a way to disable multisampling via config files? If so, disabling it will most likely fix the problem.

So far I found nothing regarding display configuration of this game but I'll keep checking. Searching on the web didn't get me any configuration file so I'll probably have to run the game on Windows.

I tried ignoring all Mesa errors with MESA_NO_ERROR=1 and a "NOW" (now loading?) showed up in the bottom right corner of the screen. Seems like the display is being stretched beyond 1080p. Anyway here's the log with that option activated: steam-263300.log

[unit73e]

I found out were the configuration file is:

$HOME/.local/share/Steam/steamapps/compatdata/263300/pfx/drive_c/users/steamuser/My Documents/ARC SYSTEM WORKS/BBCT/Config/DisplaySetting.cfg

I have the following configuration:

:WindowResolutionWidth
1280
:WindowResolutionHeight
768
:FullscreenResolutionWidth
1280
:FullscreenResolutionHeight
768
:DisplayFPS
# 1 = show , 0 = hide
1
:LightBloom
# 0 = on , 1 = off
1
:AntiAliasing
# 0 = x4 , 1 = x2 , 2 = off
2
:FullScreen
# 0 = fullscreen , 1 = window
1

It doesn't seem like there are other options. This is the screen that shows up:

The letters position is correct and is supposed to show "now loading..." but the game crashes after the "now".

I noticed there are many WMV files so perhaps it's crashing because of those. I tried moving the files away but to no effect.

This is the latest steam log: steam-263300.log

EDIT:

Having check on youtube what happens the problem is most likely this WMV:

~/.local/share/Steam/steamapps/common/BlazBlue Calamity Trigger/data/Movie/bbcsopening.wmv

Or at least there are many games crashing due to lack of WMV support: #1464

[PythonicChemist]

The game runs perfectly fine with your config file and quartz installed in regular Wine. I can't install quartz into proton prefixes though.

[unit73e]

The game runs perfectly fine with your config file and quartz installed in regular Wine. I can't install quartz into proton prefixes though.

At least that pin points the problem to DirectShow. Just a bit more information, the video codec is in wmv3 and the audio in wmav2.

[shoober420]

Compatibility Report

• Name of the game with compatibility issues: BlazBlue: Calamity Trigger
• Steam AppID of the game: https://steamdb.info/app/263300/

System Information

• GPU: GTX 760
• Driver/LLVM version: NVIDIA 440.44
• Kernel version: 5.4.15
• https://github.com/shoober420/linux-scripts/blob/main/home/shoober420/sysinfonvidia
• Proton version: 4.11-12

LOG:
steam-263300.log

Symptoms

Crash at startup, with "Failed to initialize" error message window.

[Iglu47]

I tried on usual wine and gog version, but think that need link this issue
https://bugs.winehq.org/show_bug.cgi?id=48684

[unit73e]

@Iglu47 yeah that bug matches. So it's not just a lack of WMV support and we will have to wait for the next version.

Note: I like who's assigned to, Mr. Bugs.

[Iglu47]

game still not work, but @alesliehughes added some patchset to staging that now gives Faudio error.
without extra dlls (like winetricks or etc.) and disable fullscreen

[flibitijibibo]

More than likely there’s a parse error in the engine - I don’t think we’ve come across an XACT 3.3 game yet. It may just magically work as-is but this is where it’s bailing for now:

https://github.com/FNA-XNA/FAudio/blob/master/src/FACT_internal.c#L1975

[flibitijibibo]

Latest commits may fix this unintentionally:

FNA-XNA/FAudio@99b0383
FNA-XNA/FAudio@b5f57cb

[Iglu47]

FNA-XNA/FAudio@b5f57cb - game playble in window mode
no fixme xact and can hear sound in game (xact soundbank and wavebank)
(not show opening and story movie wmv, but opening show after idle mode screenshot2 above.
and no sound from wmv files - maybe specific issue for my machine)

[unit73e]

@Iglu47 AFAIK ArcSystem games never really worked that well in fullscreen mode but I think it's possible to fake it by using the OS "fullscreen" (mode+f in i3wm). At least faking fullscreen (without using in in-game settings) works for other games like Arcana Heart 3. I'm betting 60hz is also required for the game will run properly (120hz will run too fast). Seems like ArcSystem didn't use delta times for some odd reason. AFAIK these games also only work property in one resolution so no point in changing any of that, just keep the default. These are problems that also occur in Windows.

I'm assuming you didn't use winetricks, right? Anyway this is great news. Good enough to play. I might test this as well in the weekend.

[Iglu47]

@unit73e actually, the game does not crash in fullscreen, but my advice would be better to use a virtual desktop for first run and fullscreen mode constantly

I'm assuming you didn't use winetricks, right?

correct, no winetricks or other thing link to which are blocked every time

also seems that I still have some trouble with lib32-gstreamer and plugins

[Iglu47]

if revert this https://source.winehq.org/git/wine.git/commit/29deae35 ( or if use WINEDEBUG=+all 😀) fixed (I checked on staging-5.4.r7.g36b8b8cc) - video starts to display,
but still no sound in game movies (WMA version 2)

[unit73e]

Tried with ProtonGE-5.6-2 and while the game does start and plays the WMV (without sound) it hangs on the "NOW LOADING" screen once you start a fight.

Works with ProtonGE-5.6-2 with ESYNC is disabled (otherwise gets stuck in loading). WMV does not have sound.

EDIT: Game crashes randomly sometimes but it's playable for the most part.

[unit73e]

@GloriousEggroll any chance you can help getting audio working on videos? The audio codec is WMAV2 but I don't know anything about ffmpeg, gstreamer or wine. I am a software developer though so I can debug to see what's going on.

[Iglu47]

@unit73e https://bugs.winehq.org/show_bug.cgi?id=48836#c5

[unit73e]

@Iglu47 hum, so another bug. Thanks. More importantly the game randomly crashes. I'm not sure why.

[Iglu47]

@unit73e not another, it's should be last game bug - Audio from WMV does not play
I newer see "randomly crashes", but I used old version wine 5.5 wine-staging/wine-staging@f36c844
and also I used patched LargeAddressAware flag in exe-file (because it's 32-bit game)

[unit73e]

@Iglu47 okay I don't have the LargeAddressAware option enabled so that could be it. I've been playing for a while and found out that in arcade when you win the sound is broken. I can only hear static. The other I'm not sure. Also in arcade, when you talk to someone the text is in non-stop full speed. Perhaps that's something to do with my configuration.

[Iglu47]

I've been playing for a while and found out that in arcade when you win the sound is broken. I can only hear static.

cofirm, my old build give me too

3426.895:0036:warn:quartz:DSoundRender_GetWritePos Delta too big -0.006/0.0, overwriting old data or even skipping
3426.895:0036:warn:quartz:DSoundRender_GetWritePos Skipping 1152 bytes
3426.895:0036:fixme:quartz:DSoundRender_SendSampleData Sample dropped 1152 of 32768 bytes

I check on master wine later

[unit73e]

I've been experimenting with fsync too and it seems like it doesn't work very well either. If I have no extra launch options it will freeze in the player selection screen. If I set WINEFSYNC_SPINCOUNT to a very high number it will get to the player selection screen but freeze in when the battle starts. Only disabling both esync and fsync works.

So these are the current bugs with the latest Proton GE:

• No sound in videos. Issue: https://bugs.winehq.org/show_bug.cgi?id=48836#c5
• Crashes or freezes after some time.
• Sound does not play correctly when you win.
• In Arcade when players are talking the text is skipped at full-speed.

[unit73e]

Finally got a log that shows something about the random crash:
steam-263300.log

I ran with: WINEDEBUG=+seh,+msgbox

[unit73e]

Got it to freeze as well. It's heap memory related:
steam-263300.log

[luni3359]

Using Proton-5.9-GE-5-ST I've noticed that if you tab out the game window before the intro movie loads you can actually listen to the entire music flawlessly, but once you focus the window it goes silent, then from that point onwards all videos also go silent.

[ranplayer]

I've tested with Proton 7.0-2 and the only issues found so far:

• videos have no audio
• game hangs for 5-10 seconds when you press a button on the intro video video or interact with the main menu actions (disabling esync didn't help)

steam-263300-proton70-2.tar.gz

Specs:

• O.S: Arch Linux
• Kernel: 5.15
• GPU: GTX 970 4Gb (Driver: 515.48.07)
• CPU: Ryzen 7 5700G

[ranplayer]

I've retested the game with Proton 7.0-5 and Mesa 22.3.1 and the issues I've mentioned have gone.

Specs:

• OS: Arch
• Kernel: 6.0.12
• GPU: RX 6700 XT (Mesa 22.3.1)
• CPU: Ryzen 7 5700G

[unit73e]

Tested with Proton8.0-2 and now everything seems to work, except videos sometimes don't play at all, showing a no signal screen.