sentania

works for me; thanks.

Question for the users of this mod. I've used sigma dimensions to rescale and make kerbin, etc pretty close to stock size. Kerbin orbits the Sun at just under 1 AU and I further modify the sun, such that it has similar mass and radius to our sun: The issue I'm facing is that the sun seems just plain small, I'm not sure if a mod like scatterer, SVE, SVT could be horking things up, or if that's just how small the sun is when viewed from earth Any thoughts?

Probably want to double check the cost of the fuel tanks as I forget if it's cost or mass. One of them the cfg configures the wet value of, the other it configures the dry value, or maybe both are the same. If you add stock balance, please make sure to leave the RSS values as a patch!

I think nightingale released a full 1.2 case release last night

ANy ideas on why I'm not seeing Keepfit in the applauncher?

I have done some further digging, and like the UI flickering issue, I've seen in game and referenced in the forums, this appears to be something related to the stock game, but triggered by mods, most likely volume of parts. Scenario: 1.2 with the following mods installed, all mods are up to date relative to themselves. *If* I load the game (1.2 x64), with said mod list, but with the KSP 1.1.3 compatible release of the @Nertea suite, things function as expected. *If* I load the game (1.2 x64), with said mod list, but without the 1.2 compatible release of the Nertea suite, things function as expected. *If* load the game (1.2 x64), with *only* the 1.2 compatible release of the Nertea suite, and it’s requirements, things function as expected. *If* load the game (1.2 x64), with all mods listed above, but with the 1.2 compatible release of the Nertea suite, things do not function as expected. I observe the following issues: When you load a game, all active, offered, and your completed contract history reset. When you enter the VAB, all active, offered, and your completed contract history reset. This is the error message logged when the contract history is reset: We’d have to see what nertea changed in this release, but having parsed his files, I’m guessing a lot more tags or some such – resulting in an overload of something somewhere. The bug tracker appears down at the moment otherwise this would be in there. Edit: Figures that now I go and throw all the mods back together, fire things up and it's behaving normally. SMH. I'll play around with it some more if no one else sees anything related to this, or if it crops up some more. Edit 2: There it is again. It's definitely a function of how many parts are displayed in the VAB. Toppled tech tree = sorry. Fresh, super low tech game, no issues.

Posted too soon - please check back.

I just encountered this today with 1.2, and have started to diagnose it. In a totally stock game it's fine, but adding in my mods breaks it - the weird thing is that it was working fine this morning, and all of a sudden it broke on me. I can go into the admin building, or the cheat menu and accept a contract, but when I enter the VAB or load a new game - poof. Gone. I have not checked all of the buildings.

Not that I know of

Got it on the time. why change the speed of light though? If you rescale by 10.618 to get "real size" kerbin , etc why do you need to change it? I'm just trying to understand why you change is for sigma dimensions but not RSS Got it on the time. why change the speed of light though? If you rescale by 10.618 to get "real size" kerbin , etc why do you need to change it? I'm just trying to understand why you change is for sigma dimensions but not RSS

For compatibility with sigma dimensions what are you doing for seconds in the day and the speed of light? And why?

This appears to be the result of: { useOnDemand = true }

WHat isn't working?

I don't know where it is, i just dropped KSPRC in, so I don't have a handle on it's function yet, however you likely have one or more errors in your CFG files, as it causes errors with sigma binary. If I remove KSPRC (but leave the it's dependencies), the error goes away.

What are you using to evaluate the physics of it?