Debugging page(s) on wiki and/or built-in troubleshooter

Brainstorming:

EmuHawk's prereq. checker only verifies that the prereq. libs exist, not where they are (because it really shouldn't matter even though it sometimes does). It would be nice if EmuHawk showed the paths of resolved and P/Invoked assemblies (the latter will need more groundwork) so users aren't forced to grab depends.exe/Dependencies while we're debugging with them.

Built-in, specialised troubleshooters would save me us a lot of support. These could just as easily be help pages on the wiki, but I think there's something to be gained from having EmuHawk do "live" checks. My top picks, chosen for being common topics for issues, are:

• keybinds and virtual gamepad binds—"controls weird" probably input method, autofire, or analog-->digital instead of analog-->analog
• "game slow" (checklist for getting the best performance out of your potato PC)—we should default to slow, accurate cores once switching is promoted more
• firmware for dummies
• custom gamedb entries
• rewind/TAStudio config optimisation
• broken .cue

Just a silly idea inspired by Android's "shake to logcat": When an EmuHawk window is focused and emulation is paused, check whether the mouse is being moved erratically.

You seem to be shaking the mouse violently in anger. Need a hand?
> Offline troubleshooter
> GitHub (readme / issue tracker)
> Discord

The issue proposes wiki help pages and live EmuHawk troubleshooters, including checks for assemblies, controls, performance, firmware, game database entries, rewind/TAStudio settings, and .cue files. Start by choosing one topic and defining its scope, then establish whether the result is a wiki page or an EmuHawk check with a clear completion criterion.