-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WiiU] WHDLoad support (and other stuff) broken on Wii U? #427
Comments
I made the logging a bit clearer now, but indeed it appears that the Kickstart copying fails because the destination directory is not where it should be after the image contents are supposed to get unzipped. So the automatically created HDF mode is worth a try too, since the embedded data that will be uncompressed is gz, and the default Files-mode is zip (because gz is for single files, and zip is for multiple). Same manual copy manoeuvre applies if the extraction fails. And the rest of the randomness indeed hint that there are also some memory leaks that cause symptoms in seemingly innocent places. For example keyboard and RetroPad remap code is pretty much identical in VICE. But please do post logs of those CHD and BIN crashes separately. |
CHD crash: Towards the end of the log is a line saying Will continue testing the other things as suggested and edit with results. EDIT: I'm having a hard time pinning down the CD32 bin/cue issue. If I just start a game then immediately exit RetroArch without doing anything else, it doesn't hang. But if I mess around in the Options (changing system configurations, e.g. emulated model from Automatic to CD32 2MB+8MB and back to Automatic again), I can get it to hang pretty reliably with any number of menu selections: Restart (the content itself), Restart RetroArch and Exit RetroArch all trigger a freeze. Unfortunately, this particular issue just causes the console to lock up, so there's no stack dump and logs don't get flushed out, so there's nothing particularly useful to share diagnostically. I'm just a lay user, but it does "feel" kinda memory-leak-y. EDIT 2: Attempting to use a WHDLoad game on the latest build with clearer logging, I get the following: retroarch-puae-wiiu-whdload.log Which notably includes:
I can confirm that that directory does exist (and was empty, as you suggested), so something's clearly not going well. However, copying the files straight off the repo seems to have resolved this one entirely, I just launched my first WHDLoad game and it's running with no issues so far. |
Nice. It might be some endian shenanigans in the zlib then, because both CHD and ZIP features use it. |
Any difference now with the latest changes? |
Testing on 6df64de. Going down the list recording which issues have been resolved:
|
Something might have changed again, so please test at least the keymap stuff. The "key screen" in CD32 is the NVRAM manager, which is only accessible without the disc inserted. Log would be nice. Did you enable "Game Focus" for keyboard tests, since otherwise the frontend will block any presses that would be doing multiple things? |
User error is a strong possibility here as I'm not very familiar with the Amiga, however it's worth noting that this core is fairly ... unstable on Wii U as a whole, so I wouldn't be surprised if there were other issues.
When launching a WHDLoad game, I see behavior identical to #381. I simply get dropped onto the Kickstart screen (I assume--the gray AmigaDOS workbench screen). I don't have the BootHD option configured as was the issue there and I'm not forcing any specific hardware. Here is a log of me attempting to launch a game.
retroarch.log
The part that looks most suspect to me in the log is the following:
I have all of those files in my
retroarch/cores/system
directory, and they seem to be recognized without issue when running ADF format games.Besides this, there's a whole bevy of Wii U issues
The result of this is that the core is of fairly limited use on Wii U. Keyboard-heavy games are basically unusable without a physical keyboard (the virtual keyboard exists but is not a satisfying way to play anything), and WHDLoad and CD32 support may both be completely broken (latter needs more testing). Floppy disk format games which rely only on the joystick seem like the only truly playable content on this platform.
The text was updated successfully, but these errors were encountered: