Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by Lumaan

  1. [ERR 04:58:23.422] AssemblyLoader: Exception loading 'CC_RemoteTech': System.Reflection.ReflectionTypeLoadException: The classes in the module cannot be loaded. at (wrapper managed-to-native) System.Reflection.Assembly:GetTypes (bool) at System.Reflection.Assembly.GetTypes () [0x00000] in <filename unknown>:0 at AssemblyLoader.LoadAssemblies () [0x00000] in <filename unknown>:0 Additional information about this exception: System.TypeLoadException: Could not load type 'ContractConfigurator.RemoteTech.RemoteTechProgressTracker+FakeSatellite' from assembly 'CC_R
  2. Need to have a look at the log file from KSP_Data folder, or it's hard to see whats going on.
  3. You are hitting the max RAM a 32bit program can use. KSP is running out of RAM it can use. From your error.log.
  4. But yeah, you are running into "out of memory" *32bit KSP can only use up to 3.5/3.7Gb RAM* From error.log Show that KSP can't use more memory within the space a 32bit program/game can use, and crash.
  5. *From error log 5* You are running into "out off memory" So KSP is trying to go past the max memory a 32bit program can use *around 3.5-3.7Gb RAM* Install this memory monitor mod http://forum.kerbalspaceprogram.com/threads/92907 *or find it on CKAN as "Graphic Memory Monitor"* to keep a eye on your memory.
  6. Using "-force-d3d11" when running KSP? When I used it some time back it did what you are getting, periodic lag, but never in VAB/SPH.
  7. You are running out of memory KSP can use *around 3.5Gb memory*
  8. There is no official 64bit of KSP right now, they tried before on a older build of Unity3d and it didn't really work, but there is a unofficial 64bit workaround here http://forum.kerbalspaceprogram.com/threads/117224-Windows-64-bit-community-workaround but by going this way there is no support if game crash.
  9. KSP is running out of memory it can use *Around 3.35-3.7Gb on 32bit*
  10. Steam is using a program id number system that pulls the needed info on where it has installed the game/program from the registry. But then KSP don't need to know where it's installed, it know that where the KSP.exe is the root dir. and look after "GameData" and "KSP_Data" beside the KSP.exe.
  11. And 64bit is not official supported so best to use this post http://forum.kerbalspaceprogram.com/threads/117224-Windows-64-bit-community-workaround or http://forum.kerbalspaceprogram.com/threads/113069-WIN-1-0-X-KSP-x64-Total-Unfixer-v2-2-04-08-2015 to get support. This support forum is only for 32bit windows and linux 32bit/64bit(?)
  12. From the log you are running out of memory with KSP. So you need to lower the RAM use with your mods *Take out memory heavy mods or lower the resolution of the texture files within the mods*
  13. Are you using "-force-d3d11"?? It maked my KSP stutter in 64bit.
  14. KSP is running into the 3.5Gb Memory wall, so it runs out of RAM
  15. You are having the "normal" "out of RAM" crash How much RAM (Memory) do you have? System and Video..
  16. @ArkaelDren - No matter what then we (mod-user) don't have any right to demand what mod-maker do to there mods. And so long Unity(Squad) can't make a stable(official) 64bit version, we can't demand mod-makers to make there mods work in 64bit.
  17. Can't see anything in the log. What mods do you have installed?
  18. Without a list of the mods you use and a log it's hard to help + what spec you PC have. ATM is only slow the 1st time after installed or when new mods with texture where it needs to do it's stuff on.
  19. @Youen But the thing is that MM is working on 64bit, only showing the "rainbow" cat as a warning that you run 64bit. And from my knowledge serbian don't support 64bit yet he's not blocking he's mods from running, just warning about it. So really no need to unfix MM. And I like to see the "rainbow" cat, knowing that it is my 64bit KSP I was running.
  • Create New...