The Attack of the Rainbow Textures.

[mikeysilke]

So I have been having a problem with my KSP. And, I'm not sure if this is a problem with my download because I have taken a flash drive with my game download on it and it had been broken on other macs at my school. I have a small example that I captured before it got serious, http://i.imgur.com/oJmkiWu.jpg , and if you look at the RCS port and the ASAS module, you can see what happens, but this happens every time I get on, I have inquired before, and people have said overheating problems, but this is not the case. I do not have the logs, as I am not entirely sure where to get them, because the game doesn't crash, it's just the textures mess up. I hope that you guys on the forums can help me, because I want to play some goddamn KSP! :D:mad:

- - - Updated - - -

I have a 2010 27' imac with 24 GB of ram.

[Cad01]

Finding logs ->

http://forum.kerbalspaceprogram.com/threads/92230-%21%21%21-PLEASE-READ-BEFORE-POSTING-%21%21%21-Stock-Support-Bug-Reporting-Guide

[spoiler: Crash/Output Logs]When KSP crashes it will general a folder with files with details surrounding the crash. Usually a window will pop up ingame asking you to send this information to the developers, along with the name of the folder. You can find this folder in the KSP install directory.

If KSP doesn't crash, start KSP and cause the problem. Quit KSP and find the output_log.txt (not the KSP.log) at the location below:

• Windows: KSP_win\KSP_Data\output_log.txt -OR- KSP_win64\KSP_x64_DATA\output_log.txt (depending on which used)
  - In case you installed KSP into a Windows protected directory (C:\Users, C:\Program Files or C:\Windows\ and their subfolders) the output log file may be stored in the folder called C:\Users\[username]\Appdata, this folder is usually hidden so you should enable the view hidden folders option (more information). Note that for the demo you should find the output_log.txt file located in the KSP_Data folder.
  - Steam users should right click KSP in Steam, click on Properties, then in the Properties box, click Local Files, then Browse Local Files.
  
• Mac OSX: Open Console, on the left side of the window there is a menu that says 'files'. Scroll down the list and find the Unity drop down, under Unity there will be Player.log Aka Files>~/Library/Logs>Unity>Player.log
  
• Linux: The log is written to /home/user/.config/unity3d/Squad/Kerbal Space Program/Player.log
  

You can upload these files to any file sharing site (such as Dropbox, Mediafire or File2web). These sites will give you a link you can include in your posts to share your files.

The output and crash logs are useful because they help us understand exactly what you were doing when the issue happened by providing a "play-by-play reenactment" (in text form) of your KSP session. Anything out of the ordinary will often show up in the log files, and it gives us a good idea of where to start looking for solutions.

- - - Updated - - -

It mostly running out of memory setting textures to half res should help you out here

[mikeysilke]

Why would I have to lower the graphics, I should have enough memory, as you can see i have 24GB Ram! I should be plenty fast!

[Cad01]

I'm just telling what helped other people but without your player.log i can't help you at all. I know it's frustrating, I had the same problem.

[Jouni]

0.90 seems to be less stable on Mac than earlier versions. If you switch too many times between the VAB and the simulation, the game will eventually crash, develop rainbow textures in the VAB, or show giant shadows in the simulation. There may be a memory leak somewhere, so switching to lower graphics settings may help to delay the symptoms.

[Wallygator]

As referenced in the latest dev notes, they are finally setting up a dedicated OSX test system. Hopefully by the next release we will have some relief regarding our unique OSX issues (assuming they are not Unity specific).