lodger

This is a known issue that affects Windows, Linux and Mac OS X in the same way - it has nothing to do with the operating system used or the drivers installed (see this thread and the answers provided by sal_vager). The workaround solution for this is to set your KSP game to the native resolution of your display (e.g. 1920x1080).

I'm afraid that I have to report another sad loss: we had to put our 15 year old cat Shiva to sleep last saturday. She suffered from HCM and lost the battle. She was not only a loyal friend and member of the family, but also a fan of smooth jazz music and a pleasant companion during many KSP missions. We miss her ...

I'm waiting for 1.1 to be released. If it works with my current machine (which I bought in early 2013) - fine. If not I've got a good reason to start looking for a new machine.

Well, in my mother tounge (german) it means to do something by intuition, to "listen" to the feeling in your stomach instead of following your rational thoughts.

Awesome! Exactly what helps you through a long working day at the office while away from your own KSP machine ...

Rocktes: Small, Large, Big, Huge - *Boom*

And you have all the right to be proud of yourself, new born Kerbonaut! Congratulations! That's so true. I'm playing this game for over a year now and still do most of my docking and in-orbit assmbly of larger craft manually. Well, in my science career savegame that is...

I'd like to add that this is one of the few forums where more causal players (like me, who is not so much a crack with accurate maths but more into trying-and-flying-by-belly) and the pros who really know their stuff get along quite well. There's always something new to learn by just reading these forums and in most cases things are explained in a way that the average dude is able to understand.

Did you attach the AR202 unit (can be found in the 'control' tab) or the MechJeb pod to your craft? I forgot to do that first time I installed MJ and didn't have the MechJeb buttons either.

... you just found this in a recent space.com article and immediately thought: boy, which mod is that?

I agree with those who go for the 'freedom of choice' option. In the end it's the player who decides what cheating really is. And that probably makes the game so great: because you can always have it 'your way'.

This. Yesterday I went to bed early in order to get enough sleep at the beginning of a tough work week. And I lay awake long after midnight, thinking about my Duna lander concept.

Just started a new game (sandbox mode) to test my "Duna Explorer" concept. Since this is was just a first quick shot, kind of a "proof-of-concept" mission, I didn' bother to try to land on Duna. In fact, I didn't even attach parachutes to the lander. More important, as seen in the image below, was to make sure the spacecraft gets to Duna and will be able to land on Ike for ISRU purposes. Works quite well, needs some fine tuning. The design of the lander was inspired by various posts here on these forums.

Update: I just moved to 1.0.5 a few days ago and ran it in windowed mode so far. However, I did set the resolution of my (Linux Mint 17.3 XFCE ed., x86_64, nVidia 560GTX) machine to 1920x1080 and enabled fullscreen mode. With this resolution set, no issues with the tracking station showed up. Same goes for 1920x1200, but all other resolutions still cause the error. Just wanted to let you know just in case this might help ironing out the issue for 1.1

Farewell, "Major Tom" ...

Excellent description of the gaming experience. No matter wether you are a rocket scientist or the average gamer: the pride you feel once a mission is completed successfully is something that motivates you to go further, try new designs etc. - you will never grow tired of the endless possibillities.

Aaah, I see. Didn't know that this is the case since I chose 'Normal' when I started my 1.0.x game. See, even after a year of playing I still consider myself a 'noob'.

Um, I play science mode all the time and I *do* have quicksave/load. Are you sure this is still valid for versions 1.0.0 and higher (I remember using quicksave/load in science mode even in 0.90)?

I'm playing science career mode because then you are free to do whatever mission you want and still need to gather science data in order to unlock moar tech. I think this mode is a good compromise between full career and sandbox mode. P.S.: also, I only use the KER and Docking Alignment Indicator mods as I am doing all docking and other maneuvers by hand. Otherwise it'd spoil the fun for me.

Ah, I see. As long as the science points come in I can live with that. Thanks for the quick reply.

ASES is proud to announce the go-live of its Minmus mining operation. Docked to the new "ASES Labora" space station is the upper/transfer stage of the original F5h heavy lifter rocket. It will be reused for the upcoming manned Duna mission. It is the upper stage that carried the "ASES Labora" to its current orbit. Also docked to the Labora are the mining probe and the ore coverter. The latter just arrived from Mun orbit with the tug that is still attached to it. Spaceward Ho!

Sorry to bring this topic up again. See, I understand the limit issue. But I have just a single lab in Minmus orbit, there's no science stored in the lab yet. So I get down to the surface, collect data and want to process that in the lab. Like I said, there is no science stored in the lab so far. So I want to process a ground sample (+175 science) and still the lab complains about not having enough storage room. But then the 175 science are then stored in the lab and get processed. What am I missing here?

Well, it seems that Squad might be in need of a QA team that could help them avoid silent patches and might point out flaws that were not discovered by the coders. I think it's really just a lack of proper QA that Squad is suffering from.

Not really a solution but a mere workaround. Bugs like this should get noticed before a new version is released and it's really, really annoying not to use fullscreen at the preferred custom resolution. The tracking station used to work quite well for previous versions, so I really don't get it how they could mess this up that bad.

I'm running 1.0.5 unmodded on Linux Mint 17.1 x86_64, MSI nVidia GeForce 560GTX-Ti and get the following output when entering the Tracking Station: