If you're discouraged by Kerbal Space Program's immediate difficulty, do not despair. It takes hours and hours of dedication, but it's a rewarding experience. Even managing this, you still have a lot to overcome before you can land on one a planet. Achieving escape velocity is relatively easy, but finding a stable orbit is a whole other challenge. Kerbal Space Program is tough because it's realistic, like every good simulator. From the moment you make your first rocket, until you finally send a crew of astronauts successfully to the moon, the difficulty is pretty high. The cuteness of the Kerbals shouldn't make you think there is anything easy about Kerbal Space Program. You'll research new technologies in the the Space Center, learning from your successes and failures, training astronauts and so on. In Career mode, you progress through missions, with a tight budget. Hit the space bar, and it will hopefully go through the various stages you defined on its way to space. You won't find out until launch whether or not your rocket will be successful. You can do what you want, but your rocket will still conform to physics, so they will often result in spectacular and explosive failure. Squad or the KSP devs would be willing to provide source code from before the game was released,įor possibility of compiling and optimising for arm.In sandbox mode, there are no limits to the design of your rocket. This is a relatively heavy game as it is and the Pi is underpowered. Overclocking might potentially help a bit There is the possibility of wrapping OpenGL ( this stackexchange post),īut this probably wouldn't improve performance much and might not run at all due to empty wraps.Īll of these tests were on a Pi 4 4GB with no overclock. _ksp1.5.1.mp4ġ.12.4: Snail in treacle, used ~9GB of RAM (i am glad i had ZRAM installed) and takes ~2 hours to load the menu screen. ksp1.0.5.mp4įor these following two versions I used LIBGL_ALWAYS_SOFTWARE=true to render in software rather than the GPU as they require OpenGL 3.2+.ġ.5.1: Runs terribly, takes ~20 min to load menu screen, only playable if you enjoy imposing mental pain on yourself. In practice the screen recording does not make any difference to the FPS of KSP.ġ.0.5: Runs ok, runs at 5-15 fps, takes ~10 min to load menu screen, renders on GPU, playable if you're willing to put up with the low FPS and limited part selection (Edit: "limited part selection", expansions prevent the game from loading). I tested three different versions with about the same gap between. It said the box86 stuff, Importing game controller configs, and then aborting.Īnd a black window opens, then closes when it says aborting Support/gog_com.shlib: line 94: 22768 Aborted $įor me, using the GOG games installer, a black window pops up for a moment, then $ "/home/pi/GOG Games/Kerbal Space Program/start.sh" "-launcher"įor me, using the GOG games installer, a black window pops up for a moment, then I don't own the GOG version, I bought it straight from the, so I didn't have the GOG stuff. Mono config path = '/home/pi/GOG Games/Kerbal Space Program/game/Launcher_Data/Mono/etc'ĭisplaymanager : xrandr version warning. Mono path = '/home/pi/GOG Games/Kerbal Space Program/game/Launcher_Data/Mono' Mono path = '/home/pi/GOG Games/Kerbal Space Program/game/Launcher_Data/Managed' Set current directory to /home/pi/GOG Games/Kerbal Space Program/gameįound path: /home/pi/GOG Games/Kerbal Space Program/game/Launcher.x86Įrror: Global Symbol data_start not found, cannot apply R_386_GLOB_DAT ((nil)) in /home/pi/GOG Games/Kerbal Space Program/game/Launcher_Data/Mono/x86/libmono.soĮrror: Global Symbol _data_start not found, cannot apply R_386_GLOB_DAT ((nil)) in /home/pi/GOG Games/Kerbal Space Program/game/Launcher_Data/Mono/x86/libmono.so $ "/home/pi/GOG Games/Kerbal Space Program/start.sh" "-launcher"īox86 with Dynarec v0.1.9 96f944c8 built on 00:03:56
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |