Realsim Overhaul not loading

[MasterBurte]

Hi,

I have installed KSP 1.0.5 and 1.0.4. On the 1.0.4 version I installed Realism Overhaul and some suggested mods with CKAN. Now it's not loading it stopped right where it is on the picture. I noticed that there could be issius with the yellow marked mods in the list.

How can I fix this? 1.0.5 is running well.

[IMG]http://s21.postimg.org/kvmv5pko7/KSP_Installation.jpg[/IMG]

Edit:
1. I deinstalled Testflight and VenStock Revamp. Same errror!
2. Tried to deinstall SolverEngines with CKAN. Can't because CKAN wants to remove other mods including RealismOverhaul when I try.
3. Deinstalled Testflight, Venstock and Procedural Parts. Now the KSP.exe stopps working before finished with loading. I think at nearly the same point (80%). Edited November 19, 2015 by MasterBurte

[ZooNamedGames]

Idk how you got RSS installed with CKAN as it isn't available for me but the issue is likely that your running out of ram (I'm guessing since the image won't load at my college). This is a game bug which is frequently seen on modded installs but more importantly-

RSS/RO isn't updated for 1.0.5 yet so your likely to run into a lot of bugs and issues. So I suggest waiting before using RSS/RO. Or use 1.0.4 to play RSS/RO.

[Speadge]

from sticky:

[QUOTE]
[CENTER][COLOR=#800080][SIZE=4][B]Reporting an Issue after you have followed the troubleshooting steps[/B][/SIZE][/COLOR][/CENTER]


To report an issue, please follow the following instructions. An issue report should contain the log, a set of reproduction steps, and be done in a clean environment with a list of the mod(s). [I]If you don't follow these instructions, modders will ask you to do so before providing help, and that just slows everyone down.[/I]

[B]Note that a number of mods maintain their own issue trackers.[/B] If a modder mentions (for example in the opening post for the mod, or the readme) that you should post your issue on their issue tracker (for example the issue tracker on Github) please do that rather than posting your issue here, but follow the same steps.


[LIST=1]
[*] [B]The Logs[/B]
These are text files that the game spits out for debugging purposes as it runs; if something broke horribly in-game, there will be something in here about it. You should upload the [B]entire [/B]log [I]as a file[/I] (i.e. not to pastebin); you can use [URL="https://www.dropbox.com/"]dropbox[/URL] or an equivalent host to upload the file. Make sure the entire file gets uploaded; you may have to zip it first, as logs can be very long. Here is where you can find the log:
[LIST]
[*][B]Windows:[/B] KSP_win\KSP_Data\output_log.txt (32bit) or KSP_win64\KSP_x64_Data\output_log.txt (64bit)
[*][B]Mac OS X:[/B] 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 ( Files>~/Library/Logs>Unity>Player.log )
[*][B]Linux:[/B] ~/.config/unity3d/Squad/Kerbal\ Space\ Program/Player.log
[/LIST]

NOTE: These logs are [B]not[/B] the same as KSP.log, which lacks valuable data. [B]Do not[/B] upload KSP.log; [B]do[/B] upload output_log.txt / Player.log


[*][B]The Reproduction Steps[/B]
These are essentially a recipe on how to cause the bug. If you don’t include reproduction steps, the modder won’t be able to reproduce the bug, and then can’t fix it. The more detailed you make this, the better. [B]Leave nothing out.[/B] Leaving out details can make bugs impossible to reproduce, and thus, impossible to fix. The gold standard for reproduction steps is an [I]unedited[/I] video of you causing the bug.



[*] [B]Clean Environment[/B]
If the issue stems from one mod, try to replicate it with [B][I]only [/I]that mod and its hard dependencies in a clean KSP install[/B]. If the issue stems from the use of several different mods (for instance, Procedural Wings are still producing lift underneath a Procedural Fairing while FAR is installed) then get a clean install of KSP and install [B]only[/B] the mods (and their dependencies, if applicable) in question.

This may seem like an extreme measure, but it ensures that only those mods (or the stock game) is to blame. Despite how complicated it may seem, it is actually quite simple to do (even for Steam users), as you can simply copy your install directory elsewhere as needed. It’s especially useful since interaction bugs are some of the hardest to nail down; something that appears to be a bug in one mod might actually be caused by something else.
[/LIST]

Regardless of how many mods are installed, [B]you should include a list of all mods installed [I]with their version numbers[/I][/B]; a screenshot of your GameData directory is [B]not[/B] sufficient, as it does not include version information and some directory structures may hide what mods are installed. Obviously, this is easier if you reproduce the issue with fewer mods.
[/QUOTE]

[CanadianDutchman]

I also have this problem for realism overhaul on 1.0.4 (even stops on the exact same moment) I don't want to upgrade to 1.0.5 because I've heard that 1.0.4 savegames are not compatible with 1.0.5.
if you want to delete 1 mod but CKAN deletes a bunch of mods with it just delete it from the gamedata folder (and back it up). then CKAN won't notice it is gone and you can test if that mod is the problem

[NathanKell]

You heard incorrectly. 1.0.4 saves are compatible.
If it's a career save (RP-0) don't upgrade yet, though, that's not out.

There were some metadata issues regarding 1.0.4/5 and RO mods, which should now be corrected. Do try removing (and then manually cleaning), and then reinstalling the 1.0.4 mods, if you want to play on 1.0.4.

[CanadianDutchman]

thanks for the info!
I'll try doing that tomorrow