What happened to LV-N and Ion engine?!?!?

Windspren · June 3, 2015

I was making a probe today, and I noticed that the LV-N now only has 13 thrust! The Ion engine has 0.043 thrust. I could have sworn that the LV-N had 60 thrust and the Ion had 3.75, but no! Is this just a bug with my game or is it a change with 1.0?

Jovus · June 3, 2015

Not a bug. The engines do still have those thrust values - in vacuum. In atmo, their thrust is severely reduced.

Moss · June 4, 2015

You may be looking at their values for thrust at sea level. Or they could have changed their units of measurement in the descriptions.

Camaron · June 4, 2015

Their thrust within atmosphere is terrible, but they have their full thrust power (60 and 2.0) in vacuum.

ASL = At Sea Level.

Vac = Vacuum (fully in space)

Edited June 4, 2015 by Camaron

Windspren · June 4, 2015

No, I read the VAC thrust

- - - Updated - - -

And the Rhino engine only has 1000 thrust, and the Terrier has a Vac thrust of 13

- - - Updated - - -

It also says the LV-N has a ASL thrust of 6, and the Dawn engine has a ASL of 0.001

Tankman101 · June 4, 2015

You're either mistaken or bugged.

Windspren · June 4, 2015

You're either mistaken or bugged.
http://i.imgur.com/xwuRaG9.png

Nope, that's not what my screen looks like. The 13.875 is my Vac thrust for some reason.

Tobyz28 · June 4, 2015

You're either mistaken or bugged.
http://i.imgur.com/xwuRaG9.png

I have noticed that if you run engines while converting ore to fuel, at a certain point the thrust will reduce dramatically even though the throttle is at 100% and fuel levels are "OK". I believe this is a bug.

Xavven · June 4, 2015

Nope, that's not what my screen looks like. The 13.875 is my Vac thrust for some reason.

Backup save data and reinstall

Windspren · June 4, 2015

Here is the text from the LV-N cfg file. As you can see, the MaxThrust is 13.875. It was 60 yesterday though.

PART

{

name = nuclearEngine

module = Part

author = NovaSilisko

mesh = model.mu

scale = 1

rescaleFactor = 1

node_stack_top = 0.0, 1.40383, 0.0, 0.0, 1.0, 0.0

node_stack_bottom = 0.0, -1.731957, 0.0, 0.0, -1.0, 0.0

fx_exhaustFlame_blue = 0.0, -1.6, 0.0, 0.0, 1.0, 0.0, running

fx_exhaustLight_blue = 0.0, -1.6, 0.0, 0.0, 0.0, 1.0, running

fx_smokeTrail_light = 0.0, -1.6, 0.0, 0.0, 1.0, 0.0, running

sound_vent_medium = engage

sound_rocket_hard = running

sound_vent_soft = disengage

sound_explosion_low = flameout

TechRequired = nuclearPropulsion

entryCost = 22600

cost = 10000

category = Engine

subcategory = 0

title = LV-N "Nerv" Atomic Rocket Motor

manufacturer = Jebediah Kerman's Junkyard and Spacecraft Parts Co

description = Despite the big scary trefoil painted onto the side of this engine, its radioactive exhaust, and tendency to overheat, the LV-N Atomic Rocket Motor is harmless. Mostly. Note that the LV-N is the only LV series engine to run solely on Liquid Fuel - the future is glowing bright!

attachRules = 1,0,1,0,0

mass = 3

// heatConductivity = 0.06 // half default

emissiveConstant = 0.8 // engine nozzles are good at radiating.

dragModelType = default

maximum_drag = 0.2

minimum_drag = 0.2

angularDrag = 2

crashTolerance = 12

maxTemp = 2500 // = 4000

bulkheadProfiles = size1

MODULE

{

name = ModuleEngines

thrustVectorTransformName = thrustTransform

exhaustDamage = True

ignitionThreshold = 0.1

minThrust = 0

maxThrust = 13.875

heatProduction = 240

fxOffset = 0, 0, 1.6

EngineType = Nuclear

PROPELLANT

{

name = LiquidFuel

ratio = 0.9

DrawGauge = True

}

atmosphereCurve

{

key = 0 800

key = 1 185

key = 2 0.001

}

Tankman101 · June 4, 2015

Well something weird happened...

In any case, here's my untouched cfg (whole thing just in case) that you can copy-paste over.

PART{
    name = nuclearEngine
    module = Part
    author = NovaSilisko
    mesh = model.mu
    scale = 1
    rescaleFactor = 1
    node_stack_top = 0.0, 1.40383, 0.0, 0.0, 1.0, 0.0
    node_stack_bottom = 0.0, -1.731957, 0.0, 0.0, -1.0, 0.0
    fx_exhaustFlame_blue = 0.0, -1.6, 0.0, 0.0, 1.0, 0.0, running
    fx_exhaustLight_blue = 0.0, -1.6, 0.0, 0.0, 0.0, 1.0, running
    fx_smokeTrail_light = 0.0, -1.6, 0.0, 0.0, 1.0, 0.0, running
    sound_vent_medium = engage
    sound_rocket_hard = running
    sound_vent_soft = disengage
    sound_explosion_low = flameout
    TechRequired = nuclearPropulsion
    entryCost = 45000
    cost = 10000
    category = Engine
    subcategory = 0
    title = LV-N "Nerv" Atomic Rocket Motor
    manufacturer = Jebediah Kerman's Junkyard and Spacecraft Parts Co
    description = Despite the big scary trefoil painted onto the side of this engine, its radioactive exhaust, and tendency to overheat, the LV-N Atomic Rocket Motor is harmless. Mostly. Note that the LV-N is the only LV series engine to run solely on Liquid Fuel - the future is glowing bright!
    attachRules = 1,0,1,0,0
    mass = 3
    // heatConductivity = 0.06 // half default
    emissiveConstant = 0.83 // engine nozzles are good at radiating, NTRs even better
    dragModelType = default
    maximum_drag = 0.2
    minimum_drag = 0.2
    angularDrag = 2
    crashTolerance = 12
    maxTemp = 2500 // = 4000
    bulkheadProfiles = size1
    MODULE
    {
        name = ModuleEngines
        thrustVectorTransformName = thrustTransform
        exhaustDamage = True
        ignitionThreshold = 0.1
        minThrust = 0
        maxThrust = 60
        heatProduction = 432
        fxOffset = 0, 0, 1.6
        EngineType = Nuclear
        PROPELLANT
        {
            name = LiquidFuel
            ratio = 0.9
            DrawGauge = True
        }
        atmosphereCurve
        {
            key = 0 800
            key = 1 185
            key = 2 0.001
        }
    }
    MODULE
    {
        name = ModuleJettison
        jettisonName = fairingL
        bottomNodeName = bottom
        isFairing = False
        jettisonedObjectMass = 0.1
        jettisonForce = 1
        jettisonDirection = 1 0 0
    }
    MODULE
    {
        name = ModuleJettison
        jettisonName = fairingR
        bottomNodeName = bottom
        isFairing = False
        jettisonedObjectMass = 0.1
        jettisonForce = 1
        jettisonDirection = -1 0 0
    }
    MODULE
    {
        name = ModuleAnimateHeat
        ThermalAnim = overheat
    }
    MODULE
    {
        name = ModuleAlternator
        RESOURCE
        {
            name = ElectricCharge
            rate = 5.0
        }
    }
    RESOURCE
    {
        name = ElectricCharge
        amount = 0
        maxAmount = 0
        isTweakable = false
        hideFlow = true
    }
    MODULE
    {
        name = ModuleTestSubject
        environments = 8
        useStaging = False
        useEvent = True
    }
    MODULE
    {
        name = ModuleSurfaceFX
        thrustProviderModuleIndex = 0
        fxMax = 0.7
        maxDistance = 50
        falloff = 2.5
        thrustTransformName = thrustTransform
    }
}

But it most likely requires a reinstall, who knows how many engines are borked.

Camaron · June 4, 2015

Bitches be trippin', bits be flippin'.

I wouldn't manually do anything with this. You've got at least three engines messed up for some reason, so who knows how much else is damaged? I say back your save, burn your install and replant.

Tankman101 · June 4, 2015

I wouldn't manually do anything with this. You've got at least three engines messed up for some reason, so who knows how much else is damaged? I say back your save, burn your install and replant.

Yep I forgot how many engines they had go weird .

UmbralRaptor · June 4, 2015

It sounds like a messed up upgrade from 1.0 (where engines used the 1.0 atm thrust in their CFG files) to 1.0.x (where engines use the vacuum thrust in their CFG files)

Windspren · June 4, 2015

It sounds like a messed up upgrade from 1.0 (where engines used the 1.0 atm thrust in their CFG files) to 1.0.x (where engines use the vacuum thrust in their CFG files)

Yeah, but it was fine yesterday when I sent a rover to the Mun. I looked and every single engine is messed up. Can someone post a DL for the squad folder as I don't want to reinstall everything.

godefroi · June 4, 2015

It sounds like a messed up upgrade from 1.0 (where engines used the 1.0 atm thrust in their CFG files) to 1.0.x (where engines use the vacuum thrust in their CFG files)

I doubt it. The upgrader would've simply overwritten files, it wouldn't have read them and used the values it parsed out of them to rewrite them. And even if it did, why would it have done it differently for this user than it did for everyone else?

Yeah, but it was fine yesterday when I sent a rover to the Mun. I looked and every single engine is messed up. Can someone post a DL for the squad folder as I don't want to reinstall everything.

Pretty sure not. We don't have rights to redistribute those files. If you use Steam, just run a repair, it'll just fix the files that are messed up, without downloading the whole thing. If you don't use Steam, well, why not?

Windspren · June 4, 2015

I just don't want to wait the 10 minutes it takes for me to copy and paste my mods...... Win 64 bit KSP, I reeeaally need you!

merendel · June 4, 2015

I just don't want to wait the 10 minutes it takes for me to copy and paste my mods...... Win 64 bit KSP, I reeeaally need you!

Shouldnt take that long. just move everything but the "Squad" folder inside your gamedata folder to somewhere else, run a fix or reinstall of KSP and then move it all back. Unless your trying to move it between drives the move should be near instant as your OS is just modifying a few text files that define the file structure tree not haveing to read/write all the data to disk.

No mods should have anything inside the squad folder (and if they do they should be slaped) so nothing should break from that and you can safely reinstall and drop your mods back in quickly as a group.

Mipe · June 4, 2015

It is very easy to override configs. Check your mods, particularly those that somehow modify engines.

katateochi · June 4, 2015

I have noticed that if you run engines while converting ore to fuel, at a certain point the thrust will reduce dramatically even though the throttle is at 100% and fuel levels are "OK". I believe this is a bug.

Yeah I'm pretty sure this is a bug; (my report on it). I've not seen it happen with a single engine, but with multiple engines it's really annoying as not all engines are affected so you get uneven thrust. It's actually a really old issue, I used to have this happen way back (0.18 days) when using Kethane converters.

xiombargdei · June 4, 2015

This hapened to me once with parachute data. You might want to delete a file in your /ksp directory (i think its partdata.cfg or something, i'm at work right now)

save the file and your saves, delete the file, launch the game, it will be forced to recalculate everything, see if that works.

NathanKell · June 4, 2015

This is absolutely symptomatic of a partial revert to 1.0. Do a clean 1.0.2 install.

What happened to LV-N and Ion engine?!?!?

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Join the conversation