- KERBAL SPACE PROGRAM 2 SPECS DRIVERS
- KERBAL SPACE PROGRAM 2 SPECS 32 BIT
- KERBAL SPACE PROGRAM 2 SPECS SOFTWARE
- KERBAL SPACE PROGRAM 2 SPECS CODE
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.
KERBAL SPACE PROGRAM 2 SPECS CODE
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.
KERBAL SPACE PROGRAM 2 SPECS SOFTWARE
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. This game wouldnt be playable in a classroom setting without heavyhanded assistance from someone who knows what they are doing.I've had an interesting experience with KSP 2. For banjo and kazooie n&b you create vehicles to solve whatever your goal is at the moment, where as this game your first goal is to launch your rocket off the ground, then its get to the moon, then its progress further beyond the moon where the smallest detail could cause your rocket to explode and killing your astronaut. The closest game I would say is banjo and kazooie nuts and bolts but that game didnt have the detail as Kerbal Space Program. This game is really a one of a kind game, theres nothing really like it. This game is not something you can play on a short burst or a game where you can pick it up in a single class, this is a long game and rewarding due to its game design. You don't need a ton of prerequisite knowledge to get started but to get anywhere you really have to try and actually research techniques that will help you succeed in leaving the galaxy. This game is about engineering and rocket science. This game is extremely complex, high school students or college students really. This is a huge timesink, I cant stop myself. It encourages creativity but if you want to be successful you have to combine actual engineering techniques and its a blast to surpass yourself on previous runs. I love the idea of building your own rockets and getting far far far away. This is a game I played way too much, I have like 200hrs on it on steam.
0 kommentar(er)
