Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by SeraphTroy

  1. @sal_vager It WAS working. Then, as magically as it was working, it stopped working. I think the same issue would be found with a Logitech Extreme 3D pro, as it looks like on most of the forums there's a correlation. The most up to date output log is here (https://www.dropbox.com/sh/1jx0aatrbfda0e3/AAC4myLbD3-ZMT1PHnzxgv5Ta?dl=0)
  2. I might try that out. I won't be able to test until later. Like I said I *think* got this working when I ran the KSP binary rather than the KSP_64 binary, and even the logs output different things when I checked. I'll see if I can recreate the issue, and submit it back to y'all as a bug report.
  3. If I remember correctly, I also tested the MK2 cockpit and it was fine in there, didn't notice anything. I notice it really on the ASET parts, so in this the HUD and some of the other ui elements have the hex code, but not the normal RPM monitor. Have there been any comments about when this (or the underlying ASET parts) will be updated for 1.2?
  4. Nevermind my previous post. I noticed that depending on how you launch, the log is in X:\Steam\steamapps\common\Kerbal Space Program\KSP_Data and not KSP_x64_Data. When I ran KSP.exe instead of the x64 binary it seemed to pick it up, so maybe the problem is with the x86 binary?
  5. Hi @sal_vager I tried to do that but I never get any output to line: X:\Steam\steamapps\common\Kerbal Space Program>dir Volume in drive X is Data Volume Serial Number is A2D3-F13A Directory of X:\Steam\steamapps\common\Kerbal Space Program 31.10.2016 21.43 <DIR> . 31.10.2016 21.43 <DIR> .. 15.10.2016 13.11 60 buildID.txt 15.10.2016 13.13 60 buildID64.txt 15.10.2016 13.16 <DIR> EmptySteamDepot 31.10.2016 18.41 9 312 FAQ.md 31.10.2016 21.43 <DIR> GameData 01.10.201
  6. This is working for me, after getting ModuleManager (wasn't clear I needed it). But all the labels are screwed up and are in hex. Is this a known issue?
  7. Sure, KSP https://www.dropbox.com/sh/1jx0aatrbfda0e3/AAC4myLbD3-ZMT1PHnzxgv5Ta?dl=0 For files. Note that this does detect my other joystick which you will see in the settings.cfg, and in the screenshot, you'll see that it detects both, but can only keep/set settings for the saitek. I also delete the settings.cfg at each retry. Lastly, in case you think the Saitek is a problem, I've also tried doing all of this with that joystick unplugged.
  8. Yes, I always have my joystick(s) plugged in. Do you want me to post that information in or in http://forum.kerbalspaceprogram.com/index.php?/topic/83213-stock-support-bug-reporting-guide/
  9. Hi sal, I have tried that to do that. In fact, if I do that, and move the joystick, it will display something in relation to the axis moved (either 0.1 or 1.1 or 1.x 0.x) but the bind won't save, even in the menu.
  10. Tried as I might, my joystick is unable to be recognized in KSP. The buttons can be bound, but not the axis. When attempting to bind, It'll say it's there, but dissappear as soon as I click accept, and it will not work in the game. I've deleted the settings.cfg file multiple times, installed the latest logitech drivers and application, even assigned a profile for KSP. If you run the game and look in the settings.cfg it isn't listed as an input device. This joystick works perfectly find in my other games. I've tested with x64 and x86 binaries. I've run up and down these forums and it looks like
  • Create New...