kolAflash

Maybe this will help re-enabling solar panels:

Maybe this will help you:

I'm using Kopernicus and I didn't wanted to uninstall it. So I placed this file in GameData/Kopernicus/Config/Kopernicus.cfg and now Solar Panels (Photovoltaic) are working again. // Why we are disabling the Kopernicus custom module implementing their multi-star fix: // - we can't leverage it for background simulation // - warp fixer de-facto replace their computations anyway // - a lot of our code assume a single star, multiple stars support is planned for a future release // - lack of time to further investigate the interactions @PART:HAS[@MODULE[ModuleDeployableSolarPanel]]:NEEDS[Kopernicus]:FOR[Kerbalism] { @MODULE[ModuleDeployableSolarPanel] { %useKopernicusSolarPanels = false } } https://raw.githubusercontent.com/ShotgunNinja/Kerbalism/409c648a3b2868513617a09d03970c0e560a1b82/GameData/Kerbalism/Support/Kopernicus.cfg

I just opened a bug report for the Radeon open source Linux driver. Let's see what the Radeon driver developers say about this. https://bugs.freedesktop.org/show_bug.cgi?id=92101 They'll probably need some way to test this. Unfortunately the KSP demo doesn't seem to have fairings, so one of the driver developers may need a full version of KSP.

@sal_vager Any progress on this? Maybe "Unity Technologies" can help. Did you try to make contact with the Xorg-Radeon driver developers? (I can do so if you wish)

Here's a screenshot from inside a fairing, while standing on the launch-pad. It has textures, but it also has the bug. http://postimg.org/image/4hm3z9irl/ http://postimg.org/image/4hm3z9irl/91967292/ Regarding this other post of you (sal_vager). http://forum.kerbalspaceprogram.com/threads/117130-Service-bays-and-fairings-z-fighting?p=2202294&viewfull=1#post2202294 I tried the new graphics drivers from: http://download.opensuse.org/repositories/home:/pontostroy:/X11/openSUSE_13.2/ (snapshot) https://web.archive.org/web/20150919024231/http://download.opensuse.org/repositories/home:/pontostroy:/X11/openSUSE_13.2/x86_64/ Replaced all installed system packages by the ones from that repo. Including: Mesa-11.1~git20150917-1.1.x86_64.rpm libX11-6-1.6.3-40.1.x86_64.rpm xf86-video-ati-7.99.99~git20150822-1.2.x86_64.rpm KSP.log http://pastebin.ca/3165739 ~/.config/unity3d/Squad/Kerbal Space Program/Player.log http://pastebin.ca/3165740 Sadly it didn't helped at all :-/ Regarding this post of you. http://forum.kerbalspaceprogram.com/threads/117130-Service-bays-and-fairings-z-fighting?p=2202418&viewfull=1#post2202418 I really don't think changing the display manager will help. But I tried logging in graphically with an empty session (without any desktop environment). Then I started metacity (the old Gnome2/Mate window manager) and tried KSP. Still the same bug :-/ I also tested the AMD/Radeon proprietary drivers. They actually fixed the bug. But on the opposite they completely broke my display setup (luckily I back-upped it before) and actually gave me a worse performance than the open-source drivers. So I went back to the open-source drivers. But: Now we know it's definitely the drivers! Maybe we should get in contact with the driver developers. https://wiki.freedesktop.org/xorg/radeon/

I already tried starting Kerbal like this, but it didn't helped: env LC_ALL=C LANG=C vblank_mode=0 force_s3tc_enable=true ./Launcher.x86_64 env LC_ALL=C LANG=C vblank_mode=1 force_s3tc_enable=false ./Launcher.x86_64 env LC_ALL=C LANG=C ./Launcher.x86_64 ./Launcher.x86_64 I also tried setting the graphics (in the launcher) to maximum and to minimum. And I tried using KSP.x86 (my Launcher usually starts KSP.x86_64). And I tried enabling and disabling the 3D acceleration of my window manager (KDE - KWin). Nevertheless, I think we have to search for the problem in 2 places: 1. The graphics driver. At least about me I can say, that I have 2 computers with EXACTLY the same Linux installation. openSUSE 13.2, KDE, all updates/patches installed. But the bug only appears on the one with and AMD CPU and Radeon GPU. On the notebook with the Intel i7 CPU and GPU, everything is fine! 2. The developers should have a look about what they did different when programming those "modern" parts like "Airstream Protective Shell". There must have been some difference in the development process (different tools used, different kind of texture format, ...) which causes those parts to graphically fail but all other parts to be displayed correctly. Regarding this post of you: http://forum.kerbalspaceprogram.com/threads/117130-Service-bays-and-fairings-z-fighting?p=2202418&viewfull=1#post2202418 Installing Mate would be pretty much effort. I got GNOME 3 installed and could use it for testing. But I really don't think that this would make a difference. Also, because my Intel-GPU notebook is using KDE and KWin too.

Sorry, I don't use Ubuntu/Debian on my desktop pc and notebook. I'm running openSUSE. But I'll try to find an equivalent openSUSE driver repository. https://software.opensuse.org/package/xf86-video-ati Guess it's one of these. I'll see if I'm finding some time for testing it on the weekend. http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_13.2/ http://download.opensuse.org/repositories/home:/Ground0:/branches:/home:/pontostroy:/X11/openSUSE_13.2/ http://download.opensuse.org/repositories/home:/pontostroy:/X11/openSUSE_13.2/ I already tested the newest Mesa3D 11.0.0 library by compiling it myself and using it, by setting LD_LIBRARY_PATH. But that didn't helped. http://mesa3d.org/ Compiled Mesa3D for 32 bit (because I need it anyway for other 32 bit stuff) and for 64 bit and set LD_LIBRARY_PATH for both. (for KSP I'm always using Launcher.x86_64) $ env LD_LIBRARY_PATH=~/opt/mesa3d/lib64:~/opt/mesa3d/lib LC_ALL=C LANG=C vblank_mode=0 force_s3tc_enable=true glxinfo | grep 'OpenGL ' ATTENTION: default value of option force_s3tc_enable overridden by environment. ATTENTION: default value of option vblank_mode overridden by environment. OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD CAICOS (DRM 2.39.0, LLVM 3.5.0) OpenGL version string: 2.1 Mesa 11.0.0 OpenGL shading language version string: 1.30 OpenGL extensions: OpenGL ES profile version string: OpenGL ES 2.0 Mesa 11.0.0 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16 OpenGL ES profile extensions:

Used a fresh KSP installation from Steam. start command: env LC_ALL=C LANG=C vblank_mode=0 force_s3tc_enable=true ./Launcher.x86_64 Build a Mk1-2 Command Pod with a small tank and 2,5m fairings, encapsulating the tank. Put the vehicle on the launch pad. Bug appeared in the building facility and on the launch pad. KSP.log http://pastebin.ca/3165019 ~/.config/unity3d/Squad/Kerbal Space Program/Player.log http://pastebin.ca/3165021

Probably. I got the bug on my PC (see hardware details on page 1). But at least on my notebook (running the same Linux as my PC) with Intel GPU (Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller) the bug isn't appearing. I guess the bug may also appear on NVidia GPUs, when using the open-source Linux graphics driver. Because the NVidia open-source Linux graphics drivers uses a lot of stuff, the open-source Radeon driver is using too. Anyone here having an NVidia GPU? Do you have the bug? Do you use the open-source Linux NVidia drivers or the proprietary NVidia Linux drivers? Anyone having the bug, using the proprietary Radeon Linux drivers?

Found a bug report and some other threads about this. See here: http://bugs.kerbalspaceprogram.com/issues/4787#note-2

Found a bug report and some other threads about this. See here: http://bugs.kerbalspaceprogram.com/issues/4787#note-2

I don't use the proprietary driver and I really would like not to install it. Every time I had to use the proprietary driver since ever, it broke my X-Server configuration in some way. But I tried to use the newest Mesa3D library. Sadly it didn't helped. On the other hand, on my notebook (running same OS + software) everything is fine. But the notebook has an Intel GPU instead of a Radeon GPU. For details, please see this bug report: http://bugs.kerbalspaceprogram.com/issues/4787#note-2 P.S. If it might help you to find the bug with the Opensource Radeon driver, I might give the proprietary driver a try and tell you if it shows the same bug. But I don't like to use the proprietary driver normally. Because usually the Opensource driver does a really fine job on my system.

Having this issue too. Everyone, let's report some system details so the Squad support can start fixing this. By the way: Anyone from Squad reading this? Is there already a bug report here? http://bugs.kerbalspaceprogram.com If further information is needed, please tell me! I'm experiencing the bug on the following system, running "Launcher.x86_64". OS: Linux # uname -a Linux Trada 3.16.7-24-desktop #1 SMP PREEMPT Mon Aug 3 14:37:06 UTC 2015 (ec183cc) x86_64 x86_64 x86_64 GNU/Linux # cat /etc/issue Welcome to openSUSE 13.2 "Harlequin" - Kernel \r (\l). CPU: # grep 'model name' /proc/cpuinfo | uniq -c 4 model name : AMD Phenom II X4 955 Processor GPU: # /sbin/lspci | grep VGA 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] GPU drivers: # lsmod | grep drm drm_kms_helper 65670 1 radeon drm 335594 7 ttm,drm_kms_helper,radeon # glxinfo | grep -E 'direct rendering|OpenGL version string' direct rendering: Yes OpenGL version string: 3.0 Mesa 10.3.7 RAM: # free -m total used free shared buffers cached Mem: 12037 9530 2507 52 429 6214 -/+ buffers/cache: 2886 9151 Swap: 10239 20 10219