Jump to content

sal_vager

Moderator Emeritus
 View Profile  See their activity

  • Posts

    17,670

  • Joined

  • Last visited

 Content Type 

Everything posted by sal_vager

  1. sal_vager
    Locked by request.
  2. sal_vager
    For fglrx yes, they were rather old anyway. But the Catalyst drivers are available on the AMD website, I have tried them and they are not difficult to install or remove, but it is important to follow the instructions to the letter.
  3. sal_vager
    I've let Kasper and Ted know.
  4. sal_vager
    Thanks @Green Baron, free() is a c/c++/c# command, so in KSP's case this is called by Unity3D game engine functions when objects are deleted, and by the garbage collector in Mono.
  5. sal_vager
    Hi @justspace103, it's a unified binary on Mac OSX, so it automatically runs in 64bit if it can, which your activity monitor shows. 64bit allows an application to use more than 3.5 gigabytes of RAM, but does not do anything for speed, any speed gains will be due to improvements in the software and in KSP's case that means a newer Unity engine, overhauled GUI, and new version of PhysX. To get the most from KSP or any other software it is recommended to have as few other programs running at the same time as possible, as they will be using CPU and memory, leaving less for KSP.
  6. sal_vager
    Yes it's a know issue on open source drivers @jape3, try starting KSP with the -force-glcore Unity command line argument, or try proprietary drivers if you are using Nvidia or AMD. ./KSP.x86_64 -force-glcore If that fails try. ./KSP.x86_64 -force-gfx-direct
  7. sal_vager
    It may be this, which still isn't fixed in Unity. If you have Hamachi or other unused or virtual networks try disabling them.
  8. sal_vager
    On OSX it's a unified binary, there's no separate 32bit and 64bit versions. We'll need more info to even begin to diagnose this, please see this thread. We'll need the game logs and the system specs/model of your Mac.
  9. sal_vager
    Are you getting any errors? The settings should be persisting so something is going wrong.
  10. sal_vager
    Their purpose is to allow the player to make their own custom part categories, so if you had a bunch of parts you always use for rovers you could make a custom rover category for those parts so they are all together. If you use mod parts you can also make custom categories for them, and several modders provide custom groups with their mods.
  11. sal_vager
    Locked by request
  12. sal_vager
    It sounds like you still have your Physics.cfg and Partdatabase.cfg from 1.0.5, there's a few differences. If you delete these two files KSP will make new ones when you next start, this should solve the issue.
  13. sal_vager
    Okay, no idea at this time. For what it's worth, I can get 80 to over 100 fps with small ships (< 50 parts) on Xubuntu 15.10, with an Nvidia GTX 650 and the nvidia-352 driver. This is on an AMD 5800K A10 APU, 16 gigs RAM, so your PC should be fine hardware wise. It's possibly the driver, newer drivers are in the repos on newer versions of Ubuntu, also there's the Oibaf or Edgers PPA's which add newer open source drivers, and Ubuntu now also offers an official PPA for the proprietary Nvidia drivers. It may be worth trying one of these, or updating Ubuntu, the latest LTS version came out today.
  14. sal_vager
    Hmm, steam overlay may be killing it.
  15. sal_vager
    Laptop? Powersaving can wreck performance.
  16. sal_vager
    Overclocked? KSP has been notoriously bad with overclocking.
  17. sal_vager
    Another thing to try, and I've heard this from a few players now, is starting KSP with this (from the terminal). KSP.x86_64 -force-glcore It forces the Unity engine to find the best version of OpenGL your drivers support, and uses those. It may help.
  18. sal_vager
    Okay well this repeats a few times when you're in the settings screen. I don't have that on my install, so maybe your install is a bit borked, reinstalling may help. Though it's saying it's having trouble when setting the resolution, is your resolution equal to your desktop? If this persists you may have to edit the prefs file in .config/unity3d/Squad/Kerbal Space Program/ to match the resolution you're using.
  19. sal_vager
    Hi @spacebrick3, can you please try the Launcher.app, and clicking on the gear icon. You will be able to set fullscreen mode, and that usually gets KSP to start. After it has started in fullscreen it should work properly after that, even if put back in windowed mode.
  20. sal_vager
    When was the last time you cleaned your PC/laptop of dust ?
  21. sal_vager
    As the issue appears after a half hour of play it is likely to be something else, hence the need for the logs.
  22. sal_vager
    We'll need the game logs as well, KSP.log on both platforms, Player.log on Linux and output_log.txt on Windows.
  23. sal_vager
    It might be a bad save, first open the debug screen with modkey+F2 and look for an error, it should tell you which save is bad. If not, try moving them all except scenarios and training outside of the KSP saves folder, then starting a new game. If it works then it's a bad save, you just have to find which one.
  24. sal_vager
    It's a known issue @DDay2021, and being worked on
  25. sal_vager
    All I can do is give you the same answer I gave you in the thread you made.
×
×
  • Create New...