Jump to content

Anth

Moderator
  • Posts

    2,138
  • Joined

  • Last visited

Reputation

1,096 Excellent

Profile Information

  • Location
    New Zealand

Recent Profile Visitors

12,230 profile views
  1. And that is why you have no robotics tab. You need the DLC for it to show up.
  2. @Gustavinho6768 Do you have the Breaking Ground DLC installed?
  3. A few things that might help: 1. Have the mods been removed?: So going into the KSP1 folders what is inside the GameData folder? My path to that is "D:\SteamLibrary\steamapps\common\Kerbal Space Program\GameData" If you have removed all the mods then the only folders in there should be Squad and Squad Expansion (if you have either of the DLCs). 2. The save file might have been changed by the mods you added breaking it and that's why the unknown objects are showing up.
  4. I recommend removing the control surfaces from the bottom to see if that works. My impression of what is happening if your TWR is over 1 is that the thrust is being blocked.
  5. Oh. Ok cool. By the way the link you supplied doesn't work. It comes up with a 403 error.
  6. Actually yours might be to the side... Here's a screenshot of the wheels in the right orientation. Also look to the parts menu on the left, the wheels there are also in the right orientation.
  7. Your wheels are upside down. The wheels may look like they are round but in truth they only work in one direction.
  8. Interesting bug, however KSP1 development ended a while ago (2021?) so its unlikely that it will ever be fixed.
  9. The memory leak I am talking about in my experience overshadows any other memory leaks. The developers of KSP1 at one point had fixed some other memory issues but they weren't even noticeable because of this one. If its happening over corrupted/missing files that would show up in the log file? No idea. Also the developers said it wasn't able to be fixed, so I am not sure what mods could do to counter it. Though, what they might have been meant by it not being fixable, might have been that it would have taken too much time and money to fix it.
  10. Main issue is that there is a memory leak that was introduced with 1.2, I think relating to the Unity garbage collection. When the game changes between scenes it appears to load the universe every time and it causes the memory to go up and up and also the load times get longer and longer. In addition the bigger the save file the faster the memory leak increases. If this issue was eliminated then most of the memory issues would be gone.
  11. Its a known bug. Kerbals that are too close to colliders (hitboxes) of the parts of a craft they are attached to can cause force to be applied. It doesn't happen on all parts that a kerbal can EVA for, but from what is happening the science module appears to be one of them.
  12. This was in KSP2 Mod Discussions. Moved to KSP1 Technical Support (PC, modded installs)
×
×
  • Create New...