No it does not. The only real solutions for audio latency on Bluetooth are proprietary codecs like aptX or solutions that simply use Bluetooth for pairing and then switch over to a proprietary connection afterwards.
https://gbatemp.net/threads/switch-recognised-through-usb.474500/#post-7399007
The USB descriptor for the Switch console is basically a dummy USB device that does nothing. It gets the generic HID driver from Windows.
Decrypted dumps are only better than raw dumps for one thing: Piracy. They're not good for preservation and less useful than raw dumps for emulation research. Having them decrypted only helps piracy.
To properly test lag I would need to wire up an LED to the PCB and do recording tests. However I can say I don't notice any lag personally between wired and wireless mode so any actual latency is probably very minimal.
Haven't tried it wireless connected to my PC but the input latency is low enough that I can't notice it. The actual refresh rate is weird: It fluctuates between 62.5Hz and 125Hz and averages out around ~75Hz.
You could try hooking up your TV to your computer and using MonitorInfoView to see the exact resolutions your monitor claims to support. If 1920x1080 isn't reported that could be the reason.
Yeah the HID descriptor for wired mode is complete garbage and doesn't match the actual payloads at all. Right now I'm completely bypassing the OS HID driver and doing it myself.
Started work on XInput userland drivers for the pro controller. You can find it here: https://github.com/ToadKing/switch-pro-x
It uses ViGEm (https://github.com/nefarius/ViGEm) to implement a virtual Xbox 360 controller should work with all games that support XInput. For the time being you'll...
I'm confused as to the people here saying that these white-hat hackers are bad people or "snitches". Tons of companies have been doing this for a while now. Bug bounty programs are becoming the norm, so it makes sense for Nintendo to jump on it to protect their systems.
Also Nintendo's program...