-
Posts
17,670 -
Joined
-
Last visited
Content Type
Profiles
Forums
Developer Articles
KSP2 Release Notes
Everything posted by sal_vager
-
Updated 31st March 2017 Many links are broken and formatting corrupted, it's going to take a while to fix all of this. This thread is a continuation of the original Linux Compatibility Thread! Important, new issues for 1.1+, please see the Known Issues section below. Also there is a critical issue with the Unity engine sending a bad window size to the window manager, causing the window manager to crash, there are some workarounds, please see here for more info. This is FIXED in the 1.2.9 pre-release! Workarounds: Run KSP in fullscreen mode, you can set this via the launcher. Delete the ~/.config/unity3d/Squad/Kerbal\ Space\ Program/prefs file before starting KSP. Use the xfce desktop (xfwm is immune) Force OOM Killer to target KSP instead of the window manager, latest version below. (1) Getting Started. (2) Graphics Drivers. (3) KSP on Steam. (4) Modifying KSP and importing saves. (5) Troubleshooting. (6) Known issues. (7) KSP for Windows in Wine. Index in case I ever find a way to fix it.
-
The Linux compatibility thread!
sal_vager replied to sal_vager's topic in KSP1 Technical Support (PC, unmodded installs)
It is still possible to run the Windows version of KSP in the Wine compatibility layer, KSP works best with the rawinput support of Wine 1.5.13 and higher, so make sure you are using the latest version of Wine. You will need the updated proprietary drivers for your graphics adapter and the Eufonts pack which is part of Winetricks, then KSP for Windows should work fine in Wine. There won't be joystick support, and shadows can be messed up, but actual game performance can be slightly higher then in the native Linux build, see the old Wine thread for more. -
The Linux compatibility thread!
sal_vager replied to sal_vager's topic in KSP1 Technical Support (PC, unmodded installs)
Steam keeps KSP for Linux in /home/user/.local/share/Steam/SteamApps/common/Kerbal Space Program And can also be found symlinked in /home/user/.steam/steam/SteamApps/common/Kerbal Space Program Currently, the Steam launcher will only start the KSP.x86 and not the KSP.x86_64, this is due to the still highly experimental nature of the 64bit version. The Steam version of KSP may also need the LC_ALL=C command, but it's not very reliable to start Steam using it. Instead you can add the command to the Steam on a per game basis, this is also useful for things like Optirun with Bumblebee. An elegant solution can be found here thanks to stibbons, just add LD_PRELOAD and __GL_THREADED_OPTIMIZATIONS variables to the "Set Launch Options..." box in the Properties page for KSP Or try these older commands: LC_ALL=C %command% Skarhu informs us that: If you want to start (experimental) 64bit steam version by default just add following line into game launch options: LC_ALL=C %command%_64 Don't know where to do this? See here and here. -
The Linux compatibility thread!
sal_vager replied to sal_vager's topic in KSP1 Technical Support (PC, unmodded installs)
As with OSX and Windows, KSP for Linux creates logs of information that we can use for diagnosing faults. The player.log is written to "/home/user/.config/unity3d/Squad/Kerbal Space Program" for both the store version and the Steam version. The new KSP.log can be found in your KSP game folder if using the store version, or the "/home/user/.local/share/Steam/SteamApps/common/Kerbal Space Program" folder if using Steam. These logs are essential for diagnosing faults when KSP goes wrong, and cover in-game events and basic system info. An in-game logging feature can be accessed with modifier+f2, this is useful when trying to catch an issue as it occurs. As well as the logs made by KSP, it is useful to know your full system specifications, this can be found in Debian based systems by using a program called hardinfo. -
The Linux compatibility thread!
sal_vager replied to sal_vager's topic in KSP1 Technical Support (PC, unmodded installs)
KSP works best with the proprietary graphics drivers for your graphics adapter, if using AMD or Nvidia, the open source drivers can work but are slow and can lack some effects/shaders, though their speed and capabilities are constantly improving. AMD graphics adapters Unfortunately, anti aliasing does not yet work in Unity with AMD hardware, so until this is fixed we have to put up with a bit of roughness. You can install the latest stable AMD proprietary driver in Ubuntu 14.04 by first converting the .run file into a .deb with this command: Code: sudo sh amd-driver-installer-catalyst-13.12-linux-x86.x86_64.run --buildpkg Ubuntu/trusty Then install the .deb with the following: Code: sudo dpkg -i fglrx*.deb Nvidia graphics adapters The easiest way to install the more up-to-date Nvidia drivers is to add the x-swat repository to the package manager. You can also download the latest drivers for your system directly from Nvidia's site. And finally, UndeadBanana has a fix here for Nvidia hardware that can greatly improve the speed of your game. Intel cards. Intel cards use the free open Mesa driver which has seen some recent performance boosts, there are still a few things we can do to improve our game though. Kelmv has a fix for S3TC textures on Intel cards here. Want to enable shadows on Linux for Intel Ivy Bridge graphics? Try this. This has been reported to also solve some crashing issues with these cards. Is aerodynamic FX greyed out and you see "No hardware support" on the settings screen? Then you'll want diego_gz's fix for Intel cards here Frames per second in KSP! There's a few different ways to get FPS in KSP. GLXOSD You can get an on screen FPS counter in any Linux game using GLXOSD. It's a command line tool so use it you need to start KSP from a terminal or a shell script with: glxosd "PathToYourKSPBinary" KSP-DEVTOOLS These platform agnostic tools include FPS.dll, which if plonked in your plugins folder will show the FPS of KSP, low profile but a little jittery and should work on Windows and OSX as well. VOGLPERF No I didn't sneeze in German, VOGLPERF is Valves OpenGL benchmarking tool for Linux games and has some very nice features, but it needs compiling. Thanks to Steve_V for finding these. -
The Linux compatibility thread!
sal_vager replied to sal_vager's topic in KSP1 Technical Support (PC, unmodded installs)
Some of the new spaceplane parts use .tga's for textures but most distro's do not support loading these by default, you will need to install a package to handle them such as libsdl-image Segfaults in KSP 64bit broken again!, see Addle's new fix here and below. Meeki has worked out a fix here for 0.22, helps a lot for heavily modded installs, also 0.23 has new offsets, so check out the new instructions here, thanks to MikeAeronautLZ for finding them. Also, FuzzyLlama has found how to make the above work in Gentoo! Updated by meeki. And updated again for 0.23.5 by ASCII892. Updated yet again, this time by MikeAeronautLZ for 0.24. Updated for 0.90.0 by Addle. Just run these in a terminal in the KSP directory, these are for 0.90.0: echo "0099e747: 00" | xxd -r - KSP.x86_64 echo "0099e74c: 00" | xxd -r - KSP.x86_64 If KSP crashes when you revert or pause and resume, you can try the fix here, big thanks to Misanthe for working on this one. KSP can crash on startup on non-Ubuntu systems with a stacktrace in the log, member a.g. has worked out a fix here. Locked to a resolution/fullscreen mode and unable to change? <Click here> for finding the Unity prefs file. Some players have reported that the game fails to load past the "Indicator Panel", LC_ALL=C should fix it. Mouse issues If you use a localisation that suffers from the above your mouse sensitivity can be corrupted, just delete the settings.cfg to fix it. There has also been reports of an oversensitive mouse, often caused by an addon, but also seen on Debian for no known reason. The Modifier Key (Debug Tools!) Alt is in use by many Linux distributions for dragging windows, this interferes with the Alt key in KSP so it has been remapped to RightShift, though it is easily mapped back to any key you like in the settings.cfg The debug log can be accessed with RightShift+F2, the debug tools are available with RightShift+F12 Xbox controllers Xbox controllers actually work very well in Linux, but they do require xboxdrv to be installed. Arch Linux There's a number of issues with KSP on Arch, you can find more info and fixes here. -
The Linux compatibility thread!
sal_vager replied to sal_vager's topic in KSP1 Technical Support (PC, unmodded installs)
KSP on Linux needs the Arial.ttf and ArialBd.ttf fonts installed to display correctly, these are from the winetricks eufonts pack, just place these two files in your /home/user/.fonts directory in Debian distro's. Arch Linux geniuses should check here for where to install their fonts. OpenSUSE sufferers should look here. Gentoo compilers here. Fedora wearers here. Followers of Slacktivism here. For all distro's, putting the fonts in /usr/share/fonts should do the trick, also after adding any fonts to a linux system you should run "fc-cache -fv" as this will look in the common font directory(s) and build from there (thanks meeki) KSP has some issues with some languages that interchange comma's and periods, you can solve this by starting KSP to the LC_ALL=C command: For 32bit systems, but no longer needed as of 0.90.0 Code: For 64bit systems Code: (Try LC_LANG=C if the above fails) StoliFlyer has made a small shell script that we can use to start KSP without having to type in LC_ALL=C each time, which was later improved by Ghost99: Note, getting the Steam version of KSP to work with LC_ALL=C is a little different, please see below. Important! - There is a new issue where if a player needs LC_ALL=C and starts a new save, the persistent.sfs can be corrupted in exactly the same way that the settings.cfg can be. Please see here for a fix. -
The Linux compatibility thread!
sal_vager replied to sal_vager's topic in KSP1 Technical Support (PC, unmodded installs)
piotrektt is working on testing KSP addons to see what works, check out his thread here, can you help add to his list? DorfKerbin and a team of Redditors have also checked a number of addons for compatibility with KSP for Linux, but it's a bit out of date now, click here for more. Addon parts should work fine in Linux KSP, and nearly all plugins should also work as Unity uses Mono for the C# used to code them. Issues can appear however if Monodevelop, a free tool for writing C# code, isn't used, this is because the more common Microsoft C# development tools handle things slightly differently, and incompatibilities can occur. Even if using Monodevelop there can still be occasional issues though, as the version of Mono used by Unity is always a little out of date, and is also modified by Unity themselves. -
The Linux compatibility thread!
sal_vager replied to sal_vager's topic in KSP1 Technical Support (PC, unmodded installs)
Start KSP the right way with voidi's installation script, just click here! (Direct link to script) KSP for Linux from the Squad store comes as a zip file and can be unzipped to any folder in your home directory, it does not need root privileges but the binary files (KSP.x86 and KSP.x86_64) may need to be set as executable. KSP for Linux from Steam is installed to the normal Steam games folder on your system. Supported Systems Officially, the Unity Game Engine supports Ubuntu from 12.04 onwards, older versions may fail to run KSP as they may be missing dependencies that they cannot install, and other flavours of Linux may also struggle a bit. Please note that just because Unity (and KSP) do not support other distro's, does not mean KSP won't work, but also just because it works on Distro X doesn't mean it'll work on yours. Using the ldd command I have this list of dependencies required by the KSP.x86 in Xubuntu 14.04: linux-gate.so.1 => (0xf770f000) libstdc++.so.6 => /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xf75f8000) libGLU.so.1 => /usr/lib/i386-linux-gnu/libGLU.so.1 (0xf7580000) libGL.so.1 => /usr/lib32/nvidia-331/libGL.so.1 (0xf7478000) libX11.so.6 => /usr/lib/i386-linux-gnu/libX11.so.6 (0xf7340000) libXext.so.6 => /usr/lib/i386-linux-gnu/libXext.so.6 (0xf7328000) libXcursor.so.1 => /usr/lib/i386-linux-gnu/libXcursor.so.1 (0xf7318000) libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf7310000) libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf72f0000) librt.so.1 => /lib/i386-linux-gnu/librt.so.1 (0xf72e0000) libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xf7298000) libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0xf7278000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf70c8000) /lib/ld-linux.so.2 (0xf7710000) libnvidia-tls.so.331.38 => /usr/lib32/nvidia-331/tls/libnvidia-tls.so.331.38 (0xf70c0000) libnvidia-glcore.so.331.38 => /usr/lib32/nvidia-331/libnvidia-glcore.so.331.38 (0xf4e78000) libxcb.so.1 => /usr/lib/i386-linux-gnu/libxcb.so.1 (0xf4e50000) libXrender.so.1 => /usr/lib/i386-linux-gnu/libXrender.so.1 (0xf4e40000) libXfixes.so.3 => /usr/lib/i386-linux-gnu/libXfixes.so.3 (0xf4e38000) libXau.so.6 => /usr/lib/i386-linux-gnu/libXau.so.6 (0xf4e30000) libXdmcp.so.6 => /usr/lib/i386-linux-gnu/libXdmcp.so.6 (0xf4e28000) And these for the KSP.x86_64 linux-vdso.so.1 => (0x00007fffd9400000) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f0f7b3d8000) libGLU.so.1 => /usr/lib/x86_64-linux-gnu/libGLU.so.1 (0x00007f0f7b168000) libGL.so.1 => /usr/lib/nvidia-331/libGL.so.1 (0x00007f0f7ae30000) libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007f0f7aaf8000) libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x00007f0f7a8e0000) libXcursor.so.1 => /usr/lib/x86_64-linux-gnu/libXcursor.so.1 (0x00007f0f7a6d0000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f0f7a4c8000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f0f7a2a8000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f0f7a0a0000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f0f79d98000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f0f79b80000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f0f797b8000) /lib64/ld-linux-x86-64.so.2 (0x00007f0f7b700000) libnvidia-tls.so.331.38 => /usr/lib/nvidia-331/tls/libnvidia-tls.so.331.38 (0x00007f0f795b0000) libnvidia-glcore.so.331.38 => /usr/lib/nvidia-331/libnvidia-glcore.so.331.38 (0x00007f0f76da0000) libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007f0f76b80000) libXrender.so.1 => /usr/lib/x86_64-linux-gnu/libXrender.so.1 (0x00007f0f76970000) libXfixes.so.3 => /usr/lib/x86_64-linux-gnu/libXfixes.so.3 (0x00007f0f76768000) libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x00007f0f76560000) libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007f0f76358000) If you are using a 64bit distro you may need the 32bit libraries, you can install them on a Debian based distro using ":i386" after the package name. Here's an example for the Mesa driver "sudo apt-get install libgl1-mesa-glx:i386" -
Massive and heartfelt thanks to everyone who posted here, whether seeking help or giving it, this thread and Linux support in general could not have survived without all your help, and while this thread is now closed and was archived (now unarchived) please join us at the new Linux Thread! With Unity4 officially supporting Linux, Squad have taken the bold step in offering a Linux build of KSP while the game is still in development. Linux support is still temperamental and considered "in development" by Unity themselves so there are a few issues to deal with, especially with the 64bit version so if you are having trouble it's worth sticking to the 32bit version of KSP for linux. --------------------- (1) Installation and supported systems. (2) Fonts and localisations. (3) Known issues and special features. (4) Graphics Drivers and frames per second. (5) KSP logs and diagnosis. (6) Linux KSP on Steam. (7) Addon Compatibility. (8) KSP for Windows in Wine.
-
A lot of other people suggested it as well, here and in IRC, sorry but you were not the first jfx Squad did this as it needed to be done, just be thankful they managed to get a decent deal from Amazon, someone there must play KSP
-
I think you need to try imgur voyager272 Post the link here
-
If you were the first person on mars, what would you say?
sal_vager replied to KleptoKat's topic in Forum Games!
I'd say "Wow that's a lot of red dust, it's going to take ages to clean this place up" Plus I'm moving this to Off-Topic -
If you were the first person on Gliese 581g, what would you say?
sal_vager replied to The Destroyer's topic in Forum Games!
I'd say "I hope I have enough military fuel for the jumps home" Plus this is going to Off-Topic. -
If you were the first person on Phobos/Demios, what would you say?
sal_vager replied to The Destroyer's topic in Forum Games!
This really belongs in Off-Topic Plus I'd say, "This place reminds me of the shores of hell" -
Yeah this isn't really appropriate language here, I'm going to have to edit that word but i'll leave this thread up, don't do that again though. Edit: Fixed, and didn't ruin the story.
-
Hi Drakee Skalor, welcome to the community Have fun on the forums, now go launch some rockets
-
Greetings from a rather cold and damp place in the UK
sal_vager replied to tarkatronic's topic in Welcome Aboard
Hi tarkatronic, welcome to the community Lets see, cold and damp, could be anywhere I'm on the south coast, so I occasionally see a bit of yellow on the horizon, I'm told it's the sun! -
I'd like a hat like this
-
Pushtank Biplane - Flying to Duna in style!
sal_vager replied to geb's topic in KSP1 The Spacecraft Exchange
Also, if it is an actual .txt, just change the file extension to .craft -
Things have been altered now, and it's harder/needs more fuel to do what we took for granted before, it's a new challenge
-
Just curious...are inflatable modules legit ?
sal_vager replied to germalto's topic in Science & Spaceflight
I'm pretty sure Bigelow aerospace is working on inflatable habitat modules such as this, not sure if they have launched any yet though. Edit: Looks like they have launched two prototypes with Russian help. -
Hmmm lets see if I can fix that, I won't Spoiler the first image though so people can get a taster... Edit: Cool, fixed it, they don't always work for some reason but in this case it was missing the button name, it has to have
-
Nice The pic's a little small though, if you upload the full size image to Imgur you can post the link here, and we can see it embigenated