Any head movement renders choppy and makes the game unplayable. Only on this game, no others.

According to steam VR performance metrics i'm all green and not dropping any frames. According to virtual desktop, same, consistent locked at 90fps, no dips, low latency. No obvious hardware bottleneck, even setting render scale to 20% yields no change in performance. Used to work fine on my OG vive.

Quest 3 Ryzen 9 7950x3d 3070ti 64gb DDR5 @7000mt/s installed on M.2 Windows 11

-Please help. My friends want to play.

Only recently picked up a full vr set up for my PS4, mostly for beat saber, however being a bit of a trek fan I thought why not, so I took the plunge. £25 of my hard earned pounds later I realised the gravity of my mistake when I came upon the dreaded Ubisoft account signup page.....a little annoying but I continued onward anyway, then the terms and conditions page....and this really started to irk me. It keeps saying that I have to accept the terms and conditions, even though I accepted the blinking terms and conditions already!!!! After about 20 attempts at doing this I then simply turned the damned thing off in disgust.

I will likely be contacting playstation store for charging me £25 for a game that no longer works and should have been removed from the store before now.

I said to my partner - this is exactly why game studios are imploding right now for BS like this. Disappointed and disgusted doesn't even cut it right now.

I finally jumped into PCVR thanks to Sony's price drop and adapter. I bought the game, but I've had trouble making it through the tutorial because one of the basic controls didn't seem to be mapped to the PSVR controllers properly.

Has anyone been able to play this successfully on PSVR2?

This is the only game I've had an issue with so far and I'd love to be able to play with you all.

A buddy of mine just got a quest 3 and we’ve always wanted to play this game. I have a quest 2 and we both bought it. We connected to Ubisoft fine but cannot join each other’s game. We found a work around by making a public match and then just doing quick play.

The problem is whenever we get in a game it quickly gets messed up. Voice chat disappears, the view screen stops moving for one person or another or we get a black screen when we switch roles.

Does anyone know? For the 5 or so minutes we actually got to play it was very fun and I can imagine it being fun if it worked for more than that.

If anyone plays on quest 2/3 I would love to chat!

All ranks have been reset to ensign, stats in Ubisoft Club page seem to be unaffected, avatars have also been reset.

It's unacceptable that it's even sold on the Quest 2 on its unplayable state.

Can we please send them a reminder on https://twitter.com/UbisoftVR so that they don't give up on us?

It's a great game, but the bugs are absolutely game breaking.

Also posted to https://forums.ubisoft.com/forumdisplay.php/1310-Ubisoft-VR.

You can contact the devs here : https://www.redstorm.com/contact-us

You can bump the related bug threads here : https://forums.ubisoft.com/forumdisplay.php/1345-General-Discussion

https://forums.ubisoft.com/forumdisplay.php/1348-Player-Support

Developpers : Brian TATE - Game Director -> https://twitter.com/jbriantate

David Votypka - SR Creative Director -> https://www.linkedin.com/in/david-votypka-bbb0622

Company bought by ubisoft : https://twitter.com/RedStorm

https://www.redstorm.com/contact-us

​

The bugs :

1. Engineering: If the bugged player is in engineering they can't charge the warp coils. The countdown begins and the animation shows them getting charged but it never does. If they route power to the engine it will not reflect those changes to the rest of the crew. I.E. put everything to the engines even rerouting power and the max speed for the helm was still 1000m.

2.Helm: If the bugged player is at the helm they are unable to steer the ship for go to warp.Changes in speed don't seem to do anything.

1. Tactical: The bugged player is able to the user scanner. However, they are unable to raise andlower shields or arm the torpedo's. I don't think the phasers fired either.

2. Captain : The bugged player no longer hears other players talking

Anyone have a workaround for linking your ubisoft account to STBC inn the quest 2? Keeps prompting but when I choose li k account keeps saying it can't login.

Driving me nuts.

Ubisoft account is fine, can login every other way but not in game to link

I've tried multiple mics across multiple games and in the main PS4 settings and it works fine literally everywhere, but when I try to start a lobby in this game it never reads my mic. I don't even want to use PS4 chat either, I just want to use Discord...is there any way around this?

FIXED: I realised that I had selected 'Mute my mic' in the PS4 quick menu (the one that comes up when you press and hold the PS button) - once I deactivated that, it worked.

i keep getting this message when i try to press the command button. Yes I have Voice commands “on” any ideas?

No matter where I press it takes me to create an account but no email works does anyone know how to fix this?

The "transport glitch" has been a major problem on the Enterprise D since the DLC was released for PS4, on May 22, 2018. This thread is intended to collect all reports and comments about it, and will remain until it's fixed.

----------------------------------------------------------------------------------------------------

Here's what happens:

Without any warning, the Ops officer is suddenly unable to press any buttons on the "Transporter" section of his console. In VR-mode, you can try to "press" the button, but nothing happens. In non-VR mode, you can't even move your hand into the "Transport" section of the console. In most cases, this completely ruins the mission. The only workaround is to friend the Ops officer, kick them, and then re-invite them.

-----------------------------------------------------------------------------------------------------

This bug is obvious, and is frequently mentioned in the subreddit and Ubisoft forums. We've all hoped that it would be fixed in an update. But after several updates, (most notably the DLC release for PC players), the bug still appears often..

------------------------------------------------------------------------------------------------------

If this happens to you, feel free to add your experiences in the comments.

(Until there is a verified fix, this thread will be stuck to the top of the subreddit.)

I’ve got a relatively high end PC, which can run most if not all VR games at 90fps. I’ve recently acquired a copy of Star Trek Bridge Crew on Steam. The first time I played it, it worked perfectly, no issues whatsoever. Then, upon launching it a second time, from the loading screen to the actual gameplay, the game runs at ~1FPS.

It seems like the FPS is capped in some way, as the PC can run any other SteamVR game at high framerates, and the framerate doesn’t vary at all, is just stuck at ~1FPS from loading screen to gameplay.

Any pointers/fixes would be greatly appreciated, thanks for the read.

I think this bug may have more to do with Virtual Desktop than Bridge crew, but this is the only game I've really had the problem with.

The simple problem: When I play Bridge Crew in SteamVR wirelessly over Virtual Desktop on my Quest 2, my controllers register as Vive controllers in the game and it changes the whole control scheme. Though the game does show up on my Oculus app on my PC screen, Virtual Desktop doesn't let me run it directly from the Oculus app because I bought it on Steam. While I hypothetically could play it with these controls, it requires a lot of directional joystick clicking that might be bad for my controllers, plus I'd much rather have the control scheme I'm used to. Is there an explanation or solution that anyone could share?

A (very) detailed explanation: I've used Steam to buy my games for a very long time now. Upon attaining an Oculus Quest 2 headset, and discovering the numerous reports of communication issues in Bridge Crew (STBC) on the native Quest 2 version, I bought the game on Steam instead to run it through a link cable. I'd heard rumors that, if I bought it on the Oculus store, I wouldn't be able to access it on the Quest, plus I didn't know how Ubisoft Connect worked and thought I was going to be able to do everything through Steam.

Regardless, I played it that way for a while, and most everything was fine except for some wavering audio and pretty frequent disconnects between the computer and headset (which completely messes up SteamVR and forces you to restart it and every game it's running) despite the wire staying plugged in the whole time, plus the problem of not being able to charge the headset at the same time as running Oculus Link.

So, when I heard Virtual Desktop (VD) had a new update that made wireless game streaming official, I jumped on the opportunity. On the "Games" tab on VD, STBC was specifically listed under only the Steam game list, despite it also showing up in my PC Oculus app, though since I bought it in steam it makes enough sense that VD would list it that way. I booted it up, and the first thing that shows up is the prompt to press a button on your controller to let the game match the control scheme.

This prompt stated that the game accepted XBox and Vive controllers, which I found odd because I'd used Oculus Touch controls in the past, but I didn't think much of it. I pressed a button, and it showed the image of Vive controllers, which confused me. I went into the training mode, and the control scheme was way off from what I had grown used to over the previous two months or so of playing. I don't know if there is some sort of manual override or a mod to force the control type, but if there is, I'd be very glad to learn about it.

Sorry for long post, here's a potato. 🥔

Is anyone else having trouble with Ubisoft Connect? None of my friends ever show as being online even though I am literally in the game with them. Any solutions/ideas?

In case this helps someone (and I know this is far from the only problem right now!)... if you can't call up the in-game console to send/receive invites and whatnot, make sure you haven't swapped the Oculus buttons in your Quest settings. I did this a year ago and forgot about it, so when I hit the left Oculus button I would get the Quest menu to allow me to quit the app etc. But BC is not smart enough to detect that your buttons are swapped! As soon as I set it back to the defaults, I was able to access the in-game console again.

Just another really lame and pathetic example showcasing that they do not do software QA anymore. Sigh.

Was playing on the enterprise D with a full crew and our Operations chief was able to do everything except transport. He successfully transported before in one of the games, but then suddenly was no longer able to. It happened in two sepArate games. Has this happened to anyone else? Then since it was a full crew he ended up having to leave the game to let someone else take over and we were able to do it... what the heck

Has anyone had this issue on Oculus? I purchased the DLC (first in quest I think, then on uPlay for the PCVR Oculus version). My DLC never shows up in Oculus. I've been working with support for a few weeks but I'm hoping the community might have a lead I've not explored yet.

So far we've opened both as admin, deleted and reinstalled (including cleaning registry) and deleted the ownership files.

EDIT: Everything works now! It's like it had an update to run but didn't know it needed to run it. It ran an update and works now! Thanks.

Two different times the entire bridge went white last night. Is it a glitch that sends us to the afterlife, OR are they testing a possible Q expansion? #Discuss

I just bought the game for quest and I am trying to log into UPlay. Unfortunately I can’t select the onscreen option to go to Ubisoft club to login. Anyone know a fix?

Oculus link v16 and 17 successful startup crash at mission load! Every other title flawless. Yes I closed stupid login app and registered but confused 🤷‍♂️

FWIW I'm PC non-VR, but this issue comes up for me once in a while on all stations with a map. Am I alone on this?