PlayableShow Details
Unknown
Mostly works although I wish performance was better and mic settings could be ignored
Mic support is not optional for multiplayer; had to manually select which device it was recording from via pavucontrol
Seems to drop frames in VR on head tracking; other games not so much?
Nothing other than the aforementioned mic settings
Great as soon as you get past Ubisoft Connect
Compared to other VR games the performance seems a bit sluggish
Ubisoft Connect can be a pain to get through, gets stuck on "Looking for patches"
Proton Experimental seems to fix uPlay/Ubisoft Connect activation issues. Before switching to it I deleted the compatdata prefix several times so that might've had something to do with it.
Works ootb. Played several hours with friends online on HTC Vive with Vive Wands
You need to quit Ubisoft Launcher manually, or stop the game via Steam. It doesn't quit itself. Also the Ubisoft Launcher doesn't save the credentials when "remember me" is ticked. Other than that, the game runs great.
Runs very well. I did not test VR. Only minor issue: When leaving the game it does not return to BP. You have to kill it in the overlay.
Multiplayer: I could connect but did not start a game.
The bundled Uplay version does not work. Install the latest version with protontricks 527100 uplay. The bundled Uplay would do this too if it would work.
brief black screen, then nothing
I launch the game, my screen blinks, then I get a fullscreen black display, then displays return to normal. Steam says the game is running, but I see nothing. I click "Stop" on Steam gui to kill the program.
Initially, the game would flash a black screen and crash to desktop. I resolved this by installing the wine version of UPlay:
WINEPREFIX=~/.steam/steam/steamapps/compatdata/527100/pfx/ winetricks uplay
I play without VR. The game would crash from a memory access violation everytime I attempted solo play. This launch option fixed that:
stbc.exe -non_vr
The audio was initially choppy. I fixed this by going to Ubuntu Settings->Sound and reselecting my preferred audio device.
Runs pretty well on Vive
It only worked on the second try after I logged into Uplay, but it works well after that
Everything works just fine with no tweaks required at all. Nothing is broken and the performance is on par with Windows
Sometimes UPlay is slightly buggy when updating itself, restarting the game often fixes it
Installs and runs without problems, despite complex setup procedure (Uplay, account linking,...). I played in non-VR mode though!
On the first try Uplay was hanging on "looking for paths", but on second try everything worked without any changes.
Game works perfectly.
Everything works perfectly out of the box for the game, the only problem is with Uplay not closing entirely so Steam is stuck thinking the game is still running after you closed it.
Update to my report from yesterday:
Once I got the game to run, uPlay is now less of a problem. It still starts every time you start the game and you have to exit it separately (otherwise Steam still thinks the game is running), but the game runs without any issues I've found at all in single-player mode (UX problems in the game notwithstanding - it renders identically to how it renders on Windows). (I haven't tried multiplayer mode yet. Another follow up will come at a later date with multiplayer details.)
The game seems to run fine from my experience. However, UPlay is an absolute infuriation. In order to get the game to work I had to:
- Sign up for a UPlay account.
- Sign into UPlay. At this point, it provided no way to link my Steam account. Launching the game would simply launch UPlay, which then let me know I don't have any games. Additionally, the activation code Steam gave me did not work in UPlay.
- Uninstall Star Trek: Bridge Crew
- Reinstall Star Trek: Bridge Crew
- Sign into UPlay again. This time, it gave me a chance to link my steam account. However, after linking it it still told me I had no games and refused the activation code.
- Uninstall and reinstall again
- This time, after signing into UPlay it recognised the game (automatically - no activation code needed). Note that at each step I had tried signing out of UPlay, quitting, relaunching, and signing back in to no effect.
I'll report back further once I've played the game for a while longer. So far I've spent 10 minutes in the game and about 2 hours getting UPlay not to be stupid. (My fiancee had similar UPlay issues on Windows, so this isn't a Linux incompatibility as far as I can tell)
Once running the game itself runs great, platinum level. Uplay however is a real thorn in my a**. It likes to crash or take an age to connect, all of which throws off the actual game when it's trying to load. It's been behaving lately but previously I've had to reboot a few times or delete the proton wineprefix to get it to run.
The game will not output to my headset. From my flatscreen, I can see that it is otherwise tracking and working perfectly, though.
All worked fine, did the tutorial, no issues and no lag etc. One tiny little non-issue. The first time I launched it, Uplay patched itself and asked me to log in. After I had done this Uplay didn't register the game and dumped me back to the main menu. Quitting Uplay and relaunching then bound it to my account and it worked fine.
Works fine out of the box... Including the launcher.
All working right out of the box, including uPlay.
Unknown(< 1 hour with Proton)I had to launch several time (over 10 I think) to get all the required UPlay popups displayed. The first one is to login (I had to reinstall after I missed it the first time). The second one is about linking Steam to UPlay. This only popped up after a dozen or so launches of the game.
In the runs before this worked the game wasn't showing anything but appeared running in Steam.
After this was resolved, I was able to play the tutorial missions without an issue in VR and non-VR. I still have to try the actual missions and multiplayer though.
Unknown(< 1 hour with Proton)UnknownI suspect this is a uplay related issue. More info at https://github.com/ValveSoftware/Proton/issues/2387
UnknownUnknowndoesn't start.
Unknown
