[EDIT MARCH 2021: The new 1.08 patch has fixed this issue. Emergency lighting is back online aboard the Enterprise-D.]
It seems since the last update and the Quest launch that all players (PC and PSVR) can experience a glitch where on the Enterprise-D, when the usual blue emergency lighting is activated (when the hull damage is severe enough), the bridge textures disappear and instead turns completely white.
Example (from someone else's stream; glitch happens at 1:24:25):
I'm playing on PlayStation 4. I've checked for any updates, and the game says I'm playing the latest version (1.07). This issue affects all other players in a session as well (including PC players) and is triggered when the Enterprise-D's hull is reduced to 40% or so and the emergency blue lighting is supposed to kick in.
I have recorded a fuller clip of the bug from my game on PS4 with views from multiple stations:
Since the last patch I have yet to encounter anyone ingame who does NOT see the bridge turn white when the blue lights come on. This is very clearly an issue caused by the last update.Originally Posted by UbiDork Go to original post
I can verify this issue is happening on the PC... all of us were using different VR headsets on PCs, and we all remarked about the ship turning white at the same time. We made jokes about taking so much damage we were in heaven.
Anyway - it's not an install problem.
Thanks for checking up on this!
Thanks for the updates, everyone!
If you're on PS4, please try these steps here!
If you're on PC, please try these steps here!
I have the same problem with the next generation dlc of star trek bridge crew on pc steam no vr version.
If the enterprise shell intigrity go below 40 percent, the bridge turnes white.
I tried to verified the game files in steam and changing the highendcpueffects settings in steamapps/common/startrek bridge crew/graphics... to solve the problem. With no success.
We need an other option (like a patch) to solve this. Because i am not the only one with this problem. So i hope, this error will be fixed and not ignored.
Sorry about that confusion! Here are the verifying steps for Steam. Have you also tried ensuring that you have the game and that Uplay PC launcher installed onto the same internal hard drive?Originally Posted by CaptainDickard Go to original post
Firstactionhero: Thank you for that update! Are you also able to provide a clip of how this happens within your game?