[1.1.2] Realism Overhaul v11.0.0 May 8

[Devinci]

Chances are you do not have the engine attached to a fuel tank with the correct fuel. Most to all fuel tanks in RO are defaulted to empty so, once you attach an engine to one - be it a FASA tank or a Procedural Tank, you have to right click on the tank and hit the button to fill it with the right resource.

One note is that most engines will work fine with the default Procedural Tank, but if you're using a pressure fed engine, then you need to use a Procedural Tank and set the type to 'Device Module' or use a tank that says it is 'Pressurized'.

Cheers!

I had the correct fuel for that particular engine. The tank was also set to the default non pressurised tank type because it was just a first stage.

The problem only goes away when I use that FASA umbillical tower and activate its pumps prior to launching.

I'm also having insane G-Force upon re-entry. But I managed to bring it down to around 8Gs for with a Periapsis of 60 to 80km. But I guess that's still too much.

Regards

[Autochton]

Hey. I'm having some problems with my RO/RP-0 install. Specifically, any and all chute parts are locked to a single (huge) size, right clicking them only gives a button to show chute info - none of which can be changed in any way. Launching a Tiny-Tim-based sounding rocket with a 1.5m chute is... impractical. So where do I start looking to fix this problem? I poked around in both RO and RP-0 configs, can't find anything that looks particularly out of place, but then, I don't really know what I'm looking for.

Running on Linux, installed all mods via CKAN, updated a couple mods since also via CKAN.

{
"kind": "metapackage",
"abstract": "A list of modules installed on the default KSP instance",
"name": "installed-default",
"license": "unknown",
"version": "2015.08.11.07.53.06",
"identifier": "installed-default",
"spec_version": "v1.6",
"depends": [
{
"name": "LayeredAnimations",
"version": "1.1"
},
{
"name": "RealismOverhaul",
"version": "v10.2.0"
},
{
"name": "B9AerospaceProceduralParts",
"version": "0.40"
},
{
"name": "SolverEngines",
"version": "v1.9"
},
{
"name": "ConnectedLivingSpace",
"version": "1.1.3.1"
},
{
"name": "DeadlyReentry",
"version": "v7.2.2"
},
{
"name": "FilterExtensions",
"version": "2.4.1"
},
{
"name": "KSP-AVC",
"version": "1.1.5.0"
},
{
"name": "MechJeb2",
"version": "2.5.3"
},
{
"name": "ProceduralFairings",
"version": "v3.15"
},
{
"name": "ProceduralFairings-ForEverything",
"version": "v0.0.3"
},
{
"name": "ProceduralParts",
"version": "v1.1.7"
},
{
"name": "RemoteTech",
"version": "v1.6.7"
},
{
"name": "SemiSaturatableRW",
"version": "1.10.1"
},
{
"name": "AdvancedJetEngine",
"version": "2.3.0"
},
{
"name": "TextureReplacer",
"version": "2.4.7"
},
{
"name": "Toolbar",
"version": "1.7.9"
},
{
"name": "Service-Compartments-6S",
"version": "1.3"
},
{
"name": "SXT",
"version": "21"
},
{
"name": "ALCOR",
"version": "0.9.4"
},
{
"name": "DMagicOrbitalScience",
"version": "1.0.7"
},
{
"name": "RealPlume",
"version": "1:v10.4.6"
},
{
"name": "RealSolarSystem",
"version": "v10.2.0"
},
{
"name": "NearFutureConstruction",
"version": "0.5.4"
},
{
"name": "NearFuturePropulsion",
"version": "0.5.3"
},
{
"name": "NearFutureSolar",
"version": "0.5.3"
},
{
"name": "NearFutureSpacecraft",
"version": "0.4.3"
},
{
"name": "PorkjetHabitats",
"version": "0.41"
},
{
"name": "RocketdyneF-1",
"version": "1.2"
},
{
"name": "SCANsat",
"version": "v14.1"
},
{
"name": "SovietEngines",
"version": "1.1"
},
{
"name": "AIESAerospace-Unofficial",
"version": "1.6.0"
},
{
"name": "UniversalStorage",
"version": "1.1.0.7"
},
{
"name": "VenStockRevamp",
"version": "v1.8.1"
},
{
"name": "TACLS-Config-RealismOverhaul",
"version": "v10.2.0"
},
{
"name": "RealHeat",
"version": "v1.1"
},
{
"name": "ContractConfigurator",
"version": "1.6.4"
},
{
"name": "ModularFlightIntegrator",
"version": "1.1.1"
},
{
"name": "BetterBuoyancy",
"version": "v1.4"
},
{
"name": "KIS",
"version": "1.2.1"
},
{
"name": "CrossFeedEnabler",
"version": "v3.3"
},
{
"name": "KerbalJointReinforcement",
"version": "v3.1.4"
},
{
"name": "ModuleRCSFX",
"version": "v4.1"
},
{
"name": "RealChute",
"version": "1.3.2.3"
},
{
"name": "KAS",
"version": "0.5.4"
},
{
"name": "RSSTextures4096",
"version": "v10.2"
},
{
"name": "FerramAerospaceResearch",
"version": "2:v0.15.4.1_Goldstein"
},
{
"name": "FASA",
"version": "5.36"
},
{
"name": "SmokeScreen",
"version": "2.6.7"
},
{
"name": "FirespitterCore",
"version": "v7.1.4"
},
{
"name": "TACLS",
"version": "v0.11.1.20"
},
{
"name": "ALCORIVAPatch",
"version": "0.9.4"
},
{
"name": "ASETProps",
"version": "1.3"
},
{
"name": "RasterPropMonitor-Core",
"version": "v0.21.2"
},
{
"name": "ReflectionPlugin",
"version": "1.2"
},
{
"name": "ModuleAnimateEmissive",
"version": "v1.9"
},
{
"name": "InterstellarFuelSwitch-Core",
"version": "1.15"
},
{
"name": "NearFutureProps",
"version": "0.4.3"
},
{
"name": "RealFuels",
"version": "rf-v10.5.1"
},
{
"name": "CommunityResourcePack",
"version": "0.4.4"
},
{
"name": "Kopernicus",
"version": "1:beta-02-4"
},
{
"name": "PreciseNode",
"version": "1.1.3"
},
{
"name": "AeroGUI",
"version": "v2"
},
{
"name": "DockingPortAlignmentIndicator",
"version": "6.2.0"
},
{
"name": "EditorExtensions",
"version": "2.12"
},
{
"name": "KerbalFlightData",
"version": "R19"
},
{
"name": "KerbalFlightIndicators",
"version": "R10pre"
},
{
"name": "VOID",
"version": "0.18.3a"
},
{
"name": "ToadicusTools",
"version": "15"
},
{
"name": "RP-0",
"version": "v0.35"
},
{
"name": "KerbalConstructionTime",
"version": "1.2.0"
},
{
"name": "KerbalConstructionTime-RP-0-Config",
"version": "v0.35"
},
{
"name": "KerbalRenamer",
"version": "0.4"
},
{
"name": "ModuleManager",
"version": "2.6.7"
},
{
"name": "CustomBarnKit",
"version": "1.1.1"
},
{
"name": "CommunityTechTree",
"version": "2.1"
},
{
"name": "TweakScale",
"version": "v2.2.1"
},
{
"name": "Trajectories",
"version": "v1.4.3"
}
]
}

[Devinci]

Hey. I'm having some problems with my RO/RP-0 install. Specifically, any and all chute parts are locked to a single (huge) size, right clicking them only gives a button to show chute info - none of which can be changed in any way. Launching a Tiny-Tim-based sounding rocket with a 1.5m chute is... impractical. So where do I start looking to fix this problem? I poked around in both RO and RP-0 configs, can't find anything that looks particularly out of place, but then, I don't really know what I'm looking for.

Running on Linux, installed all mods via CKAN, updated a couple mods since also via CKAN.

{
"kind": "metapackage",
"abstract": "A list of modules installed on the default KSP instance",
"name": "installed-default",
"license": "unknown",
"version": "2015.08.11.07.53.06",
"identifier": "installed-default",
"spec_version": "v1.6",
"depends": [
{
"name": "LayeredAnimations",
"version": "1.1"
},
{
"name": "RealismOverhaul",
"version": "v10.2.0"
},
{
"name": "B9AerospaceProceduralParts",
"version": "0.40"
},
{
"name": "SolverEngines",
"version": "v1.9"
},
{
"name": "ConnectedLivingSpace",
"version": "1.1.3.1"
},
{
"name": "DeadlyReentry",
"version": "v7.2.2"
},
{
"name": "FilterExtensions",
"version": "2.4.1"
},
{
"name": "KSP-AVC",
"version": "1.1.5.0"
},
{
"name": "MechJeb2",
"version": "2.5.3"
},
{
"name": "ProceduralFairings",
"version": "v3.15"
},
{
"name": "ProceduralFairings-ForEverything",
"version": "v0.0.3"
},
{
"name": "ProceduralParts",
"version": "v1.1.7"
},
{
"name": "RemoteTech",
"version": "v1.6.7"
},
{
"name": "SemiSaturatableRW",
"version": "1.10.1"
},
{
"name": "AdvancedJetEngine",
"version": "2.3.0"
},
{
"name": "TextureReplacer",
"version": "2.4.7"
},
{
"name": "Toolbar",
"version": "1.7.9"
},
{
"name": "Service-Compartments-6S",
"version": "1.3"
},
{
"name": "SXT",
"version": "21"
},
{
"name": "ALCOR",
"version": "0.9.4"
},
{
"name": "DMagicOrbitalScience",
"version": "1.0.7"
},
{
"name": "RealPlume",
"version": "1:v10.4.6"
},
{
"name": "RealSolarSystem",
"version": "v10.2.0"
},
{
"name": "NearFutureConstruction",
"version": "0.5.4"
},
{
"name": "NearFuturePropulsion",
"version": "0.5.3"
},
{
"name": "NearFutureSolar",
"version": "0.5.3"
},
{
"name": "NearFutureSpacecraft",
"version": "0.4.3"
},
{
"name": "PorkjetHabitats",
"version": "0.41"
},
{
"name": "RocketdyneF-1",
"version": "1.2"
},
{
"name": "SCANsat",
"version": "v14.1"
},
{
"name": "SovietEngines",
"version": "1.1"
},
{
"name": "AIESAerospace-Unofficial",
"version": "1.6.0"
},
{
"name": "UniversalStorage",
"version": "1.1.0.7"
},
{
"name": "VenStockRevamp",
"version": "v1.8.1"
},
{
"name": "TACLS-Config-RealismOverhaul",
"version": "v10.2.0"
},
{
"name": "RealHeat",
"version": "v1.1"
},
{
"name": "ContractConfigurator",
"version": "1.6.4"
},
{
"name": "ModularFlightIntegrator",
"version": "1.1.1"
},
{
"name": "BetterBuoyancy",
"version": "v1.4"
},
{
"name": "KIS",
"version": "1.2.1"
},
{
"name": "CrossFeedEnabler",
"version": "v3.3"
},
{
"name": "KerbalJointReinforcement",
"version": "v3.1.4"
},
{
"name": "ModuleRCSFX",
"version": "v4.1"
},
{
"name": "RealChute",
"version": "1.3.2.3"
},
{
"name": "KAS",
"version": "0.5.4"
},
{
"name": "RSSTextures4096",
"version": "v10.2"
},
{
"name": "FerramAerospaceResearch",
"version": "2:v0.15.4.1_Goldstein"
},
{
"name": "FASA",
"version": "5.36"
},
{
"name": "SmokeScreen",
"version": "2.6.7"
},
{
"name": "FirespitterCore",
"version": "v7.1.4"
},
{
"name": "TACLS",
"version": "v0.11.1.20"
},
{
"name": "ALCORIVAPatch",
"version": "0.9.4"
},
{
"name": "ASETProps",
"version": "1.3"
},
{
"name": "RasterPropMonitor-Core",
"version": "v0.21.2"
},
{
"name": "ReflectionPlugin",
"version": "1.2"
},
{
"name": "ModuleAnimateEmissive",
"version": "v1.9"
},
{
"name": "InterstellarFuelSwitch-Core",
"version": "1.15"
},
{
"name": "NearFutureProps",
"version": "0.4.3"
},
{
"name": "RealFuels",
"version": "rf-v10.5.1"
},
{
"name": "CommunityResourcePack",
"version": "0.4.4"
},
{
"name": "Kopernicus",
"version": "1:beta-02-4"
},
{
"name": "PreciseNode",
"version": "1.1.3"
},
{
"name": "AeroGUI",
"version": "v2"
},
{
"name": "DockingPortAlignmentIndicator",
"version": "6.2.0"
},
{
"name": "EditorExtensions",
"version": "2.12"
},
{
"name": "KerbalFlightData",
"version": "R19"
},
{
"name": "KerbalFlightIndicators",
"version": "R10pre"
},
{
"name": "VOID",
"version": "0.18.3a"
},
{
"name": "ToadicusTools",
"version": "15"
},
{
"name": "RP-0",
"version": "v0.35"
},
{
"name": "KerbalConstructionTime",
"version": "1.2.0"
},
{
"name": "KerbalConstructionTime-RP-0-Config",
"version": "v0.35"
},
{
"name": "KerbalRenamer",
"version": "0.4"
},
{
"name": "ModuleManager",
"version": "2.6.7"
},
{
"name": "CustomBarnKit",
"version": "1.1.1"
},
{
"name": "CommunityTechTree",
"version": "2.1"
},
{
"name": "TweakScale",
"version": "v2.2.1"
},
{
"name": "Trajectories",
"version": "v1.4.3"
}
]
}

You have to go to the Action Groups' page and click on the parachute, then on previous or next size.

[Autochton]

Ah! That was the one place I didn't look for it. It's a little unintuitive as a user experience, I'll say, but eh, as long as I can send up glorified fireworks, I'm happy.

Thanks, Devinci.

[Devinci]

Ah! That was the one place I didn't look for it. It's a little unintuitive as a user experience, I'll say, but eh, as long as I can send up glorified fireworks, I'm happy.

Thanks, Devinci.

You're welcome. I still wonder why they didn't put it on the right click menu? And tweakscale doesn't work with it too, sadly.

Edited August 11, 2015 by Devinci

[Autochton]

I rescaled my chute, and gleefully launched my rocket... Only to end up with FAR refusing to voxelize my nosecone correctly, realized when my slick, smooth rocket tumbled like it had a string attaching it to the ground. Debug voxels showed a rectangle of voxels off to one side of the nosecone (procedural nosecone, 0.313m diameter, peaked #1 shape - different shapes cause different errors). Where do I go to get help for that? Ferram has said he wants no truck with CKAN, after all.

[JeffersonFlight]

I'm sorry if this has been answered before, I have googled with no success. I apologize in advance if this has been asked. I'm having an issue with realism overhaul breaking the placement nodes of the Saturn V parts from the FASA pack. The heat shield appears inside the Command Pod and none of the nodes are correct.

*EDIT* Picture include to show an example of the problem occurring. http://i.imgur.com/oyMCin7.jpg

Edited August 11, 2015 by JeffersonFlight

[Yaivenov]

You're welcome. I still wonder why they didn't put it on the right click menu? And tweakscale doesn't work with it to sadly.

It lets you spin your rocket around and click madly trying to get at those little parts without worry of ripping off a stage or five.

- - - Updated - - -

I'm sorry if this has been answered before, I have googled with no success. I apologize in advance if this has been asked. I'm having an issue with realism overhaul breaking the placement nodes of the Saturn V parts from the FASA pack. The heat shield appears inside the Command Pod and none of the nodes are correct.

*EDIT* Picture include to show an example of the problem occurring. http://i.imgur.com/oyMCin7.jpg

I had a bug similar to that with the KW Rocketry parts. The "community fix" that CKAN forced fed along with KWR turned out to be the culprit and was messing with RO's changes to the parts.

[Laie]

Does anyone know what "Insufficient resources to ignite means"? My engine is not starting at all from the pad.

It's quite straightforward, really: you need something to ignite an engine. Electricity for a spark plug or special chemicals (later engines carry something called TEATEB and use a little at every ignition).

The engine that won't ignite, would that perchance be the LR89 (Atlas Booster)? Because that engine won't ignite for me no matter what and I don't have the FASA umbilical tower to work around it. According to the config, it just requires some fuel/oxidizer/electricity to ignite, but it won't work for me. I've eventually resorted to using the bigger LR79 engine.

[Devinci]

It's quite straightforward, really: you need something to ignite an engine. Electricity for a spark plug or special chemicals (later engines carry something called TEATEB and use a little at every ignition).

The engine that won't ignite, would that perchance be the LR89 (Atlas Booster)? Because that engine won't ignite for me no matter what and I don't have the FASA umbilical tower to work around it. According to the config, it just requires some fuel/oxidizer/electricity to ignite, but it won't work for me. I've eventually resorted to using the bigger LR79 engine.

LR89 worked for me.

I wish it would say which resources are insufficient. Even though my rocket had all of those resources aplenty it still only worked with the FASA towers. I also tried different fuel with the same result.

[Boris33fr]

I have installed ATM also, but my game keep crashing, even after deleting the file you told me to. :(

Still crash when i'm loading a scene.

My output log

https://www.dropbox.com/s/gjtwkgrd6qalx6r/output_log.txt?dl=0

Thanks :'( ^^

Nobody have same crashes as i do have ?

[gruneisen]

LR89 worked for me.

I wish it would say which resources are insufficient. Even though my rocket had all of those resources aplenty it still only worked with the FASA towers. I also tried different fuel with the same result.

Which engine are you specifically trying to ignite? Please upload your craft file so we can see if the problem is specific to your install or occurs across all platforms.

Looking at the LR89, I went through the blame on Github for the FASA files, and it looks as though the ignitor resources were all touched to update ModuleEngineIgnitor configs...

https://github.com/KSP-RO/RealismOverhaul/commit/aa319d9bf31e4accdb5214bd7ed8323d82b92925?diff=split

https://github.com/KSP-RO/RealismOverhaul/issues/367

I wonder if this update is causing some problems for folks...

[Laie]

For the LR89, I've opened an issue with RealFuels: https://github.com/NathanKell/ModularFuelSystem/issues/101

As far as ignition stuff is concerned, it's config is identical to the LR-105 which works fine for me. But the LR-89? Not at all.

No craft file, because it won't work for me even with a bare-bones vessel: engine, tank, command module -> ignition failure because resources. And yes, I have the right fuel.

Edited August 11, 2015 by Laie

[gruneisen]

For the LR89, I've opened an issue with RealFuels: https://github.com/NathanKell/ModularFuelSystem/issues/101

As far as ignition stuff is concerned, it's config is identical to the LR-105 which works fine for me. But the LR-89? Not at all.

No craft file, because it won't work for me even with a bare-bones vessel: engine, tank, command module -> ignition failure because resources. And yes, I have the right fuel.

Madness - I'll have to see if I can replicate this when I get home tonight!

[Yaivenov]

Should I just assume that none of the ideas I posts are particularly interesting then?

[gruneisen]

For the LR89, I've opened an issue with RealFuels: https://github.com/NathanKell/ModularFuelSystem/issues/101

As far as ignition stuff is concerned, it's config is identical to the LR-105 which works fine for me. But the LR-89? Not at all.

No craft file, because it won't work for me even with a bare-bones vessel: engine, tank, command module -> ignition failure because resources. And yes, I have the right fuel.

Madness - I'll have to see if I can replicate this when I get home tonight!

So last night I was able to reproduce the failure of the LR89 engine...to an extent. Basically, if I hook up a procedural tank to the LR89 with all of the required resources, it does not ignite. I don't get quite the same error in that there are no reports of incorrect or insufficient resources, but the throttle goes to '0' even though the engine says everything is stable and nominal.

I then wanted to see if the stock FASA Atlas Mercury craft which uses these engines would work and they did! I was able to light all of the engines, the LR89s and the LR-105, and fly successfully. Of course, when I went to stage off the LR89s and the Booster Decoupler, the LR-105 died as well, which is certainly strange and may be related!

So I then built my own Atlas Mercury craft, drained and filled all fuel tanks, and got the same result - everything worked except for the LR-105 dieing on staging! This makes me think there is something that the FASA SLV-3A tank is providing that all other tanks are not. So, I took the LR89s attached to the Boost Decoupler w/ the LR-105 and instead of the SLV-3A tank, just placed and filled a procedural tank on top w/ a probe core and tried to light engines........and nothing worked.

I went back to the VAB and took off the Procedural Tank and replaced with the SLV-3A and a probe core, drained and refilled, the tank, launched, lit the engines, and it all worked!

So, it appears as though there is something in the SLV-3A tanks that makes the LR89s happy...I looked through their config files and I didn't see anything out of order, but this may warrant further investigation.

Just wanted to share my results! Cheers!

[Laie]

So last night I was able to reproduce the failure of the LR89 engine...to an extent.

This is curioser and curioser.

Of course, when I went to stage off the LR89s and the Booster Decoupler, the LR-105 died as well, which is certainly strange and may be related!

I'm not familiar with the FASA pack. Have there been command modules on the boosters? Staging those momentarily shuts down the engines. Barely noticeable in the stock game, but with real fuels, you need an ignition to keep them going. Don't have one? Too bad.

[JeffersonFlight]

It lets you spin your rocket around and click madly trying to get at those little parts without worry of ripping off a stage or five.

- - - Updated - - -

I had a bug similar to that with the KW Rocketry parts. The "community fix" that CKAN forced fed along with KWR turned out to be the culprit and was messing with RO's changes to the parts.

Sorry for the late response. Thank you for your reply and attempt to provide a solution, I tried looking for packs that might be interfering or any obvious problems but was unable to find any. The problem still persist.

[TKFT_ExTr3m3]

I noticed the mk16 parachute does not work when I install this pack. There is no stage part for the chute when it is placed on a rocket.

[TinyPirate]

Hi guys, I feature the Realism Overhaul and Real Solar System mods in my recent 2 Minute Mods video. Hope you enjoy!

[gruneisen]

I noticed the mk16 parachute does not work when I install this pack. There is no stage part for the chute when it is placed on a rocket.

Do you have this problem with any of the other SQUAD parachutes? There is nothing in the MK16 RO config file which would make it unique.

[Einkleinermensch]

Hi, guys. I'm playing RO on Ubuntu 14.04 with it's compatible mods (all of them are installed via CKAN), here is the list:

http://pastebin.com/ZbBdnGLX

Today I've got very strange bug - AIES satellite buses in my crafts exploding on launchpad due to overheating. If I launch only single bus from VAB, it explodes without any logs and points camera in, uhmmm, sort of hyperspace without sun and planets.

I've tried to make a clean install, but this problem still existing.

Here's my player.log:

https://drive.google.com/file/d/0Bz1hgIQ7T02fa2hibTF1dDFndlU/view?usp=sharing

[gruneisen]

Hi, guys. I'm playing RO on Ubuntu 14.04 with it's compatible mods (all of them are installed via CKAN), here is the list:

http://pastebin.com/ZbBdnGLX

Today I've got very strange bug - AIES satellite buses in my crafts exploding on launchpad due to overheating. If I launch only single bus from VAB, it explodes without any logs and points camera in, uhmmm, sort of hyperspace without sun and planets.

I've tried to make a clean install, but this problem still existing.

Here's my player.log:

https://drive.google.com/file/d/0Bz1hgIQ7T02fa2hibTF1dDFndlU/view?usp=sharing

That is certainly a little wild - I too use Ubuntu 14.04 to run KSP with RO / RSS and I've never encountered the problem you describe. I'll check your mod list and revisions versus mine tonight to see if there're any differences, but this is certainly a strange one.

[chrisl]

Is kerbal experience earning hard coded or something that modders can tweek? Once you start playing RO/RSS, you pretty much cap your kerbals at the experience they can gain by landing on the Moon. I guess you could also maybe get experience for landing a kerbal on Mars but that's going to take quite a bit of effort, especially if you're also using RP-0. It would be really nice if kerbals could earn experience multiple times for the same activity. I.E., if you have Jeb land on the Moon 5 times, he gets more experience then if Valentina only lands once.

[schoff123]

Just a heads up, the FASA and KW RO configs move most of the nodes around, making some pretty odd stuff happen when building crafts with those parts. I didn't know if you were aware