But Damage would depend on how much velocity the ship has at the time of ramming
Karg
Printable View
But Damage would depend on how much velocity the ship has at the time of ramming
Karg
>But Damage would depend on how much velocity the ship has at the time of ramming
Yeah, velocity times mass equals momentum. (I may be wrong, though. Dutch physics laws sometimes use different terms from the English ones to describe certain effects....)
That's how I do it as well :)Quote:
Originally posted by Brad
I always used Shipboard Systems for capital ships and Vehicle Ops for smaller vessels. I think it makes more sense to do it that way.:)
Makes senses to me :)
Opinions may vary, but I use vehicle operation for any flight related ability, example: your transporter operator with the Shipboard Systems, Transporters at a 3[4], and a Vehicle Operations, Shuttlecraft at a 1[2] might by real good at pushing buttons to get a computer to do things, but the knowledge of momentum has nothing to do with it (unless you count the motion of your hands...he he), or the ability to shift a vehicle like an extension of yourself in combat. Now while the Conn uses button pushing to move the ship there's more to it then that.
But as I said, opinions may vary.
Phoenix...
There's a description somewhere (hows that for helpful) that lists there's one person that works half the controls, and another person working the other half when it comes to the Starfleet Fighter ships - Methinks it's the Ship Recognition Guide...
I figure you're using "Shipboard Systems" on anything you're not flying solo. To me, Vehicle Operations is when you're operating the entire vehicle by yourself, such as in shuttles/shuttlepods. For the fighter, I vaguely recall that description splitting piloting/tactical/navigation/sensors etc up between two people. That's just my little humble opinion, and likely not up to snuff for everyone else. ;)
The Doc
Sounds about right to me too
Karg