Dolphin bug tracker: Issueshttps://bugs.dolphin-emu.org/https://bugs.dolphin-emu.org/favicon.ico?12023-12-15T06:49:29ZDolphin bug tracker
Redmine Emulator - Emulator Issues #13433 (New): Shader compilation triggered by graphics settings change...https://bugs.dolphin-emu.org/issues/134332023-12-15T06:49:29Zmbc07jhonn.copperfield@gmail.com
<p><strong>Game Name?</strong><br>
Any</p>
<p><strong>Game ID?</strong><br>
Any</p>
<p><strong>MD5 Hash?</strong><br>
N/A</p>
<p><strong>What's the problem? Describe what went wrong.</strong><br>
If you have "Compile shaders before starting" enabled and then, while a game is running, toggle a graphics settings which requires reloading the shaders (e.g. enabling/disabling "Per-Pixel Lightning" or MSAA), the game will pause and the shader compilation progress bar will show up. While the progress bar is showing, the compilation can't be aborted, trying to do so (e.g. clicking "Stop" button from Dolphin's toolbar) will freeze up the entire GUI until the compilation is finished. </p>
<p><strong>What steps will reproduce the problem?</strong><br>
1) Make sure "Compile shaders before starting" is enabled and boot any game<br>
2) While the game is running, enable/disable "Per-Pixel Lightning" or MSAA<br>
3) The game will pause and the shader compilation progress bar will now show up<br>
4) Before the shader compilation finishes, try to stop the emulation (e.g. Stop button in the toolbar)<br>
5) The entire GUI will now freeze, until the shader compilation is done </p>
<p><strong>Is the issue present in the latest development version?</strong><br>
Yes. Tested on 5.0-20734</p>
<p><strong>Is the issue present in the latest stable version?</strong><br>
N/A. Last stable doesn't have ubershaders, nor the "compile shaders before starting" option</p>
<p><strong>If the issue isn't present in the latest stable version, which is the first broken version?</strong><br>
N/A</p>
<p><strong>What are your PC specifications?</strong> (CPU, GPU, Operating System, more)<br>
<strong>OS:</strong> Windows 11 Insider Preview (build 26016.1000)<br>
<strong>CPU:</strong> Intel Core i7-11800H<br>
<strong>GPU:</strong> NVIDIA GeForce RTX 3060 Laptop</p>
<p><strong>Is there anything else that can help developers narrow down the issue?</strong><br>
I remember this used to be a issue when booting up games, you could cause the same GUI freeze by trying to stop emulation before the compilation was done. This is now fixed (pressing Stop in the toolbar will abort the shader compilation immediately and won't freeze the GUI), but it only works when booting up. Extending this behavior to cases where the shader compilation is triggered later (like when enabling/disabling "Per-Pixel Lightning" or MSAA while the game is running) should fix this issue.</p>
Emulator - Emulator Issues #13121 (Invalid): [Regression] Updater always fail with "Could not fet...https://bugs.dolphin-emu.org/issues/131212022-12-11T00:53:11Zmbc07jhonn.copperfield@gmail.com
<p><strong>Game Name?</strong><br>
N/A</p>
<p><strong>Game ID?</strong><br>
N/A</p>
<p><strong>MD5 Hash?</strong><br>
N/A</p>
<p><strong>What's the problem? Describe what went wrong.</strong><br>
Starting with Dolphin 5.0-17693 on Windows, updater always error out with "A fatal error occurred and the updater cannot continue: Could not fetch current manifest. Aborting."</p>
<p><strong>What steps will reproduce the problem?</strong></p>
<ol>
<li>Download Dolphin 5.0-17693 or newer (make sure to go at least one version older than the latest available build, otherwise there won't be any updates to apply).</li>
<li>Select the Dev update track in Dolphin's auto-update settings.</li>
<li>Either close and reopen Dolphin, or go to Help => Check for updates.</li>
<li>New update popup will show up. Click "Install Update".</li>
<li>Updater will fail with "Could not fetch current manifest. Aborting." error.</li>
</ol>
<p><strong>Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.</strong><br>
Yes. Tested on 5.0-18042.</p>
<p><strong>Is the issue present in the latest stable version?</strong><br>
No.</p>
<p><strong>If the issue isn't present in the latest stable version, which is the first broken version?</strong> <br>
The problem started with 5.0-17693 (the merge of <a href="https://github.com/dolphin-emu/dolphin/pull/11189" class="external">PR #1189</a>). The updater works fine on 5.0-17691 or older.</p>
<p><strong>If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible.</strong><br>
N/A</p>
<p><strong>What are your PC specifications?</strong><br>
Intel Core i7-11800H<br>
NVIDIA GeForce RTX 3060 Laptop<br>
Windows 11 Pro (Insider Preview)</p>
<p><strong>Is there anything else that can help developers narrow down the issue?</strong></p>
<ul>
<li>I'm aware the updater now checks the installed VC++ Runtime version, but I don't think that's the problem. For reference I have the most recent version (at the time this issue was opened) of VC++ 2015-2022 installed: 14.34.31931 </li>
<li>I've confirmed the directory where Dolphin is installed is writable (both by regular users as well as administrators)</li>
<li>I tried executing both Dolphin and the Updater with elevated privileges, but nothing changed</li>
<li>With the aid of Process Explorer I checked the command line passed to the updater in 5.0-17693 (first broken version) and 5.0-17691 (last working version) but didn't notice anything wrong apart from the new "--binary-to-restart" parameter, which seemed correct anyway</li>
</ul>
Emulator - Emulator Issues #12865 (Invalid): "Perform Online Update" doesn't work anymore (Ninten...https://bugs.dolphin-emu.org/issues/128652022-03-16T20:42:51Zmbc07jhonn.copperfield@gmail.com
<p>I've seen a report on Reddit of an user being unable to perform an online update with 5.0-16101 on Android, just checked on Windows with Dolphin 5.0-16143 and the same is happening there too. Log says:</p>
<p><code>E[COMMON]: Failed to POST http://nus.shop.wii.com/nus/services/NetUpdateSOAP: Failed to connect to nus.shop.wii.com port 80: Connection refused</code></p>
<p>I don't know if this is something temporary or if Nintendo had pulled the update servers for good. If the latter, perhaps "Perform Online Update" should be hidden from the GUI to avoid confusion...</p>
Emulator - Emulator Issues #12764 (Work started): [Android] [Scoped Storage] Consider moving the ...https://bugs.dolphin-emu.org/issues/127642021-12-15T09:59:20Zmbc07jhonn.copperfield@gmail.com
<p>Since version 5.0-15348, Dolphin complies with Scoped Storage requirements by storing the user folder under Internal Storage => Android => data => org.dolphinemu.dolphinemu. That folder, however, has restricted access and the transition hasn't been exactly smooth (we've seen phones that deny access to the folder even when accessed on a computer via USB, phones that hides the only system app that still has full access to the folder, among other related issues). </p>
<p>I've been watching how other apps that used to store content in bare folders at the root of the internal storage reacted since the Scoped Storage enforcement went live on the Play Store and noticed that a few opted to use Android => media instead of Android => data (e.g. WhatsApp). At first I thought only media files could be stored there but those apps are storing all kinds of files there. The most important benefit, however, is that the media folder doesn't have the same access restrictions of the data subfolder: any app can read/write files there, even in the folder of other apps and using that directory seems sufficient to comply with the Scoped Storage requirements.</p>
<p>I haven't investigated if there are other implications in using the Android\media folder that might affect Dolphin, but given the benefits it might be worth considering the switch, if feasible?</p>
Emulator - Emulator Issues #12755 (Fixed): [Android] "Open System File Manager" button on User Da...https://bugs.dolphin-emu.org/issues/127552021-12-08T06:08:45Zmbc07jhonn.copperfield@gmail.com
<p><strong>Game Name?</strong><br>
N/A</p>
<p><strong>Game ID?</strong><br>
N/A</p>
<p><strong>MD5 Hash?</strong><br>
N/A</p>
<p><strong>What's the problem? Describe what went wrong.</strong><br>
Since the adoption of Scoped Storage, the Android port of Dolphin has an "User Data" screen (Settings => Config => User Data) with a shortcut to launch the system file manager (DocumentsUI), as it's the only system app that retains full access to the Android folder on internal storage. However, on Samsung devices (tested with Galaxy A71, A72 and S20 FE -- all running Android 11), the shortcut doesn't work (you get a popup saying "Sorry, Dolphin couldn't find the system file manager on your device").</p>
<p>Looking at the source code, the shortcut tries to launch the <code>com.android.documentsui.files.FilesActivity</code> and if it can't find it, the popup appears. However, even through that activity exists on the Samsung devices I tested, Dolphin still fails to launch it and shows the error popup instead. </p>
<p><strong>What steps will reproduce the problem?</strong></p>
<ol>
<li>Make sure you're running Dolphin 5.0-15348 or newer on a Samsung device updated to Android 11</li>
<li>Open Dolphin, go to Settings => Config => User Data</li>
<li>Click on the "Open System File Manager" button</li>
</ol>
<p><strong>Is the issue present in the latest development version?</strong><br>
Yes. Tested on 5.0-15586</p>
<p><strong>Is the issue present in the latest stable version?</strong><br>
N/A</p>
<p><strong>If the issue isn't present in the latest stable version, which is the first broken version?</strong><br>
N/A</p>
<p><strong>What are your <del>PC</del> smartphone specifications?</strong><br>
Tested on the following devices:</p>
<ul>
<li>Samsung Galaxy A71 (Snapdragon 730, Adreno 618, 6 GB of RAM, Android 11)</li>
<li>Samsung Galaxy A72 (Snapdragon 720G, Adreno 618, 6 GB of RAM, Android 11)</li>
<li>Samsung Galaxy S20 FE (Snapdragon 865, Adreno 650, 6 GB of RAM, Android 11)</li>
</ul>
<p><strong>Is there anything else that can help developers narrow down the issue?</strong><br>
On the tested devices, the DocumentsUI activity can be launched without issues via <a href="https://play.google.com/store/apps/details?id=de.szalkowski.activitylauncher" class="external">Activity Launcher</a> (source code <a href="https://github.com/butzist/ActivityLauncher" class="external">available here</a>). It can also be started from ADB (<code>adb shell "am start com.google.android.documentsui/com.android.documentsui.files.FilesActivity"</code>). I personally only experienced the problem with Samsung, but I've seen one or two reports of the same issue with other phone brands in the Dolphin Reddit Community...</p>
Emulator - Emulator Issues #12597 (Working as intended): Integrated GBAs are started even when ru...https://bugs.dolphin-emu.org/issues/125972021-07-24T18:18:59Zmbc07jhonn.copperfield@gmail.com
<p><strong>Game Name?</strong><br>
Any Wii title</p>
<p><strong>Game ID?</strong><br>
N/A</p>
<p><strong>MD5 Hash?</strong><br>
N/A</p>
<p><strong>What's the problem? Describe what went wrong.</strong><br>
If you have any GameCube input set as "GBA (integrated)" and then boot a Wii game, a mGBA instance will be started for every port set as GBA, even though no Wii titles have GBA integration support.</p>
<p><strong>What steps will reproduce the problem?</strong><br>
1) Set one or more GameCube input ports as "GBA (integrated)" in the controller settings<br>
2) Start any Wii game or software (Channels, Virtual Console, WiiWare, etc)<br>
3) Watch instances of mGBA popping up on screen even through they're useless in Wii titles</p>
<p><strong>Is the issue present in the latest development version?</strong><br>
Yes. Tested on 5.0-14731</p>
<p><strong>Is the issue present in the latest stable version?</strong><br>
N/A (5.0 stable doesn't have the mGBA integration, it only appeared in 5.0-14690)</p>
<p><strong>If the issue isn't present in the latest stable version, which is the first broken version?</strong><br>
N/A</p>
<p><strong>What are your PC specifications?</strong><br>
CPU: Intel Core i7-3630QM<br>
GPU: NVIDIA GeForce GT 650M<br>
OS: Windows 11 (Insider Preview)</p>
<p><strong>Is there anything else that can help developers narrow down the issue?</strong><br>
Perhaps a better behavior would be partially overriding the GameCube input settings when Dolphin is booted in Wii mode, temporarily setting any port set as "GBA (integrated)" or "GBA (TCP)" to "None"?</p>
Emulator - Emulator Issues #12515 (Fixed): Wii System Menu 1.0U (v33) crashes at boot with DSP HLEhttps://bugs.dolphin-emu.org/issues/125152021-05-20T19:05:57Zmbc07jhonn.copperfield@gmail.com
<p><strong>Game Name?</strong><br>
Wii System Menu</p>
<p><strong>Game ID?</strong><br>
0000000100000002</p>
<p><strong>MD5 Hash?</strong><br>
b10537aeb4e917fd80e93d4e50acff63</p>
<p><strong>What's the problem? Describe what went wrong.</strong><br>
Dolphin will always crash at boot when attempting to boot Wii System Menu 1.0 if DSP HLE is selected. With DSP LLE the problem doesn't happen.</p>
<p><strong>What steps will reproduce the problem?</strong><br>
(Wii System Menu 1.0 isn't available on Nintendo Update Servers, you'll need a copy of the Wii Startup Disc to reproduce this)</p>
<ol>
<li>Make sure you have an empty NAND (e.g. Wii folder on Dolphin's user directory is empty)</li>
<li>Boot the Wii Startup Disc in Dolphin (game ID for the disc is RAAE01)</li>
<li>Wait until the install is finished</li>
<li>When it asks, eject the disc by going into File => Eject disc</li>
<li>The installer will exit to the Wii System Menu and Dolphin will crash now if DSP HLE is selected.</li>
</ol>
<p>After using the Wii Startup Disc once, you can skip the installer by going into Tools => Load Wii Menu 1.0U directly. It'll always crash at boot unless DSP LLE Recompiler or Interpreter is selected (the free DSP ROM replacement bundled with Dolphin works fine)</p>
<p><strong>Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.</strong><br>
Yes. Tested on 5.0-14245</p>
<p><strong>Is the issue present in the latest stable version?</strong><br>
5.0 stable can't boot Wii System Menu 1.0. It'll always hang on a black screen, regardless of the settings (it doesn't crash, though)</p>
<p><strong>If the issue isn't present in the latest stable version, which is the first broken version?</strong><br>
N/A</p>
<p><strong>What are your PC specifications?</strong><br>
CPU: Intel Core i7-3630QM<br>
GPU: NVIDIA GeForce GT 650M<br>
OS: Windows 10 (build 21382)</p>
<p><strong>Is there anything else that can help developers narrow down the issue?</strong><br>
I've tried other settings (single core, MMU, cached interpreter), the only thing that prevents the crash is switching to DSP LLE. I've also attached a log file of what happens in Dolphin between clicking on Tools => Load Wii System Menu and the crash...</p>
Emulator - Emulator Issues #12049 (Fixed): Medal of Honor Vanguard can't find its save data since...https://bugs.dolphin-emu.org/issues/120492020-04-12T22:29:24Zmbc07jhonn.copperfield@gmail.com
<p><strong>Game Name?</strong><br>
Medal of Honor: Vanguard</p>
<p><strong>Game ID?</strong> <br>
RMVE69</p>
<p><strong>MD5 Hash?</strong><br>
44cddd3c37c3585b58cc2ac107fe2d34</p>
<p><strong>What's the problem? Describe what went wrong.</strong><br>
Since 5.0-11578, the game won't find its save data. It can successfully create and save profiles, but on the next game run, no save files will be found.</p>
<p><strong>What steps will reproduce the problem?</strong><br>
Create a profile, play one of the campaigns, save your progress, then reboot the game. Save data will not appear in-game, even through it exists on the virtual NAND.</p>
<p><strong>Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.</strong><br>
Yes. Tested on 5.0-11832.</p>
<p><strong>Is the issue present in the latest stable version?</strong><br>
No. Saving works fine on 5.0 stable.</p>
<p><strong>If the issue isn't present in the latest stable version, which is the first broken version?</strong><br>
The last working build is 5.0-11558. Starting with 5.0-11578 (IOS/FS: Reimplement many functions in a more accurate way), saving is broken.</p>
<p><strong>What are your PC specifications?</strong> <br>
CPU: Intel Core i7-6700<br>
GPU: AMD Radeon RX 480<br>
RAM: 16 GB<br>
OS: Windows 10</p>
<p><strong>Is there anything else that can help developers narrow down the issue?</strong><br>
<a href="https://forums.dolphin-emu.org/Thread-wii-game-won-t-recognize-save-files-medal-of-honor-vanguard" class="external">https://forums.dolphin-emu.org/Thread-wii-game-won-t-recognize-save-files-medal-of-honor-vanguard</a></p>
Emulator - Emulator Issues #11910 (Fixed): Just Dance series crashes/freezes/hangs when the emula...https://bugs.dolphin-emu.org/issues/119102019-11-27T20:54:12Zmbc07jhonn.copperfield@gmail.com
<p><strong>Game Name?</strong><br>
Just Dance 2<br>
Just Dance 3<br>
Just Dance 4<br>
Just Dance 2014<br>
Just Dance 2015<br>
Just Dance 2016<br>
Just Dance 2017<br>
Just Dance 2018</p>
<p><strong>Game ID?</strong><br>
SD2E41<br>
SJDE41<br>
SJXE41<br>
SJOE41<br>
SE3E41<br>
SJNE41<br>
SZ7E41<br>
SE8E41</p>
<p><strong>MD5 Hash?</strong><br>
545c5a833dd274e0cc62d72d91559dca<br>
e46877c360dcbb6cc8c5814762b424a3<br>
cfa93ad1209bd9dd61cf9df3d9b6adc4<br>
64d469178d925d5b79ae26f7289d165b<br>
6142795d6f0700963b9754ca59c92d90<br>
8041c2a5ad9465cb5fac6657514e3ea2<br>
31e872f305d4355416a4ce345fdd9c4c<br>
fe3219a6caac46e5f4f233f197e860f8</p>
<p><strong>What's the problem? Describe what went wrong.</strong><br>
<strong>Just Dance 2/3/4:</strong> these games will randomly freeze when the emulated console has internet connectivity. When they freeze, only the background music keeps playing and only a forced shutdown (clicking Stop button twice) can stop the emulation.<br>
<strong>Just Dance 2014/2015/2016/2017/2018:</strong> these games will hang on an infinite loading screen when trying to create or edit a dancer card. Since on the first boot you must create at least one dancer card, this renders those game unplayable.</p>
<p><strong>What steps will reproduce the problem?</strong><br>
Make sure the Wii network certificates (<code>clientca.pem</code>, <code>clientcakey.pem</code>, <code>rootca.pem</code>) exists on the root of your NAND, then:<br>
<strong>Just Dance 2/3/4:</strong> just play the game, they'll eventually freeze, sometimes even before you can start a song. On Just Dance 2, trying to access the shop once seems to be required before the random freeze occurs.<br>
<strong>Just Dance 2014/2015/2016/2017/2018:</strong> create a Dancer Card (you must do this on the first time you start the game), or in case you already have an existing save file, click on the Dancer Card option at the top-left portion of the main menu and create a new / edit an existing Dancer Card. When you're done, you'll be stuck on an infinite loading screen (the game won't crash nor freeze, though).</p>
<p><strong>Is the issue present in the latest development version?</strong><br>
Yes. Tested all on 5.0-11288.</p>
<p><strong>Is the issue present in the latest stable version?</strong><br>
Yes. Tested all on 5.0 stable, except for Just Dance 2014/2015/2016/2017, which were tested on 5.0-775 (the first Dolphin version that can boot these games).</p>
<p><strong>If the issue isn't present in the latest stable version, which is the first broken version?</strong><br>
N/A</p>
<p><strong>What are your PC specifications?</strong><br>
CPU: Intel Pentium G3258 @ 4.2GHz (OC)<br>
GPU: NVIDIA GeForce GT 440 @ 1GB DDR3<br>
RAM: 16GB @ DDR3-1600 (4x4GB)<br>
OS: Windows 10 (version 1909)</p>
<p><strong>Is there anything else that can help developers narrow down the issue?</strong><br>
Issues that I strongly believe are connected to the same "root" problem and that probably could be merged on this one: <a class="issue tracker-1 status-13 priority-2 priority-default closed" title="Emulator Issues: Just Dance 2014 freezes at Ubisoft logo if .pem files are present (Duplicate)" href="https://bugs.dolphin-emu.org/issues/11441">#11441</a> <a class="issue tracker-1 status-13 priority-2 priority-default closed" title="Emulator Issues: Just Dance 2014/2015/2016/2017/2018 hangs during save file creation (Duplicate)" href="https://bugs.dolphin-emu.org/issues/11342">#11342</a> <a class="issue tracker-1 status-13 priority-2 priority-default closed" title="Emulator Issues: Just Dance 3 - after 20s California Girls hangs with music. Emulation needs force close (did'nt t... (Duplicate)" href="https://bugs.dolphin-emu.org/issues/10873">#10873</a> <a class="issue tracker-1 status-8 priority-2 priority-default closed" title="Emulator Issues: Just dance 3 hang ubisoft logo on dolphin trunk 18370 WITHOUT internet conection (IPC_HLE related) (Invalid)" href="https://bugs.dolphin-emu.org/issues/8597">#8597</a></p>
<p>Any of the following workarounds works both in 5.0 stable and on current development builds and prevents triggering this issue:</p>
<ul>
<li>Physically disconnecting your computer from the internet before playing the game;</li>
<li>Temporarily disabling your network adapter(s) or enabling airplane mode if on a laptop;</li>
<li>Deleting <code>clientca.pem</code>, <code>clientcakey.pem</code> and <code>rootca.pem</code> from your NAND's root (however current development builds will keep throwing a Panic Alert saying these files are missing every time the game tries to connect to the internet).</li>
</ul>
<p>Most of these issues (especially on Just Dance 2/3/4) were seemingly fixed for good once Dolphin implemented Wii Network functionality back in the now ancient 3.5-2143 build. I can't really confirm this since I only got aware of the problem with the earlier games recently but it seems that Wii Shop closure is what brought back all these problems to life again. In fact, looking at the Dolphin log, there's always a spam of the following lines moments before the earlier games freeze and the later games hang on the infinite loading screen:</p>
<pre><code>core\ios\network\socket.cpp:247 I[IOS_NET]: IOCTL_SO_CONNECT (00000000, 216.98.48.66:443) = -1
core\ios\network\socket.cpp:119 E[IOS_NET]: SO_CONNECT failed with error 10037, ret= -1
</code></pre>
<p>The actual IP varies between the games, but it's always pointing to servers that just time out without any response if, for example, you try to ping them. It seems as our network code doesn't correctly respond to the game that the connection timed out and thus it keeps retrying until it freezes (earlier games) or until it hangs on the infinite loading screen (later games), as none of these problems occurs on a real Wii / vWii.</p>
<p>Since the workarounds aren't too convenient (especially for less tech-savvy users), it would be good having a per-game option in Dolphin to emulate a Wii console without internet access. I tried booting to Wii Menu and clearing all saved network profiles and then launching the game from the Disc Channel but nothing changed as the games still had internet access and ended triggering the issue (Dolphin seems to override whatever setting is configured on the network profiles from the Wii Menu).</p>
<p>For records, Just Dance 1, Just Dance 2019 and Just Dance 2020 doesn't have any kind of internet connectivity an thus doesn't experience any freeze or hang. I don't own any of the spin-off or compilation Just Dance games so I can't tell if they're also affected, but given the pattern, it seems reasonable to assume they are affected too if at some point they had online related features...</p>
Emulator - Emulator Issues #11906 (Fixed): Dolphin's built-in GCZ compressor generate broken file...https://bugs.dolphin-emu.org/issues/119062019-11-26T05:11:06Zmbc07jhonn.copperfield@gmail.com
<p><strong>Game Name?</strong><br>
Probably any Wii game (tested only Super Smash Bros Brawl)</p>
<p><strong>Game ID?</strong><br>
RSBE01</p>
<p><strong>MD5 Hash?</strong><br>
Source ISO, untouched: 52ce7160ced2505ad5e397477d0ea4fe <br>
Source ISO converted to nkit.iso: a3957f79521cc9d8bb576f2b33852f8a<br>
nkit.iso compressed to GCZ via Dolphin: 56e8fb25c3f924e2a61ea4130325f700</p>
<p><strong>What's the problem? Describe what went wrong.</strong><br>
If you use Dolphin to compress a Wii ISO in nkit.iso format to GCZ, the resulting file will be a very small (but still valid) GCZ file with just empty partitions.</p>
<p><strong>What steps will reproduce the problem?</strong><br>
1) Use Dolphin to compress a Wii ISO in nkit.iso format to GCZ<br>
2) Check the resulting file:<br>
Input ISO in nkit.iso format: 6.89 GiB<br>
Output ISO in GCZ format: 22.4 MiB</p>
<p><strong>Is the issue present in the latest development version?</strong><br>
Yes. Tested on 5.0-11288</p>
<p><strong>Is the issue present in the latest stable version?</strong><br>
Not tested. As far as I know, 5.0 stable doesn't support NKIT processed ISOs</p>
<p><strong>What are your PC specifications?</strong><br>
CPU: Intel Pentium G3258 @ 4.2GHz (OC)<br>
GPU: NVIDIA GeForce GT 440 @ 1GB DDR3<br>
RAM: 16GB @ DDR3-1600 (4x4GB)<br>
OS: Windows 10 (version 1909)</p>
<p><strong>Is there anything else that can help developers narrow down the issue?</strong><br>
Since NKIT can convert plain ISOs to nkit.gcz format directly, I think we can just make Dolphin refuse to compress the ISO to GCZ if it detects the input ISO is in nkit.iso format and call it a day. We just need a fool-proof check in Dolphin to stop users from messing their NKIT procesed ISOs...</p>
Emulator - Emulator Issues #11808 (Working as intended): [Feature Request] Dump emulated console ...https://bugs.dolphin-emu.org/issues/118082019-07-26T20:06:21Zmbc07jhonn.copperfield@gmail.com
<p><strong>Game Name?</strong><br>
N/A</p>
<p><strong>Game ID?</strong><br>
N/A</p>
<p><strong>MD5 Hash?</strong><br>
N/A</p>
<p><strong>What's the problem? Describe what went wrong.</strong><br>
While Dolphin has a very useful debugger built-in (well, as long as you launch it with -d parameter) it lacks an option to create a memory dump of the emulated console's RAM. Although you can workaround this with external tools (e.g. by creating a memory dump of the whole emulator process using Windows Task Manager), the resulting dump is always super big as it includes all memory used by Dolphin, not just the emulated console's RAM (which should be 40 MB for GameCube games and 88 MB for Wii games AFAIK).</p>
<p><strong>What steps will reproduce the problem?</strong><br>
N/A</p>
<p><strong>Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.</strong><br>
Yes. Tested on 5.0-10713</p>
<p><strong>Is the issue present in the latest stable version?</strong><br>
Yes</p>
<p><strong>If the issue isn't present in the latest stable version, which is the first broken version?</strong><br>
N/A</p>
<p><strong>If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible.</strong><br>
N/A</p>
<p><strong>What are your PC specifications?</strong><br>
N/A</p>
<p><strong>Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,<br>
configuration files, savefiles, savestates)</strong><br>
Nope</p>
Emulator - Emulator Issues #11775 (Fixed): Windows Updater: choosing "update after closing Dolphi...https://bugs.dolphin-emu.org/issues/117752019-06-23T17:15:39Zmbc07jhonn.copperfield@gmail.com
<p><strong>Game Name?</strong><br>
N/A</p>
<p><strong>Game ID?</strong> <br>
N/A</p>
<p><strong>MD5 Hash?</strong><br>
N/A</p>
<p><strong>What's the problem? Describe what went wrong.</strong><br>
With automatic updates enabled, if you choose "update after closing Dolphin", the updater is immediately launched and keeps waiting. I'm not sure if that's by design but I think it should be launched only when you close Dolphin, as implied by the checkbox.</p>
<p><strong>What steps will reproduce the problem?</strong></p>
<ol>
<li>Launch a Dolphin build which isn't the latest available</li>
<li>In Dolphin Auto Update settings, select "Dev (multiple times a day)"</li>
<li>Click Help => Check for updates or close and reopen Dolphin</li>
<li>Mark the checkbox "update after closing Dolphin" and click "Install Update"</li>
<li>The updater will launch immediately instead of waiting for Dolphin to close</li>
</ol>
<p><strong>Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.</strong><br>
Yes. Tested on 5.0-10551</p>
<p><strong>Is the issue present in the latest stable version?</strong><br>
No. Updater isn't available in 5.0 stable</p>
<p><strong>If the issue isn't present in the latest stable version, which is the first broken version?</strong><br>
Seems to be present since the updater was introduced in 5.0-7088</p>
<p><strong>What are your PC specifications?</strong><br>
CPU: Intel Core i7-3630QM @ 2.4GHz<br>
GPU: NVIDIA GeForce GT 635M @ 2GB DDR3<br>
RAM: 12GB @ DDR3-1600 (4+8GB)<br>
OS: Windows 10 (Insider Preview)</p>
<p><strong>Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,<br>
configuration files, savefiles, savestates)</strong><br>
Nope</p>
Emulator - Emulator Issues #11342 (Duplicate): Just Dance 2014/2015/2016/2017/2018 hangs during s...https://bugs.dolphin-emu.org/issues/113422018-08-13T06:40:57Zmbc07jhonn.copperfield@gmail.com
<p><strong>Game Name/ID?</strong></p>
<ul>
<li>Just Dance 2014 [SJOE41]</li>
<li>Just Dance 2015 [SE3E41]</li>
<li>Just Dance 2016 [SJNE41]</li>
<li>Just Dance 2017 [SZ7E41]</li>
<li>Just Dance 2018 [SE8E41]</li>
</ul>
<p><strong>What's the problem? Describe what went wrong.</strong><br>
Upon first booting any of the mentioned games, you need to create a Dancer Card (works like a profile) so you can keep track of your game progression. After selecting your avatar, nickname and other stuff, the game will get stuck in a never ending loading screen and you can't proceed.</p>
<p><strong>What steps will reproduce the problem?</strong></p>
<ol>
<li>Boot one of the affected Just Dance games with no existing save files on your NAND</li>
<li>The game will ask you to create a Dancer Card</li>
<li>Enter a nickname, select an avatar and the other stuff, click on "Continue"</li>
<li>Game will now get stuck in a never ending loading screen</li>
</ol>
<p><strong>Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.</strong><br>
Yes. Last tested on 5.0-8563</p>
<p><strong>Is the issue present in the latest stable version?</strong><br>
Yes (see additional info below). Last tested on 5.0</p>
<p><strong>If the issue isn't present in the latest stable version, which is the first broken version?</strong><br>
So, that's where it gets tricky. At least until November 3rd, 2017, those games didn't experience this issue in 5.0 stable nor in 5.0-4877, which was the development build I was using at that time. On February 10th, 2018, an user on the forums complained about having this issue in both 5.0-4877 and also in 5.0-6304, and upon retesting again in a fresh Dolphin install, I also started experiencing this save hang issue in any build from Dolphin 3.5-2143 (!!!) and onwards, even in the same 5.0-4877 build I'm 100% sure it worked before.</p>
<p>The closest Dolphin build I could find before 3.5-2143 is Dolphin 3.5-1936, where the issue doesn't occur, and that's also the last Dolphin build made before the merge of wii-network branch (and consequently, wii-usb branch too, because it was merged into wii-network sometime before wii-network branch got merged into master). For last, I tried finding old builds of the wii-network branch (before it was merged to master) to try bisecting this gap a little more but I couldn't... </p>
<p><strong>What are your PC specifications?</strong><br>
CPU: Intel Core i7-3630QM<br>
GPU: NVIDIA GeForce GT 635M<br>
RAM: 8 GB dual-channel<br>
OS: Windows 10</p>
<p><strong>Is there anything else that can help developers narrow down the issue?</strong></p>
<ul>
<li>What I've tried in recent builds: single core mode, cached interpreter instead of JIT and even MMU emulation, nothing changed, the issue still occurred exactly the same.</li>
<li>Looking at the Dolphin log since the game boot until it gets stuck at the infinite loading screen, there aren't any warning or error messages there.</li>
<li>If you create the save file in a previous known working version (e.g. Dolphin 3.5-1936) then transfer it to the current development builds, the game will work and will also save your progress just fine (that's the workaround listed on the wiki, BTW). However, if you try to edit the existing Dancer Card (e.g. change the avatar or nick), the game will get stuck in the infinite loading screen once again, and upon rebooting the game, nothing will have changed.</li>
<li>If your NAND has save files of previous Just Dance games, Just Dance 2014 and onward acknowledges that and thanks you by unlocking some exclusive avatars. This seems to indicate the game can read NAND content just fine but it has trouble creating new files?</li>
<li>The issue started occurring even in Dolphin builds known to work in the past, the games geting stuck during the save file creation envolves file access, since in the past we had similar file access issues on Zelda Wind Waker due a buggy Visual C++ runtime, I tried downgrading the redistributables to several old versions of VS2017 and VS2015 but nothing changed.</li>
<li>I can't think of anything else that might be causing this issue, the only certainty I have is that an external factor (a random Windows update? Drivers? whatever) made this issue show up in Dolphin, since even builds known to work in the past now have this problem too. At this point I just gave up and opened this issue ¯\<u>(ツ)</u>/¯</li>
</ul>
Emulator - Emulator Issues #10128 (Accepted): Just Dance 2/3/4 issues with multiple DLC songshttps://bugs.dolphin-emu.org/issues/101282017-02-28T04:34:09Zmbc07jhonn.copperfield@gmail.com
<p>Big issue report incoming!</p>
<p><strong>Game Name?</strong><br>
Just Dance 2<br>
Just Dance 3<br>
Just Dance 4</p>
<p><strong>Game ID?</strong><br>
SD2Y41<br>
SJDY41<br>
SJXE41</p>
<p><strong>MD5 Hash?</strong><br>
None of my MD5 hashes will match good dumps as I scrubbed the ISOs, but all of them passes in Dolphin's built-in Partition Integrity Check.</p>
<p><strong>What's the problem? Describe what went wrong.</strong><br>
The mentioned games have weird issues if you have more than 11 DLC songs on the NAND dump at the same time. What will happen varies depending of the game, but the three basically won't play some of those DLC songs and will end throwing infinite "Invalid read/write from 0xXXXXXXXX, PC=0xXXXXXXXX" at some time:</p>
<p><strong>Just Dance 2:</strong> The preview in the track selection menu won't play for any of the DLC songs, regardless of how many songs you have on the NAND. If you have more than 11 DLC songs, the song you selected might start throwing "Invalid read/write from 0xXXXXXXXX, PC=0xXXXXXXXX" upon starting the song. If you disable Panic Handlers, Dolphin won't crash and the game will just be there sitting at the start of the DLC song (as if it were paused at 0:00). Sometimes you'll also hear a high pitched, continuous sound, or the game might simply keep repeating the last SFX played indefinitely. You can still pause and go back to the main menu to select another song when that occurs.</p>
<p><strong>Just Dance 3:</strong> if you have more than 11 DLC songs it'll start throwing "Invalid read/write from 0xXXXXXXXX, PC=0xXXXXXXXX" as soon as you hover over some of the DLC songs in the track selection menu. If you disable Panic Handlers, the game will completely freeze with FPS 0/VPS 60 when you hover one of these DLCs that causes the Panic Alerts and the only thing you can do is force stopping the emulation (graceful shutdown won't work either after the game freezes).</p>
<p><strong>Just Dance 4:</strong> if you have more than 11 DLC songs it'll start throwing "Invalid read/write from 0xXXXXXXXX, PC=0xXXXXXXXX" as soon as you hover over some of the DLC songs in the track selection menu. If you disable Panic Handlers the game won't crash, it just won't play the preview of the DLCs that causes the Panic Alerts but you can select that song and play it anyway, and although the lyrics, pictograms and background animations/effects will show and animate normally, the dancers won't appear and the music won't play. You can still pause and go back to the main menu or jump directly to another song from the pause menu when that occurs.</p>
<p><strong>What steps will reproduce the problem?</strong><br>
You just need to have a NAND dump with more than 11 DLC songs for any of the mentioned games to trigger the issue, and it doesn't need to be a complete NAND dump (e.g. manually copying only the ticket and the DLC contents -- 00000001.app, 00000002.app, etc -- to the proper location is enough).</p>
<p><strong>Which versions of Dolphin did you test on? Does using an older version of Dolphin solve your issue? If yes, which versions of Dolphin used to work?</strong><br>
I tested current and previous stable releases (3.0, 3.5, 4.0.2 and 5.0) and the current development build (5.0-2668) and all of them exhibits this issue.</p>
<p><strong>What are your PC specifications?</strong><br>
CPU: Intel Core i7-3630QM @ 2.4GHz<br>
GPU: NVIDIA GeForce GT 635M @ 2GB GDDR3<br>
RAM: 8GB @ DDR3-1600 (2x4GB)<br>
OS: Windows 10</p>
<p><strong>Is there any other relevant information? (e.g. logs, screenshots,<br>
configuration files)</strong><br>
That's something I've been trying to debug for a while, and those are my findings:</p>
<ul>
<li><p>I didn't notice anything relevant to this issue in the Dolphin log when triggering the problem.</p></li>
<li><p>By messing with the DLC files on the NAND, I noticed all of the three games can play all of the DLCs fine, the issue only occurs if you have more than 11 DLCs at the same time and even then, some will still play normally while others will just trigger the issue.</p></li>
<li><p>The song(s) that will trigger the issue varies depending of the number of DLCs you currently have on the NAND. For example, if I have 12 DLC songs, on the track list the 3rd DLC listed here will always cause the issue, but if I put more DLC songs (e.g. 14) the 3rd DLC which would previously trigger the issue will now work fine and the 7th DLC listed on the track list which previously worked (when I had 12 DLCs) will trigger the issue now. I don't know if there's a pattern between the number of the DLC songs vs the DLC which will trigger the issue, at least I couldn't find. Depending of the number of DLCs, more than one song will trigger the issue too.</p></li>
<li><p>On the NAND, all .app files for those games are U8 packed files (except for one I'll talk below) and are stored on a different folder on the NAND (e.g. normal Wii save files generally goes to User\Wii\title\00010000<game ID in hex>, the DLCs from those games goes to User\Wii\title\00010005<game ID in hex starting with 7>)</p></li>
<li><p>If there's no ticket corresponding the ID the games use for DLC (73443245 for Just Dance 2, 734a4445 for Just Dance 3 and 734a5845 for Just Dance 4, for example) inside User\Wii\ticket\00010005, the games won't "see" any DLC song, even if they're on the correct folder.</p></li>
<li><p>You can swap DLCs by putting/removing .app files from the previously mentioned NAND folder directly. I'll detail this below. </p></li>
<li><p>Every song correspond to an specific .app file (you can move these in and out freely and the game will reflect that only showing the songs from the files which are there), but you'll also have other two smaller .app files which doesn't map to any song. </p></li>
<li><p>The first .app file which doesn't map to any song is a very small .app file (around 20 to 30 kb). It's the only .app file which is not an U8 packed file, from a quick look through a hex editor it seems to store some kind of "metadata" for the DLC songs (you can read strings with the song names and some kind of timestamp, like "sD2E_v7_26dlcs.1103301553"). I didn't notice any difference in the game after I moved this file in or out of the NAND, all DLCs still played normally as long as you didn't have more than 11 on the NAND at the same time. </p></li>
<li><p>The second small .app file (of around 2 to 3 MB) is an U8 packed file just like the others and seems to be some sort of "catalog" of all available DLCs, as I found small preview tracks for all the DLC songs when I unpacked it, even of DLCs I don't have. Also, the game complains that the DLCs are corrupted and you need to go to the Wii Shop to redownload them if you move this file out of the NAND and boot any of the three games.</p></li>
<li><p>With that findings, it's possible to create "DLC packs" and it's what I did as workaround. Basically, I created multiple "content" folders inside User\Wii\title\00010005<game ID in hex> (e.g. content_a, content_b, etc). On each content folder you must have a copy of title.tmd, the "catalog" .app file and up to 11 of the bigger .app files (each one corresponds to a song, remember?). Having the smaller .app file which seems to store metadata seems irrelevant, I didn't notice anything different by having it there or not. Even without it, you're still limited to only 11 DLCs, if you put more you trigger this issue. To switch the "packs", just rename the one you want to play to "content" and boot the game.</p></li>
<li><p>Probably not relevant, but if you play a DLC song then swap to another pack without it then switch back to the previous pack which had it, your high scores will still be there.</p></li>
<li><p>Deleting/Moving the song to the SD Card from the "Archives" menu in-game does nothing. It'll claim the song was deleted/moved successfully but it'll still be there as if nothing happened.</p></li>
<li><p>This one applies only to Just Dance 2014 and onwards (they switched to a new engine AFAIK) but might be relevant: JD2014 and 2015 doesn't suffer from this issue and you can have more than 11 DLC songs without any kind of issue -- for record I have 18 DLC songs on JD2014 and 15 on JD2015 -- but I noticed both JD2014 and 2015 lists all DLCs, even the ones I don't have on their "Archives" menu, but they don't appear on the track selection (probably a different issue). Also, on the NAND there's no "catalog" file anymore (the small .app file with preview music for the DLCs the previous Just Dance games had and complained if it wasn't there), that info seems to be stored directly on the big .app file of the actual song now (and every song has a copy of the info of all other DLC songs too -- IDK why). The smaller .app which apparently stores metadata is still there, though, and just like before, deleting it makes no visible difference in the game. Moving files in and out of the NAND doesn't affect anything, all songs (even the ones I don't have) will still appear in the "Archives" in-game menu, but not in the song selection menu. JD2016 and 2017 uses the same engine and probably have this same behavior but we'll never know as they don't have a DLC store following the Nintendo WFC shutdown...</p></li>
</ul>
Emulator - Emulator Issues #10127 (Won't fix): [Feature Request] Global switch for "Speed Up Disc...https://bugs.dolphin-emu.org/issues/101272017-02-28T02:03:37Zmbc07jhonn.copperfield@gmail.com
<p>While it's nice Dolphin now has accurate disc transfer timings (as of 5.0-2431), I noticed the loading times of many games are way faster with speed up disc transfer option in the game properties (that's what the option does after all). It would be nice having a way of enabling it for all games instead of manually enabling the option in every game. Either a new checkbox in the GUI or a new INI key if exposing this in the GUI isn't desired would cut it, I think...</p>