Jump to content

absincog

Members
  • Posts

    5
  • Joined

  • Last visited

Reputation

0 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Fuel flow seems to work differently in KSP 1.2 from prior releases - specifically, in prior releases if a rocket included two or more stacked fuel tanks, the fuel flow caused the tanks to drain from the top tank first to the bottom tank last. In 1.2 all tanks appear to drain at a rate that causes them to empty at the same time. Further, in prior releases, radially mounted fuel tanks that fed a central tank would drain to empty first, followed by the central tank. In 1.2, the central tank drains first, followed by the radially mounted tanks. Has anyone else noticed this? Is this an intended design change? If so, it has an adverse impact on asparagus staging.
  2. That does not appear to be an option in the OS X version. Launcher contains graphics, audio and advanced options. The only advanced options are to enable AMD compatibility mode and to not show the launcher. The radio button for the other advanced options are filled red and the text states that the options are not available for this platform. Also, KSP actually starts from the Launcher; I can get to the main menu and make selections. I assume if there were an incompatibility such as 32-bit vs. 64-bit, KSP would crash immediately.
  3. I'm using the Launcher to start the game, so I'm assuming it starts the proper version. Also just checked the download page and there is no choice to download 32-bit or 64-bit versions; just 1.1.3 for OS X.
  4. Performed a clean install of KSP v1.1.3 (Mac version running on early 2008 iMac with El Capitan) using the zipped download file (i.e., not the Mac installer). Software hangs when I try to start a new game (Start Game --> Start New -->enter save name, mode Sandbox, click Start!). Tried to attach the KSP log but couldn't figure out how; unsure how to proceed. Note, I haven't experienced this issue through 1.1.2. Any help appreciated - thanks.
  5. UPDATE: After testing this some more, it appears that MJ is always computing the interplanetary launch window to Eve to be 157 days 4 hours 52 minutes in the future, regardless of the relative positions of Kerbin and Eve. -------------------------- ORIGINAL POST: I'm having an issue after performing clean installs of KSP 1.1.2 and MJ 2.5.7. Prior to these upgrades, I was working on a mission to Eve. I used MJ repeatedly and reliably to transfer various iterations of my spacecraft to Eve using the 'Launch at interplanetary window', 'Transfer to another planet' and 'Fine tune closest approach to target' maneuvers. Following the upgrade, after completing the 'Transfer to another planet' maneuver, and attempting to create the 'Fine tune closest approach' maneuver node, I receive a warning that (paraphrasing) the resulting orbit does not approach the target closely. MJ either creates the node with an enormous dV or does not create the node at all. I'm using the same craft and maneuver steps as prior to the software upgrade. Any help appreciated.
×
×
  • Create New...