Service bays and fairings z-fighting

[leopardenthusiast]

When I attempt to use the new stock fairings and service bays, they appear to have rather severe z-fighting. This does not happen to service bays in flight, but it still affects fairings. EDIT: This also affects the autofairings for heat shields, though like the service bays, they are fine in flight.

I am running KSP 1.0.0.0 from Steam

Hardware:

CPU: Intel i5-2500

GPU: Sapphire-branded Radeon HD 5770

RAM: There's 8GB of it

I am running Fedora 21, fully updated and running the open-source driver for my graphics card. I can provide any other information on request.

Edited April 28, 2015 by leopardenthusiast

[Supernovy]

What's your anti-aliasing set to in the graphics settings?

[leopardenthusiast]

What's your anti-aliasing set to in the graphics settings?

It's turned off.

[Supernovy]

Thanks.

Try turning it to 2x, to see if that does anything to the fairings and cargo bays.

[leopardenthusiast]

Turning AA to 2x has no effect.

[jhnphm]

Can also confirm this on Arch Linux, using open source drivers on Radeon 6870:

OpenGL vendor string: X.Org

OpenGL renderer string: Gallium 0.4 on AMD BARTS

OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.5.3

OpenGL core profile shading language version string: 3.30

[jhnphm]

Turned AA all the way up to 8x, still no effect.

Snippet from glxinfo, since previous post didn't show up, below. Running on Arch Linux via Steam.

OpenGL renderer string: Gallium 0.4 on AMD BARTS

OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.5.3

OpenGL core profile shading language version string: 3.30

[sal_vager]

Several people are having texture issues, it seems driver related so please check your graphics driver and update it if required.

[GreeningGalaxy]

I've got this too, on Debian 8. Antialiasing doesn't normally work at all in my experience with my card and any distro, unless I install fglrx/Catalyst and force-enable it with amdcccle. Since fglrx/Catalyst tends to thoroughly break the graphics in several of my other games, I prefer not to install it, so I don't know if the fairing z-fighting occurs under Catalyst as well.

I hope this can be fixed, because it often gives me a headache, and fairings aren't exactly optional with the new aerodynamic system. :/

[kolAflash]

Found a bug report and some other threads about this. See here:

http://bugs.kerbalspaceprogram.com/issues/4787#note-2

[sal_vager]

Is this issue only occurring with the Radeon driver?

[kolAflash]

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?

[sal_vager]

The open source drivers do share a lot of parts, so it may be worth testing the drivers from the Oibaf PPA, these are more recent than those in the Ubuntu repositories and include updates to X as well.

[kolAflash]

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:

[sal_vager]

Another member, E.Nygma, says he solved this by changing to the Mate desktop with the Slim display manager, would you be able to test this?