Star Trek: Bridge Commander

aka: STBC
Moby ID: 5920

Description official description

Star Trek: Bridge Commander puts the player in the role of the new captain of the starship USS Dauntless right after the previous captain perished in a sudden and mysterious explosion of the Vesuvi star which wiped out the nearer half of the planets in the system. Narrowly escaping the fallout, the ship is repaired, receives a new first officer and is tasked with investigating the background of the event throughout the region of space referred to as the Maelstrom, encountering other Federation, Klingon, Ferengi, Romulan, and Cardassian ships, as well as a new race known only as the Kessok.

The player can control the ship and its operations by speaking to the relevant personnel (e.g. hailing and moving the ship by talking to ensign LoMar, or managing the ship's power output and repairs by talking to chief engineer Brex), and can do so either from a first-person perspective from the captain's chair or by viewing the ship from the outside. The ship is almost entirely controllable through hotkeys, and its weapons can be fired manually via mouse controls. If the player's ship is joined by other friendly ships, they can be given simple commands.

The singleplayer campaign is split to 8 episodes, each with its own sub-missions, which form a larger storyline. Unlike many other licensed Star Trek games, combat is not the only focus of the game, as there are missions where exploration and assisting endangered colonies and ships is the main objective. A diplomatic decision late in the game affects the circumstances of the finale. Between missions, the player often moves to Starbase 12 for repairs, stocking on torpedoes, and occasionally to receive more delicate assignments.

Aside from the singleplayer campaign, the game has a so-called "Quick Battle" mode where the player can initiate battles using ships, stations and other objects which appeared in the main campaign, and the player can control any ship from the list. This game mode is also available in multiplayer.

Groups +

Screenshots

Promos

Videos

See any errors or missing info for this game?

You can submit a correction, contribute trivia, add to a game group, add a related site or alternate title.

Credits (Windows version)

229 People (188 developers, 41 thanks) · View all

Creative Director
Project Lead
Network & Interface Programming
AI & Sound Programming, Physics & Simulation Programming
3D Graphics Programming
Interface Programming
Character & Bridge Programming, Save/Load Programming
Game System Programming
Lead Game Design
Game Design, Mission Scripting, Story
Art Lead, Environmental Art
Bridge Sets
Ship Art
Character Animations
Art Technician
[ full credits ]

Reviews

Critics

Average score: 79% (based on 23 ratings)

Players

Average score: 3.9 out of 5 (based on 29 ratings with 8 reviews)

Totally Games totally drops the ball on what should have been a classic.

The Good

'Star Trek: Bridge Commander' does a very nice job of recreating the feel of the Star Trek universe. The overall look of the game is very true to the series. You play the part of a nameless (and faceless and voiceless) captain, out to uncover a secret plot to destroy the Federation. Not exactly original, but not the worst story they could have came up with either.

Gameplay takes place either through the first person perspective of the captain on the bridge, or in a much more interesting and useful tactical mode. The tactical mode is a view of your ship from behind, in which you use the W, S, A, and D keys to control movement, and the number keys for throttle. The mouse buttons are used for firing weapons, and the function keys bring up all the various bridge functions. While your tactical officer is competent enough, the only way to really do well in the game is to use the tactical mode almost exclusively. Besides, the bridge models are relatively ugly and blocky, and the lip sync for the characters in the game is abysmal. It's much prettier out in space.

That said, space combat can be fun. The ships handle as you would expect from a big lumbering starship. The ships turn slowly, and don't race around the screen like, say, an X-Wing or a Tie Fighter would, and this is a good thing for this sort of game. When targeting an enemy ship, you have the option to target various subsystems, whether to take out their impulse engines, warp drive, weapons, or what have you. Unfortunately, this works out better in theory than in practice, as most of the time an enemy ship ends up being destroyed before you are able to take out certain subsystems.

**The Bad**

Sadly, the first word that comes to mind when writing about this game is 'boring'. It's painfully boring in fact. For a game in which you are supposed to be in command of a starship, you end up feeling more like an ensign than a captain. As I said earlier, your character has no voice. Presumably this is to make you feel more like the captain yourself, but if you are like me, you don't feel especially comfortable sitting at home alone barking orders at your monitor.

The game offers absolutely no sense of exploration or adventure, which are qualities you would expect from a game based on a TV show about exploration and adventure. But no, not here. In fact, in this game you will be literally led from mission to mission by the hand, told what to do, where to go, how to avoid being detected, etc. There is nothing left for the player to figure out. There is no puzzle solving whatsoever. The game boils down to warping your ship from system to system (again, you can ONLY go where you are told to) and shooting up any bad guys that may be there.

Another irritating feature of the game is your obnoxious first officer. It feels like she is the captain of the ship, not you. She does all the talking to people on the view screen, she issues orders to the crew, she even reprimands YOU when something goes wrong. That leads me to another point. If you make one mistake, the game is over. Starfleet is notified of your ineptitude and you're canned. Does anyone remember Captain Kirk or Captain Picard ever being relieved of duty for one small mistake or failure? It's ridiculous, and makes you feel like the game should be called 'Star Trek: Bridge Peon'.

Unfortunately the problems don't stop there, not by a long shot. The game has two (more) very serious problems, which in my mind ruin the entire experience. The first is the lack of an in-mission save. Some of the missions are very long, and not being able to save during them means that you will have to play some over and over and over again all the way through. That also means replaying all of the mundane tasks such as recharging the battery, scanning the area, orbiting a planet, listening to messages from this or that person, and so on. It's all pretty dull the first time, and nearly unbearable by the fifth or sixth.

This leads me into the other major mistake made by Totally Games. You cannot, under any circumstances, skip a cutscene. So, if you are forced to play the same mission 7 or 8 times (because of a lack of in-mission saves) you will also be forced to watch the same badly acted, poorly lip synced cutscenes 7 or 8 times. To make matters worse, some of them are several minutes long. This is really unforgivable in my opinion, and quickly kills any desire to keep playing what is already a terribly flawed game.

Graphically the game looks pretty nice, but not as nice as many would have you believe. I hear a lot of talk about how this looks just as good as the TV show, and that is just nonsense. The interiors are dull and ugly, and the exteriors tend to be dark and muddy. Though to be fair, the ship models are very well done and have a great amount of detail. It'd just be a lot nicer if I could see them clearly when in tactical mode, instead of having enemies appear as dark shapes against a star field. The absence of an in-game brightness adjustment option is another amateurish oversight.

**The Bottom Line**

Despite a good record, Totally Games really didn't get it right this time out. From the people that brought us such classics as the X-Wing and Tie Fighter series, I would have expected a lot more. Sadly, all the irritating flaws add up to a game-killing problem. It's just not fun, and for the $50 you will spend on it, there are a lot of much better games out there you could buy. Maybe a hardcore Star Trek fan would be able to overlook, or even completely ignore all of the games glaring faults. For anyone who doesn't speak Klingon or own a Starfleet uniform however, I'd stay away from this disaster.

Windows · by Entorphane (337) · 2002

One of the better Star Trek games released - but not for gamers that get easily bored

The Good
Almost everything - besides, it's not every day you get to sit in the captains chair of Star Trek ships.

I'll go into minor detail: Excellent atmosphere which really re-lives the famous Star Trek feeling from the series and some of the movies, great plot, great voice-acting, good controls, good strategic combat, and overall a well accomplished game.

The Bad
Being a gamer that values freedom, I really think they could have out even more into this Star Trek title - I mean, we got the bridge of a starship; and everything in the game is almost just right to make the new Elite, or 3D StarFlight - imagine if we could go to other systems to trade and explore freely in this Star Trek universe...

But this is not the case; the player is only led trough a certain chain of missions, without any real chance of freedom - sure, there is a skirmish-mode available, but it really don't give much more freedom either - you just get to blow up different ships from various species.

There's also the thing that this is not a game for most action gamers; there's long conversations, and often long periods of waiting in this game, and quite often you find yourself going ahead of the game itself. For me, this is not a problem, as I like such things, but for others, it might be quite annoying at places.

The Bottom Line
Overall though, Star Trek: BC is a good game with lots of sadly unexplored potential; it is not everyones cup of tea, but if you like Star Trek, or better yet, if you like sci-fi (like myself), this is a game I recommend - just don't expect too much; it IS a good game, but it could have been much better (but then again, its a commercial space-game).

So, I give it one thumb up - for a good game with good plot and fairly well accomplished.

Windows · by Stargazer (99) · 2003

Good Presentation, Flawed Game Play

The Good
The story is intriguing and well-written; a worthy bit of Star Trek fiction. You are cast in the role of first officer on the U.S.S. Dauntless, a Galaxy class starship investigating some anomalous solar activity in the Vesuvi system. While in the system, the ship's captain takes a shuttle to rendez-vous with a Federation terraforming outpost. As the shuttle approaches the outpost, the core of the Vesuvi system's star suddenly and inexplicably destabilizes. The captain orders you to get the ship out of danger, just before his shuttle is engulfed in a solar explosion. Hence the reason for your sudden promotion to captain.

As the Dauntless leaves the system, the science officer notices a strange object warping out of the system but he is unable to identify it. Suspicions abound that the Cardassians have something to do with this mysterious turn of events. Now in command of the Dauntless, you are ordered by Starfleet Command on a series of investigative missions aimed at discovering what happened in the Vesuvi system. The various missions serve to unfold the plot and the entire thing remains intriguing throughout.

The interface is extremely well designed in my opinion. Next Generation style LCARS panels are overlayed over a first-person 3D view of the bridge. In contrast with earlier Star Trek based simulations, you don't jump around between different control panels here. You never lose sight of your bridge and crew. The LCARS panels are there when you need them and move quickly out of your way when you don't. This interface is the most successful that I've seen so far in terms of making you feel like you're in the captain's chair overseeing the bridge and crew rather than jumping around from station to station micro-managing everything.

The graphics, in my opinion, are attractive overall. Bridge layouts are accurate, if simplified. Starship exteriors are nicely modeled. Light sourcing and specular highlights are used to good effect. There is a nice glow effect for lit windows, phaser beams and warp nacells and shields shimmer semi-translucently when absorbing hits.

There was an interesting design decision regarding the faces of the characters. Bitmapped character faces are pasted onto the heads of the character models. The mouths are animated when characters speak but, other than this, there is little facial animation. Eyes don't blink and expressions remain neutral. The result is characters that are instantly recognizable (Picard looks like Picard and Data looks like Data) but there is no real lip synching and character faces seem bland and expressionless, almost like everybody is wearing some kind of mask. The features also tend to look somewhat angular at times. This is something that I, personally, can live with, especially remembering that this game was released in 2002, when graphical hardware was not as advanced as it is now.

Sound is also nicely rendered. Phasers and torpedoes sound as they do in the television shows and movies. The voices of Captain Jean-Luc Picard and Lt. Commander Data are provided by Patrick Steward and Brent Spiner respectively. Voice acting for other characters (not seen on TV or in the movies) is likewise competent and believable. The musical soundtrack is typical for a Star Trek feature, grand and orchestral with a more dramatic cadence during battle engagements.

The Bad
Some of the missions are designed to be ridiculously hard, pitting your ship alone against hoards of enemy attackers with little or no support from Starfleet. What's worse, the penalty for getting out of some of these scenarios alive yet failing your primary objective is an unreasonably harsh dressing down by the Starfleet admiralty who, in my opinion, should really be impressed that you even managed to save your ship and crew, never mind knock out that enemy sensor array. Likewise you can successfully complete mission after mission, being lauded and praised by your superiors after each victory, only to be dismissed as an incompetent fool when you finally do fail. I guess it's true what they say; people really do remember your last mistake. One wonders, at times, whether one hasn't been unwittingly drafted into the service of the Imperial Klingon Fleet. Total and unqualified success, death or dishonour! Those are your options.

The mission structure suffers from the same weakness seen in Larry Holland's Star Wars games; namely, they are linear and heavily scripted and some are designed such that success depends on performing certain actions in a certain sequence or at a certain time. Doing anything else inevitably results in failure, and this makes several of the missions feel more like puzzles to be solved rather than tactical situations to be evaluated. It's no coincidence that failed missions are more successful the second or third time around, once you have the benefit of foreknowledge of what's going to happen.

I've read some other reviews of this game which complain about the inability to skip the cut scenes. I'd like to clarify this issue by pointing out that, although the cut scenes can't be skipped entirely, it is possible to skip to the next line of dialog by pressing the backspace key. Do this shortly after each line of dialog begins and it is possible to "skip forward" through all cut scenes quite quickly. Still, I do agree that it would have been nice if there had been a key to skip directly to the end of a cut scene or, better yet, a config setting allowing cut scenes to be turned off, or at least to be played only the first time through. This could have been handled better, but it's not as bad as some would have us believe.

The characters seem to blindly follow their scripts at times without any regard for what actually happens in the game. For example, at the start of one mission, my first officer recommended that we should return to the starbase for repair and resupply, even though:

a) We were already at the starbase b) They had just told us that they could only re-supply but not repair us. c) We had just finished docking and our supplies had been replenished.

Similarly, characters sometimes react to occurrences without considering the full situation. For example, in the heat of one particular space battle, my weapons officer targeted an enemy ship with photon torpedoes. The torpedoes failed to lock properly and missed their target, unfortunately hitting a friendly starbase that was beyond the target. My first officer reacted by promptly relieving me of command for firing on a friendly, apparently oblivious to the fact that I had never given any command to attack the starbase nor had I personally fired the errant torpedoes, never mind that the whole thing was obviously an unfortunate mishap. I might have understood had she decided to relieve the weapons officer for incompetence, I suppose.

Engagements between starships can last quite some time. It takes a while to destroy or disable a starship, unless the combatants are woefully mismatched. Your weapons officer will normally make intelligent decisions such that, with only a few exceptions, you can usually allow him to select his own targets and systems and such. This is as it should be. It does mean, however, that you can spend much of your time during battles, especially prolonged engagements involving multiple starships from various sides, simply watching the battle unfold. You might occasionally order your chief engineer to channel more power to the shields or the weapons or whatever system seems most important at the time but, other than this, you need do very little. This can make missions seem rather dull to some. On the other hand, you can manually take control of the ship and do all the fighting yourself, but this seems less in keeping with the Star Trek mythos, and you'll usually do no better than your weapons officer would have, in any case.

One graphical effect that bothered me more than the weird, angular faces of the characters was the fact that starships insist on belching smoke when damaged. Smoke in the vacuum of space? Whose idea was that? Fire, yes. Sparks, of course. But smoke? Methinks Larry Holland must have cannibalized his Secret Weapons of the Luftwaffe engine when building this game and forgotten to kill the smoke effects.

The graphics engine also attempts to show exposed decks beneath punctured hulls on severely damaged vessels, but this doesn't quite work for me either. Somehow, the effect looks too much like a 2D bitmap. It was done much better in Interplay's Star Trek: Klingon Academy.

The Bottom Line
Star Trek: Bridge Commander does have its flaws but, overall, I enjoyed it. It's strength is in its presentation. Its weakness, unfortunately, is in the actual gameplay. Still, I think it fair to say that it comes as close to simulating the experience of commanding a Federation starship as any Star Trek game has to date, even if it doesn't entirely hit the mark.

Windows · by Halmanator (598) · 2005

[ View all 8 player reviews ]

Trivia

If you click on Brex several times in a row, he will say some amusing things.

Analytics

MobyPro Early Access

Upgrade to MobyPro to view research rankings!

Related Games

Star Trek: Bridge Crew
Released 2017 on Windows, PlayStation 4, 2019 on Quest
Star Trek: Bridge Crew - The Next Generation
Released 2018 on PlayStation 4, Windows
Star Trek
Released 1979 on TRS-80
Star Trek
Released 1981 on DOS
Star Trek
Released 1978 on Mainframe, 1979 on Sol-20
Star Trek
Released 1979 on Poly-88
Star Trek
Released 1982 on BBC Micro
Star Trek
Released 1979 on TI Programmable Calculator

Related Sites +

Identifiers +

  • MobyGames ID: 5920
  • [ Please login / register to view all identifiers ]

Contribute

Are you familiar with this game? Help document and preserve this entry in video game history! If your contribution is approved, you will earn points and be credited as a contributor.

Contributors to this Entry

Game added by Kartanym.

Additional contributors: Apogee IV, Erik Novales, Independent, Plok.

Game added March 8, 2002. Last modified October 11, 2023.