halrick

Hi! I'm wonder if I'm the only one who is seeing mods being updated in Kerbalstuff (and having a CKAN "tag") but these updated versions not being available in CKAN itself; i.e. Editor Extension 2.3 in CKAN, while Kerbalstuff has v2.6 as current, or Mechjeb2 Dev release v2.5.0.0-345 being available in on the external site, but only v2.4.2.0-435 being available via CKAN. I absolutely LOVE using CKAN, but these issues force me to download the mods externally, which is something I'd rather not do, but am forced to, given that the versions listed in CKAN aren't compatible with KSP v1.0. Any reply would be greatly appreciated!

Thank you! It seems that this solved the issue.

I hope someone can help me. The problem I'm having is that the settings.cfg file isn't being followed. After getting this bug with only editor extensions installed, I figured I'd go back to basics with a fresh Install, I checked the camera sensitivity inside the vab & on the launchpad; in both cases normal. With no changes to settings made, I launched ksp again, only to be blasted by the music at 1000% (that's what it said in the options menu). After reducing ALL audio settings back to the previous value (all values were at 1/100th of the faulty value, so I set the music volume back to 10%), I entered the VAB and did a sensitivity test with the camera. I'll just say it wasn't anywhere near stock. What would have been a 10° change in perspective, became almost a 360° change (checked mouse hardware sensitivity, to ensure that that's not the cause). Same glitch with the camera on the launch pad. In essence, it's like this: fresh install 1st launch of ksp; all is normal 2nd launch of ksp; volume beyond funny and camera sensitivity nowhere near acceptable I figured that perhaps ksp somehow changes the settings file upon closing ksp. So I did another fresh install, launched ksp, checked settings, did resolution change, pressed both accept and apply, and then, without closing ksp, set the settings.cfg file to "read-only". Despite this drastic measure, KSP still boosts the volume to extremes and the camera sensitivity problem still persists. Values of the influenced settings (at least as far as I can tell) as they are in the config file: VAB_CAMERA_ORBIT_SENS = 0.04 VAB_CAMERA_ZOOM_SENS = 0.1 FLT_CAMERA_ORBIT_SENS = 0.04 FLT_CAMERA_ZOOM_SENS = 0.5 SHIP_VOLUME = 0.40 AMBIENCE_VOLUME = 0.30 MUSIC_VOLUME = 0.10 UI_VOLUME = 0.30 VOICE_VOLUME = 0.20 Any help is greatly appreciated. Final Update: Problem solved thanks to vexx32

I know for a fact that MechJeb has this feature ("current Biome" & "Raw Biome"). If you just want that Info, just create a custom windom with those data points and don't use mechjeb otherwise (as tempting as it may be, for some).

While I do use MechJeb automation extensively, I make it a point to execute a mission every now and then completely by hand (containing pretty much everything from launching, inclination changes, transfers to other planets, docking, landing and finally returning home) just to make sure that if I didn't have MJ, I still could do everything I use MJ for (being covenience over doing repetitive things ad nauseum [and more precisely]). The most "important" thing I use MJ for, even for manual mission, is Staging dV info and t/w ratios while constructing.

You have my thanks for this great mod. While there have been hickups (2.4 completly broke my install -> reinstall, but even then, with the previously working 1.1, ksp just wouldn't load), 2.6 is most definitely a step in the right direction, as ksp now requires even less ram than with 1.1 . Best wishes for the new year to you (and this great mod)!

Had the auto-staging in ascent ap on, found out that said autostaging was only active DURING ascent. Just also activate auto-staging in the utilities tab to get autostaging no matter the circumstance.

Raise apoapsis to desired level -> cut engines -> just before reaching ap, fire engines toward prograde to bring pe up to desired level. You'll, ideally, want to burn 50% of the circularization burn before reaching ap and 50% after; i.e. for a 20 sec burn, don't wait to reach t-0 at maneuver node but rather start burning at t-10. To get a better feeling for all things orbital maneuvers, burn pro- and retrograde at both ap and pe and see how they influence the orbit (when a stable orbit is reached)