Riivolution builds, but does not work on Console.

[IonicPixels]

After the updates made, Riivolution builds just fine. I moved the boot.elf from the build and put it on my Wii SD Card. I tested on both the OG Wii and Wii U and neither booted Riivolution. What could I have done wrong in the build?

[IonicPixels]

here is an image of the error:

[AerialX]

Heh, just because it compiles doesn't mean it will work! Comparing with the latest official release, does it behave the same or is this message unique to your built version? You might need to set up more logging...

[IonicPixels]

this message is unique to the built version. I can give more details through Discord if you would like. If you do, message me at IonicPixels#3139

[AerialX]

comment out the define on this line to get more logging out of it. You're mostly on your own though, as I don't actually have a setup for testing anything now. I might suggest starting by tackling the relevant gcc warnings.

I wonder if it would be possible to set up more automated testing via dolphin or something... does it even include an ARM emulator for IOS or does it just simulate it with a HAL?

[IonicPixels]

I will try that. I'll let you know if that works. I have been testing on console this entire time btw, making sure that the error is not Dolphin only

[IonicPixels]

alright I got this:

[galaxymaster2007]

I can confirm this issue exists.

I wonder if it would be possible to set up more automated testing via dolphin or something... does it even include an ARM emulator for IOS or does it just simulate it with a HAL?

Dolphin only simulates IOS.

[IonicPixels]

hey @AerialX do you think it would be possible for me to screenshare to you how I am even building Riivolution? I ask so you can tell me what exactly I am doing wrong and if there is anything code-wise that needs to be fixed. If you are open to a screenshare DM me please. (IonicPixels#3139 on Discord)

[AerialX]

It doesn't seem like you're doing anything wrong, it's clearly running! If you're really concerned about that you could just download the elf from github instead.

if there is anything code-wise that needs to be fixed

I mentioned fixing warnings earlier, which I've put together some changes for in extern-syms. I'm not sure what to blame though since my changes don't seem likely to help (and hopefully I didn't mess up the change and break it even more).
It's just old code that needs to be tested and debugged and I don't have the time or hardware to do that right now, sorry.

Dolphin only simulates IOS.

Yeah I figured, that's unfortunate.

[IonicPixels]

@AerialX do you happen to still have the source files for Riivolution v1.06? iirc it updated the DKP version which could be very helpful for trying to get Riivolution loading on Console

[IonicPixels]

I am building the Master branch by the way. I dont know if thats what I am supposed to do or not. I just built the program, I can only test on Dolphin at the moment (does not run Riivolution) and I got a black screen. I have no idea if that is a good thing or not. However I will ask someone to run the elf on a real Wii or Wii U.

[AerialX]

do you happen to still have the source files for Riivolution v1.06

AFAIK 1.06 was only a build with an updated libogc dependency to fix a wiimote crash bug, and did not involve any additional source code changes.

I am building the Master branch by the way. I dont know if thats what I am supposed to do or not.

That's normally fine, except for the part where I suggested trying a new branch above.

I just built the program, I can only test on Dolphin at the moment (does not run Riivolution) and I got a black screen.

Yeah there's no point in trying Dolphin really, unless the previous or released elf gets farther which could indicate a difference or problem - but it won't get nearly as far as it did in your above screenshot regardless.

What even is your goal and why are you trying to build it? Despite the recent updates this is all still just a messy old codebase I wrote in high school, it won't be easy to work with if you aren't familiar with C or basic troubleshooting... You might want to start by looking at the Wiibrew debugging page; though it's hacky I've used the wifi debugger stub in the past (but it's usually a pain to get working)...

[IonicPixels]

@AerialX I am trying to edit Riivolution. It can be pretty buggy so it would be nice to patch out those bugs. It only makes it a little harder to do that if Riivolution wont boot lol. Could you maybe try building this source like you were building an official release and send it? Idk if GitHub allows .elf files to be sent though. If it does I can try running a build of Riivolution that you build yourself

[IonicPixels]

I will say that Galaxy Master commented out most of haxx.cpp and Riivo actually did load, but as soon as the console was supposed to look for a disc it cut to a black screen, and on Wii U it turns off the console

[AerialX]

I am trying to edit Riivolution. It can be pretty buggy so it would be nice to patch out those bugs

This is also a bug and you seem to be completely out of your element. To patch bugs you kind of have to apply critical thinking methods to the problem to know how to approach it and what to do next - and thus far you only seem to be asking others to do things for you? Fixing a bug involves understanding what differs between what the code is attempting to do vs what it's actually doing - which also requires understanding what it's trying to do.
This problem should certainly be fixed, but your behaviour is just confusing as it doesn't match up with what I'd expect from someone who would actually want to work with the code.

That said, feel free to file issues on this repo for known bugs that you plan on fixing, it'd be nice to properly keep track of existing bugs and have others potentially weigh in on them!

Could you maybe try building this source like you were building an official release and send it?

The only way to make a build "like an official release" would be to go back in time and use an ancient version of devkitPro. I don't suggest doing this, and can't help you do so, but you can try it if your only goal is to get a working build going.

I already linked you to where you can download official builds from github, just click on the relevant commit. This seems unlikely to help though it's worth comparing your version against. I suggest trying out the extern-syms branch if you haven't had a chance to yet.