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
    This doesn't seem to occur on Linux even with maximum repeat speed.
  2. sal_vager
    This decoupler is known to cause a crash on some Macs, you can fix it by changing PhysicsSignificance to 0 on line 32 of the part.cfg, in /GameData/Squad/Parts/Structural/Size3Decoupler/ like this.
  3. sal_vager
    @thereaverofdarkness2. your graphics driver is out of date, you can find the latest here. @Hrv123, please try without mods. And make sure KSP is using your graphics card, not a GPU built into the CPU, you can do this in your graphics card software.
  4. sal_vager
    @Fwiffo, have you considered using the retractable ladders as a switchable junction?
  5. sal_vager
    Nah it's an old stock bug, quicksave then quickload should restore it.
  6. sal_vager
    Nope. @Frybert?
  7. sal_vager
    I see no means of renaming docking ports in 1.0.5, are you sure you were not using a mod?
  8. sal_vager
    How about moar struts ?
  9. sal_vager
    I don't know, I don't have a Steam controller to try. I have read that they only work in Steam big picture mode, but I assume you are already using this.
  10. sal_vager
    Only DirectX 9 is supported on Windows at this time, forcing OpenGL is a Unity engine feature, it is not provided by Squad, sorry.
  11. sal_vager
    Unfortunately that will not work, as KSP reads in and writes out the settings.cfg when you start, added spaces will be removed.
  12. sal_vager
    This thread serves no purpose, closing.
  13. sal_vager
    Removed an offensive post, sorry you guys had to see that.
  14. sal_vager
    That looks a lot like my tests as well.
  15. sal_vager
    Yes, I think it's trimming whitespace when writing to the file, you can see the trailing spaces are missing from the settings.cfg There is a Unity method for this and it's probably required elsewhere in KSP, so rather than removing it and potentially breaking something else it could be applied to the results of Input.GetJoystickNames() so they match. Previously the names were truncated as was visible in the settings.cfg, so trailing whitespace was lost except on very short controller names. I'll make sure the devs know of this issue @Badsector, well done you may have solved this!
  16. sal_vager
    Whoop! You had me worried it was still broke
  17. sal_vager
    Well I can't even launch these, they are too big. Have you stopped to consider that 3000+ parts may be too many?
  18. sal_vager
    Have you actually tried your stick in 1.1.2 ? Because this was addressed and tests with a Saitek X52 showed it was working.
  19. sal_vager
    This is going to take more work to figure out, but didn't you have this issue before and you fixed it by moving your parts out of the main ship ?
  20. sal_vager
    Just looking at your screenshot crashed my KSP
  21. sal_vager
    Oh spotting bugs is easy @Alshain, but there's a little thing called severity, and issues are triaged so the most important ones are addressed when there is limited developer time, though I'm sure you know this Closing!
  22. sal_vager
    Your fix is a change to the behaviour, so it's best described as feedback or a feature request, so this forum is the most appropriate place for it. And as I mentioned previously during pre-release... The same held true prior to pre-release, and currently. The tracker allows issues to be managed, assigned, tracked and resolved, the forum is not suited to this.
  23. sal_vager
    You know the forum isn't the place for bug reports, there is an issue tracker
  24. sal_vager
    The button still works, it's just not tied to the contents of the action group, hence it's a good suggestion that this be changed.
  25. sal_vager
    Hi @Strasser_BR. You are running a modded game in 32bit and you are running out of memory. Please try KSP 64bit, or use fewer mods, thank you.
×
×
  • Create New...