Jump to content

armand

Members
  • Posts

    3
  • Joined

  • Last visited

Reputation

0 Neutral
  1. As macOS now officially supports eGPUs over Thunderbolt 3 (and with a small workaround on Thunderbolt 1/2), internal display support would be amazing. My TV isn't made for a good gaming experience, but I just saw Kerbin in all its high resolution glory for the first time, and I would love to get that opportunity on the internal Macbook Pro display as well. 9to5mac notes that this has to be enabled by the developer, and I read it as being a pretty simple process, but I'm no developer, so that's not for me to say: https://9to5mac.com/2018/03/29/state-of-egpu-apple-introduces-official-egpu-support-in-macos-10-13-4-internal-display-acceleration-opt-in/ I imagine a lot of Mac power users will obtain eGPUs over the next months, so internal display eGPU support would be a good and much appreciated feature moving forward!
  2. That seems to have solved it, used AFBW Revived and it worked well. Thank you, soulsource!
  3. MacOS 10.13.4, KSP 1.4.3.2152, Saitek x56 Rhino stick and throttle When I assign axes to their corresponding controls, KSP recognises the movement and all looks well: But as soon as I hit "accept" and reopen the assignment window, it's gone: This only applies to axis movement, as buttons, switches and triggers work just fine. Tried a full reinstall of KSP, and the joystick(s) are fully recognised by MacOS, but alas, the outcome is quite the same. For the record: I also tried manually editing the settings file (and undid that as it did not work), and the plane is not responding to any axis movement (but buttons work just fine.)
×
×
  • Create New...