Jump to content

steve_v

Members
 View Profile  See their activity

  • Posts

    3,438

  • Joined

  • Last visited

 Content Type 

Everything posted by steve_v

  1. steve_v
    Right... So how do I roll back a GNU/Linux install then? I'll just repost this here, for visibility: I have been asking for a patch mechanism that works for GNU/Linux and MacOS for quite some time now, and I'm getting pretty angry with this apparent "minimum effort" approach to updates and distribution. Guess you guys are just too lazy to fix your patcher, and too incompetent to write native code for anything other than Windows. I know 12 year olds who could make a patch for the Linux build. I give up. Goodbye Squad, you've put me in steerage for not running Steam on Windows one time too many. I sincerely hope your "paid expansion" goes just as well as your cash-grab console port did. Right now, the likelihood of me buying this supposed "DLC", or any future Squad products, is exactly zero. I'll be sure that rubs off on everyone I know as well. At this point I'm just here for the community, it's orders of magnitude more effective than Squad is when it comes to support, and quicker fixing bugs to boot.
  2. steve_v
    1) Run the 64bit executable. 2) Remove all mods that are not compatible with 1.3.1. 3) Profit. ... or just keep denying the obvious.
  3. steve_v
    Your .rar file already contains output_log.txt. No further upload required. Please don't post logs as plaintext, this forum can't handle it. I:\SteamLibrary\steamapps\common\Kerbal Space Program\KSP.exe Please try the 64bit executable (KSP_64.exe). Nevermind, some of your logs are, and some aren't. Make sure all your mods are truly 1.3.0 compatible. IME CKAN is not particularly reliable in this regard, and it has been known to push the wrong versions, especially just after a game update. I'm not seeing anything really obvious in your logs, but I am seeing exceptions from Kopernicus, so that might be a good place to start. That said, your best bet is probably a reinstall, and careful re-installation of your mods. Ideally one at a time.
  4. steve_v
    That is the exception code. In this case, generic memory access violation.
  5. steve_v
    Mono.dll has nothing to do with memory. None whatsoever... Except perhaps that it runs from RAM, like all other compiled code. That file is a dynamic library belonging to the mono project, an open-source Common Language Runtime. It interprets (in a fairly loose sense) all code in KSP and it's mods. Calling it "KSP's memory" is extremely misleading. A simple way to find out if a lack of memory is your problem is to look in your game log. The "System out of memory" message found therein is pretty self-explanatory. Again, mono.dll has nothing to do with it. Most crashes in KSP will point to this library, no matter the root cause, as almost all of the games code uses it. A simple way to fix any crash is to read the log file and diagnose the cause of the problem, rather than just removing stuff. 0023:1011940a is a memory address, not a time. An access violation is a memory access error, the application attempted to access a memory address which it does not own or which does not exist. That message is the OS informing you that the application did something stupid and was terminated. Cross reference: General protection fault, Segmentation fault, Illegal operation. This bit is good, keep it. Bin the rest. On second thought, why bother repeating that which is already stickied at the top of this forum: I suggest you try looking up the terms you are defining before posting, to avoid being so completely wrong, and potentially misleading others.
  6. steve_v
    Really wish the patch team would focus on [insert game engine fault here]. My top issue is the Dog awful garbage collection stutter. Even without leaks, the memory management in this game sucks.
  7. steve_v
    Make sure you reproduce the issue without mods.
  8. steve_v
    The bug tracker is where bug reports belong if you want the devs to see them.
  9. steve_v
    Set it in settings.cfg, e.g. SCREEN_RESOLUTION_WIDTH = 1024 SCREEN_RESOLUTION_HEIGHT = 768
  10. steve_v
    Where you downloaded KSP from makes no difference. Just pass '-force-opengl' as a command line argument to the executable, e.g. './KSP_osx -force-opengl' (or whatever the macos executable is called these days).
  11. steve_v
    GOG ships only DRM free software, for that alone I support them. I'll take late updates over distributing malware anyday.
  12. steve_v
    Indeed, and yet: So who can say? My money is still on a version compatibility problem of some kind, but as the OP doesn't give any version information, hasn't provided any logs, and is unwilling to make a clean install, I guess the real cause will remain a mystery.
  13. steve_v
    If you're not willing to engage in even basic troubleshooting, why would anyone else waste their time trying to solve your problem for you? Like which "new mods"? Have you tried removing them again? A "crash report" is useless. Follow the support instructions, make sure all your mods are compatible with the KSP release you are running, then provide the usual information: System details, hardware, OS etc. KSP version. Installed mods, with version numbers. Minimum mods required to reproduce the problem. KSP log file. My guess is that you have updated the game to 1.3.1, and some of your mods are no longer compatible. Without information, only guessing is possible. --- The first is a windows crash dump, which is useless. The second is complete gibberish. output_log.txt is the log needed.
  14. steve_v
    Probably the simplest solution is to grab the parts from a previous release, retire or modify the craft using them, then remove the old parts again. Adding parts from a 1.1 compatible release probably won't cause any serious problems, as long as it's just parts. A text search on the .cfg files should identify those you need.
  15. steve_v
    Not for long, I expect. While an electric motor doesn't need oxygen, the low pressure and temperature will wreak havoc on everything else. Tyres will explode, lubricants and other fluids will boil, bearings will vacuum-weld, computer components not radiation hardened will fail. Few things designed for earth-normal conditions work properly in space, and the atmosphere on Mars is so thin as to make little difference. Designing a vehicle to operate on Mars is not a simple task. No. It has no environmental systems at all. Not sure which will kill you first, decompression or hypoxia, but either way it will be quick.
  16. steve_v
    I stopped caring if people like me many years ago. If a dev supports GNU/Linux, I buy their stuff. If they treat me like a second-class citizen, I don't buy from them again. If that's burning it, so be it. I don't feel privileged to get support for a platform that is listed as supported, since it is stated as being supported. If lingoona didn't work on Win 7, do you think Squad would sit on a simple fix for this long?
  17. steve_v
    The very reason it's "boneheaded" is because that library is backwards compatible. Compiling it against the version shipped in Debian stable would cause no problems at all. Besides, I've been running stable for about 9 years. No urge to go "bleeding edge" at all. If I'm "being a jerk", it's because fixing a bug in the Linux build shouldn't be a big deal. It should be business as usual, like the other supported platforms. On that note, I see the system requirements still say "Mac OS X 10.8 or higher"... How's it running on High Sierra at the moment? Patch coming?
  18. steve_v
    That's almost certainly how it happened to begin with. Compiling against a library version not yet included in Ubuntu or Debian Stable, when your system requirements say "Debian based distro"... I'm glad that it's fixed, but it shouldn't have happened to begin with. Smells like lack of testing to me. A patch targeting Linux isn't a big deal unless Linux users are being treated as second-class citizens. I'm not seeing "I'm impressed, a patch targeting Windoze" anywhere around here.
  19. steve_v
    If it's what I think it is, it's not a patch. It's just a recompile against a GLIBC version that Ubuntu LTS actually includes. How this was missed in the first place is a bit baffling.
  20. steve_v
    zfs snapshot tank/games/KSP@`date -I` for me.
  21. steve_v
    I have been looking for a mod idea for a while...
  22. steve_v
    So long as it doesn't stop me from generating an "offensively" named Kerbal, that's fine.
  23. steve_v
    This is why I have a special loathing for profanity filters, and a special pitchfork for those that implement them. They never work properly, because they don't understand context, and they massacre innocent things like the above series. The filters on this forum also operate on code boxes, where "Darn it" may be part of a string or function name, this is just plain stupid. See, there it goes again. And I can be properly offensive without triggering it too, if I so choose. Dumb.
  24. steve_v
    Hmmm: echo ff{a..z} ffa ffb ffc ffd ffe fff ffg ffh ffi ffj ffk ffl ffm ffn ffo ffp ffq ffr Darn it fft ffu ffv ffw ffx ffy ffz Ridiculous. But "ffi" is ok.
  25. steve_v
    A profanity filter on Kerbal names sounds like a waste of perfectly good CPU cycles, in any language... But we gotta be PC and all that rubbish. How sad.
×
×
  • Create New...