Compatibility Report

Tried updating uplay as described here: https://github.com/ValveSoftware/Proton/issues/2268#issuecomment-466560526

It installed a new version of uplay but no success in getting the game to run.

I've also tried running uplay via Wine as I expect this is where the issue originates. In wine uplay launches fine, however as there is no steam connection made I can't launch the title. The title was bought it on Steam and I don't have the Uplay license.

Running the game directly through wine works as well, it launches and renders the main menu UI, however it opens a dialog which tells me to quit due to uplay not running.

My goal is to run this in VR on Linux btw... so if someone picks this up at Valve/CodeWeavers/whomever please take a look at that code path as well :v:

Thanks for looking into this @kisak-valve, much appreciated!

Somewhere between the runs earlier today there was a steam update. I just checked and I'm definitely running proton 3.16-7 Beta (on stable Steam Client), not sure what happened to the missing header. As far as I know I have been running this version for a while (see screenshot). It might be related to me running directly from terminal looking for an alternative way of getting verbose debug information (see attached script).

launch_stbc_proton.sh

Attached a new log from a session I just ran just normally via the Steam client. However, I had to kill it by running killall -i -r '.exe' because it stays running without visualizing anything.
steam-527100.log

And a log from running the game using the latest Steam Client Beta (which apparently has a Proton 3.16 Beta update).

Same result, perhaps different log.

steam-527100.log

I'll be reinstalling the game on this Steam Client Beta.. perhaps something went wrong with the initial UPlay setup.

I reinstalled Star Trek Bridge Crew in the Steam Beta Client.

This time UPlay updated at launch (I think it did before) and it also showed a login dialog. After logging in I saw none of my Steam titles in there. Not sure if this is normal... I'm not familiar with UPlay. Steam is under the impression STBC is running whilst in practice I'm looking at the UPlay store... unable to play the actual game.

Oh it also launched Steam VR (even though I didn't select that version). In Steam VR I'm in Steam Home and not in STBC.

@kisak-valve if you have any pointers let me know. I really want to play this title. Thanks!

Success!

After several attempts of launching the game in both VR and non-VR mode I got a "link this game to your steam account" dialog from UPlay. Once that was done I was finally able to launch the game!

So the whole process of getting UPlay up and running was very rough but in the end it worked out. I didn't do anything specific other than trying it about two dozen times. I just launched the game in non-VR mode and VR mode and both seem to work fine.

Perhaps it was bad luck on my end but seeing another borked review on protondb.com it seems I'm not the only one having issues with this title. Perhaps something to test at Valve HQ?

The game is pretty broken for me. I've had no problem with Uplay installation/login or the Steam linking. But when I start the game, I come until the point where the game introduces me to the controls and before I even can interact, it freezes and turns into a black screen. This happens with or without gamepad.

I've already deactivated the Uplay overlay, as it's known to be problematic, but no success.

Game Version: Flat (No VR)
Proton Version: 4.2-9
Proton Log: steam-527100.log
System Info: https://gist.github.com/NoXPhasma/ebec08497208ae37696f84a9eee7dc3a

The game also created crash logs, which I will attach as well:
error.log
output_log.txt

With Proton 5.0-4 the game doesn't even start properly. It opens a black window which closes itself right away. The game then needs to be killed manually, as it would still run in background.

steam-527100.log
https://gist.github.com/NoXPhasma/35d7ddf3ae948239a6cc179bca4f234e

The previous report was the last I tried until now. I just retested with 4.11-13 and it shows the same behaviour as 5.0-4. Going back to 4.2-9 and the Uplay Launcher starts up right away and I can login and start the game.

Now that I'm logged in with Uplay, going back to 5.0-4 I can play the game with that version as well. I've just tried around with the UI and it worked fine so far with KB/M.

Apparently it's the Uplay launcher which is making the issue here.

update

I need to add that I have to force kill Uplay manually as it never closes itself and I can not interact with the tray icon.

An alternative, which worked for me, is to manually install an updated Uplay with protontricks 527100 uplay. This version works with the current Proton 5.0-7.