Search the Community

Gillermoo's Kerbal Engine Mapper is a tool that can help you determine the optimal rocket for your mission. Optimize for either lowest mass or lowest cost. Install here: [snip]

So i had create engine model and how to make it generate thrust i know there are tutorial but i also want to create custom engine particle and these two conflict,And all those tutorial is for 2018 not 2020 and also ksp has changed to unity 2019

I just started to play this game and I am having fun. But I just can't make the liquid engine work! I tired unsing the space bar, but it didn't do anything. Then I tried to right click and click activate engine, but it still didn't work. Help! P.S. i am having trouble loading the screenshot.

Hello, I am playing with the parts cfg and came to the Multi Mode Engine. As far as I can see, there can only be 2 engine modes (primary and secondary). Is there any possibility to have a third (fourth, fifth...)? I can add more modules and they appear at the parts description in VAB, but I cannot switch to them.

I would like the RD-0410 Russian Nuclear Thermal Engine to be added to the game because it will balance out with the LV-N "Nerv" Atomic Rocket Motor. Also it will add a great deal of fun, experimenting, and using it to go to places that you have wanted to go. All in All the RD-0410 Russian Nuclear Thermal Engine is a great engine to be added to the game because it teaches the player on how nuclear engines work.

so, i don't know how much fuel to pack till duna, because if you pack too low amount, then for circularizing and for all that, you'll not have enough fuel, and if you pack too much, then your weight will be too big, and you will consume a lot of fuel for a small amount of deltav

Hello ! Im working on my first ksp mod who's gonna add new propulsion systems (like nuclear fusion or antimatter for example). I have a little problem with one of my engines : im using a module enginesFX for the engine principal informations and a prefab_particle for the flame. And the flame, dont want to apears when the engine start. If someone can check the code and tell me if there is errors, it will be very helpful ! Thank you !! PART { name = EtrFusion1 module = Part author = Lgg159 mesh = model.mu rescaleFactor = 0.78125 node_stack_top = 0.0, 0.16, 0.0, 0.0, 1.0, 0.0, 1 TechRequired = heavyRocketry entryCost = 0 cost = 36000 category = Engine subcategory = 0 title = "ETR-1" Aerospike Fusion Engine manufacturer = UTech Nucler Science Inc. description = The "ETR-1" engine use a new technology : it uses nuclear fusion and electromagnetic fields to create and propulse very hot helium in the space. attachRules = 1,0,1,0,0 mass = 2.7 heatConductivity = 0.06 skinInternalConductionMult = 4.0 emissiveConstant = 0.8 dragModelType = default maximum_drag = 0.2 minimum_drag = 0.2 angularDrag = 2 crashTolerance = 10 breakingForce = 200 breakingTorque = 200 maxTemp = 3000 bulkheadProfiles = size1 tags = fusion etr nuclear helium he3 magnetic tritium deuterium MODULE { name = MultiModeEngine primaryEngineID = Helium3 primaryEngineModeDisplayName = Helium3 secondaryEngineID = Tritium secondaryEngineModeDisplayName = Tritium autoSwitchAvailable = False } MODULE { name = ModuleEnginesFX engineID = Helium3 powerEffectName = running thrustVectorTransformName = thrustTransform exhaustDamage = True ignitionThreshold = 0.1 minThrust = 0 maxThrust = 5600 heatProduction = 400 fxOffset = 0, 0, 1.2 PROPELLANT { name = DeuteriumFuel ratio = 4.5 DrawGauge = True } PROPELLANT { name = Helium3Fuel ratio = 3 } atmosphereCurve { key = 0 20000 key = 1 19800 key = 6 0.001 } } MODULE { name = ModuleEnginesFX engineID = Tritium powerEffectName = running thrustVectorTransformName = thrustTransform exhaustDamage = True ignitionThreshold = 0.1 minThrust = 0 maxThrust = 5500 heatProduction = 390 fxOffset = 0, 0, 1.2 PROPELLANT { name = DeuteriumFuel ratio = 4.5 DrawGauge = True } PROPELLANT { name = TritiumFuel ratio = 3 } atmosphereCurve { key = 0 19800 key = 1 19200 key = 6 0.001 } } EFFECTS { running { AUDIO { channel = Ship clip = sound_rocket_hard volume = 0.0 0.0 volume = 0.05 0.6 volume = 1.0 1.5 pitch = 0.0 1.2 pitch = 1.0 2.0 loop = true } PREFAB_PARTICLE { prefabName = fx_exhaustFlame_blue transformName = thrustTransform emission = 0.0 0.0 emission = 0.05 0.0 emission = 0.075 0.25 emission = 1.0 1.25 speed = 0.0 0.25 speed = 1.0 1.0 localOffset = 0, 0, 0 } PREFAB_PARTICLE { prefabName = fx_exhaustLight_blue transformName = thrustTransform emission = 0.0 0.0 emission = 0.05 0.0 emission = 0.075 0.25 emission = 1.0 1.25 speed = 0.0 0.25 speed = 1.0 1.0 localOffset = 0, 0, 0 } } } MODULE { name = ModuleGimbal gimbalTransformName = thrustTransform gimbalRange = 3 } MODULE { name = FXModuleAnimateThrottle animationName = ksp_l_midrangeEngine_anim responseSpeed = 0.001 dependOnEngineState = True dependOnThrottle = True } MODULE { name = ModuleAlternator RESOURCE { name = ElectricCharge rate = 6.0 } } MODULE { name = ModuleTestSubject useStaging = True useEvent = True situationMask = 127 CONSTRAINT { type = REPEATABILITY value = ALWAYS prestige = Trivial } CONSTRAINT { type = REPEATABILITY value = BODYANDSITUATION prestige = Significant } CONSTRAINT { type = REPEATABILITY value = ONCEPERPART prestige = Exceptional } CONSTRAINT { type = ALTITUDEENV test = GT value = 4000 prestige = Trivial } CONSTRAINT { type = ALTITUDEENV test = LT value = 8000 prestige = Trivial } CONSTRAINT { type = ALTITUDEENV test = GT value = 2000 prestige = Significant } CONSTRAINT { type = ALTITUDEENV test = LT value = 4000 prestige = Significant } CONSTRAINT { type = ALTITUDEENV test = GT value = 1000 prestige = Exceptional } CONSTRAINT { type = ALTITUDEENV test = LT value = 2000 prestige = Exceptional } CONSTRAINT { type = ALTITUDE test = GT value = 0 // this just registers altitude as something to care about situationMask = 8 } CONSTRAINT { type = ALTITUDE test = LT value = 300000 situationMask = 16 body = _NotSun } CONSTRAINT { type = ALTITUDE test = LT value = 600000 situationMask = 32 body = _NotSun } CONSTRAINT { type = SPEED test = GT value = 0 situationMask = 8 prestige = Trivial } CONSTRAINT { type = SPEED test = LT value = 600 situationMask = 8 prestige = Trivial } CONSTRAINT { type = SPEED test = GT value = 300 situationMask = 8 prestige = Significant } CONSTRAINT { type = SPEED test = LT value = 1200 situationMask = 8 prestige = Significant } CONSTRAINT { type = SPEED test = GT value = 600 situationMask = 8 prestige = Exceptional } CONSTRAINT { type = SPEED test = LT value = 2500 situationMask = 8 prestige = Exceptional } CONSTRAINT { type = SPEEDENV test = LT value = 200 prestige = Trivial } CONSTRAINT { type = SPEEDENV test = GT value = 100 prestige = Trivial } CONSTRAINT { type = SPEEDENV test = LT value = 100 prestige = Significant } CONSTRAINT { type = SPEEDENV test = GT value = 50 prestige = Significant } CONSTRAINT { type = SPEEDENV test = LT value = 50 prestige = Exceptional } CONSTRAINT { type = SPEEDENV test = GT value = 20 prestige = Exceptional } } MODULE { name = ModuleSurfaceFX thrustProviderModuleIndex = 0 fxMax = 0.8 maxDistance = 50 falloff = 2 thrustTransformName = thrustTransform } }

I've been paying much closer attention to delta V, engine weight, and twr as of a late, and I've noticed some interesting things. To start, I've just recently noticed that the overall delta V of a craft is heavily affected by engine weight, sometimes even to the point of affecting which engines I'd prefer to use. Previously, I'd picked engines solely based on their ISP, size relative to the craft/stage, and the overall twr of the final craft/stage. However, since 1.6 added the delta V display to the stock game, I've been gradually prioritizing it over those other things. Nowadays, I'm often shocked to find that the Delta V shoots up when I use an engine with noticeably lower thrust and ISP, seemingly just because of how light the engine is comparatively. I've started using the Spark engine over the terrier in all my deep space 1.25m craft in my early science games, despite the size the difference being quite noticeable; the delta V will tend jump up by shocking amounts just by swapping into the lower efficiency engine! I've even run into some scenarios that make seemingly worthless engines worthwhile; despite the poodle appearing to be inferior to the wolfhound in a variety of ways, it actually gives the craft more delta V in many cases! I'm sure this is an obvious thing that rocket science has to take into account, and I probably look quite dumb to a lot of people right now, but I just find it fascinating how a difference in mass of 1.55 tons can make 113m/s of delta V come from a noticeably less efficient engine! I was just wondering if there was a good way to quickly quantify this at a glance looking at the engine stats. As it stands, I'm only really able to find the best engine for a craft through trial and error, since I'm not really sure how the engines weight plays into things. I've gained a general intuition for how thrust and ISP factor into a crafts design, and this new variable is getting me all confused And now for the "Kerbal" aspect of things; I've recently been infatuated with the idea of making a rocket with the highest possible twr that can reasonably be achieved. I personally find it hilarious when I make rockets that are so powerful, that they are immediately burned up before they could ever hope to hit space Does anyone have any tips for getting the most twr per part, while keeping burn time high enough to use that twr? I'd love that

As you are aware, In Kerbal Space Program there exists the IX-6315 "Dawn" Electric Propulsion System, commonly known as the Ion engine. It's small, and produces low thrust, but has incredible fuel efficiency. Is it useful, or useless?

There's a definite lack of Russian engines in KSP. Apart from the Kodiak and Cub there aren't really any. That's a shame because Russian engines are some the best looking and best performing of all. Here's a few I think would make great additions to KSP. 1. RD-170. This is the most powerful rocket engine in the world, and it baffles me how there isn't an equivalent to it in KSP. For thrust we could be looking at around 2300-2400 kN. Size would be 2.5m. 2. RD-180 This would be a varient of the RD-170. For thrust, it would be between 1300-1350 kN, this would give it enough thrust to lift an Atlas 5 replica. Size would be 1.875m, this would mean it either is exclusive to MH-owners or would need the introduction of a stock adapter. 3. RD-191 The third and single nozzle varient of the RD-170. It's thrust would be around 600-700 kN at a size of 1.25m. 4. RD-0120 This won't be a seperate engine but a varient of the Vector to give it some more visual variety. 5. NK-33 The engine that was supposed to launch cosmonauts to the moon. How this isn't in KSP yet astounds me. The thrust would be around 600-650 kN at a 1.25m size. (Yes, I know the picture is of the AJ26-58) 6. RD-58 This engine was made to be used on an upper stage of the N1 and evolved version were to be used on the Buran spacecraft. This would be a low-thrust, high efficiency upper stage engine. Around 50-75 kN thrust at a possible 0.625m size. 7. S5.92 This engine is currently used in the Fregat upper stage. It would function as a great, small upper stage engine. Thrust would be around 20-30 at a 0.625m size. 8. RD-0210 It's thrust would be around 200-250 kN at a 1.25m size.

So, I'm making a radial jet engine- think the Vector's way of attaching vs the huge jet's version. How do I set up points in Blender so that it can function with a Gimbal and everything else? I'm around halfway through modelling it. Thanks for any help!

I have a problem... I tired everything but I can't solve it.The particles don't stay on their place.I want a normal engine plume. [noparse] //Ren1 //d_s___3 PART { name = ds3_engine_Ren1 module = Part author = d_s___3 mesh = Ren1-M scale = 1 rescaleFactor = 1 node_stack_top = 0.0, 0.1, 0.0, 0.0, 1.0, 0.0, 1 node_stack_bottom = 0.0, -0.5, 0.0, 0.0, -1.0, 0.0, 1 fx_smokeTrail_light = 0.0, -1.6, 0.0, 0.0, 1.0, 0.0, running TechRequired = nuclearPropulsion entryCost = 450000 cost = 9000 category = Engine subcategory = 0 title = Ren1 manufacturer = #autoLOC_501627 //#autoLOC_501627 = Jebediah Kerman's Junkyard and Spacecraft Parts Co description = --MOD-- Ein tolles Triebwerk! attachRules = 1,0,1,0,0 mass = 3 heatConductivity = 0.06 // half default skinInternalConductionMult = 4.0 emissiveConstant = 0.85 // engine nozzles are good at radiating, NTRs even better dragModelType = default maximum_drag = 0.2 minimum_drag = 0.2 angularDrag = 2 crashTolerance = 9 maxTemp = 2500 // = 4000 bulkheadProfiles = size1 radiatorMax = 0.15 //Kühler tags = #autoLOC_500438 //#autoLOC_500438 = active atom efficient engine inter liquid (nerv nuclear nuke orbit propuls radio reactor vacuum MODULE { name = ModuleEnginesFX engineID = ds3_exhaust_Ren1 thrustVectorTransformName = particleFX runningEffectName = running_closed exhaustDamage = True ignitionThreshold = 0.1 minThrust = 0 maxThrust = 90 heatProduction = 150 fxOffset = 0, 0, 1.5 PROPELLANT { name = LiquidFuel ratio = 0.9 DrawGauge = True } atmosphereCurve { key = 0 800 key = 1 185 key = 2 0.001 } } MODULE { name = ModuleSurfaceFX thrustProviderModuleIndex = 0 fxMax = 0.7 maxDistance = 50 falloff = 2.5 thrustTransformName = thrustTransform } EFFECTS { running_closed { MODEL_MULTI_PARTICLE { modelName = Exhaust2/FX/Ren1_Exhaust transformName = thrustTransform emission = 0.0 0.0 emission = 0.1 0.5 emission = 1.0 1.0 speed = 0.0 0.8 speed = 1.0 1.0 } } }

Ah, the Skipper! What a nice looking engine... But does it need an overhaul? or should we leave it alone? that is up to you to decide. I vow to have it be unchanged, and that other parts should base their design on this, but that is my opinion. Do you have any thoughts?

Announcing the 0.1.0 alpha release of Simple Procedural Engines. Aerobees too small for you? F-1 slightly too big? Agena more thrust than you need? Then have we got solutions for you! S. P. Engine allows you to create procedural engines from several real-world-inspired families, by setting the thrust and ignition count within the supported range. After tooling a design, you can follow its upgrade path as you unlock further techs, saving many many funds as compared to a brand new design. S. P. Engine is built for use with the Realism Overhaul suite of mods, and in particular has a hard requirement for RealFuels. (That's why I'm releasing for 1.3.1 rather than something more recent; the various Realism mods are still back there.) Currently supported engine families (with mnemonics): A: (Aggregat) Ethanol/LOx booster. B: (Bees) Small aniline/furfuryl/nitric acid sustainer. D: (Delta) Pressure-fed hydrazine/nitric acid upper stage. F: (F-1) Huge kerosene/LOx booster. G: (aGena) Pump-fed hydrazine/nitric acid upper stage. J: (J-2) Large hydrolox upper stage (and later aerospike sustainer). K: Kerosene/LOx booster up to about 1MN thrust. (Like LR79, H-1 and Merlin1.) L: (Lr105) Kerosene/LOx sustainer. Matches nicely with K-class to make Atlas-style stage-and-a-half. M: (M-1) Massive hydrolox upper stage (later also sea-level). Q: Small, throttleable hydrolox upper stage engine. (Like throttling RL10s developed for Lunex.) R: (Rl10) Small hydrolox upper stage engine. S: Small staged-combustion kerosene/LOx upper stage. (Like S1.5400/11D33/RD-58 family.) Several more are planned. Read this far? Download S.P.Engine 0.1.0 and give it a try!

Hey! Beginner question here, I recently made my first custom part for ksp, an engine. While making the .cfg I noticed a field called "ratio" in the propellant section. Only answer I've found on google is from the documentation wiki which says it notes how much of a resource is used in 1s. Although, all engine .cfgs I've seen use 0.9 for the fuel and 1.1 for the oxidizer. So, what does that line do and how is it correlated to the overall workings of the part?

I haven't used this account in quiet some time, nor do I play much KSP anymore... But this has been an ongoing issue for me for ages. Any engine with a rotor, be it stock (Goliath) or modded (in this case Airplane+), the rotors seem to spin backwards. I feel that this isn't major enough to put in any other forum section and may seem trivial, but it's been bugging me for ages. Redownloading the game isn't something I want to do (due to my very slow internet and limited bandwidth) and I've tried removing all mods, but this minor issue still remains. If anyone has any ideas on what I can try before giving in and reinstalling, it would be greatly appreciated. Here's a gif so you understand what I'm talking about. Edit: I just reinstalled the game, no mods, nothing other than stock parts and settings... Rotors still going backwards. This is an issue with the core game. Although minor, I think it should be fixed. No jet engine I've seen IRL pushes air out the front

Disclaimer: English isn't my native language, I do my best. Clay Parts; no it's not about clay but its malleability. My idea is a completely revamp part system where your parts adapt to the shape, size, fonctionnality and visual you want. Less parts (even with a lot of mods), just highly configurable ones and configurations. ClayAddons will be a serie of standalone mod that interact with each other alot. This post is about discussing and defining the theoretical rules between each part and functionality. Ex: relation between size and thrust of an engine. As ClayAddons will contain alot of stuff we will go step by step. First one engine! How engine are handle by the mod (ClayEngine). Engines includes everything that allow movement, motion or implied motion ex electric generator. In fact the mod include no engine, but engine module or component (you can have multiple engine module in one part and module on a part can interact with module on other parts). Ex1: the propeller is a module, piston engine is another one. Ex2: combustion chamber is a module, tuyere (nozzle) is another one. Each module have a whole range of option ex: size, number of piston(piston engine), number of blades(propeller). Each module can have one or multiple virtual and physical nodes. Module node are port for linking modules with each other like electric plug. Nodes can be connected when module are placed inline or with various cable: electric cable, fuel line, shaft, cable(rope or metal cable), track(for wheel), chain, belt, pipes(yes pipes for air, water and ??????. So air intake need to be connected to engine using pipes.) Virtual nodes are for internal use only. Physical nodes will lead to the outside of the part of his module if not linked to anything else ex: exhaust, air intake. For physic ease all those internal logic will be simplified at vessel load. I need your help to define module their nodes and options. +Mass etc let focus even more---> Propeller engine + Piston engine Propeller component: core (nose cone): size, mass, drag, internals blades: number, size, drag, design, thrust ressource: torque, rotation, air, thrust, data Piston engine component: piston: number, size, configuration, mass, power ressource: electricity, gas(oxygen), gas(CO2), liquid fuel, torque, rotation, heat, data Gearbox: type(planetary, ....), mass, size ressource: torque, rotation Shaft: mass, size ressource: torque, rotation Those four element interact by torque and rotation For later

This is a stock 1:1 replica of the SABRE hypersonic precooled hybrid air-breathing rocket engine currently being developed by Reaction Engines Limited. This engine is slated for prospective use on a variety of hypersonic aircraft, although most famously for the Skylon launch vehicle. I would suggest throttling down slightly before switching over to rocket mode, this isn’t strictly neccessary but I found that the sudden burst of thrust from the Vectors occasionally caused the engine to explode. This engine is powered by 8 R.A.P.I.E.R.s and 4 KS-25 engines. SABRE Engine Information: Download Link: https://kerbalx.com/Kronus_Aerospace/SABRE-Engine Part Count: 110 Replica Thrust Rocket-Mode Vac: 2940 kN Replica Thrust Jet-Mode SL Mach-1: 1920 kN Replica Gimbal Rocket-Mode: 1.6° Replica Gimbal Jet-Mode: 3° Replica Mass: 38.9 tonnes Real SABRE Thrust Rocket-Mode Vac: 2940 kN Real SABRE Thrust Jet-Mode SL Mach-1: 1960 kN Real SABRE Gimbal Rocket-Mode: Unspecified Real SABRE Gimbal Jet-Mode: Unspecified Real SABRE Mass: Unspecified

This is a stock replica of the GP7000 Turbofan developed by Engine Alliance, a joint venture between General Electric and Pratt & Whitney. This replica’s central feature is definitely its spinning turbine, which is functionally a turboshaft as it is powered by two Juno’s set to very low power. This method of spinning the turbine means that the turbine actually throttles with the actual engines, which is obviously super cool. This engine uses 3 Wheesley’s which in total provide similar thrust to the real thing. The one downside of this engine is that you will need to place intakes in a seperate location on your craft, as there is no way of incorporating intakes into the engine itself. Download Link: https://kerbalx.com/Kronus_Aerospace/GP7000 Part Count: 113 Engine Mass: 9.97 tonnes Engine Thrust: 330 kN

Do you guys think that propeller engines should be added to KSP? Propellers would serve as precursors to Jet engines in Career mode. They would have less thrust, but would drain fuel slower. They would also be cheaper than other jet engines.

I would really like to see a modular engine mod, which let's you design your own engine by changing nozzle size, combustion chamber size, fuel used and etc. Hopefully someone will take on this mod someday, thank you for reading.

so I downloaded the GN-Drive mod for Ksp. and ran into some issues since its an outdated mod. I am hoping to find someone or a group of people that would want to make a collab mod with engines and Reactors from several TV-shows and Anime. in the current version of KSP.

Hi, I think the RE-12 'Skiff' Liquid Fuel Engine needs some tweaking. With the collection of new parts from the 'Making History Expansion', it seems obvious that most of these parts are there to make replicating historical rockets easily, namely the Saturn 5. This is easily one of my favorites so I wasted no time in building my own replica, which I have done many times throughout playing KSP. This part seems a good pick to simulate the J2 engines featured on the second and third stage of the rocket (at least aesthetically), but in KSP their function is just not right and don't fit with the parts associated with them. I have tried many different ways and either my second / third stages have lackluster TWR or burn for too long which ends up with a weird looking Saturn 5 in order to compensate. If this part was not intended at all for this then this is purely academic and disregard, but otherwise if this could be addressed in some way that would be great. I think an increase in thrust and a decrease in ISP values will solve this issue.

Hi, The 'Kerbadyne Engine Cluster Adapter Tank' part has a bug where if you have 'Rigid Attachment' on, it will break off your rocket on launch regardless of how much support you give it through struts. For those who might be having trouble, just turn off 'Rigid Attachment' for the time being. I have found it to be fine without any support.

So I wanted to use one of my premade planes but now when I try to fly them, they just spin out and go wild. Also I do use cheats in my science save cause why not. Though I only use Unbreakable Joints, No crash damage, Inf Electricity and Inf Propellant. I have accidentally click on the physics tab but went back. So I don't think I changed the aerodynamics myself as they worked the last time I play KSP. Was there a change I wasn't aware about? Also running 1.4.1