Star Trek™: Bridge Crew, playable in both VR and non-VR, will immerse you in the Star Trek universe. In co-op, form a crew of four players to serve in the roles of Captain, Helm, Tactical or Engineer. Make strategic decisions and coordinate actions with your crew.
Recent Reviews:
Mostly Positive (40) - 77% of the 40 user reviews in the last 30 days are positive.
All Reviews:
Very Positive (887) - 83% of the 887 user reviews for this game are positive.
Release Date:
May 30, 2017
Developer:
Publisher:

Sign in to add this item to your wishlist, follow it, or mark it as not interested

Buy Star Trek: Bridge Crew

Buy Ubisoft VR Bundle BUNDLE (?)

Includes 3 items: Eagle Flight, Werewolves Within™, Star Trek: Bridge Crew

 

Recent updates View all (7)

July 16

DevBlog - Star Trek: Bridge Crew and Watson



To provide better insight into how our AI crewbots work we put together this blog to give everyone some clarity on how exactly they work and how the Watson powered voice recognition works with them.

While Bridge Crew was designed as a Social VR game first and foremost, there are times you may be a player or two short or you may just feel like exploring space on your own for a bit. The crewbots were developed to help fill in those blanks. The game is playable and beatable with an AI crew, but they were not intended to replace human players and may not perform as well as your buddies would.

Keep in mind that with VR, performance is at an extreme premium to keep framerates high to avoid player discomfort so highly sophisticated AI that heavily affects that performance was not in the cards. The crewbots are a very effective solution that meets the goals of providing basic crew substitutes without any negative impact on framerates.



To interact with your AI crew members you can either issue commands to them directly using a contextual UI, or you can issue crew wide orders from the Captain’s chair. Most misconceptions are about how crew wide orders work as well as how having humans occupying some of the stations affects these orders.

Crew Wide Orders

Crew wide orders were developed to help reduce menu complexity and simplify some complex, common, behaviors. These commands will work with any combination of players and AI manning stations but in the case of humans operating stations the AI assumes that the players will handle their appropriate tasks.

“Analyze Target” for example, will cause tactical to try to scan once in range, engineer to set full power to engines, and helm to fly to the target. You could do this without the crew wide order, however you will have to drill down into each station’s command list in order to do so, and you’ll have to wait for tactical’s scan order to become valid. We execute this sequence of events commonly enough in the game to warrant a nice “macro” for the behavior. “Transport Target” works in a similar fashion. Assuming a target has been scanned, helm will fly to the target, tactical will lower shields if they are up, and engineer will begin the lock on process.

Crew wide orders can be fairly nuanced. For example, the “Cloak Hunt” order (Only available on the 1701-D) will send crew to scanners, adjust power for phasers and shields, arm torpedoes, switch them to proximity and steer the ship toward the radar blip. Once “close” the Tactical crewbot will fire. However, the “Engage Target” order will respect the ship’s current torpedo armed state. So if the captain had previously ordered “arm torpedoes” through tactical’s order panel or via red alert, “Engage Target” will fire torpedoes, if they are not armed, the order will not arm them, and we only shoot phasers.

Think of crew wide orders as a large collection of tiny individual commands whose result is chasing an enemy to fire upon, hunting cloaked ships, etc. There are many things going on in the background during one of these orders.



Now let’s talk about one of the crew orders that needs further clarity, Engineer’s repairs.

When a mission starts, the Engineer Crewbot is initialized with an “auto repair” behavior this is the most basic and default repair mode. This behavior has a few different outcomes depending on if you are on the Aegis/TOS bridge or EnterpriseD. On the Aegis/TOS bridges, if the ship has 100% subsystem health across all subsystems, the Crewbot will unassign the repair crews. If the ship has subsystem damage, auto repair waits until 40% subsystem damage before acting. This means no crews will be assigned to repair until these points are reached.

Auto repair works with a priority list. When it picks what subsystem to fix first, it will choose based on this list. Once a subsystem is repaired, it will reevaluate based on this list and reassign crew to other subsystems that are below the damage threshold.

The Auto Repair behavior can be overridden by either player interaction with the repair panel, or captain’s orders. If the captain orders a “Balanced Repair” the 40% limitation is removed and the crewbot will act based on the priority list if any system has less than 100% health. Otherwise, the behavior is the same as auto repair. Once all subsystems are healthy, we return to the auto repair behavior.

If the captain orders repairs on a specific subsystem, the crewbot will repair this system until 100%. It will then return to the auto repair behavior. The behavior is similar if a player sits at Engineering and sets repair crews. If a player modified any repair crews, the Engineer Crewbot will not run any auto repair logic. Instead, it will leave the crew where they are until those subsystems become 100% healthy. After which, we will return to the Auto Repair default behaviors.

Repair works differently for the Enterprise D. Since leaving crew at a subsystem will give a perk if it is healthy, the Ops Crewbot behavior in this instance is to leave crew at a station if assigned by order or manual player action. Additionally, the “Optimize” orders are essentially presets. This helps ensure if the captain orders a preset, the Crewbot will not reassign crew designated for the preset for repair duty. Typically, our preset orders will have one floating crew to deal with subsystem repairs that are outside the desired optimizations. If a player assigns crew at all, the crewbot will not automatically move crew around on the Enterprise D. Instead, you will have to (as captain) assign a preset to clear any previous player’s settings.

Watson powered voice recognition

Late in our development cycle, in fact after the crewbots were developed, we got the opportunity to work together with our partners at IBM to utilize Watson to make all of this better. What Watson brings to the table is an easier, more intuitive way to operate the crewbot system. It simply takes the place of the in game UI with voice driven commands.

Here’s how it works in a diagram:


The crewbots in operation under Watson command execute the very same code as when run with the UI. So if for any reason Watson is not available the crewbots are still available with the same functionality. What that also means is that you can see what voice commands are possible by looking at what UI driven commands are available. The big advantage Watson brings to the table is a quicker more intuitive way to issue those commands.

So other than a simpler way to execute these commands, what does Watson’s vaunted cloud functionality give us? Well in addition to a very powerful and effective voice recognition service, Watson is able to interpret what you said and give its confidence level in what you are asking for. Thus, it is able to tell us what command to execute even if you do not say it exactly the “right” way. Thus, we can have “make it so” and “punch it” and “engage” and many other variations result in the same command executed. We then have enhanced this by “training” Watson with Star trek terminology so it has a better idea of what to expect and how to interpret what players say.

The result, more than 80% of the time someone presses the button and says something to Watson we end up executing a command. Now when you factor in how many times people press the button and change their mind, or say nothing or just goof off, this is a very high success rate.

So in summary, the crewbots can be given orders directly for a single station or crew wide orders can be given that affect multiple stations at once. The Watson voice recognition feature is then available to help issue those exact same orders in an easier fashion.
3 comments Read more

June 27

Star Trek: Bridge Crew PATCH NOTES - Title Update 6



PLEASE NOTE: Some elements of this patch operate exclusively on the TNG DLC, which will be releasing on PC on July 24. On all PC versions, these elements will automatically be applied to the DLC.

FEATURE IMPLEMENTATION
  • Implemented Watson powered voice recognition on the TNG bridge
  • Added the ability for PSVR players to point

MISSIONS
  • Fixed an issue with incorrect enemies sometimes spawning for TNG Rescue Ongoing Voyages
  • Fixed an issue with Rescue missions with two players where the civilian ship does not always appear
  • Corrected Borg spawning in Melgar’s Point, Elgar. This was to correct an issue where the Borg could spawn in an exclusion zone which would result in them flying through space rocks as they navigate
  • Fixed an issue with the Borg failing to attack players in an exclusion zone
  • Fixed an issue where the Warbird does not engage during a Defend the Suribachi mission on the TOS bridge
  • Corrected an issue where a Rescue Ongoing Voyage could have the ship carrying survivors get destroyed before the players could reach it making it impossible to complete the mission
  • Corrected an issue with Rescue missions on the TNG bridge where players could not find or rescue civilians off of a vessel or enemy ship
  • Fixed an issue where an Ongoing Voyages Patrol could not complete the “turning in findings” objective
  • Corrected research missions so you cannot complete them by impulsing away from the space station when enemies appear
  • The USS Raleigh no longer has 4 lights following it on Defend missions
  • Fixed a problem on Patrol/Explore Mode where warping away from final turn-in could result in a mission unable to be completed
  • Fixed an issue where the “Destroy Enemy Forces Attacking Convoy” objective doesn’t clear if the prototype is transported before killing all hostiles
  • Fixed an issue during a Borg Resistance mission on the TNG bridge where switching from the Captain to the OPs position could result in the transport panel blacking out
  • Corrected 2 anomalies in Keth that had incomplete information

BUG FIXES
  • Fixed an issue with enemy ships of the same class missing identifiers in their names
  • Fixed an issue where the "Weaponized Subspace Communication Array" (EMP) visual effect could not be seen by clients
  • Fixed an issue on the TOS bridge where manually lowering the shields could prevent them from being raised again
  • Corrected an issue with the engineering station camera on the TOS bridge where the camera pans to Helm preventing proper use of Power Distribution
  • Fixed an issue with loading screens not appearing for Oculus and Steam non-VR, and Steam WMR/Vive VR
  • Removed a second, erroneous “transport from target” option under tactical crewbot orders on the TOS bridge
  • Corrected an issue where initiating shield modulation would result in inconsistent UI behavior when the station is taken over by a second player
  • Fixed an issue where a player could not modulate shields after they had been brought down (manually or by damage) and then brought back up
  • Corrected an issue in engineering and Ops where repair crews in a fully repaired system would not be reassigned if a repair crew was still in a damaged system
  • Fixed an issue where you could not select the transporter target with your left hand on the TNG bridge
  • Made corrections to TOS bridge view screens as they could look low resolution
  • Fixed a problem where impulsing to new locations sometimes caused enemies to not be on the host player’s Nav Map
  • Improved a number of sound effects including adding a TNG appropriate sound to that bridge when the hull gets to 40% damage
  • Fixed an issue where Avatar android male head type 1 appears to have an extra long forehead (cue the Mike Meyers “HUGE HEAD” comments)
  • Corrected an issue where the female Vulcan head would appear under male Vulcan race type
  • Fixed an issue with objective markers disappearing on the lower ¼ area of the local map
  • Stopped the helm crewbot on the USS Aegis from spinning in place at the beginning of mission 5. He was getting dizzy
  • Removed a purple light that would appear to the right of tactical on the TOS bridge when warping
  • Fixed an issue where the warning indicator for damaged engines on the TOS bridge would not apply to all impulse screens
  • Fixed an issue on the TOS bridge where different players manning the engineering station see different repair crew allocations
  • Fixed an issue on the TNG bridge where an enemy’s cloak audio can disappear while cloaked and the visual effect can persist after decloaking.
  • Corrected an issue where escape pods destroyed by a planet killer would not clear from the transporter bay.
  • You will now correctly see the Borg Cube’s green lights fade out and in when it powers off and on for repairing
  • Gave T’nar some training so that crewbot would properly reassign repair crews from systems at 100% after a player has assigned repair crews
  • You will no longer see “He’s dead Jim” appear for dead crews at the Ops station. Scotty is back on the right ship
  • Fixed an issue where arming torpedoes while being damaged to 59% could cause the remaining torpedo to repeat the loading sequence
  • Fixed an issue where the shields on the TOS bridge needed to be toggled on if all power was removed from shields by the engineer
  • Fixed an issue where System Intrusion sound effects would not be heard when activated
  • Fixed an issue with VOIP audio only playing through the right ear during some mission outros
  • Corrected an issue on the TOS bridge where client assigned repair crews are invisible upon returning to the engineering station
  • Corrected an issue on the Aegis bridge where a player can get the camera stuck on the options menu if the crew bot UI is open
  • Stopped male tactician’s feet on the TNG from constantly shaking.
  • Corrected TOS bridge crew bot UI lag
  • Corrected some shadowing issues with Dynamic shadows settings
  • Made a number of additional improvements and corrections to crewbot interaction
  • Corrected a number of audio bugs
  • Corrected a number of UI and text issues
  • Corrected some character clipping issues and hand positions
  • Fixed a number of crash bugs
12 comments Read more

Feature List

  • Playable in both VR and non-VR, serve as an officer with hand tracking with full-body avatars and lip-sync.
  • Operate as a crew to make strategic decisions and coordinate actions as Captain, Helm, Tactical or Engineer.
  • Take command of the unique U.S.S. Aegis, the first ship of her kind.
  • Play on the original bridge of the legendary U.S.S. Enterprise NCC-1701.
  • Join a shared galactic adventure where communication, trust, and close coordination are the keys to victory.

About This Game

Star Trek™: Bridge Crew, playable in both VR and non-VR, will immerse you in the Star Trek universe. The game puts you and your friends in the heart of the U.S.S. Aegis.
Your mission: explore a largely uncharted sector of space known as The Trench, in hopes of locating a suitable new home world for the decimated Vulcan populace. The Klingon Empire is also active in the region, and their purpose is a threat to the Federation’s plans.

Make strategic decisions and coordinate actions with your crew to complete the mission.
In co-op, you can form a crew of four players to serve in the roles of Captain, Helm, Tactical and Engineer. In addition to a dynamic storyline, the game features an “Ongoing Missions” mode, procedurally generating missions for countless hours of Solo and Co-op adventure.

In Star Trek™: Bridge Crew, you’ll need more than just individual skill to overcome the challenges; communication, trust, and close crew coordination are the keys to victory.

Uplay account and Uplay PC application required for game activation and installation.
A permanent internet connection is required in order to play the game.

System Requirements

    Minimum:
    • OS: Windows 7 x64
    • Processor: Intel Core i5-4590
    • Memory: 8 GB RAM
    • Graphics: NVIDIA GeForce GTX 1050 Ti, AMD Radeon RX 570
    • Network: Broadband Internet connection
    • Storage: 8 GB available space
    • Additional Notes: Resolution: 2160 x 1200 @90Hz; Video Preset: Msaa 2x, all video options ON; VSync:Off
    Recommended:
    • OS: Windows 10 (64-bit versions only)
    • Processor: Intel Core i5-4590 / AMD Ryzen 1500X
    • Memory: 8 GB RAM
    • Graphics: NVIDIA GeForce GTX 970 / GTX 1060 6GB, AMD Radeon R9 290X / RX 480
    • Network: Broadband Internet connection
    • Storage: 8 GB available space
    • Additional Notes: Resolution: 2160 x 1200 @90Hz; Video Preset: Msaa 2x, all video options ON; VSync:Off
Customer reviews
High Volume of Reviews Detected:
Exclude  or  View Only
Review Type


Purchase Type


Language


Date Range
To view reviews within a date range, please click and drag a selection on a graph above or click on a specific bar.

Show graph



Display As:
Review Beta NEW!
When enabled, will sort reviews by new Helpfulness score. Read more about it in the blog post.
Show graph
 
Hide graph
 
Filters
Review Helpfulness Beta Enabled
There are no more reviews that match the filters set above
Adjust the filters above to see other reviews
Loading reviews...