TheBlazinLoony
-
Posts
10 -
Joined
-
Last visited
Content Type
Profiles
Forums
Developer Articles
KSP2 Release Notes
Posts posted by TheBlazinLoony
-
-
You have run out of memory (KSP is a 32bit process, and thus restricted to about 3.4GB memory usage, no matter your system RAM). Please remove some part mods, use Active Texture Management (or up the scale= line if you do), or run KSP in OpenGL mode (risky but seems to work for many people).
I have already tried running in OpenGL mode, if anything it crashed more (with the same error). I am also already using texture reducing mods as I was aware I would have issues regarding memory when reverting back to 32 bit.
What I am still confused about is the fact that my memory is displayed as "0 MB", which is not normal and would obviously cause problems like mine, I just have no idea what is causing this. I have tried removing large parts mods just in case, with no success.
-
After updating to 0.25 (changed to 32 bit in order to use many mods which will not support x64) I am having seemingly random crashes within a few minutes of starting the game. Some textures are also playing up, with the directional nodes on the nav ball flashing between the correct symbol and what seems like 4 symbols in a square rapidly, and parts being translucent compared to the launch pad.
The error report seems to show that I have 0 RAM, although all other games/programs are running perfectly, and my PC specs are:
Intel Core i7-4770K @ 4.2GHz
16.0GB RAM (I am aware 32 bit only makes use of 3.5 )
64-bit Windows 7 Home Premium
NVIDIA GeForce GTX 760
Here is what the error report throws out:
Unity Player [version: Unity 4.5.2f1_9abb1b59b47c]
KSP.exe caused an Access Violation (0xc0000005)
in module KSP.exe at 0023:0038bf96.
Error occurred at 2014-10-23_175232.
C:\Users\Tom\Desktop\KSP_win\KSP.exe, run by Tom.
34% memory in use.
0 MB physical memory [0 MB free].
0 MB paging file [0 MB free].
0 MB user address space [114 MB free].
Read from location 00000004 caused an access violation.
Context:
EDI: 0x00000004 ESI: 0xfb63f144 EAX: 0x03310dc4
EBX: 0x00fcf3e8 ECX: 0xec8f0028 EDX: 0xeccf0028
EIP: 0x0038bf96 EBP: 0x00fcf3d0 SegCs: 0x00000023
EFlags: 0x00010202 ESP: 0x00fcf3ac SegSs: 0x0000002b
Bytes at CS:EIP:
8b 1f 89 77 fc 8b 46 08 81 e3 00 00 00 c0 c1 e8
Thanks to all you helpful people in advance, I'm off to Elite: Dangerous for now!
-
You are mistaken. I use it in 0.21.1 every day.
Ah, so I am, was misled by the "0.20.x" tag. Thanks!
-
Look for Subassembly Manager.
Seems like that only works for 0.20, unless I am mistaken?
-
I was just wondering if any of you guys knew of a sub-assembly loader type thing for 0.21. I'm pretty sure I had one before the latest update of 0.21.1 but I cannot for the life of me remember what it was called!
If any of you could post a link to one that would be awesome.
Thanks!
-
This is a brilliant idea, I was just thinking last night that something like this was needed! Great job!
KSP crashing and thinks I have 0 RAM
in KSP1 Technical Support (PC, modded installs)
Posted
Thanks for the info, I shall take a look.