birdspider

have there been any announcements regarding (unity) engine changes/optimizations/general performance improvements/regessions ?

+1, Can confirm same bahaviour and fix (although I just tested it with re-moved, not moved)

hi, after mistakenly using ckan's windows version of AFBW on linux, I installed the linux one but (in contrast to the windows one - in linux) the settings icon does not appear. does the extracted (snipped) log help? Also I made sure to have libSDL2 installed. Just out of curiosity: I need the 64bit variant of libSDL2 for KSP.x86_64- right? (that is: I do not need the lib32-libSDL2 one ?)

how is it seeded ? some sort of default seed or is every new game different or do I missunderstand the concept ?

Hello, I can't seem to find doc on the various slider controls in the wing context menu. (Pitch,.., AoA%,) 1) are those from FAR ?, 2) can someone point me to a wiki/doc where those are explained ?

then again most AAA 32 bit games handle their memory more efficently, therefore have not need for x64 - contrary to KSP

archlinux - so linux 3.17 and mesa 10.3.2 - afaik as up to date as you can get without [testing] EDIT: I just read that KVV might me the cuplrit ( in the post with the picture ) - I will try this with KVV removed

While building a 0.65 m (tiny) sattelit with attila engine, I found out that there is no (tiny-small) LiquidF-Only tank (no oxydizer) in my mod setup. Does anyone know a mod which provides one one? I thought about copying/edititing the Toroidal Fuel Tank to come as a LF-only version, but before I do that I want to get some feedback if maybe there is a mod out there that has what I need.

wow, I'm not the only one (yay) - I too experience this issue (linux x64/radeon though) - exactly like Batz_10K's screenshot

hello, could it be that the impact functionality of the seismic acclmeter is broken (in only shows default one instead - "toggle display" or so) or is it just my install [0.25] ?

Because I didn't know and someone may look for this bit of info: add GALLIUM_HUD=fps to you command and measure fps like a pro (mesa 9.2 upwards)

IFF you have an ati card and use the radeon driver unter linux. Either in grub while the system is starting - press 'e' on the start-menu-list-entry - this brings up a simple editor - in the kernel line I think add (write) radeon.pcie_gen2=1 - press 'b' to boot that. Or to make the change persistent so you don't have to do it every time. Change the same line somwhere in /boot/grub/<whatever>.cfg. I can't give you the exact wording because I dont use grub. But these steps should more or less take you there. The modinfo and modparams stuff is just to check what the current/default value of radeon.pcie_gen2 is. Just "cat /sys/module/radeon/parameters/pcie_gen2" in an termial to show what the parameter currently is. EDIT: https://wiki.archlinux.org/index.php/kernel_parameters

Hello, I was mucking around with KSP recently because I wasn't satisfied with the games performance (I seemed that something was wrong). That is I tracked cpu usage and stuff and things didn't seem to fit. (60% one core only, while having yellow time at lauchpad). I tried http://forum.kerbalspaceprogram.com/threads/59005-0-23-Release-2-15-Active-Texture-Management-Save-RAM-without-reduction-packs! and various linux tweaks and finaly reached out for the radeon.* kernel-mod parameters. First of all I wanted to see what was enabled: modinfo -p radeon ... well I didn't see exactly what was enabled so I found a script (see below). EDIT(this should also work: cat /sys/module/radeon/parameters/pcie_gen2)/EDIT The param of interest was radeon.pcie_gen2 which was set to -1 which seems to mean "auto", whatever that means. This param is well known and not knew, I just assumed that it would be 1 by default these days. I added radeon.pcie_gen2=1 to my bootloaders kernel-line (options root=/dev/sda4 rw radeon.dpm=1 radeon.pcie_gen2=1 in my case). You can add this in grub by pushing 'e' in your boot menu, change the line and then 'b' to boot. To make it persistent add it to your bootloader(grub,lilo,syslinux,gummiboot or whatever) This made a difference. I can now have smooth shadow (32 shadow cascades, 32 pixel light source) and green time text. Maybe this is useful for someone. [birdspider@blackbox bin]$ cat modparams #!/usr/bin/env sh module="$1" echo "Module: $module"; \ if [ -d "/sys/module/$module/parameters" ]; then \ ls /sys/module/$module/parameters/ | while read parameter; do \ echo -n "Parameter: $parameter --> "; \ cat /sys/module/$module/parameters/$parameter; \ done; \ fi; \ echo; \ [birdspider@blackbox bin]$ ./modparams radeon Module: radeon <snip> Parameter: msi --> -1 Parameter: no_wb --> 0 Parameter: pcie_gen2 --> 1 <------------------------------------- Parameter: r4xx_atom --> 0 <snip> Things I also tried: LC_ALL=C R600_HYPERZ=1 R600_STREAMOUT=1 R600_SURF=1 R600_TILING=1 R600_GLSL130=1 ./KSP.x86_64 see: https://wiki.gentoo.org/wiki/Radeon#Tuning which didn't seem to do anything. ArchLinux x64, ATI HD6850, 8 GB

Hello, 0.23 with a bunch of mods runs fine for me, that is archlinux 64, ati HD 6850 - radeon driver, KSP.x86_64. Now that it it works I have a last issue with the shadows. It's not game-breaking just frustrating when I see other peoples videos with perfect shadows. Here is an extreme example of it but there are less invasive occurences. It is most annoying when I do a landing manouver and the shadow which is always helpful while landing is a fuzzy blob which little resemblence to the craft. Also self shadows are obviously ugly. Has anyone encountered something like this before. I'm not even sure how to call it. Googling for 'shadow flicker' and stuff didn't help much.

Can you be more specific ? Orbit of which planet ? Lag as in 'low fps' or 'stutter spikes'? What are 'almost full graphic options' - you did not put the light count setting to the far right - did you ? Also Linux Mint Ubuntu Based or Debian ? Which graphics driver (nvidia binary or noveou, see /var/log/Xorg.0.log)? How much RAM do you have. The more info you provide, the more precise it is, the better are your chances that someone helps you - also Mint is not offically supported.

@NardoLoopa: I'm no expert but this page tells me that your GPU has very limited linux support - especially Hardware TCL. You really want a newer/better supported gpu under linux. Also for bedtime reading phoronix article about intel legacy driver

For those of you who segfault (core dumped) on the loading animation. The only thing you can do is wait to get it fixed. At this moment - to my knowledge - it is unknown if this is a Unity or mesa or both bug. Though the correlation with mesa ati drivers is a strong one. Therefor either provide the devs with information i.e. here http://bugs.kerbalspaceprogram.com/issues/722 or the corresponding mesa bug as pointed out here http://forum.kerbalspaceprogram.com/showthread.php/24529-The-Linux-compatibility-thread%21?p=381728&viewfull=1#post381728. My personal opinion is that this wont get fixed anytime soon (maybe as an sideeffect of a additional fix) because the official support (KSP wise) is Ubuntu+ati-propiatary (which seems to work btw.), Ubuntu+ati_opensource seems to be a minor combo therefor has no or less priority and other Linux's are not supported at all.

while you may have a working setup, I wouldn't recommend anyone - especially linux starts - to setup the nvidia binary blob* driver as the standard route to try to fix any general issue they have, also - what problems did you have where this action did help ? * you basicly circumvent the package manager - can be nasty when deinstalling/updateing packages - also no dependency management

please read the first post of this thread, your 'plugging' problem may be very well solvable with "LC_ALL=C" before staring the game, (be sure to delete the settings.cfg)

i think this is a segfault, as described in http://forum.kerbalspaceprogram.com/showthread.php/24529-The-Linux-compatibility-thread%21?p=381728&viewfull=1#post381728 I postet a bugreport but they do not support any linux other than ubuntu. There is hope though as this might be an mesa upstream bug. you can run 'gdb ./KSP.x86_64' and then '(gdb) run' which will print something about segfault - as far as I know you cannot do anything about this until the bug is found and fixed

yes I understand that, and my response was indeed a bit harsh if one could say that. In the end I just wanted to gather information regarding this segfault, hence the link to the mesa bug. I'm not in touch with gdb or other debugging tools to do bughunts on my own - my guess was that ubuntu had a rather older mesa or other lib and this segfault might reoccour on some 'offically supported' OS. So I figured why not look into it now, instead of waiting until it effects a lot of people. I don't honestly know how to 'tweak' archlinux to represent ubuntu* except from downgrading which is against how archlinux works. I can only say that arch is by design very close to upstream and that I expect that such bugs on arch (or gentoo in this context) will occour on other distros with slower update cycle unless fixed somewhere along the way. *actually I will research this on the weekend

Hi, I'm adding 2 segfault issues, because I think they might play a part in the future since both distros metioned (archlinux and gentoo) are fairly upstream centric, and maybe some unoffical linux guru can point one in the right direction. Both describe a segfault more or less right after resource loading. http://bugs.kerbalspaceprogram.com/issues/534 [0.19] <- this is some other guys report http://bugs.kerbalspaceprogram.com/issues/684 [0.20] <- this has been closed on me Edit1: might be a mesa bug https://bugs.freedesktop.org/show_bug.cgi?id=64913