Terrain textures glitched out

[Maolagin]

KSP Version: 0.25.0

Platform: Debian 64-bit

What Happens: All planet surface textures (except for the KSC itself) are glitched out, appearing either black, black with visual noise, or one one occasion starfield with visual noise. See screenshot below for a representative example. This problem is new in 0.25.0 -- on the exact same system with the exact same graphics settings 0.24.2 works normally.

Mods / Add-Ons: None, freshly unpacked stock

Steps to Replicate: Start KSP. On my machine this is 100% reproducible.

Result: See screenshot

Fixes/Workarounds: None that I have found.

Other Notes/Pictures/Log Files:

My graphics settings below are typical. However, 0.24.2 works normally across a wide range of settings, and 0.25.0 displays the buggy rendering in every graphics setting I have tried. In particular, I have already tried both fullscreen and windowed, resolutions down to 640x480, render quality, light quality, texture resolution down to minimum values, and turning AA off.

My settings.cfg is currently using:

SCREEN_RESOLUTION_WIDTH = 1280

SCREEN_RESOLUTION_HEIGHT = 864

FULLSCREEN = True

QUALITY_PRESET = 4

ANTI_ALIASING = 4

TEXTURE_QUALITY = 0

SYNC_VBL = 1

LIGHT_QUALITY = 8

SHADOWS_QUALITY = 4

FRAMERATE_LIMIT = 120

FALLBACK_PART_SHADERS = True

PLANET_FORCE_SHADER_MODEL_2_0 = False

PLANET_SCATTER = True

PLANET_SCATTER_FACTOR = 0.5

AERO_FX_QUALITY = 3

System: HP Elitebook 8540p with Nvidia GT216M graphics

Hardinfo report: http://pastebin.com/YEjGBFMB

Player.log: http://pastebin.com/BUEMcAxd

Here is a screenshot of the behavior:

[SasquatchQB]

I had similar issues with an Nvidia GeForce GTX 260 when I first installed 0.25. I had luck with disabling antialiasing in KSP itself and forcing it through the Nvidia utility (I'm running Manjaro 8.10, but I believe the issue with AA isn't limited to one distro or another). sal_vager mentions it in this post on The Linux Thread - http://forum.kerbalspaceprogram.com/threads/92231-The-Linux-Thread?p=1380988&viewfull=1#post1380988.

Edit: I read it the first time, and it still slipped my mind - I blame the late hour. You already said you tried disabling AA.

Edited November 21, 2014 by SasquatchQB
Edited for late hour inattentiveness.

[steve_v]

Looks like you're running nouveau / Gallium, have you tried the NVIDIA binary drivers?

Also maybe worth mentioning, reports from Arch linux that running the 32bit build on a 64bit OS with multilib can cause graphical issues - you are running 64bit KSP right?

Edited November 21, 2014 by steve_v

[Maolagin]

Yup, this system is running the nouveau drivers. I'll see if I can switch over to the binary ones to test, and I'll also try updating nouveau. However, I'd still argue that this is a regression, since the immediately previous release worked perfectly in the same setup, and the observed behavior is more severe than simply reduced performance.

I forgot to note in the report, I did also try the 32-bit version. Idential behavior.

[steve_v]

0.25 works just as well as 0.24.2 for me - with the NVIDIA driver. I'm also running Debian sid but I haven't tried nouveau since (historically at any rate) it causes boot failures with KMS on this machine.

Desktop system with a _slightly_ beefier GPU though

I tempted to say that GPU doesn't have a lot of VRAM - maybe the requirement for 0.25 is higher & you're not able to load all the textures? But I'd expect something in the logs if that were the case...

[pypi]

I'm running Arch Linux (64 bit, 84 series GPU, nouveau drivers). I had an identical problem, although I've only tried KSP 0.25 on this machine; after some fiddling I discovered that disabling SM3 fixed the issue (for me). Does that help?

I've had no such issue on a slow Intel GPU.

pypi

[Maolagin]

I'm running Arch Linux (64 bit, 84 series GPU, nouveau drivers). I had an identical problem, although I've only tried KSP 0.25 on this machine; after some fiddling I discovered that disabling SM3 fixed the issue (for me). Does that help?

I've had no such issue on a slow Intel GPU.

pypi

Interesting. Pretty sure I tried that in 0.25 and it didn't help, but I just turned off SM3 textures in 0.90 and I'm back in business. With crappy-looking terrain of course, but flying and not glitching. Yay!

[Aristarchus]

Interesting. Pretty sure I tried that in 0.25 and it didn't help, but I just turned off SM3 textures in 0.90 and I'm back in business. With crappy-looking terrain of course, but flying and not glitching. Yay!

I was having the same problem with my GeForce 8400 graphics card with all graphics to their lowest setting except SM3. Saw your post last night, turned it off, and now Kerbin is no longer a giant, headache inducing disco ball. I can't wait to play tonight. Thanks.

[Kendrick]

try turning off Edge Highlighting (PPFX) and see if the game works normally

[JSilvanus]

I had this same problem when running KSP 1.0.4. in Linux (Ubuntu 15.04 LTS 64bit) through Steam. The problem was fixed when the game was started manually using the 64bit executable instead of the 32bit. I hope this information is helpful to your case as well.

[sal_vager]

This is pretty old, over 6 months in fact, I'd hope that Maolagin would have figured it out by now, usually this is an anti-aliasing issue with the proprietary AMD driver but I bet it'd effect the older Nvidia cards as well.

Now it's interesting that you fixed your issue by using the 64bit binary, you likely don't have the 32bit mesa libraries installed, but I'm glad you found a fix

Setting as solved as it should be by now, and closing as it's old old old.