Kalista

I keep running into an issue with this mod with version 1.6.2 where on game load it constantly hangs on loading the rapier engine and refuses to go any further. Removing AJE solves the problem and the game loads fine ( 1.6.1 also will load fine ). Output Log

Negative both tests I did had the debugger off and last time I used trim was before the change to sas ( god did I HATE asas).I'll also do a test with logs and vid on the difference with 5.2 and 5.3.1 will take me about an hour with how slow time warner uploads to youtube. Edit: After doing the 5.3.1 test you may have been right with me bumping a trim button since it settled correctly so the only persistant issue I'm seeing is that parts are melting off when they should be shielded.

That might be why I lost all of my US stuff on my very first sucessful test ( tho my cute thats hiding behind a clampotron jr was spared while the US stuff is below the DP,cute and Pod.)

Taking DRE off makes the craft go shield first entire way down where as with the new DRE ( 5.2 didn't behave this way) has it wanting to go docking port first till below 30km. Craft File This is how the testing I did went dropping the ship from 70km @ pitch 60 heading 270 No Dre: craft begins to go retrograde near the 65km mark and except for some bobbing holds that point entire way down building up a slight rotation ( which is by design) DRE 5.2: Exactly the same as no DRE. DRE 5.3 w/Fixes: Craft begins to go prograde right around the 62km marker requiring control input and sas to hold retrograde.Just under 30km craft will hold retrograde on its own but will start developing a hard rotation on its own. All these tests were done with FAR because I refuse to fly with squads default soup atmosphere.

Would that also be why my craft wants to flip on its head till about 28-25km then it settles and wants to go shield first? Doesn't bother me it wants to do that since SAS corrects it with little trouble but was a behavior this ship didn't have in 5.2.

Yup always do a clean install when I update a mod so the CFG is the one that comes with the download

Works now lost both of my US fuel cells and one monotank ( lost other on way down) and burnt thru my entire shield on reentry using same test that I posted before.

Knew I forgot somethin try it now.

I just tried Nathan's fixed version + starwasters CFG edit and can confirm the heat isn't building up at all. Ran a test with DREs debugger up and heres the log and video ( when its up anyways) https://drive.google.com/file/d/0BwYzqg0314S0QTZqUlEyTXZscDA/view?usp=sharing Video One thing to note only diff between this test and my last 3 is the craft needed SAS on the way down since it now wanted to flip nose first ( when its designed to be aerodynamicly stable going HS first).

No change same altitude for temp plateau still never saw the reg temp break freezing till 1200m. https://drive.google.com/file/d/0BwYzqg0314S0XzFoYmNEeTdpdGc/view?usp=sharing edit: Encoding the video of my test and will post a link here soon as I got it up on youtube. This is also the order of events that I did to my game from yesterday to today ( yesterday other than out of memory errors on long sessions worked like it should). Updated Real Fuels and DRE also changed MM file from 2.4.4 to the 2.4.5 one included with DRE now DRE is going nuts which leads me to believe its either a bug with the new version of DRE or MM. video http://youtu.be/Z-rSG_NnsIM

Watching the fraps video I made of that run ( FYI cooking and attempting to fly a rocket at the same time doesn't work out very well) the only times the temps went over freezing was Ambient spiked at 2c @38km then ran quickly down to -58c and didn't break 0 again till 2200 when it jumped up to the normal 19c. Reg temp didn't break freezing till 1200m.

Been having the exact same error heat shield doesn't really break the freezing mark till its floating down to the ground. Not using RSS on my end and alot of these mods I have that are now throwing errors weren't in the previous version. https://drive.google.com/file/d/0BwYzqg0314S0UDVudFBlOXlzT0U/edit?usp=sharing

Hey Chris is it intentional that the RC chute parts have 0 cost to them and all there costs comes from chute size and materials used? Because right out of the gate it makes them far more cost effective than a MM modded stock chute that charges you for the part+size/materials for it ( not much of a cost but still a clear cost).

Heres an idea to magico. Have a means of selling outdated parts from your inventory to get some funds back from it ( even at 25-50% rate anything would be nice). Take for example I have a ton of the 1 man pods laying around and I'm now far enough into the tech tree the odds of me using any are almost nil. Would be nice to get a small amount of money back for those since I won't be using them ( and my OCD won't drive me bananas seeing 50+ parts I won't ever use).

Well if you need another bug checker to make sure flight school and .24 are bug free for the main release I'm willing to beta test it.

https://drive.google.com/file/d/0BwYzqg0314S0RnRDaEJtbDRpNGM/edit?usp=sharing Craft file there. Nope single probe core with a few science experiments I sent on a flyby of the Mun for cheap points fairly early on in my save.

Found my issue. Seems Nova Punch's probe core is no longer got the spu in the MM configs by default.

Flight computer itself showed that it had a delay attached to it. Tomorrow I can do a quick video of it if it flips out again since that might help more than a SS.

It's set to true by default on mine. It's just weird that the FC reads that I want a 8 hr delay and doesn't que it at all just fires it soon as I touch an action group.

I'm having an issue where putting in a time delay then hitting an action group ( say very early career mode flying probes on a flyby that return to Kerbin and having it perform science at the periapsis of the Mun) refuses to work. It will fire the action group the moment I touch it even tho the flight computer registers that I have it set to an 8 hr delay.

I'd still like to see hiring Kerbals come with a time like ships and tech since hiring a handful of them and sending them out on a mission that day is alittle immersion breaking ( and because the only mod that comes close to doing that is keepfit and its more about keeping kerbals in shape after their hired to go on missions and not the simulated training to become kerbalnauts when hired).

adjustCollider = -0.015 just that part or the entire module entry? I'll try either and see what happens. edit: Just removed that one line was getting a shockwave reading up until I armed the chute @ 18km after that until it opened @5km it was reading as shielded.

Just had another odd incident of a part being shielded when it realisticly shouldn't have been. First flight in a new career mode saw my rocket go nose first with the leading part being a real chute 1.25 cone parachute that hit the atmosphere at 2km/s. Checked the DRE debug menu and it was showing the part is shielded. Might be intentional for this part to do this so that early rockets dont melt down on the first launch but wanted to report it incase it wasn't. screenshot http://cloud-4.steampowered.com/ugc/559882784511444350/86ABF3CAF6C233A3145CB54045010A961AC23853/ output log https://drive.google.com/file/d/0BwYzqg0314S0S0Zqbm41aExmdDg/edit?usp=sharing No video since I wasn't actively testing anything and not seeing the overheat indicator not poping up took me by surprize.

Just had an interesting bug hit me. Was testing another mod ( trying to get friends back into playing mission control again) when on a fresh sandbox save turning off KCT caused the game to flip out. No buildings were clickible backing out of the space center scene to the main menu failed and ended up alt f4ing to start over. output log https://drive.google.com/file/d/0BwYzqg0314S0TlR1NU04bXlBemc/edit?usp=sharing order of events I did ( since fraps wasn't running). Started game > went to current career like a dummy> backed out to main menu made a new save for sandbox> turned off KCT then the problems hit> alt F4ed game.

Did you see that VV just got updated to 0.5? Might be stuff in the update that you want that wasn't in 0.4 ( which was the current one when I asked about support).