StoryMusgrave

Well, now I'm really confused. Redid my install, just KSP, RH, MFI, and MM and I have no issues really. What I have noticed is that warping really messes with temperature. At 100x temps will climb to 350/375K. Now kinda toggle back and forth between say 50x and 1000x quickly and those 350+ temps magically drop to the 315K range. The rad flux figure is still 20+, fwiw. I also noticed another little bit. The physics.cfg that comes with a fresh install of KSP 1.04 is different than one generated by KSP under stock conditions if the original physics.cfg is deleted. What differences that makes, no clue. I'm at a loss. All I can say is BRING ON 1.05. EDIT: WHOA...so using the auto generated physics.cfg causes exactly what is happening (skyrocking temps). Using the physics.cfg that comes with a fresh install temps stay nice and cool.

Well...this is odd. Same test as before. Now my temps (both skin and 'regular') barely crack above 300K. Difference. The new RealFuels that was JUST released. (v10.7). The test was done using the Mk1 Cockpit which DOES have a "ModuleFuelTanks" of RealFuels in the RO config... Is it possible both you NathanKell and Starwaster were using this new version of RealFuels??? While some others were using the 'old' version.

I'd hope it's a 1.04 bug too. Still very strange indeed that clean installs for some are having issues, while others are not. I know some devs from time to time have had 'new' yet to be released stuff in files that have created troubleshooting nightmares because their new stuff has fixed the errors seen by others. Not saying this is the case this time, but still strange strange strange.

Whoops, missed a big word there. They are *NOT* exploding. So while temps are higher than what they realistically should be, it doesn't prevent me from playing.

Ok, that sounds like a good plan. RO has a HM7-B with something else I think, so if a person wants ECA should still be doable.

For what it is...You have the ECA version done, and while it may not 'look' pretty, can we still get it too? It's nice to have options IMO. I have no problem waiting a bit for complete release when we get the additional ME version too. Especially since we aren't going to see the Ariane 5 ME in real life since it was cancelled from everything I can tell.

Mark7: Configs for KK rockets are already included in RO, if not the current release they are in github and will be included in the next release of RO.

I'm just saying that those issues described by kpstjeev and others are identical to those experience by myself when following their duplication steps. Grabbing the latest version of everything as provided by either github or when not available there kerbalstuff. I'm not really going to worry about it at this point because 1. My ships are *NOT* exploding. 2. I know that 1.05 and/or 1.1 are going to provide vastly better thermal simulation than what 1.04 does. Not to mention you Nathan apparently leading that charge:) It is interesting that those steps done by another *are not* producing the same effects. There has got to be something different in the versions of RealHeat or MFI used by each party because something doesn't jive. I'm also going to agree that the physics.cfg provided by starwaster and that same file provided by kpstjeev is identical absolutely no question to it. In fact the physics.cfg of starwaster is identical to both that in the 'clear_reheat' folder AND in the 'modded' folder.

Cajun: You've uploaded the logs that help the least. Please upload "output_log.txt" found in KSP_Data folder of KSP.

Well....I made a fresh install of KSP. Win 7 64bit. Running 32-bit KSP. RSS + RO (Dependencies with Deadly Reentry). I'm getting skin temps in the 500-550K range and temps <300K.

If a guy wants to edit his own files, to each his own. Sure the LR-91 could have been designed to be reignited. It wasn't, so that's why it is the way it is in RO. Just to answer your question as to why it only had 1 ignition in the config to begin with. It's the premise that was presented that hypergolics should have many/unlimited restarts.

Yeah DIV will come after the Falcon stuff with KK. As for Saturn. While FASA does have Saturn-ish stuff, they aren't real scale. RO does a decent job of making them so. Both DennyTX and DECQ have made Saturn Vs as well. Each far more real scale than what FASA original ever was. Haven't seen DennyTX around recently, and DECQ is slowly rebuilding his SaturnV, but has yet to release anything.

Just because an engine is hypergolic doesn't mean it should have multiple restarts. In the case of the LR-91 as used by the Titan series was only fired once, regardless of RP1/LOX or hypergolic.

I love the caption to the picture of that article...

I would agree. Start with 1.0, we've been without a good 1.0 for a while now. Then make the steps to 1.1 and 1.2/FT.

KK is already included with RO, and since this is a brand new release, it'll be a bit until they release a new version of RO with the new KK stuff in it.

I concur with Cheesecake. That is one error. There are a few other issues I see. 1. Model load error in 'C:\Kerbal Space Program\GameData\Launchers Pack\Rockets\Minotaur V\Star48BV.mu File error: Failed to read past end of stream. at System.IO.BinaryReader.ReadByte () [0x00000] in <filename unknown>:0 at System.IO.BinaryReader.Read7BitEncodedInt () [0x00000] in <filename unknown>:0 at System.IO.BinaryReader.ReadString () [0x00000] in <filename unknown>:0 at A..ReadMaterial (System.IO.BinaryReader br) [0x00000] in <filename unknown>:0 at A..ReadChild (System.IO.BinaryReader br, UnityEngine.Transform parent) [0x00000] in <filename unknown>:0 at A.. (.UrlFile ) [0x00000] in <filename unknown>:0 2. In the following - GEM-46_air.cfg, GEM-46_ground.cfg, Castor4A.cfg all have a sound file being called that is not present. sound_GEM60_engage = engage Should either include the sound file, or remove that line from those 3 part configurations. 3. Part "KK_DII_LR101" has a bad node attachment Presently "node_attach = 0.0, 0.0, 0.0, 0.0, 1.0". Should be: "node_attach = 0.0, 0.0, 0.0, 0.0, 1.0, 0.0, 0" 4. Texture load error in 'C:\Kerbal Space Program\GameData\Launchers Pack\Rockets\SpaceX\m1c\model004.dds'. Not sure what needs to happen there, but probably minor. 5. I'd also recommend removing ModuleEngineIgnitor from your configurations because it's not up to date and RealFuels has taken over it's functionality. 6. Some more texture errors: [LOG 12:53:00.145] Load(Model): ATK_Propulsion_Pack/GEM40SRM/GEM40 [ERR 12:53:00.155] Texture 'ATK_Propulsion_Pack/GEM40SRM/GEM40_model001_NRM' not found! [LOG 12:53:00.157] Load(Model): ATK_Propulsion_Pack/GEM40SRM/GEM40AL [ERR 12:53:00.173] Texture 'ATK_Propulsion_Pack/GEM40SRM/GEM40_model001_NRM' not found! ... [LOG 12:53:07.169] Load(Model): Launchers Pack/Rockets/Delta/D3DCSS_LH2tank [ERR 12:53:07.379] Texture 'Launchers Pack/Rockets/Delta/d3dcss_tex2_NRM' not found!

I see a KerbalStuff update:)

Alright, just found this. Looking forward to giving it a try!

Agreed. Wait

You be better off talking to the procedural fairings people. RO doesn't really have anything to do with it.

Oh getting excited more and more. Kk and liquid both with releases imminent....insert George takei 'oh my' here.

Yukon0009: Without a log, anything is pure conjecture.

Bring this up in the RealFuels thread. They are the ones responsible for boil off.

@ebigunso: So seems like ullage is working correctly. Am I right? Because before it seemed it didn't work at all for you. Never moving into any sort of stable state. Now it is.