Proton: Strike Vector EX (476360)

Created on 3 Nov 2018  Â·  4Comments  Â·  Source: ValveSoftware/Proton

Compatibility Report

  • Name of the game with compatibility issues: Strike Vector EX
  • Steam AppID of the game: 476360

System Information

  • GPU: Intel HD Graphics 630 (i7-7700K)
  • Driver/LLVM version: mesa 18.2.3
  • Kernel version: 4.18.16
  • Proton version: 3.16

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 gets stuck and controller reconnection causes it to wake up. Can't play campaign, only menu working.

Reproduction

Well, I've bought this game because former Strike Vector isn't working, besides being old. Strike Vector EX isn't working too. The game launches but gets stuck after the two initial banners in a spinning wheel screen. Controller reconnection causes the game to wake up and report controller disconnection, it works to past this. The game menu and settings setup works fine, but once entering the campaign it gets stuck again, controller reconnection works to bring a menu to exit to main menu, but the game campaign simply refuses to start.

Game compatibility - Unofficial XAudio2

Most helpful comment

Oh, why haven't I searched this GitHub repo for Strike Vector related issues for so long... (Didn't expect anyone to submit it, honestly.)

We have known for long time that the game is mostly working, and the intro video can be bypassed (add ?nologos to the launch options).

Unfortunately, the campaign is still unavailable because of unplayable videos, only multiplayer is available.

I wonder if the meta-issue #1464 is relevant. I think it should be, considering #327 and #1571 are there (other UE4 games). The proton log attached to the issue seems to have mf.dll and mfplat.dll mentioned.

ffprobe and MediaInfo from the intro video: https://gist.github.com/KillyMXI/c68b878526c2c7f29ed77f658c3faa04

All 4 comments

From log it looks like the game hangs when failing to play media files, the two times it gets stuck, one on launch and another on campaign start, seems due to that:

â‹®
40214.244:0027:0028:warn:debugstr:OutputDebugStringA "[2018.11.03-13.39.43:270][255]LogMediaAssets:Error: Could not find a native player for file://E:/Steam/steamapps/common/StrikeVectorEX/SVEX/Content/Movies/SV_TRAILER_CC_BLANK_no_logo_H264.mp4\r\n"
â‹®
40564.221:0027:0028:warn:debugstr:OutputDebugStringA "[2018.11.03-13.45.33:247][668]LogMediaAssets:Error: Could not find a native player for file://E:/Steam/steamapps/common/StrikeVectorEX/SVEX/Content/Movies/Animatique_01_H264.mp4\r\n"
â‹®

Log files:

Oh, why haven't I searched this GitHub repo for Strike Vector related issues for so long... (Didn't expect anyone to submit it, honestly.)

We have known for long time that the game is mostly working, and the intro video can be bypassed (add ?nologos to the launch options).

Unfortunately, the campaign is still unavailable because of unplayable videos, only multiplayer is available.

I wonder if the meta-issue #1464 is relevant. I think it should be, considering #327 and #1571 are there (other UE4 games). The proton log attached to the issue seems to have mf.dll and mfplat.dll mentioned.

ffprobe and MediaInfo from the intro video: https://gist.github.com/KillyMXI/c68b878526c2c7f29ed77f658c3faa04

@KillyMXI thanks for pointing #1464 out, surely it's the same problem.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

AwesamLinux picture AwesamLinux  Â·  3Comments

ArekPiekarz picture ArekPiekarz  Â·  3Comments

prototype99 picture prototype99  Â·  3Comments

AwesamLinux picture AwesamLinux  Â·  3Comments

juppso picture juppso  Â·  3Comments