GUI loads, but rest of screen and navball are black, KSP stops responding

[Cetera]

KSP: 0.90 Windows 32-bit

Problem: When trying to launch a vessel, the GUI loads, including staging, navball, toolbar, elevation counter, etc, but the screen/environment area is all completely black. Kerbin never loads, the rocket never loads, and the Navball itself is also all black. KSP at this point stops responding, and nothing seems to work (including trying to take a screenshot to illustrate).

Recreate/symptoms: I crashed (memory limit after a couple of hours of play) while launching a satellite. The satellite had not yet cleared the atmosphere. Upon reloading the game, the satellite launcher appears on the launchpad, but when I try to go into it to launch it, the above happens.

Closed the game again, relaunched, and now the rocket is not on the pad. Go into the Tracking station, and it has the satellite listed as "Splashed down" but the Tracking station screen showing Kerbin doesn't load, and is all black. I click on the satellite name and click the "kill/destroy" button. The game stops responding again. I repeated this, same result.

I make a backup of my save directory. Then I go into the persistent save file and delete the satellite from the save file. Relaunched the game again, this time everything seems better, the satellite isn't listed, and the Tracking Station loads. However, any attempt at launching any craft recreates the black screen issue described above.

Revert my save folder, relaunch the game, and go into the tracking station. It loads fine. Fly a vessel in orbit, and it loads fine. Do a ctrl+F9 to recover an older quicksave that should not have any corruption in it (I'll lose a few hours, no biggie) and the same thing happens when loading this lander on the moon (GUI fully populates, but the rest of the screen and navball are black, game freezes).

Log File: https://dl.dropboxusercontent.com/u/62531235/output_log.txt

Mods List: (I think I have them all, and correctly listed)

Active Texture Management x86 aggressive 4-3

ALCOR 0.9

ALCOR IVA 0.9

ASET Props 1.0.2

B9 Aerospace R5-2-8

Better Buoyancy 1.1

ContractConfigurator 0.6.5

ContractPack-AnomalySurveyor_1.0.1

Contracts_Window_3.2

CrossFeedEnabler_v3.2

Outer Planets Mod 1.5.5.1

Distant Object Enhancement 1.5.2

Editor Extensions 2.5

Enhanced NavBall 1.3.5

EVE 7-4

FASA 5.22

FAR 14.5.1

FreeEVA 0.3.0

FuelTanksPlus 0.6

Hot Rockets 7.9

Kerbal Attachment System 0.4.10

Kerbal Joint Reinforcement 2.4.5

Kerbal Alarm Clock 3.2.3.0

Kerbal Engineer 1.0.15.2

KSPRC 0.1.9.5

KW Rocketry 2.6d2

LazTek SpaceX Launch Pack .90

Magic Smoke Industries Infernal Robotics 0.19.3

MechJeb2 2.4.1.0

MechJeb and Engineer for All v?

MOARdv FASA Gemini IVA 2.0

Modular Rocket Systems Parts Pack 1.5.1

Module Manager 2.5.4

NavyFish DockingPortAlignment 4.0

Near Future Construction 0.4.0

Near Future Electrical 0.3.1

Near Future Propulsion 0.4.0

Near Future Solar 0.4.0

Near Future Spacecraft Parts 0.3.1

PlanetShine 0.2.2.1

RasterPropMonitor dev19

RCS Build Aid 0.5.5

RealChute 1.2.6.1

RemoteTech 1.6.2

SafeChute 1.6

SCANSat 10.0

SCART91 head textures

ScienceAlert 1.8.3

Smokescreen 2.5.3.0

SoundingRockets 0.2.0

SpaceY Lifters 0.11

StageRecovery 1.5.2.1

TAC Fuel Balancer 2.4.1.1008

Texture Replacer 2.2.5

Toolbar 1.7.8

Trajectories 1.1.3

Tweakable Everything 1.6

TweakScale 1.49

Universal Storage 1.0.0

VNG Parachute 1.2

VNG Plugin 0.7.2

Waypoint Manager 2.1.2

Any help here would be great. I'm guessing the save file got messed up with the vessel in a position where it probably couldn't be easily saved, but I would think that loading a previous save without this would resolve the issue. I'm really not sure what to do, and I really don't want to lose my progress on this save. Any help would be greatly appreciated.

Edited March 15, 2015 by Cetera
Editing Prefix to Workaround

[Cetera]

Here's a new output log. This is from the game crashing now when I try to launch a vessel.

Output Log 2: https://dl.dropboxusercontent.com/u/62531235/output_log2.txt

- - - Updated - - -

By the way, this crash is definitely not the normal "out of memory" crash. When it died, KSP had grabbed about 2.6 GB of RAM. A lot, but nowhere near the ~3.5 GB limit.

Also, here is a screengrab I was able to get trying to load the vessel on the launchpad, before the game crashes. The navball is still working in this screenshot. The center has not yet all turned black.

Edited March 13, 2015 by Cetera
inserting pic

[Cetera]

More to add. I was able to successfully take a named quicksave file, copy it to a new folder, name the folder as a new save, rename the named quicksave to persistent.sfs, and then edit the save file to put the folder name as the save name. Load the game, and load this new, renamed save, and everything works. Works well. I lost some game time, but it isn't the end of the world. I haven't fully tested everything yet, but it sure looks promising.

However, trying to load this quicksave from the original save-game still results in the black screen as shown above. I have no idea what could be causing corruption from the save that breaks other loaded saves, but that seems like something wrong more with KSP itself than with any mod I might be running. Especially since I can make a new save from a quicksave file and run it in the same installation of the game with the same mods, and have no problem.

Any thoughts there? This post has quite a few views, but no responses.

[Cetera]

OK, here's a screenshot of the issue as it is occurring. This is now happening too in the recovered save game I was able to get working. I really am not sure what the issue is now.

Edited March 13, 2015 by Cetera
inserting pic

[Cetera]

Anyone, anyone? Bueller?

[RainDreamer]

Noticed you got the "Look rotation viewing vector is zero." Might have something to do with texture replacer and some certain part having problems.

[Cetera]

Thanks, RainDreamer, for starting me off. I'll ask the Texture Replacer guys if they can help.

[RainDreamer]

I had the same problem before, but it was texture replacer interacting weirdly with ven's stock revamp. Since you don't use Ven's stock revamp, I am not sure. But it could be the case.

[Cetera]

Oh, I definitely do use Ven's Stock Revamp. It may not have gotten listed, as I don't think it makes its own folder in the GameData folder, and that is how I was cross-referencing what I have installed vs. what I have downloaded. Do you know what the fix was, or a workaround?

[Cetera]

I checked my GameData folder, and Ven's does have a folder there. I'm using 1.7.2, which appears to be the latest. Today 've also updated every single mod or checked every single mod that has parts (copy and pasting using TeraCopy and letting it run a hash check on each file) and they all are up-to-date or correct.

[Cetera]

Ok, after a very lengthy process of removing parts and trying to launch, I believe I've tracked the issue to the Gigantor XL Solar Array. Any vessel with that part on it has the error, and so far any that doesn't is fine. Any thoughts there?

[Tarheel1999]

Oh, I definitely do use Ven's Stock Revamp. It may not have gotten listed, as I don't think it makes its own folder in the GameData folder, and that is how I was cross-referencing what I have installed vs. what I have downloaded. Do you know what the fix was, or a workaround?

See my response in the TR thread but Ven's definitely has a folder in Gamedata. If you don't have it, you have an install problem in addition to other problems. You may also want to make sure you have current versions of all mods, like TR.

[Cetera]

OK, the root cause of this issue is the part redo in Ven's Stock Revamp mod. Commenting out the reflection part for the largesolarpanel in Ven's Texture Replacer config did the trick. There is something incompatible between Ven's redo of the Gigantor XL Solar Panel and Texture Replacer.

Tarheel1999 gave me the workaround here: http://forum.kerbalspaceprogram.com/threads/107471-0-90-TextureReplacer-2-2-6-%2810-3-2015%29?p=1786979&viewfull=1#post1786979

I'll edit this post to have the category of "Work Around." Thanks for your help, Tarheel!