Iam aspaceman

PC Win 10 pro Steam 64bit I went into the settings.cfg file and the F1 and F2 keys are shown as correct there. Where else could I look for changes?

I can't take screenshots or hide the UI using F1/F2...every other function key works as always. Was curious if this was a change / bug / or something else entirely? Thanks

I did get this error from CKAN when I was trying to update it and I do remember going into the Game Data folder and manually deleting the IFS folder and reinstalling it through CKAN: Oh no! It looks like you're trying to install a mod which is already installed, or which conflicts with another mod which is already installed. As a safety feature, the CKAN will *never* overwrite or alter a file that it did not install itself. If you wish to install InterstellarFuelSwitch-Core 2.0.6 via the CKAN, then please manually uninstall the mod which owns: GameData/InterstellarFuelSwitch/Plugins/MiniAVC.xml and try again. Your GameData has been returned to its original state. Error! then the problems started. Might I have erased something to another mod or game folder communication that could have caused this problem?

Well - I am at work atm so I can't get a screenshot, but I will as soon as I get home. However, the ONLY thing that changed was IFS update when this started. I had actually loaded the save and as I was going to the VAB to work on my latest miracle of space faring technology, decided to go ahead and exit to perform the update. So...everything was fine immediately before the update...and not immediately afterward. I am not saying it is IFS specifically but possibly having to do with the CKAN update? Also - it might not be a save corruption it might just be looking for information that is no longer there and won't do anything till it finds it (that occurred with another mod a few months ago - but I was able to unload / reload it and fix the problem). I can pan and rotate the view of the KSP complex, just not enter into any of the buildings or exit the program (normally). However, I know as much about computer programming as I do about being an astronaut...;-) I know the module listed was an IFS fuel tank module...I'll send the screenshot in a bit. Thanks!

Anybody install the latest update and it breaks an existing career game? CKAN told me that there was an update - so I installed it. When I started my existing career game it told me 2 of my ships were unloaded due to a missing fuel tank and wouldn't let me do anything. I could only enter the R&D area and I couldn't exit again. It wouldn't let me exit the game either - I had to do that from windows. So I uninstalled IFS and the core and the same thing happened. I reinstalled IFS and the same thing happened - each time telling me two of my vessels couldn't be loaded. Any ideas as to how to salvage my career game?

So you break the burn up into a few orbits? Burn for a bit at the correct trajectory angle, stop the burn then complete an orbit and start to burn again, wash rinse repeat until you have completed the burn? Hmmm, I will have to play with this. After I added the structural supports on the sides, the craft was actually pretty rigid...no noodling to speak of, so the actual burns went pretty smoothly after I turned off MJ. I was curious how good they would work since they were attached using decouplers so I could eject them before separating everything (lander from return ship, etc.) - apparently it didn't affect anything adversely. On a general note, I had Hyperedit installed, but never used it for the mission. I DID however use it a lot to test the parts and pieces this past weekend before attempting the entire mission Monday evening. Oddly, the mining portion was the only thing I didn't test using Jeb and was surprised how long it took to fill the tanks. I used the same strategy on Duna with an engineer and it only took a week or so to fill up larger tanks. Obviously I might have landed in a rich area on Duna and a sparse one on Eve...I hadn't scanned the planet in this save to know the ore density...I just crossed my fingers and started mining. Also I noticed I have the habit of moving my KER window down and out of the way quite a bit while performing maneuvers, etc. If I need to post shots of any of the vessel information, I can break it out into the various parts for anyone's viewing pleasure. TBH, I might try it again with a 2 kerbal lander just to see what that does to the lander requirements.

Trying to get in under the 1.1 wire... So after stranding various pilots on Eve early in my KSP career, I started a career around Christmas with the sole purpose of heading to Eve, setting up a permanent orbital science station, landing on the surface and returning the pilot back to Kerbin (presumably w/ lots of science goodies) using life support mods (Roverdude's) and NF space station parts (just for the cool factor). After spending an embarrassing amount of time sorting out how to land w/o burning up, taking off w/o burning up and having the Delta V to make it into orbit I was ready to go (thank goodness for Hyperedit once I discovered it)...however 1.05 wasn't and my master creations crashed the computer more times than I can count. I had (with satellites, a mining base, and a Duna orbital station) 17 flights up at any given time and coupled with my behemoth Eve mission it just couldn't take it. So I moved on to other things waiting for 1.1...then I saw this challenge last week. So I copied my ships into a new sandbox save, removed NF mods and LS, simplified the mission parameters, and here is my submission: Mission parameters: Primary mission: to visit the surface of Eve and return to Kerbin to tell the story. Tertiary mission: bring some friends along to pass the time. The lander was sent with no fuel and added mining / refining equipment to save on weight during landing. Which at this point I will point out that using a pilot to mine and fuel the lander takes forever... It was performed with one launch, 373 parts, and 1553 tons. After a few floppy launches, some structural I'm a spambot, report me. <<<(LMAO was supposed to be the trade name for the little blue pill but the forums swapped it out to say this) was added to stiffen everything up. Taking off from Eve was surprisingly easy - it only took 2 tries (of course not counting the 6,543 attempts before this) - first with MechJeb Ascent which started performing acrobatics at around 22km and came crashing down, the second (successful) launch done manually - with little regard to gravity turns...lol. Straight up till around 50km then started the turns. Made it to orbit with around 1800 dV remaining. I was maybe a little too concerned with weight and left out some RCS controls and additional battery on the lander vehicle - but tbh, they weren't missed too much...though one of my solar panels burned up on landing so a battery would have been nice during the ascent. I was going to have the mining equipment powered by PB-NUK Radioisotope Thermoelectric Generators to keep things as stock as possible, but it would always show insufficient power and shut everything down as soon as I sped up time (did I say that it takes forever to mine ore with a pilot?), so I switched to using Roverdude's nuclear generators - (2) of the .625 sized. I added the Lithobrake landing legs to get added ground clearance (just to be safe) and used a few of the FASA decouplers (they are a little lighter, and while the lander assembly wasn't all stock, it could easily be and still work fine. A final note - I was going to use MechJeb for the transfer planning to/from Eve but when it would be time for the transfer, I would start up MJ and it would tell me that the transfer would be in another 1-2 years or it would start the burn and I would see that the trajectory was nowhere near Eve...so not sure if it was me doing something wrong or a bug w/ MJ but I ended up doing everything myself...so it probably wasn't as efficient as it could have been.

Trying to sort this all out. My 4 Kerbal mission to Minmus had 100 supplies and when this updated it went from 4 supplies / day to consuming 81 supplies / day...? Needless to say, they all left as soon as I took off....so not sure what to do to save a 5 yr career game. Ideas? Also, why? Why change the number of supplies per kerbal per day? Where is this all outlined and explained? The Habitation space referred to above...isn't this the forum? Or do I need to go someplace else to get caught up? Thanks!

I landed a ship on Minmus to satisfy a couple of contracts - one was for a tourist to visit the base that was constructed there. First off, the portions of my base that were inflatable (Wild Blue's Pathfinder mod) were gone. There had been no update or anything that would have changed the game contents since it had been built (though I did do a couple of the exit / restarts to prevent those wonderful game crashes). So, ok, strange but not unheard of - something spontaneously exploding due to vibration, uneven setup location, etc. I connected a crew tube (again Pathfinder) from the lander to the remaining colony elements so that the tourist could "visit" the colony. She did, contract complete. I moved 3 Kerbanauts to the base, another contract complete. All good so far and making money. Transfer everyone back to the lander, remove the tube, and take off. Here is where it gets strange: I get to an Ap of 6km, oriented for creating a stable orbit, go to map to start adding maneuver nodes...and no trajectory line (or whatever the blue line showing Ap / Pe is called), the lander is now classified as a "base" (which I assume is due to connecting it while landed) it is obviously 4-5km above the surface and moving, but when I clicked on it, it says that it is "landed" at 0km. There is no error or crash logs to link, obviously a modded install, but other that the updates that Roverdude posted for his mods, there haven't been any updates to the game ( am not using any of Roverdude's mods for this base) - and those updates were installed before I had even added the Pathfinder habitats, etc. I use several mods, but have never had this issue or anything close to it come up, so not even sure what information is useful to help sort it out. I am at work atm, but if anybody has any ideas as to where to start to "fix" this, when I am home I can post the information. The lander itself is 100% stock other than adding a KIS inventory container and some food supplies (Roverdude's Life Support). What I have NOT done yet was to go to an earlier save game and load it...which will be my next step.

The KiSS - capable of moving from LKO to wherever with minimal resupply requirements. Using USI life support and Karbonite mods during my career mode...so Karbonite unlocks sooner than Ore mining, etc. Went to Duna stayed for a year and returned safely - overall a success. [IMGUR]I5OTz[/IMGUR]

I decided to try to do a deep space exploration vessel that would be capable of staying out indefinitely with minimal resupply needs. I am using the USI life support mod so food was the most critical concern. Overall I would say it was a success. No major failures (thankfully), but a few things to do differently in the future. I hadn't successfully gone to Duna and returned without having to rescue someone...so am happy with the outcome. [IMGUR]I5OTz[/IMGUR]

Hey all...I was wondering how to link my screenshots directly into my forum post...I figure it's easy (or maybe not) but that I am ignorant. I know I can use imgur or something similar (and maybe that is the only way) I just saw so many posts with the pictures directly imbedded and wasn't able to figure it out. Thanks!

So this is more of a Poll rather than asking for support per se. I have a modded install (on Windows *sigh*) and before I start to remove some to see if it is the mods I thought I would throw out the question. I know that at any given time the game becomes buggy for one reason or another for us individually but I am trying to gauge this overall for the community. My problems are mostly encountered in the VAB. When I save a sub-assembly the game begins to act slow(er) and many times when I try to put the assembly back onto the vehicle (after the save) it many times won't let me (the attachment nodes are gone or unresponsive). ctrl-z to duplicate small assemblies seems to be totally broken atm. When I bring in a previously saved sub-assembly it is far worse and more often than not breaks the vehicle where it won't save it, allow me to modify the stages or it won't even recognize that there are any stages at all. It doesn't seem to have anything to do with size / complexity of either the sub-assembly or the main assembly - in one instance it was a simple (stock) lander (40 parts or so with the science attachments) and I was trying to add the launch engine assembly (again stock parts) which was 24 parts and it placed it to the side and wouldn't let me select it, remove it or anything, I ended up starting over (after restarting the game). In the past when this on occasion would occur, leaving the VAB would remove the unattached assemblies and leave the main - not now. I have to exit the game and restart it before it will remove the corrupted assembly (and it will save it as the last auto-saved ship...and so help me if I reload it...) Struts attach correctly, fuel lines attach correctly, I save, exit and return to find them either missing or totally rearranged (incorrectly). Probe cores don't recognize that they have SAS when they in fact do - I tried to send an engineer into orbit to perform an eva repair, I would turn on the SAS, but when I switched to map view to time the launch, and returned to the ship view, it had turned it off and said that I had no SAS capabilities when I tried to turn it back on. If I take the exact same vessel and launch it straight from the VAB without switching views it works fine. If I remove the engineer and launch it unmanned, it launched fine - even after switching views, etc. Does any of this sound familiar? When Steam auto-updated my 1.04 install (Grrr) it was a total game breaker and I uninstalled and reinstalled a clean copy of the game - with no mods. But my addiction couldn't be sated until I added some mods back in...

I struggle with knowing when to run experiments without this...looking forward to the update. Keep up the good work!

I think Varsi misunderstood the op's statement. KSP (windows) is still a 32 bit system based program and apparently it is a problem for squad to update this game so us windows based players aren't flooding the support pages with crash reports, etc. I very much hope that 1.1 comes out soon and these RAM issues are fixed.