Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: Bobboau on May 01, 2004, 04:31:35 pm
-
ok last night I fixed the bug were if you nock out a subsystem that a thruster is atached to it would not nock out the thruster glows, but now there is the problem of a ship haveing full power even when just one itty bitty engine is still working, or worse when all the glows are atached to the smallest engine subsystem(s) on the ship, so I've been thinking it might be a good idea to have engine capabilities degraded as engine subsystems are taken out, the percentages could be determined by either the hit point percentage or by the radius of the glows atached to it, 'main' engines can be given more priority and/or small engines (like the ones on the arms of the sathanus) can be made so that the ship can't move if these are the only ones left.
discuss
-
Sounds like a good idea to me Bobb, the only thing that occurs to me is that while it would be good if the Sathanas was unable to move by taking out it's main engines, but could still turn on the spot using those rotational thrusters to fire at the enemy? Would that be feasible?
-
Bobb: sounds good, except ANY engine power is enough to move in space. It takes longer to accelerate, but acceleration is still possible.
-
movement may be posable but navagation might not be, you'll be able to generate thrust but you won't realy be able to controle what your doing if all you have is som odd manuvering thruster on the end of a long stick, pointing in an odd direction
-
Okay, so when that happens, make it so that they fly in a neverending circle :lol:
-
heh, that happened to the main character in the X-wing books. He got half of his engines disabled and started spinning uncontrollably.
-
hmm, never read those books. they any good?
-
very... but let's not derail bob's thread, okay?
-
It's a good idea Bob. What you could do is assign each engine a percentage of the maximum thrust on the ships.tbl.
That way old campaigns wouldn't have this effect and wouldn't get broken by this (Cause as a FREDder I can see exactly how big a nightmare this could become :D )
-
Originally posted by ShadowDrakken
Bobb: sounds good, except ANY engine power is enough to move in space. It takes longer to accelerate, but acceleration is still possible.
When has FS been realistic? You can put more power to your engines and go faster so... :p
@bob: making them smaller in size is a good idea, but I would combine it with some size flickering. The engine should look like its gonna die, i.e. flicker around wildly.
-
I like the idea, but it'll need a checkbox in FRED to disable/enable the feature. :nod:
*ahem* feature? I meant bug... :p
-
I agree with WM, since enabling this by default would alter existing missions, and thus break backward compatability. Other possible ways to selectively enable this feature would be with command line flags, or a new flag and entry in the ships table file, as Kara suggested.
Later!
-
Command Line arg is your friend.
-
I like a lot the idea of a screwed navigation, it also sound realistic, and I like too the idea of using hitpoints/thrusters size (mmm luke and wedge in the trench...)
-
Originally posted by Lightspeed
Command Line arg is your friend.
Bad idea to do it as a command line arg.
1) Suppose I've made a mission where the player has to save a ship that is badly damaged and limping to a jump node. If the player hasn't set command line arg up then the ship gets to the node 2 or 3 times as quickly and jumps out before the enemy ships start arriving in force.
2) Suppose you're playing a mission which wasn't set up to work this way. The ship would take twice as long to reach the node again screwing over the mission.
This is something that absolutely has to stay under the control of the FREDder. Doing it as a table would be a bit of a pain so either that or a tickbox in FRED will make me happy but there is no way this should be a command line arg.
-
But then again it would not work with any mission we already have.
Hmm... maybe make it FRED control along with a command line to force it to "on" for all ships?
-
It would in general be a bad idea to use it with missions that were written without this in mind.
It would break a lot of missions. But a command line to force it is reasonable as long as people are willing to take the risk :)
-
Originally posted by Lightspeed
But then again it would not work with any mission we already have.
Hmm... maybe make it FRED control along with a command line to force it to "on" for all ships?
What's wrong with FRED's checkboxes? :wtf:
It's really not all that hard to add a FRED control or two...
-
Lightspeed wants to use this feature with existing mission where individually opening the missions and adding the flag would be a pain.
I keep telling him there's a good chance that will break the mission but if he still wants to try it I say it's his funeral, let him try :)
-
There's already a function in FS2 that decreases ship speed based on engine strength. I'd rather not change it.
-
There is? For capships?
-
I thought that's how they worked, they slowed down when their engines got close to going out. Is it tied to damage instread?
-
Yeah... the funny thing is that it appears to be in two places.
// AL 11-15-97: Rules for engine strength affecting max speed:
// 1. if strength >= 0.5 no affect
// 2. if strength < 0.5 then max_speed = sqrt(strength)
//
// This will translate to 71% max speed at 50% engines, and 31% max speed at 10% enginesand// routine to return the strength of a subsystem. We keep a total hit tally for all subsystems
// which are similar (i.e. a total for all engines). These routines will return a number between
// 0.0 and 1.0 which is the relative combined strength of the given subsystem type. The number
// calculated for the engines is slightly different. Once an engine reaches < 15% of it's hits, it's
// output drops to that %. A dead engine has no output.From the code, it looks like the effects are cumulative, but from the test I just ran with a Deimos, it looks like only the first effect is used. Odd.
-
Yes... I ressurected a 8 month old thread... so sue me :) ...
Any developments in this thruster thingamabob? I've been slaving away with different heirarchy structs with a fighter class POF to get engines to cut out when its subobject is destroyed.
I'm trying to get my Viper to have 3 engines that can be shot out. Its annoying though because when I knock an engine out, its still glowing. Its damage model is showing, but the glows just keeo glowing. Is there anyway to disable thruster glows when it's corresponding subobject is taken out (without using Fred).
I've experimented using the "Special" tab in PCS and had duplicate engine names for both subobject AND "special" and I noticed a pissible GOOD glitch when one of the glowpoints stopped glowing... but it was the wrong one I believe.
-
Thrusters should turn off if the engine subsystem is destroyed. It's based on thruster *banks* though and not the individual glows on the bank. If recent builds aren't working like you expect then send me a copy of the problem model and any relevant data (tbls, images, etc.) and I'll get the code problem fixed.