Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
It is however likely to be some sort of problem with your system. I say this because very few people complain about this kind of behaviour.
My recommendation would be to do some RAM testing. Remove half of it and see if the problem persists. If it does, swap halves out. Run Memtest.
Do you have any active anti virus memory scanners that could be interfering?
Sorry man, but no real other way to describe a one off issue
I'm not saying its a hardware issue, just pointing out a faulty premise. Having specs capable of running something doesn't always mean the machine will.
I fully agree that set up should run this game just fine.
Without being able to see it, play around with it myself, tough to troubleshoot since it sounds like you have done some digging on the game end. All I can really tell you is it isn't a common problem.
Do you have an inordinate amount of stuff flying around simultaniously? This game has been known to get wonky in various interesting ways if you have piles of large space litter flying around.
Much ppl think its so good cause of its core count... but in real this FX CPUs are not really gaming machines... okay i know AMD has nothing better to offer atm... but against an I5 the loose in indi games so much power
KSP has a 32 bit version and a 64 bit version. If you have never changed the command in KSP's properties in steam, you are running the 32 bit version even if you have a 64 bit windows (which you should).
The 32 bit version of KSP, like any 32bit program, has limits on how much memory it can use and will start to behave badly as you approach those limits, frequently crashing but sometimes lagging. Stock KSP won't use up that much memory, but if you have a bunch off mods installed you can easily hit this limit.
The 64 bit version of KSP, like any 64bit program, has memory limits so high you will likely never encounter them. Unfortunately, the windows 64 bit version of KSP is very buggy right now, and can lag and crash even with zero mods installed.
So: If you are using the 64 bit version of KSP, drop back to 32 bit. If you are already using the 32 bit version of KSP, try un-installing some mods and/or google up the active texture management mod which can reduce your other mods's memory usage.
Good luck.
and i am alsop running it with everything set to "High" still no fps drops or anything....
http://forum.kerbalspaceprogram.com/threads/93096-micro-stutter-freezing
Long story short kerbal space program uses a rather poor engine called unity. It does not work with multicore at all and causes many problems for many users with multiple cores.
while some may not notice the stutter i have read that many have it. i guess its just about having a refined eye for this sort of stuff. my detection of the stutter may be a bit better than those who claim not to notice.
I thank you for your opinions but many of you posters are just flatout wrong or voicing personal opinion as though it were fact.
The simple FACT of the matter is that many people have problems with games in the unity engine (same goes for kerbal) and that thread has many good points on it.
Make an account and loggin so you can click the link midway down to go to the real discussion it is worth it just for the read on how unity works.
But seriously you should not blindly throw your opinion around about how you know what causes these problems and its an end user thing when it turns out. You just pulled that out of your butt and its an unavoidable engine issue that many people end up having. So knockitoff with the Fanboyism and Brand Hate and try to have a discussion.
If you can climb down from your high horse for just a second and read this thread, it might actually help you.
I had not run it yet but after reading your post i had to do it. So memtest ran from geekstick during bios startup and we are all good on all 16 gigs of ram.. but then to quell any other doubt in my mind i pulled the paired sticks and alternated them and did two seperate reboots..
The game had frame issues every time.. No different from any other time. Not to mention i have run this game on two seperate drives. A ssd and a 3.0 usb external hdd. No difference.. so source drive speed is out of the question.
SO YES thank you for your recomendations but at this point after the testing has been done i must INSIST.. that it is a problem inside the unity engine that shows itself in certain setups and it just so happens that i have one of those setups.
However not all is lost as I am reading that I may be able to use cpu affinty settings to mess around and get it to smooth out.. we will see.
Its just unfortunate, but it seems that slowly but surely the overall gaming industry is headed in the direction of multicore. kerbal and multicore would be a perfect match.
Thank you for all the recomendations. I will do more reading but i doubt i will find relief as the more I research the more i find it is a single core engine that just does not like multicore.
In the future i would recomend that people take more effort to blame people less when they come in looking for help with a problem. you should assume i had done most of my research ahead of time and that bothering others with my problems would be a last resort.
Reduce the amount of mods or delete some of the parts they include you do not use.
If forcing opengl, which increases the load on the CPU, try running the game normally or try forcing DirectX 11. If already forcing DirectX 11 of course switch to trying to run the game normally. Doing this may mean to reduce the amount of mods you use.
Try editing the settings config for oceans: minDistance=4, minSubdivision=1, maxSubdivision=6
Lower the resolution.
Of course lowering other graphic settings will help.
I am not sure that the update caused the game to be more CPU intensive but it is my guess.
Do you run the enhanced clouds mod, have you tried a lower rez pack from the cloud selection in that mod?
I agree though im afraid naturally kerbal has gotten slighly more demanding, given i struggle to play and record fraps now, whereas before it was a breeze in 23.5
Sorry I didn't think of it. Coulda saved you some digging around.
Intel CPUs and Nvidia GPU for gaming man. It won't avoid every problem, but goes a long way.
CPU yes.. GPU no NVIDIA only was 3 years ago now ATI is equal