• Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About Hyperion101

  • Rank
    Bottle Rocketeer

Recent Profile Visitors

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

  1. Wish I remembered to respond to this topic once I fixed the problem, which happened. As I mentioned in my original post I tried AFBW but it didn't work, however recently I got the newest AFBW finally working, and that eliminated the input lag for once. Some bad news though, SST isn't usable anymore in KSP, since it introduces a delay on my emulated inputs and repeats them weirdly, which hasn't happened before in any other game I've used it on. But the AFBW menu makes me able to use key combinations which is enough for KSP, and I can live without the mode selector here.
  2. Is there any possible fix for the solar panels malfunctioning thanks to this mod?
  3. Well then what am I doing wrong... just installed all of the mods by following the steps, it's so easy there's not much I could possibly screw up. But none of them are for 1.4.3, so I'm surprised it's even supposed to work
  4. This is not supposed to work with 1.4.3, right? Nor any of the required or optional mods
  5. How do you run this mod on 1.4.3? I cannot get it to work at all, even with the fixed .dll from blackrack. Only the menu shows up but doesn't seem to have any effect.
  6. I don't think the profile matters as long as the axes retain their delay. You can test it on a default profile without any bindings just fine. Don't use the newer Logitech one, it's clearly inferior...
  7. I would love to hear more on that, especially when it gets released on Windows. Please keep us posted
  8. As I mentioned, try the drivers and see if you're experiencing. I said I'm not using Logitech drivers, since they downgraded the functionality. No. I need to use the SST for other simulators.
  9. Thanks for replying. I use the 64bit drivers which are the newest MadCatz ones. The current drivers are by Logitech but they made some changes to the tray icon (by removing functionalities like default profile) and the programming suite (like not making the window resizable anymore, for some reason...), while not addressing any of the bugs that I know, so I downgraded to the MadCatz drivers. I never had issues with them on Windows 8.1 or now 10. So I would look for those ones if you haven't already.
  10. After testing update 1.4.0, the issue still persists
  11. Okay, now it shows but I'm stuck with this. And the input lag is still there
  12. I cannot use my Saitek HOTAS in KSP because of the horrible input lag it introduces. There is about half a second delay for all axes, making precise flight infeasible. Some said the problem is common for other Unity games aswell, but surely there must already be a workaround for it. Other people reported success with vJoy but that bypasses the Saitek drivers which I definitely don't want to, as I rely on their programming suite where I have over a dozen complex profiles for aircraft in another simulator called DCS. I've tried Advanced Fly-By-Wire aswell, with updated .dlls, but it changes absolutely nothing on my game. The lag is there in space aswell as in atmo. Windows 10 Pro N, tested both 32bit and 64bit game versions
  13. How do you open the menu? The keyboard shortcut doesn't work for me and I can't even see any in-game button for it. At least you can get there, mine doesn't change anything within the game...
  14. Yeah I do, I installed it by moving all the files to my game folder, including the licence files. I'm on Windows 10 N Pro including Media Feature pack, all updated.
  15. Logitech doesn't offer to install the drivers and programming software separately anymore, but setups them both in one installer. Did you install the Logitech one (, or the newest Saitek SST? ( Just removed the Logitech drivers, installed Saitek ones, kept the Logitech programming software, restarted, didn't work. Removed Logitech programming software, installed good ol' Saitek SST, didn't work. Reinstalled Logitech drivers while retaining the Saitek programming software, getting rid of the Logitech software and keeping only their DirectOutput drivers, didn't work. Tested on both 64bit and 32bit versions of the game. My AFBW config xml still doesn't list a single controller. How is it possible that it works for everyone else but not me?