- #Kerbal space program 2 specs install#
- #Kerbal space program 2 specs drivers#
- #Kerbal space program 2 specs 32 bit#
- #Kerbal space program 2 specs full#
Check our guide to the original Kerbal Space Program system requirements. Kerbal Space Program 2 release date for early access is set to February 24, 2023. However, the developers recommend a CPU greater or equal to an Intel Core i5-11500 to play the game. An Intel Core i5-6600K CPU is required at a minimum to run Kerbal Space Program 2. Futhermore, an NVIDIA GeForce RTX 3080 is recommended in order to run Kerbal Space Program 2 with the highest settings. Provided that you have at least an NVIDIA GeForce GTX 970 graphics card you can play the game.
#Kerbal space program 2 specs full#
If possible, make sure your have 16 GB in order to run Kerbal Space Program 2 to its full potential. Kerbal Space Program 2 system requirements state that you will need at least 12 GB.
#Kerbal space program 2 specs install#
The recommended requirements from the developers suggest you have 60 GB space in order to install the game. KSP 1 was pretty safe even with low frame rates, it was however loading issues with large surface bases.The minimum Kerbal Space Program 2 download size is 45 GB for installation. Had many rovers gotten their wheels stolen in KSP 1 and Elder scroll Oblivion had one there an Orc who would sell you an house might fall to his death because he loaded before an bridge. One weird race condition might be that you load environment and you load objects, you want the objects to be loaded before the environment and both before physic is applied.
#Kerbal space program 2 specs 32 bit#
Lack of memory is the most obvious one, this was an major issue in 32 bit KSP 1, also an serious issue on the PS 3 as it had little memory. Pretty common for games to get more buggy if they are pressed to the limit. And then there are all the workarounds only used near the minimum spec which no one on the development team uses so have seen less testing. Other timing-related bugs can show up on potatoes when the order things occur in changes due to a slow HDD, memory stalls, less parallelism, etc. A thread going through code that should have been mutexed has greater odds of getting preempted at a bad time on slow hardware as the Windows scheduler uses wall-clock time for time-slices, converting an exposure that might have been microseconds to milliseconds.
Race conditions are more likely on a potato.
#Kerbal space program 2 specs drivers#
Was your last PC up to date - windows updates, hardware drivers etc.? Or maybe really old CPU that wasnt supported perfectly? Edited March 11 by VlonaldKermanįor the poll: Substantial bugs means bugs which would preclude you from finishing your mission, were it not for quickloads, or that did cause the mission to fail. Software developers: is this possible? If so, why?įor the poll: Substantial bugs means bugs which would preclude you from finishing your mission, were it not for quickloads, or that did cause the mission to fail.
I don't think I can make this poll correlate the responses to the two questions, but I'm nonetheless curious to see if there's a trend between higher-end gear and fewer bugs. I'm wondering, then, what other peoples experiences are. Still many bugs, but a quickload usually resolves things. I would say that not only is performance much better (duh) but I'm having way fewer game-breaking bugs. I've upgraded my PC to a top-of-the-line build: its a falcon northwest PC w/ RTX 4090, i9 13900KS, 64 GB VRAM, etc. loading a quicksave usually spawned a new bug, rather than solving one. I experienced tons of bugs- teleporting KSC, vehicles spontaneously assuming landed state while in orbit, kraken attacks, etc. I started playing on my old PC which had a GTX 1070. I've had an interesting experience with KSP 2.
0 kommentar(er)
