Jump to content

shrx

Members
  • Posts

    70
  • Joined

  • Last visited

Posts posted by shrx

  1. Has anyone managed to run KSP over SSH? What command should I use?

    If I try ./KSP.x86_64 I only get a brief flash of a black window which quickly disappears and nothing else happens.

    The output in the console is

    Set current directory to /home/shrx/.steam/steam/steamapps/common/Kerbal Space Program

    Found path: /home/shrx/.steam/steam/steamapps/common/Kerbal Space Program/KSP.x86_64

    Mono path[0] = '/home/shrx/.steam/steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed'

    Mono path[1] = '/home/shrx/.steam/steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono'

    Mono config path = '/home/shrx/.steam/steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono/etc'

  2. shrx: Bodies without an existing atmosphere won't have an AtmosphereFromGround created for them. Kopernicus will do that, I think, if not now, soon.

    Regarding the temperatureCurve: not sure why it's not loading. I'll check.

    Thanks. I'm not really concerned by the visuals, just the physical effects.

  3. atmoshpereTemperatureMultiplier never worked, and is likely a legacy feature. You probably could try using the HazardOcean module to emulate atmospheric heating.

    Thanks, I will check it out. The funny thing is, atmoshpereTemperatureMultiplier kind of worked once, I set it to 4.9. Then I got some freezes, reinstalled the mod, and to get the same effect as before I now had to set it to 3500. Then it stopped working again.

  4. I can't get atmoshpereTemperatureMultiplier to work. I want to restore Moho's atmosphere to what it was in 0.17. I enabled atmosphere and set atmoshpereTemperatureMultiplier to 1. The next time I load the game and switch to a vessel landed on Moho it displays a black screen and locks up. What's the problem? I am running 32bit KSP. Happens with no other mods installed. Here is the cfg that kittopia produces when I save the configuration: http://pastebin.com/DN9c5Ld3

  5. OK, this is the updated cfg:

    REALSOLARSYSTEM
    {
    Moho
    {
    atmosphere = true
    useLegacyAtmosphere = true
    atmosphereMultiplier = 0.005
    atmosphereScaleHeight = 2
    maxAtmosphereAltitude = 27640
    temperatureCurve
    {
    // The units are km, °C, dK / dkm, next dK / dkm.
    key = 0. 500. 0. -20.
    key = 10. 300. -20. -17.0068027211
    key = 27.64 0. -17.0068027211 0.
    }
    }
    }

    Pressure now works correctly, but temperature still doesn't work as it should.

  6. I'm trying to restore Moho's atmosphere to pre-0.18 values with RSS.

    This is my config (atmosphereMultiplier = 1 so the atmosphere should be more noticeable and temperatureCurve values are just placeholders):

    REALSOLARSYSTEM
    {
    Moho
    {
    atmosphereMultiplier = 1
    atmosphereScaleHeight = 2
    maxAtmosphereAltitude = 27640
    useLegacyAtmosphere = True
    temperatureCurve
    {
    // The units are km, °C, dK / dkm, next dK / dkm.
    key = 0. 500. -10000. -20.
    key = 10. 300. -20. -17.0068027211
    key = 27.64 0. -17.0068027211 0.
    }
    AtmosphereFromGround
    {
    waveLength = 0.49, 0.5, 0.53, 1.0
    innerRadius = 247500 // 0.99
    outerRadius = 312500 // 1.025
    }
    }
    }

    However it does not seem to work.

    Pressure is always 0 (barometer displays "IN VACUM").

    Temperature on the ground is 0° instead of 500°.

    Temperature at 10 km is 0.45° instead of 300°.

    How can I make it work? This is the first time I'm trying to make something with RSS. Any help will be appreciated.

  7. You have to right click on the KSP.app and click 'show package contents' then in the contents folder, navigate to each individual folder (data, macOS, frameworks and resources) and replace the necessary items. Also, do this with a completely new install or back up your current one, it might ruin your KSP.app so at least back that up.

    Thanks, I managed to start up KSP with no mods. But when I tried to load KSO and Astronomer's pack, it would not finish loading but freeze at about 80%. So this method does not work for now.

  8. You need the latest version of unity, 4.5.2 http://unity3d.com/unity/download

    OK, thanks. I found the next problem, the Windows instructions tell me to

    Find "Editor\Data\PlaybackEngines\windows64standalonepla yer\Data\Mono\mono.dll" and copy it to "KSP_Data\Mono"

    but there is no KSP_Data folder on OS X and I can't find mono.dll.

    I replaced KSP.app with UnityPlayer but it closes very quickly when I run it and nothing happens.

  9. In regards to the hack working or not, its incredibly buggy, to the point of not being usable. I was using stock with the KSO as memory testing, and it still crashed at about 2.2GB's of ram. I think it would be best to just wait till Unity puts out a more mature x64 release.

    Where did you get 64 bit unity player? It's not in the PlaybackEngines folder:

    AndroidDevelopmentPlayer            LinuxStandalonePlayer
    AndroidPlayer MacDevelopmentStandalonePlayer
    BB10DevelopmentPlayer MacStandalonePlayer
    BB10Player NaclPlayer
    FlashSupport WebPlayer
    Linux32HeadlessStandalonePlayer Windows64StandalonePlayer
    Linux64DevelopmentStandalonePlayer WindowsDevelopmentStandalonePlayer
    Linux64HeadlessStandalonePlayer WindowsStandalonePlayer
    Linux64StandalonePlayer iPhonePlayer
    LinuxDevelopmentStandalonePlayer

  10. Perhaps because, as with the Windows x64 build, the team at SQUAD have their hands tied and are forced to wait for the guys at Unity to come up with fixes for the OS X x64 issues. It would then make sense that SQUAD isn't commenting on Mac x64, as they have no direct control over whether or not it'll become available.

    I'd assume that SQUAD will do right by their Mac customers once the guys at Unity fix all their Mac issues and they can release a mostly stable build for Mac x64.

    (emphasis added by me)

    This doesn't make sense to me. If this is the case and they are waiting for Unity support, then they should say so, and we will be less impatient than we are now with their ignorance.

  11. Delete your GameData\ThunderAerospace\TacLifeSupport\PluginData\TacLifeSupport\LifeSupport.cfg

    The old mod stored the consumption per day in the settings, the new version does consumption per second, so instead of consuming 1 unit a day it's now consuming 1 unit of oxygen a second and depletes almost immediately. You don't need to do anything else, on the next launch the mod will find that there is no config and just create a new one with default values.

    Unless you're having old ships that were created before TACLS 0.9, in that case the containers are probably of the wrong size and will run out quicker than intended.

    Thanks, I have only one manned ship with the old TACLS parts on so it won't be too big a problem to fix them.

    ANd yes I have deleted all mods and redownloaded them when the game updated.

  12. I have a save game from 0.23.5, when I was playing with TACLS 0.8.

    Now I updated to 0.24.2 and TACLS 0.9#3.

    Can I manually fix my persistent.sfs save game so it will work with the new mod version? Because now Kerbals die of oxygen depletion as soon as I focus a manned spacecraft. I do not have the Modular Fuel Tanks mod.

×
×
  • Create New...