Jump to content

Mark Kerbin

Members
  • Posts

    664
  • Joined

  • Last visited

Community Answers

  1. Mark Kerbin's post in Laggy smoke was marked as the answer   
    Ehh. Cut the particle effects. Otherwise the fact is that you are asking your pc to render a crud ton of particles. So better pc is also a good option .
    (Main settings config)
  2. Mark Kerbin's post in Sandbox VAB after mission crashes was marked as the answer   
    @tonimark I would suggest you make a new thread since you have a entirely different install.
     
    @KerbOrigin First off, I think I had something like that happen to me. I think reinstalling MM entirely, ie removing all its configs, fixed it. That being said we still need an output log. 
     
    @tonimark this is for you too;
    How to get an output log.
    Step 1: do whatever you did the first time
    Step 2: shut off game after it finishes breaking
    Step 3: find log using these paths;
    Windows:KSP_win\KSP_Data\output_log.txt (32bit) or KSP_win64\KSP_x64_Data\output_log.txt (64bit) or %USERPROFILE%\AppData\LocalLow\Squad\Kerbal Space Program\output_log.txt Mac OS X: Open Console, on the left side of the window there is a menu that says 'files'. Scroll down the list and find the Unity drop down, under Unity there will be Player.log ( Files>~/Library/Logs>Unity>Player.log ) Linux: ~/.config/unity3d/Squad/Kerbal\ Space\ Program/Player.log Since neither of you have attempted to sell me a new operating system I’ll assume you have a windows PC.   
    If so just hit Windows Key + R then paste in this; (Just navigates to a file in your directory, it’s safe)
    %USERPROFILE%\AppData\LocalLow\Squad\Kerbal Space Program\output_log.txt
    That will open ksp’s log file.
    Delete the output_log.txt part of you just want to see it in the file folder.
    Upload it to Dropbox or Google drive so you can share it with us.
     
×
×
  • Create New...