Festivefire

If you made the strut a zero capacity fuel tank our wing you could attach things top the surface and if you made it a control surface you could have rotating radar dishes and solar panels

i think that we need to find a way to incorporate mass of the engine into the efficiency equation, cause you could make a perfectly efficient engine of 5000 thrust, and have it weigh 0.000000001 mass units, making it way overpowered, or have an engine with an efficiency of 30 and max thrust of 30, but make it weigh 40 mass units, rendering it useless, even though the equation says it overpowered. this way we can have more or less efficient engines without having them be accused of being cheat parts for challenges and campaign mode. OR we could balance weight of the engine dependent on size, crash resistance, and heat tolerance, and make heat production dependent on efficiency and weight. this way you get a triangle of values, but they don\'t all have to be in the same equation.

i think that is a great eqation for the balancing and marketing of parts. unfortunately, a ridiculous price will not deter players until campaign mode is added. however, the area were balance is currently most important, challenges, can have budgets or limits on parts packs.

once you get all of the ratios in place, you could probably add a tolerence equation for the thrust/consumption ratio. like if you want a +5 tolerence for 30, you could have a equation like (((heat tolerence / heat production) * mass) /10) - (cost/100) = positive tolerence. this also means you can have finicky engines for more thrust or efficiency, and you could ramp the cost through the roof for cheat parts, but this equation still needs tweaks cause it makes the lv-t30 have a -7 point something tolerence, meaning its more efficient for its price, but it should be the baseline. if someone could fix it and explain what i did wrong, or just post something else that works and explain why i\'m wrong that would be great.

cool, gimbaling works now.

just downloaded 0.4. i went through the engines in game, and realized that they weren\'t vectored. you have the thrust vectoring commented out of the .cfg // thrustVectoringCapable = True // gymbalRange = 10 when it should be something like thrustVectoringCapable = True gimbalRange = 10.0 without the double slashes, cause // means to ignore as code, and its just there to help the reader follow what the code is doing like //this section controls engine gimbals thrustVectoringCapable = True gimbalRange = 10.0 meaning that the the rest of the line after // is ignored by the game.

you can do reserve tanks that feed the parent tank with tricky placement, if you put the capsule on top of the reserve tank, then couple the main tank to it, then you put your capsule on the next reserve tank and attach the main tank to it again, do this until you have the desired amount of reserves feeding your main, then put your capsule on the main tank.

even if modders don\'t initialy make their pods duds, we can easily change that through the wonders of notepad.