• 0 Posts
  • 49 Comments
Joined 3 months ago
cake
Cake day: June 3rd, 2024

help-circle











    • Microsoft has their own controller protocol, xinput, it only works with xbox and PC

    • Sony and Nintendo both use BT HID, but add their own non-standard extras to deal with trackpads and gyros, on PC there are drivers to deal with this (inc. w/Linux kernel, extra on Windows)

    • For Wireless, Sony and Nintendo both use standard Bluetooth, you can pair a Switch or PS4/5 controller straight to a PC (though you will need extra software on Windows)

    • Microsoft uses either their somewhat proprietary 802.11AC implementation (only works with their dongles - you will need extra software on Linux, fully supported in Windows ootb) or standard Bluetooth, their BT has the highest latency of any of the 3 major controllers, but their 5ghz 802.11AC has the lowest. BT mode requires no extra drivers and will work fine ootb on Linux or Windows. You can’t use a headset plugged into the controller or connected by BT (to the controller) if you’re connecting the controller via BT.

    • MS has additional trigger rumbling/tension on the Xbox One/Series controllers, in Windows it will only work with MS Store apps - it won’t work on any Steam game :( on Linux it will work, but nothing really supports it either.

    • Sony has a much better implementation in the PS5 controller, nothing outside Sony published games use it though - but it’s compatible on Windows with additional drivers (DS4Win) (not sure about Linux here)

    • For Nintendo Switch on Windows you will need BetterJoy (previously, BetterJoyForCEMU) to support switch controllers properly, this also makes a DS4Win style gyro server, so anything that support ds4win will support Switch gyro too.









  • That’s what’s happening though.

    Microsoft has implemented a standard Direct3D API for upscalers (DirectSR), so instead of game needing to directly target DLSS AND FSR AND XeSS, it targets DirectSR and your GPU driver provides the rest (ie. nVidia drivers will target DLSS, Intel XeSS, AMD probably nothing for now, since Microsoft’s built-in scaler is a port of FSR3)

    This would only be better if Khronos had beaten them to the punch, this is Windows only, but at least it’s GPU vendor neutral.