Frankenchokey

Members
  • Content Count

    21
  • Joined

  • Last visited

Community Reputation

3 Neutral

About Frankenchokey

  • Rank
    Bottle Rocketeer
  1. Just run the installer, and point it to your KSP 1.4.1 directory when prompted. If it works, the expansion should then be installed under <kspdirectory>\GameData\SquadExpansion\MakingHistory.
  2. This happens to me in windows if I run KSP with the -force-opengl option. Also notice the icons overlapping the controls at the bottom of the list in opengl mode. Forcing dx11 causes a different issue where the icons appear without texture. Running with the default dx9 works fine. Win x64 Opengl: Win x64 dx11:
  3. Just curious, if there are updates to this branch over the next couple of weeks, how will they be delivered to the KSP Store version?
  4. There was mention in the Devnotes that some HOTAS controller issues had been solved, but I'm not seeing it in the patch notes, unless I'm just overlooking it. Anyhow, thanks for the speedy bug fixes, Squad.
  5. Now to see if the patcher works ... And the answer is no, at least not yet. Oh well, just curious
  6. Just out of curiosity, would going into the config file and manually changing the axis to joy1.1 do anything? It's probably more of a windows thing, but the other problem I have continually run into is the various input devices changing device Id's. It would be nice if something like Advanced Fly by Wire's solution could be implemented in the base game though.
  7. Are both your throttle and stick listed separately in the settings.cfg file? I did a quick test using both my F710 gamepad and T16000m, and they assigned the axes correctly. However, those two controllers have different names in the config file, and I seem to recall there being some issue with longer, similar, names being truncated and causing confusion. For example both "Saitek Pro Flight X-55 Rhino Joystick" and "Saitek Pro Flight X-55 Rhino Throttle" ( I don't know the exact names) both showing up as "Saitek Pro Flight X-55 R" in truncated form. Though, your buttons work as mentioned so maybe that isn't it.
  8. Interesting. It does revert 1.0.5. I was curious if the patcher would pick up the missing 1.1 x64 files from the KSP Store version. It did not, but I suppose it is hard to determine if it could do so if it's not even updating to the correct version.
  9. Hmm, that's what I was expecting, but it isn't there. Maybe this is an issue with the Store version.
  10. Just out of curiosity, is there any way to tell in game which version is running? Task manager is reporting KSP.exe as a 32 bit application. Using the KSP store version, with the launcher option set to Run 64 bit Player.
  11. That's a good idea, and I have used playonlinux before. There are some performance compromises to be made with using Wine though, aren't there? As I said, maybe I just need to challenge myself and try it out more seriously for a while. The problem with having both Windows and Linux on dual boot, is that it's all too easy to run back to the familiar when I hit a snag.
  12. I'm always a bit envious of those who are able to make the switch to Linux. I keep a Linux dual boot on my system these days, just in case something goes wrong with windows and really like it when I decide to play around with it for a while. Unfortunately, however, as long as I can only run some of my games on it, I'll probably continue to end up using Windows a significant portion of the time. If it weren't for that, I'd likely have switched over long ago. Maybe a self imposed challenge of only using Linux for a week or two would be a good idea sometime.
  13. Have you tried turning on PPFX directly in the settings.cfg file? If not, try setting EDGE_HIGHLIGHTING_PPFX=True manually in the file and see if it works. I had this issue, though not with steam, in .90 after I replaced my graphics card. Though the new card was quite capable of using the feature, the setting in game would not recognize it. Editing the settings file directly solved this issue.
  14. I did a little bit more experimenting with this, but still can't quite pinpoint the cause. I had both a logitech F710 and Thrustmaster T16000m attached originally. I removed the F710 from, mapped some axes and buttons to the T16000m. Shutdown KSP and restarted a few times with no issue. Then reattached the F710 and tried to assign some buttons to it, which mostly worked (had the issue with the accept dialog never appearing on the axis), but buttons worked fine. Relaunched KSP a few times, no issue with settings reverting to default. T16000m was assigned to Input id =0 and F710 =1. So I tried unplugging the T16000m, restarted KSP and got the reset to default issue again. Checking the settings.cfg, the Logitech as again assigned to Input Device 0 and the T16000 was no longer listed. While this reset to default happened right after I changed the devices, it could just be coincidence. Will keep trying to see if I get similar results.