Frequently Asked Questions
These are the games we support currently:
You sure can! You have select the Controller option in the wiimote configure window and bind the camera options to your stick of choice.
Controller guide coming soon..
You must dump your own game yourself!
See these two guides:
https://wii.guide/dump-games.html
https://dolphin-emu.org/docs/guides/ripping-games/
See the glitches and bugs page..
Emulation is tough and many things could cause it, see the performance guide page..
The map screen isn't optimised very well, all of the geometry of each room is loaded and rendered. Dolphin struggles to emulate it which unfortunately causes the framerate to tank. See the performance guide page to improve your framerate.
Yes you can! The FOV option is under Graphics > PrimeHack GFX > Field of View
Usually audio problems are related to low performance.
Try changing your Audio Backend to cubeb in Config > Audio
You may also want to try the more stable DSP LLE Recompiler engine in the same tab, however this is more performance intensive than HLE. Note you must have the game closed to change this option.
The lower the FPS, the slower your game runs. See the performance guide page..
We primarily support Windows, Linux and Mac.
Prebuilt Mac binaries (requires GitHub login): https://github.com/shiiion/dolphin/actions
Official Linux Packages:
-
Flatpak:
flatpak install flathub io.github.shiiion.primehack - Arch https://aur.archlinux.org/packages/dolphin-emu-primehack-git/
- OpenSUSE https://build.opensuse.org/package/show/home:KAMiKAZOW:Emulators/primehack
Or you can also compile PrimeHack yourself fairly easily. This is currently required if you want a portable installation.
Unfortunately there is no Android support. We are very open to any developers who would like to introduce support to more platforms.
Yes! Simply multiply your source engine sensitivity by 4.62.
For example, Team Fortress 2's default sensitivity 3.00 in PrimeHack is 3.00 * 4.62, which is 13.86.
Firstly, you should see the performance guide page. Input is based on frame-rate, so low frame-rates will have more latency and generally more stutters.
The faster the camera moves, the poorer and less smooth camera movement will become. This is primarily visible with mouse movement, as mouse users generally use much higher sensitivities than controller users. Likewise for native wiimote controls, as the turning speed is locked.
The only theoretical solution we have right now is to increase the FPS cap from 60, but this is a large challenge with many problems already.