Bug #4787
new fairings and service bays rendering issues on linux using opensource radeon graphics driver
100%
Description
The new fairings and service bays render is very glitchy on my system. Specifically I am running:
Arch linux 64bit
ATI Radeon (http://www.asus.com/Graphics_Cards/EAH6850_DC2DIS1GD5/) video card, using the opensource radeon driver (https://www.archlinux.org/packages/?name=xf86-video-ati)
64bit KSP linux install
To reproduce, create a new fairing or load a Service Bay in the VAB.
Service bays ONLY glitch out in VAB/SPH, once launched they work as intended (fantastic at that).
Fairings glitch out both in VAB/SPH and during launch.
Glitches look like textures are flickering very fast. Moving the mouse around or stopping it seems to affect the frequency of this flickering.
Happens both with Anti-Aliasing turned ON, as well as turned fully OFF.
Screenshots attached, fairings are pretty much un-usable in this state, the service bays are definitely usable just a bit glitchy inside the VAB/SPH
History
#1 Updated by drazed over 9 years ago
Also of note, the heat-shield cowling (between the stack separator and heatshield) exhibits the same glitchy behavior.
#2 Updated by kolAflash about 9 years ago
Having the same problem. See my system details here:
By the way, on my notebook everything is working fine. It has exactly the same OS + software running, but the hardware is different (Intel GPU).CPU:
- grep 'model name' /proc/cpuinfo | uniq -c
4 model name : Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz
GPU: - /sbin/lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
I tried to use the newest Mesa3D 11.0 version (compiled it myself), but that didn't helped too.
http://mesa3d.org/relnotes/11.0.0.html
Some other forum threads about this:
http://forum.kerbalspaceprogram.com/threads/117186-Fairing-Texture-Issue
http://forum.kerbalspaceprogram.com/threads/117130-Service-bays-and-fairings-z-fighting
#3 Updated by Ruedii over 8 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Seems resolved as of 1.1. Reopen if it isn't.
#4 Updated by TriggerAu over 8 years ago
- Status changed from Resolved to Closed