Homebrew Official Retroarch WiiU (wip.)

  • Thread starter Thread starter aliaspider
  • Start date Start date
  • Views Views 2,687,507
  • Replies Replies 15,196
  • Likes Likes 93
Do you change the cores manually or with auto detecting via loading a ROM and picking the core to associate it with? I've swapped between Snes9x and Genesis Plus using the second method without issue, but I'm glad that a major Genesis Plus issue has been resolved. This app just keeps getting better and better :P

Edit; Oh right, yes, the RA channel itself seems to mitigate this issue.


Edit 2: Do we simply use the new core by itself or do we need to update all the RPX files?



Sega Saturn is so poorly documented and hard to emulate on PC, good luck seeing a port of it on other platforms XD
It happens with the auto core loading (tbh I don't manually switch cores so it may happen there too)

Players choice, I think You can just update the Gens Core but you may as well update to the newest build.
 
  • Like
Reactions: the_randomizer
It happens with the auto core loading (tbh I don't manually switch cores so it may happen there too)

Players choice, I think You can just update the Gens Core but you may as well update to the newest build.

Huh, odd indeed, I got the error when loading the app in the hombrew launcher, but not in the RetroArch launcher, using the auto core detect method. It only happened when I loaded the core manually (which isn't a necessary thing anymore). I'm not sure when I'll try the latest build, as the one I have right now is working surprisingly stably. I wonder though, how we can narrow down the last remaining DSI exception issue, or if loading the cores individually as apps will mitigate the issue.

Edit:

Manually changing cores (deprecated method), via RetroArch in HBL = crash
Changing cores using auto detect method in RetroArch Launcher = more stable
 
Last edited by the_randomizer,
Huh, odd indeed, I got the error when loading the app in the hombrew launcher, but not in the RetroArch launcher, using the auto core detect method. It only happened when I loaded the core manually (which isn't a necessary thing anymore). I'm not sure when I'll try the latest build, as the one I have right now is working surprisingly stably. I wonder though, how we can narrow down the last remaining DSI exception issue, or if loading the cores individually as apps will mitigate the issue.

Edit:

Manually changing cores (deprecated method), via RetroArch in HBL = crash
Changing cores using auto detect method in RetroArch Launcher = more stable
Yeh, its definitely a strange one. It will do it through the auto core load too, if you load enough cores in a single session.
 
Yeh, its definitely a strange one. It will do it through the auto core load too, if you load enough cores in a single session.

Cripes. Good point, but where should we begin to isolate it? It's definitely something reproducible, which is good. Does it occur when each core is loaded as its own app, instead of through the main RA app? Or renaming one of the cores to the RetroArch core and then testing it that way? I am curious to see it the rename method bypasses it.
 
Cripes. Good point, but where should we begin to isolate it? It's definitely something reproducible, which is good. Does it occur when each core is loaded as its own app, instead of through the main RA app? Or renaming one of the cores to the RetroArch core and then testing it that way? I am curious to see it the rename method bypasses it.
It's isolated to the switching of cores (loading of RPX files) so it seems to me its related to the loader code, ekeeke said something about "embedded elf/rpx loader does not clear BSS segment before launching the core executable" he said it wasn't the cause of his Vorbis error but mentioned it SHOULD be done anyway just in case?

What he said exactly...

Well, I got this wrong, WiiU build of Genesis Plus GX indeed uses dynamic allocation for the large memory area that holds ROM buffer, cartridge & Mega CD hardware structures. so this is not part of BSS segment as I said early and clearing BSS would probably not fix this issue (it's still recommended to do it though).
 
It's isolated to the switching of cores (loading of RPX files) so it seems to me its related to the loader code, ekeeke said something about "embedded elf/rpx loader does not clear BSS segment before launching the core executable" he said it wasn't the cause of his Vorbis error but mentioned it SHOULD be done anyway just in case?

What he said exactly...

Well the Vorbis issue has been resolved, so that's one less variable in the equation, but how does the second issue be addressed, who can look at it and make sure the BSS segment is cleared?
 
Quarktheawesome Radius4 or rioray? they are the only people who currently work on the WiiU port?

Not entirely sure, Twinaphex does work on it too, I believe. I want to help squash this bug in any way that I can, but maybe we can try the "rename one of the cores to call it retroarch.rpx" method?
 
Not entirely sure, Twinaphex does work on it too, I believe. I want to help squash this bug in any way that I can, but maybe we can try the "rename one of the cores to call it retroarch.rpx" method?
I dont think it works.. Didnt for me anyway, it was the reason i ended up installing the channel [emoji14]

Sent from my GT-I9505 using Tapatalk
 
We need someone who can look at the code and debug the issue, we cant do it. All we can do is bring it to the attention of the devs?

I did make a bug report (different from the Genesis Plus GX one, which has been resolved), but as of yet hasn't received a reply. All we can do is wait.


Edit: Hmm, never mind. I thought I did, but it was for another issue.


Edit 2: Dammit, I misread it XD


https://github.com/libretro/RetroArch/issues/5274

I did make this, but it's somewhat redundant; gonna need to redo the bug report since it won't let me rename.
 
Last edited by the_randomizer,
  • Like
Reactions: ploggy
IMG-20170815-WA0005.jpg

Why is my virtual keyboard all white?
 
For what it's worth, I used to have constant DSI errors and going from haxchi to cbhc, deleting my config and (coincidentally or not) switching from rgui to xmb has drastically reduced the errors to basically none.

Also, is there a Sega 32X core available for the wiiu? I tried searching but couldn't find anything due to "32X" being too short.
 
For what it's worth, I used to have constant DSI errors and going from haxchi to cbhc, deleting my config and (coincidentally or not) switching from rgui to xmb has drastically reduced the errors to basically none.

Also, is there a Sega 32X core available for the wiiu? I tried searching but couldn't find anything due to "32X" being too short.

32X is only available in a couple of emulators, Picodrive and Kega Fusion, as far as I know Picodrive would have to be ported to Wii U.
 
  • Like
Reactions: skeetskat
for what it's worth, I'm still getting the vorbis error on the latest nightly :V
Unless I'm not downloading the right one or something.

edit: https://buildbot.libretro.com/nightly/nintendo/wiiu/2017-08-16_RetroArch_rpx.7z this is the nightly I downloaded
Im using the same nightly and the genplus gx core is giving me an ISI error i dont know if its the same error your getting but its there. Also the atari800 core does not work for me it loads and plays the game but none of the buttons work does anyone know a fix?
 

Site & Scene News

Popular threads in this forum