Jump to content

SCVsUnion

Members
  • Posts

    6
  • Joined

  • Last visited

Posts posted by SCVsUnion

  1. @SCVsUnion: I knew that would happen eventually. I talked to ryan about putting that file in memory but he said it's a good idea to see what config the server has. That file must be changed on the server, the client one gets overwritten on connect.

    EDIT: Also note KMPPartList.txt is completely unused now.

    Thanks for the response godarklight. So my problem is that I'm running the server on the same machine as I'm running the client. If I understand correctly, I need to run the server on a different computer? Or maybe I'm not understanding... :)

  2. I'm having an issue where every time I run KSP and connect to my local server, the KMPModControl.txt file seems to get reset. I've added the mods to the file using MultiPlayer Part Manager and it seems to work, but after running KSP the mod entries have been removed. The result is that I get the "prohibited parts" message whenever I try to launch anything. Any thoughts? Thanks!

  3. **Update Release Version 3.1**

    Download now on SpacePort

    ChangeLog

    v3.1

    *Fixed bug where linux folders were denied. Now the program checks if ksp.app, ksp.exe, ksp.x86 or ksp.x86_64 is present in the chosen ksp folder.

    Problem solved - thanks!

    Unfortunately I'm now having a different problem - KSPModControl.txt seem to get reset every time I run KSP. Your program adds the mods nicely, but then they get removed as soon as I run KSP and connect to my local server. But, I suspect this is an issue for the KMP folks, not you. Thanks!

    EDIT: Solved it. Apparently KMP Server has its own KSPModControl.txt file that needs to be modified too. The learning never stops!

  4. I personally only use OSX and I guessed it works on Windows, else someone would have told me I suppose. Actually no clue about linux. However, I think this is the same bug as mentioned some posts above.

    Not sure if this works, but try this:

    In the 'data' folder edit the 'config.cfg' and replace the '.' with a folder path. So for example 'directory= /ksp_osx' or something else (not familiar with linux paths).

    The '.' refers to the working directory in OSX, however, not sure what this is in an other OS. After you choose a folder for the first time it will remember that path. So it might be a first time thing only.

    I will try to come up with a hot-fix this week.

    Is it alright if I'll contact you to test it for linux?

    Thanks for the quick response! I tried changing the default directory and it now starts in my KSP folder, but it still won't work. I just get the initial screen. Could it be because the Linux version of KSP doesn't use KSP.app or KSP.exe (your help file indicates that it needs to see one of these)? The Linux version seems to have KSP.x86 and KSP.x86_64. It seems to be looking in the right place, but not seeing whatever it needs.

    I'm happy to help out with Linux testing, but fair warning, I'm a total Linux noob (as you may or may not be able to tell).

×
×
  • Create New...