azander

Finally had a chance to change desktop managers. KDE4 + Plasma (original) has the resize issues. Gnome seems to work okay, if a big sluggish doing screen refreshes... and lots of issues with my sound card. IceWM... don't even try, it will lock your system up hard. It doesn't properly support the openGL video drivers and when launched, it locks up. Tried several OpenGL programs, not just KSP to verify this. I will test more as I can. These were just the initial tests for each Windows Manager. Az

That I haven't tried, yet. I have xfce and Gnome installed as well. I'll give them a shot. Az

Nothing in syslog. Screen outputs always show graphic type errors, or out of memory errors (when using mods). PLayer.log and KSP.log are always similar to those I posed about 2 pages back.

@joelleEmmily Twice. Even switched distros once, and had to go back for other reasons. I don't wish to use Ubuntu, so sent from OpenSuse to Debian, then back. Debian has similar issues to OpenSuse when it came to this issue. Az

I've run out of ideas. My KSP is unplayable except on Windows (I really loathe windows). Isn't someone going to take a hard, deep, look at this? I have posed logs, I have tried everything suggested. At best, I can play 1 time out of every 40 because of this issue. Often times that 1 will even crash taking the system down with it (hard reboot required). One of the reasons I tried this game in the first place was because it DID run so well on linux. Now... Now... I feel like nobody cares about the linux users. I am really hoping that 1.2 fixes it. Somebody better test it though, because it feels like 1.1.x wasn't tested on many different distributions of Linux. Remember, unlike Windows, there are many linux flavors and each is slightly different. *one very frustrated gamer* Az

Because that is where the cat likes to sleep. Why do we allow politicians to lie to us and not be held accountable for that lie?

I was getting that too with that long script. It never happened bore I started using it. Haven't had a chance to debug it yet so I can only confirm it happening at this point.

prefs is absent, I make sure of that before loading KSP every time. It starts out with the correct resolution, then sometime during the load it changes. Usually just before the squad logo appears. The different solutions I get are: 0x720, 1280x10, 1x1, 0x0, 1280x1. 10x720, and less often others.

Nice Script @psycho_zs though it doesn't fix my problem. I still get the screen size wierdness... and on top of that xwininfo -name "Kerbal Space Program" outputs the original starting resolution, and not the current one, so your checker never sees that it resized after opening and is unplayable.

I spent several hours watching NASA TV before the last shuttle launch. They have multiple 3 inch binders of checklists. Each for a specific job. The one for closing the hatch was 2 binders. I saw several binders worth of checklists for just strapping the astronauts into their seats. I can imagine the "oops we forgot X" situations that led to such complex, and detailed checklists. So, I follow the professional's method. Checklist, check list, checklist. Then when something still gets missed, I add it to the checklist.

I believe is is using 1280x720 or something close to that. xrandr shows this: Player.log shows: Default vsync count 0 requesting resize 1280 x 720 resizing window to 1280 x 720 Desktop is 1600 x 900 @ 60 Hz

OpenSuse 13.2 64-bit, KDE install. I'll try the OOM killer too. What do I need to do?

I have the most "up to date" drivers for my distro. (OpenSuse 13.2, Opengl 3.3 via NVIDIA propriety drivers) @sal_vager I tried that. works properly more often, but still sometimes glitches out to strange resolutions, even though the prefs file never gets updated with the wierdness.

Yes, same issue. This is really getting annoying.

Semi-random (may not be random?) Issue during start up here. I see many people with the same issue. During startup the screen size starts out normal sized, then changes to some unusual size making the game unplayable. It resized just as unity hands off to KSP from the looks of things. To test, I have removed all config files and logs file. Then started a clean steam-based, stock copy of KSP using "./KSP.x86_64 -force-gfx-direct" as suggested many times above and elsewhere. The Player.log file is here and the KSP.log is below. I have tried forcing the prefs file, removing the pref file, getting a good startup, then setting hte prefs file to read-only. I have tried 64 bit, 32 bit, 64bit with options, etc. This is making the game unplayable for me. What else can I do?

I too experience this problem. OpenSuse Linux 64bit. Modded and unmodded. No log files generated before it causes the issue. The only file that gets created is the pref file. I've had to create a bash script to auto-delete it before starting just to make the game playable. So far nobody has an answer. I've tried all of the above, and still get similar results.

I'm having problems with the NASA Docking System. It doesn't want to release. Can you point me to where I can look to find out why?

What is with all the gripes? Does ANYONE here run a OS (Windows, Linux, Max, etc) that DOESN'T and HASN'T ever needed updates? Lets give these people the credit they deserve and not the hate? anger? they seem to be getting from this thread. Windows monthly updates. Mac Updates, Linux updates, cellphones update, apps update, but these were advertised and shipped as ready to use! Should we be whining about those too? (I know people do) Remember when Bill Gated Demo'd Windows XP and it BSOD'd at bootup? Yes, it did happen. As it was said above, software is complex. Get used to it. Windows has something like 25,000 people with their finger in the code. MacOS X isn't too far off that number. Linux has even more. Gone are the days of 1 programmer, 1 program. This means bug WILL happen, and will need fixing. That means updates. Yes there were a lot of bugs in 1.1.0, but so what? In the ~month it was out on steam as a pre-release they squashed hundreds of them, yet people were screaming that it was taking too long. They released it (don't know what the decision making was on that, don't care either), and now many of those same people are screaming that they didn't test it well enough. Get over it! Either it takes a VERY long time to get the bugs worked out, OR you release buggy code. It is an either/or equation. There is no middle ground, especially in such a big and complex changeover in the underlying game engine. I say thank you to those who have worked on this, and enjoy your vacation. When you get back, there will be much to do, as always. To those complaining I say get over it. This is how the world works. Az

You may want to remove the %homedir%/.config/unity3d/Squad/Kerbal\ Space\ Program/prefs file and try again. I've had issues with the Pre-release corrupting that file. I just added remove it to my startup script and so far, things have worked fairly well.

When you load a saved game, you cannot change focus away from KSP. The result is exactly what you describe. Happens in Windows(32 bit), and Linux(32 and 64 bit). I can reproduce it every time. Az

I'm a computer programmer by training, and Systems Administrator now. Worked toward a degree in Computer Science but Life got in the way. I work for a small Internet Provider and hosting company in the Midwest US. When not taking calls for helpdesk, or doing other system admin duties I spend the time tinkering in KSP.

You may want to keep an eye open for Kerbalstuff's replacement. There is quite a lot going on to get it up and running. See the IRC channel #CKAN for details.

What I do is using 2 machines, connected via NFS (Linux), or Samba (Windows) I share the "saves/<name>/Ships" folder. I do similar to the mod folders in the GamaData folder (but not the GameData folder itself). This way they have the same mods. I build using one machine, and fly using the other. Once built, I save the ship, when then can be loaded using the other machines VAB "load" option. Once it is in the VAB or hanger, I move it to the launch point normally and launch.

I spent the last week building this ship for planet hopping. Tool a long time due to very low FPS with this large part-count ship. The separated capsule is the last of the builders leaving. The station-like shp has a small Duna rated lander, and a moon(s) rated miner attacked. It was launched in 4 main sections, and then another rocket to deliver the lander and miner.

They don't share the persistant.cfg file. They share the saved craft dir. I edit them in one, save it, then load it into the other. I use the same GameData dir as well. Took some tweaking, but it works.