MKDD Tint Issue RPI5

[TPR]

@gvx64 said in MKDD Tint Issue RPI5:

@TPR OK, so if you were able to successfully generate the dolphin-emu-qt2 binary following the steps that I outlined in the previous post. You should now be able to add it to your emulationstation gamecube launch screen by doing the following.

First input the following command in your terminal:

sudo cp /home/pi/dolphin-rpi2/dolphin-rpi/Build/Binaries/dolphin-emu-qt2 /opt/retropie/emulators/dolphin-rpi/bin/

This will put dolphin-emu-qt2 in the same file location as your other dolphin 5.0 emulators. After doing this, you can delete the /home/pi/dolphin-rpi2 folder if you would like free up ~300MB of disc space.

Next, add the following line to your /opt/retropie/configs/gc/emulators.cfg file:

dolphin-rpi-configure-hotkeys = "XINIT-WM:/opt/retropie/emulators/dolphin-rpi/bin/dolphin-emu-qt2 -u /home/pi/DolphinConfig5.0/

You should now be able to configure your hotkeys using this new emulator option. When you launch dolphin-rpi-configure-hotkeys within emulationstation you may get a warning message asking you to switch to the WX build. Just ignore the warning and proceed with the qt version. Then just follow the steps I laid out in post 84 to setup your hotkey combos. After that is done, exit the emulator and that should be it.

As a final check, you can take a look at the time stamp on /home/pi/DolphinConfig5.0/Config/Hotkeys.ini to see if the file has been created/updated by using the following command:

ls -al /home/pi/DolphinConfig5.0/Config/

Finally, just remember that after configuring, in order for your hotkeys to work you will need to launch your games using the emulator named dolphin-rpi-gui (do not use dolphin-rpi).

Can you please let me know if all of this works for you?

Ok so I've managed to get to this point:

But here's the problem I'm having. When I run your build, I get no mouse pointer on the screen. So I can't select anything. When I run the normal version of dolphin, the mouse pointer works just fine. So any idea how I can fix that?

[TPR]

@gvx64 Ok so I've managed to work blindly without a mouse pointer and get into the hotkeys and I set my "exit" hotkey on the controller to the SELECT button which does seem to work in game. But now I'm getting this on my screen:

And the only way to get rid of that seems to have a keyboard connected, which I do not have connected all the time.

So the game works without the blue tint.... I can now exit out of the game with the SELECT button... but now I get an error on the screen that requires a keyboard. Any way to fix that last issue?

[TPR]

@gvx64 Ok I created my own work around!

I created a 1 pixel by 1 pixel image and called it dolphin_logo@2x.png and put it in the folder:
/usr/local/share/dolphin-emu/sys/Resources

Then I got an error saying it was looking for dolphin_logo.png
and then it was looking for: Dolphin.png

So now I have three files in the folder:
/usr/local/share/dolphin-emu/sys/Resources

And now the game loads without any errors!

I realize this is a hack, but it works!

[TPR]

@TPR said in MKDD Tint Issue RPI5:

But here's the problem I'm having. When I run your build, I get no mouse pointer on the screen. So I can't select anything. When I run the normal version of dolphin, the mouse pointer works just fine. So any idea how I can fix that?

Any idea on how to fix this? Having to go in blind without a mouse pointer really makes it very difficult to do anything.

[TPR]

Here's another interesting issue...

When I put in my roms folder under settings:
/home/pi/RetroPie/roms/gc

These are the only two games that show up?

Even though my roms folder is fully populated.

EDIT: I see... those are the only two .ciso files I have where everything else is an .rvz file. How can I make the rest of the show up like they do in my other Dolphin emulator?

[TPR]

Trying to load Resident Evil 4 I get this error:

And then this one:

And then it just loads to a black screen.

[TPR]

Crap, now I just loaded up Mario Kart and I'm also getting this same error:

And the game is running slow as shit.

So I'm afraid I might have accidentally checked or unchecked a box somewhere flying blind without a mouse pointer on screen. Any ideas? At this point I might have to start all over again...

[TPR]

Ok I have tried every possible option here:

And I'm still getting the unrecognizable cpu_core:1 error.

I think I'm at the point of giving up. I've been at this a few hours now and not being able to see where my mouse is pointing to is very frustrating and I think that is what is causing most of my problems.

I'm not sure I want to start over from square one again.

[TPR]

@gvx64 OKAY.... I went back to square one and here's what I've figured out and what works for me....

1. I installed everything based on your instructions above and that all worked great! Thank you!

2. In order to get rid of the "Failure to load image..." error I made the three 1 pixel images and put them in the folder: /usr/local/share/dolphin-emu/sys/Resources as I stated above.

3. My error I ran into with the unrecognizable cpu_core and the slowdown is that it seemed that I accidentally checked one of the CPU Emulations Engines under "Advanced Settings" when I was flying blind with the mouse. Leaving all three of those options unchecked seemed to work just fine:
   

4. Upon loading Resident Evil 4 I ran across another error:
   

5. I was able to fix this by going back into the configuration screen and unchecking the "Use Panic Handlers" box:
   

6. I can now confirm that Mario Kart, Resident Evil 4, and Mario Golf all load up just fine without any tint issues or errors that pop up on screen when they load. I also was able to configure SELECt as the exit hotkey on my controller:
   
   
   

Three questions:

1. Where is the config file for this version of dolphin kept?
2. Is it possible to change the renderer to opengl? I would just like to compare how these games run in gl versus Vulkan.
3. Can anything be done about the mouse pointer?

Thank you for putting all this together!

[gvx64]

@TPR I am glad that you were able to get things working OK.

I am not sure why your mouse cursor is not showing up for you in the qt gui. On my build, I have to wiggle the mouse around a bit in order for it to show up but it usually appears after a couple of seconds of movement (no clicking, just back and forth movement). Have you tried moving your mouse around for a bit after it first loads?

Also, I only intended for you to use the dolphin-rpi-configure-hotkeys build to configure your hotkeys. For other configuration settings you can add the following new line to your /opt/retropie/configs/gc/emulators.cfg file:

dolphin-rpi-configure-main = "XINIT-WM:/opt/retropie/emulators/dolphin-rpi/bin/dolphin-emu -u /home/pi/DolphinConfig5.0/

Please use this for any configurations you are making that are not hotkey-related. Hopefully, the mouse will work better in this gui screen for you, as well.

Note that you should be able to open .rvz files from emulationstation using your dolphin-rpi emulator core or opening them manually inside dolphin-rpi-configure-main. I didn't add any rvz support to the qt interface mainly because I only intended for it to be used to configure hotkeys.

I agree with your approach to disable panic handlers when using the gui version of dolphin. That missing .png image error and the font loading error are nuisance errors and they disappear when you disable panic handlers. That core error could be problematic and you should have "Jit Recomplier" set in the advanced settings but if it is not giving you a problem now maybe it is best to just leave it alone. If you need to make anymore changes to these types of settings please use the dolphin-rpi-configure-main core for this (not the hotkey one).

Just to answer your last two questions:

1. /home/pi/DolphinConfig5.0/Config/Dolphin.ini is your main configuration file. There is a file in there called GFX.ini that has additional graphics settings and there is GCPadNew.ini for your gamepad settings.
2. You can try OpenGL (GLES 3.1) but I am pretty sure that it will run very slowly (let me know if that is not the case). My experience is that it is best to stick with Vulkan on this particular build if you are using a Pi5.

Can you please let me know if you are able to see your mouse in the qt interface screen after moving it around?

[TPR]

@gvx64 said in MKDD Tint Issue RPI5:

@TPR I am glad that you were able to get things working OK.

I am not sure why your mouse cursor is not showing up for you in the qt gui. On my build, I have to wiggle the mouse around a bit in order for it to show up but it usually appears after a couple of seconds of movement (no clicking, just back and forth movement). Have you tried moving your mouse around for a bit after it first loads?

Yes and I can see the pointer pop up for a fraction of a second sometimes but then goes away again.

Also, I only intended for you to use the dolphin-rpi-configure-hotkeys build to configure your hotkeys. For other configuration settings you can add the following new line to your /opt/retropie/configs/gc/emulators.cfg file:

dolphin-rpi-configure-main = "XINIT-WM:/opt/retropie/emulators/dolphin-rpi/bin/dolphin-emu -u /home/pi/DolphinConfig5.0/

Same issue with the mouse pointer here

Just to answer your last two questions:

1. /home/pi/DolphinConfig5.0/Config/Dolphin.ini is your main configuration file. There is a file in there called GFX.ini that has additional graphics settings and there is GCPadNew.ini for your gamepad settings.

Thank you. This is useful.

2. You can try OpenGL (GLES 3.1) but I am pretty sure that it will run very slowly (let me know if that is not the case). My experience is that it is best to stick with Vulkan on this particular build if you are using a Pi5.

You are correct. OpenGL caused lots of issues.

[gvx64]

@TPR said in MKDD Tint Issue RPI5:

Yes and I can see the pointer pop up for a fraction of a second sometimes but then goes away again.

OK, can you please try launching your configure hotkeys interface using the following command from the bash terminal instead:

sudo xinit /opt/retropie/emulators/dolphin-rpi/bin/dolphin-emu-qt2 -u /home/pi/DolphinConfig5.0/

All I am trying to do is to get you access to this interface so you can setup your hotkeys and then exit. Again, please try moving your mouse around when it first loads. You don't need to be able to launch games or do anything else from inside this interface.

Please let me know if this works better.

[sugarfree]

I haven't found time to test the latest version, so I would like to ask if it supports .m3u files and auto swapping of the disks?

[gvx64]

@sugarfree m3u (multi-disc) support was added to dolphin in 5.0-9343 (https://dolphin-emu.org/download/dev/1d3e3de44b177eb7bdd07a02afefb83ac9ba5812/ - committed on January 15, 2019). That was about 1.5 years after the commit date for 5.0-4544. So no, dolphin-rpi does not support m3u files at this time.

I might be able to roll the code forward to implement m3u support. Personally, I always found it pretty easy just to swap ISO's the old-fashioned way. That said, if you would like to have .m3u functionality, I will try to add it. Multi-disc support is potentially relevant for RE4 which is one of the games that currently requires this fork of 5.0-4544 on the Pi.

Note that I am currently working on improving RVZ support that I previously introduced. I have discovered that certain Wii RVZ files like The Last Story will not open with the current level of rvz support that I have added to this fork. I need to roll the code ahead further. I would like to fix this issue because I would like to implement the following patch for The Last Story in dolphin-rpi:

https://github.com/mimimi085181/dolphin/commit/4798448cbf6b1c6dab4c82133bcae447b640b0f5#diff-47b51c8ee279a2240221fc346fbd6321c8ac041fd729583f315c0c1bd85096d7R1162

This patch effectively doubles the performance of The Last Story and I can confirm that it brings this game to the cusp of playability even on an aggressively overclocked Pi4. I believe that this patch will do wonders on a Pi5. I can't get this patch to work properly on current builds of dolphin as the code has changed too much but 5.0-4544 just so happens to be from the same vintage as the commit that this patch was originally forked from.

The only problem is that I need to figure out why The Last Story RVZ file will not open. The ISO is 8.5GB and so I know that people will definitely want to be able to play this game in RVZ format. I am hoping that I can find a solution to this problem.

[DTEAM]

@gvx64

In the updated @sugarfree
post, this line is missing:

mv dolphin-emu-qt2 /opt/retropie/emulators/dolphin-rpi/bin/

I also added (optionnal) :

addSystem "wiiware"

[TPR]

@gvx64 said in MKDD Tint Issue RPI5:

@TPR said in MKDD Tint Issue RPI5:

Yes and I can see the pointer pop up for a fraction of a second sometimes but then goes away again.

OK, can you please try launching your configure hotkeys interface using the following command from the bash terminal instead:

sudo xinit /opt/retropie/emulators/dolphin-rpi/bin/dolphin-emu-qt2 -u /home/pi/DolphinConfig5.0/

All I am trying to do is to get you access to this interface so you can setup your hotkeys and then exit. Again, please try moving your mouse around when it first loads. You don't need to be able to launch games or do anything else from inside this interface.

Please let me know if this works better.

That worked! Thank you!

[TPR]

Question for all of you who know this stuff better than I do....

Do we ever think that Dolphin will have the ability to auto-detect a controller like Aethersx2 or retroarch does?

I have an XBOX 360, PS2, and an 8Bitdo controller that I like to swap between depending on the game and every time I swap on Dolphin I have to go into the backend and re-configure or at least tell the emulator what controller I currently have plugged in.

It just gets annoying to have to load up the backend every time I want to load a game. (I load games from ES, not from Dolphin. It's just a personal preference.)

Is there any way to have Dolphin auto-detect a controller or is it just not a feature of that core?

[gvx64]

@TPR I am really glad that it worked. Let me know if you need any other assistance for getting your hotkeys configured properly.

I don't know how to make dolphin auto-detect gamepads but I think that it would be very doable for you to setup multiple emulator cores in ES that each point to different configuration directories where each config directory contains a config file that defaults to a different gamepad (e.g. dolphin-rpi-XBOX, dolphin-rpi-PS2 and dolphin-rpi-8Bitdo cores). You then wouldn't have to manually change anything, just select the core that you want to use depending on the gamepad that you are using.

The one challenge with this method is that you would have different save files for each core but if you are willing to try creating symbolic links I think that it might work where you would be able to share save files between the three emulator cores.

It's going to involve some Linux shell commands, but if you are interested in giving it a try I can post some instructions on how to do this over the next couple of days when I have time.

[retropieuser555]

@TPR regarding automapping you can attempt my script but I can't test it with many controllers as I only own 8bitdo ones so YMMV

https://github.com/RetroPie/RetroPie-Setup/pull/3969

Although if you make a profile for your controller how you like it, the script will realise it exists and just use that one, rather than overwriting it, so you could set all your controllers up as profiles then whichever you have connected would be used for that session, similar to mupen64plus

[DTEAM]

@TPR

Hi @TPR , are you able to save?