DOLPHIN cores has been updated to current stream october 2025

General
#81

Weird… it was working before the update. I think I’ll try deleting the .opt files again.

edit Ok, deleting the .opt file got it working again.

2 Likes
#82

As promised, here’s a few tips to improve your experience with LibRetro Dolphin:

Core Options

Start with the default settings.

  • If you already messed with things, then recreate the defaults using Core Options > Manage Core Options > Reset Core Options.
  • If you’re coming from a previous version, then it may be needed to recreate the settings file entirely. In that case, delete the following file inside the RetroArch main directory: retroarch/config/dolphin-emu/dolphin-emu.opt.

Then, change the following:

To improve shader caching stutters

  • Set Core Options > Graphics > Settings > Shader Compilation to Async (UberShaders)

This is equivalent to the Hybrid Ubershaders on standalone Dolphin. It helps with shader caching stutters, but not necessarily eliminate them; it will depend on your machine and video driver. This will not help if your stutters happen because your hardware cannot run the game properly, not all games have the same performance requirements.

To improve frame pacing

  • Set Core Options > Core > Emulation Speed to 100% (Normal Speed)
  • Set Core Options > Core > Precision Frame Timing to On
  • Set Core Options > Graphics > Hacks > Skip Duplicate Frames to Off

A few games may still run badly (like Soulcalibur II and Alien Hominid), because they need to disable the Dual Core option, which RetroArch cannot do. A workaround is to add SyncGPU = True to the [Core] section of the corresponding INI file of the game, inside the directory retroarch/system/dolphin-emu/Sys/GameSettings/.

To reduce graphical glitches

  • Set Core Options > Graphics > Hacks > Skip EFB Copy to RAM to Off
  • Set Core Options > Graphics > Hacks > Skip XFB Copy to RAM to Off

Those are equivalent to the Store EFB/XFB Copies to Texture Only on standalone Dolphin. They’re not much useful as speedhacks, and cause graphical problems on several famous games. Of all the speedhacks which cause problems, those two are probably the ones that give the most benefit by turning them off.

Naturally, Dolphin (standalone or libretro) is quite a complex emulator in terms of solving problems per game. So visiting their wiki and searching for a game (https://wiki.dolphin-emu.org/index.php?title=Special%3ASearch) is the best guide for specific cases.

After properly configuring the Dolphin core, I also suggest using the standalone to generate calibration values for your analog sticks and pasting them into RetroArch’s configuration files. More details here: https://www.reddit.com/r/RetroArch/comments/yhl9cv/dolphin_core_and_analogue_stick_sensitivity/

5 Likes
#83

Works fine here.

Check if Core Options > System Configuration > Widescreen (Wii) is set to On. Restart the core afterward. You may need to recreate your option file, if it’s not working.

2 Likes
#84

In theory, if we just disable all the hacks in the “hacks” section, should the compatibility/accuracy be the best possible?

#85

Perhaps. A few of them are actually necessary for some games. That’s why I highlighted those two speedhacks as “safe to disable”, particularly because they cause issues, whilst fixing none. Their speed boost is also very small, so no worries about that.

1 Like
#86

The core has undergone a complete overhaul, adding many missing features and sorting them out. However, currently, playing with the GL Core driver at 60 fps is unplayable. I hope this can be fixed. I also hope the core will continue to be supported and updated, so we won’t have to wait 5+ years for the next major update, as we did recently.

#87

seems okay here with glcore. it’s reported 120 fps for some reason, but it’s a full 60. I just played through the first level of ikaruga with it.

#88

Check out F-Zero Gx, for example. Although it shows 60 fps, but it’s actually 30. The issue is reported at https://github.com/libretro/dolphin/issues/367

#89

I think the F-Zero graphics were all messed up previously, so it’s a step in the right direction.

#90

I’m still looking for a solution to get Resident Evil 1 PAL fully working. I can now launch the game, after adding the following line to the .ini file:

[Core] GPUDeterminismMode = fake-completion

However, the game gets stuck on a black screen just before reaching the intro scene in the mansion. We’re getting closer. It’s a real pleasure to play other games with this new version of the core! I’m still searching for a way to make this game work completely.

Any help or suggestions would be greatly appreciated!

#91

Does the US version work? Does it have to be PAL?

#92

The American version works, but without subtitles it’s pointless. yes for PAL

#94

I would like to provide feedback on several issues that need to be fixed or added to the core.

First, WiimoteNew.ini is missing specific lines. While not every game requires these “Features” commands, titles like Skyward Sword , No More Heroes , and The Last Story rely on the “Swing” command.

This leads to a major issue: Customization . Currently, the core does not save changes; as soon as you exit a game, everything reverts to default. Unlike other cores that work seamlessly, this core’s Custom.ini and Profiles features are non-functional. Implementing a working custom system (e.g., allowing a SOUE01.ini file) would let the core load game-specific controls at launch, solving many problems.

Additionally, adding options to enable/disable Swing , Swing Angle , and Swing Speed would make per-game customization much easier. Currently, you must manually add the text below to the .ini file. However, if the file isn’t set to “Read-Only,” the core creates a .ini.xxx shadow file, rendering any manual edits useless.

To make sword swinging more reliable, players also need a “Precise” button option. This would allow the right analog stick to toggle between IR aiming and sword swinging when the button is held.

Missing .ini lines:

Swing/Up = 
Swing/Down = 
Swing/Left = 
Swing/Right = 
Swing/Forward = 
Swing/Angle = 
Swing/Speed =

I managed to get the sword working briefly, but now the core constantly generates WiimoteNew.ini.xxx files, which deletes command lines or reverts them to null. Fixing this would be huge for RetroArch . Right now, players are either forced to buy a Mayflash sensor bar for real Wiimotes or switch to Dolphin Standalone . Improving these core features would keep users within the RetroArch ecosystem.

Could we please get a fix for these issues? Also, if anyone has found a workaround for Custom.ini , Profiles , or the .ini.xxx file generation, please let me know.

1 Like
#95

the reason it does the WiimoteNew.ini.xxx is because i have the file Read-Only I know this but should not do this if controls and commands are correct.

Hence why Custom ini need to be a thing.