Jump to content

KBM

Members
  • Posts

    14
  • Joined

  • Last visited

Everything posted by KBM

  1. @EnterTheNameHere You're very welcome! I couldn't see the stock chutes or RealChute either so that's why I decided to workaround it as it broke the career game for me.
  2. I found a workaround by editing all "@category = none" to "@category = Utility" in: GameData\RealChute\ModuleManager\Stock_RealChute_MM.cfg and "category = none" to "category = Utility" in: GameData\RealChute\Parts\stack_chute.cfg GameData\RealChute\Parts\cone_chute.cfg GameData\RealChute\Parts\cone_double_chute.cfg GameData\RealChute\Parts\radial_chute.cfg This made all the parachutes appear in the "Utility" part category. All seems to be working as expected.
  3. Are you running the default 32-bit version of KSP or have you done the "Windows 64-bit workaround"? If you haven't then you most likely need Active Texture Management mod - try with the standard version first - then the aggressive if the game still crashes. Also you might be interested in the Dynamic Texture Loader mod. The textures from KSPRC is very heavy on the RAM = the 32bit version of KSP will crash when addressing more than 3.5GB RAM.
  4. This is indeed correct, I read somewhere that setting the PHYSICS_FRAME_DT_LIMIT to zero could increase the framerate but slow down time, but I would recommend to set this to 0.01 instead or try the default value of 0.04. Sorry for the fault in the file. The file has now been corrected to 0.01. Edit: 0.04 and 0.01 in PHYSICS_FRAME_DT_LIMIT instead of 0.4 and 0.1 which I typed by accident.
  5. I have now checked that all the settings are correct - you can find my settings.cfg here. Just download and put it in the main data directory (where KSP.exe is) - replace existing. There are three presets, defaulting to High V2. Try that one first or else try Default V2 or Low V2 (terrain quality). I really recommend leaving all the other settings as-is. Of course you should change to your native resolution and tick fullscreen. Let me know how it goes.
  6. No worries, of course. I'm at work now and must see if the settings file I've uploaded is the correct one. I will get back to you in the evening.
  7. Try following this post a few pages back. It may severely help with your framerate issues. Though EVE is still quite heavy on itself still. When I did this on the Win64-version community workaround of KSP my framerate was around 18-25 on the launchpad and around 40-50 orbiting Kerbin. As Unity5 is coming for KSP 1.1 we hopefully experience performance optimizations due to the multithreading capabilities that also hopefully will be implemented. Also I really recommend using my tweaked settings file. Let me know if you need it.
  8. I have to concur! Let me know if you need any help with just about anything.
  9. Have you tried following this post one page back? Worked for me regarding increasing performance - however I have not been to EVE yet and can therfore not confirm the cloud issue you are experiencing.
  10. Have you tried following this post one page back? Worked for me regarding increasing performance - however I have not been to EVE yet and can therfore not confirm the cloud issue you are experiencing.
  11. I've tested it out with 0.24 and it works in 32-bit. Have not yet tested in 64-bit.
×
×
  • Create New...