5/9/2023 0 Comments Ancient space low fpsThe easiest way to test this, is in the Main Menu. Try limiting your framerate to 60fps, or use V Sync. Hey hey! There ya go! Lots of frames! Now, the goal is to see if you can smooth out the framerate, and make it less jumpy. In my case Chaka Monkey mod doesn't explode any vessel decoupling, that happened with FASA last time I tried in 1.0.5. Thank You sir, just installed stock without mods and everything on low and voila: You can get some frames by adjusting the Max Physics Delta Time parameter in your settings. All the physics calculations are run through the CPU. Your CPU clock-speed will greatly effect your frames when dealing with large vessels, and physics.When you're tuning performance, do so without any add-ons installed, and then add mods as you go, noting the effects of each addition. Wait for a properly supported update to run Chaka. Both are tough on performance. Additionally,I believe Chaka Monkey still has concave colliders, so if your rockets are exploding when you stage them, that's why. On top of that, in my opinion, Chaka Monkey is a really badly optimized add-on, at least in it's current state. It's got a ton of unconverted. In your case, the Chaka Monkey add-on is specifically stated to be not supported in KSP 1.0.5. All the good info seems to be scattered about the forum. I'd like to start one big gigantic performance thread. This is a general list of information I'm trying to assemble. Use the debug toolbar (Alt-F12) to check your framerate, and more importantly, your framerate smoothness, as well as checking the debug log for errors.Your GPU has little impact on performance at the moment. Usually, your CPU will be the limiting factor, lesser-so, the GPU.Your in-game speed will slow down so that your computer can keep pace with physics without cutting corners. Decreasing the value will make the game run smoother, but slower.Increasing the value will make the game appear to run faster and choppier, but your physics will be less accurate, as less physics calculations will be run per second, thereby decreasing physics accuracy.Close everything out, and perhaps reboot. All the physics calculations are run through the CPU.īecause the CPU is heavily utilized by KSP, the framerate is sensitive to other processes running on your computer. Regarding the 64-bit workaround, remember that it will only increase the amount of memory that the game can use before crashing, not your FPS. This will allow you to load full textures in most cases, and use more add-ons without crashing. dds, and most mod-authors now fully adopting, there's little reason in most cases. You could use a texture reduction add-on, like Active Texture Management, but with the stock game now using. If you don't see the resolution you want in settings, you can set a custom resolution in the settings.cfg. It'd be nice to run it at at least 1920x1080, but for some, it's just too much. Obviously, your resolution effects frames a lot. For windowed-borderless, in Steam, you can use the startup command -popupwindow. Run in windowed or windowed-borderless mode. You can also force KSP to run in OpenGL by using -force-opengl. You can force KSP to run in DirectX11 by using -force-d3d11. If you're on Windows, your game will run on DirectX9 by default. In Steam, you can use -force-opengl if you want, but I don't believe it has any effect. There is no DirectX on either of these platforms. If you're on Mac OS X, or Linux, your game will be using OpenGL by default. I believe they are tough on frames, so disable if you can. They have no collision, so you can pass right through them. Terrain Scatters are the rocks you see on the moon, the trees you see on Kerbin, etc.Follow this forum link here to keep them from killing your frames: Oceans on Kerbin, Laythe, and Eve are rough on frames.You won't see a bad frame hit as far as I can tell. If you're using the 64-bit workaround version on either Windows, Mac OS X, or Linux, go ahead and use full textures. If you're running the standard 32-bit build of KSP, run half textures, or lower. Render Quality effects shadow rendering, as well as particle stuff and light counts. Note that this will override the Pixel Light Count and Shadow Cascade settings. It's a huge FPS killer.ĭrag Render Quality down to Fast, or Fastest if you can. You can reset all your settings by just deleting the settings.cfg, and starting the game. Start the tuning process with stock KSP, and a brand-new settings.cfg file. So, with extensive testing, I've figured out a few things:
0 Comments
Leave a Reply. |