Emulator Issues #11494
closedMetroid Prime trilogy having graphic bugs, when opened due to the option "Immediately Present XFB" being disabled automatically on starting the game.
0%
Description
Game Name?
Metroid Prime Trilogy (Wii, Pal)
Game ID? (right click the game in the game list, properties, info tab)
R3MP01 (0001000052334d50)
MD5 Hash? (right click the game in the game list, properties, info tab, MD5 Hash: Compute)
98f53f0ee7568f33601043a8970b5bfc
What's the problem? Describe what went wrong.
BEFORE YOU READ WHAT I WROTE DOWN THERE: To sum it all up, it's an graphic issue, wich can be fixed, by simply having the option "Immediately Present XFB" still being checked, because it unchecks itself, when the game starts, because the font of that option changes to a fat font.
Metroid Prime 1 and 2 have graphic bugs, when being directly started from dolphin and not the Wii menu. The loading screen will be missing for all 3 games (instead of that there will be a pink screen) and when you are in gameplay the loading screen is going to flicker in and out of sight (it's looking like it's alternating every 2 frames between gameplay and the loading screen. I think that this is a known issue wich is resolved by activating the option "Immediately Present XFB". But my problem is, that when I activate it, it isn't saved for the next start up of the trilogy in dolphin. When I activate it, when the game is already launched, wich is the only way of activating it on that game, then the whole screen will be a little bit shrinked, because of a not very big black bar on the bottom of the window and everytime you go in one of the two pause menus in both games there will be (depending on the backend: on some it randomly alternates between two graphic bugs and on some it alternates with 2 graphic bugs and how it's supposed to look, but in both the graphic bugs change color, when the camera is not in Samus' helmet to blue for example when you activate the morphball) a strange graphic in the background. When I noticed that during gameplay I started testing all the different backends on all games to see on wich it happens and on wich it doesn't and when I tested I accidentally hit the button on the home menue to go to the wii menu, where I noticed, that when I started the trilogy from there with the option "Immediately Present XFB" enabled, it didn't have any graphic bugs at all: there was no black box, the loading screens were there and when hitting pause it didn't have any graphic bugs.
By the way from that point on, when I discovered what was causing the problems I stopped documenting the graphic issues, because it wouldn't be very accurate and it doesn't happen everytime.
What steps will reproduce the problem?
starting the game with "Immediately Present XFB" either enabled or disabled, because it disables it by default, because the font changes to a fat font. And of course enabling it again ingame.
Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.
Yes, Dolphin 5.0-9213
Is the issue present in the latest stable version?
For some strange reason, Dolphin 5.0 gives me a warning about something when I start it, where I can click infinetly on OK, but I don't think, that I need to test this dolphin version, because I described what the cause of this issue is.
If the issue isn't present in the latest stable version, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)
I don't know and if you want me to, then I will try to test the versions.
If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible. Screenshots showing what it is supposed to look like from either console or older builds of Dolphin will help too. For more information on how to use the fifoplayer, please check here: https://wiki.dolphin-emu.org/index.php?title=FifoPlayer
Look at the attached pictures. I don't know how to create a fifolog, so if I make a video, I would upload it to YouTube.
What are your PC specifications? (CPU, GPU, Operating System, more)
Intel I5 6600k, AMD Radeon R9 285 (2gb vram), Windows 7 Ultimate 64 Bit, 16 GB DDR4 RAM, AMD Radeon Adrenalin 2019 version 18.12.3
Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)
If you want me to make a video for whatever reason, I can make one. If you need me to test anything else too, than ask me please, because I don't have anything better to do with my free time.
Files
Updated by JosJuice almost 6 years ago
- Status changed from New to Questionable
Enabling Immediately Present XFB makes the emulation less accurate, so I don't think it is a proper solution for your problems.
When it comes to the loading screens... Most likely, having it enabled makes the animated loading indicator go away, while having it disabled makes everything on the loading screen other than the animated loading indicator go away. Please try disabling Store XFB Copies to RAM instead of enabling Immediately Present XFB.
I know less about the flickering, but please try disabling Store XFB Copies to RAM for that too.
Updated by Leonsa almost 6 years ago
JosJuice wrote:
Enabling Immediately Present XFB makes the emulation less accurate, so I don't think it is a proper solution for your problems.
When it comes to the loading screens... Most likely, having it enabled makes the animated loading indicator go away, while having it disabled makes everything on the loading screen other than the animated loading indicator go away. Please try disabling Store XFB Copies to RAM instead of enabling Immediately Present XFB.
I know less about the flickering, but please try disabling Store XFB Copies to RAM for that too.
I tried that and found out that it could have something to do with the audo emulation engine, because I only get it on the DSP LLE Recompiler (I didn't try the slow one). Here's a video of it: https://www.youtube.com/watch?v=OYy01luEuew&feature=youtu.be . If you want a fifolog from me than I will look into it.
Updated by JosJuice almost 6 years ago
The DSP emulation engine shouldn't affect the graphics other than through its impact on performance, which in combination with dual core is known to cause issues like the black bar issue. Turning off dual core will likely help. If turning off dual core makes DSP HLE act the same as DSP LLE, the DSP emulation engine is just a red herring.
Updated by Leonsa almost 6 years ago
Leonsa wrote:
JosJuice wrote:
Enabling Immediately Present XFB makes the emulation less accurate, so I don't think it is a proper solution for your problems.
When it comes to the loading screens... Most likely, having it enabled makes the animated loading indicator go away, while having it disabled makes everything on the loading screen other than the animated loading indicator go away. Please try disabling Store XFB Copies to RAM instead of enabling Immediately Present XFB.
I know less about the flickering, but please try disabling Store XFB Copies to RAM for that too.
I tried that and found out that it could have something to do with the audo emulation engine, because I only get it on the DSP LLE Recompiler (I didn't try the slow one). Here's a video of it: https://www.youtube.com/watch?v=OYy01luEuew&feature=youtu.be . If you want a fifolog from me than I will look into it.
Ok, I'm completely wrong, it also happens on the fast one.
Updated by Leonsa almost 6 years ago
JosJuice wrote:
The DSP emulation engine shouldn't affect the graphics other than through its impact on performance, which in combination with dual core is known to cause issues like the black bar issue. Turning off dual core will likely help. If turning off dual core makes DSP HLE act the same as DSP LLE, the DSP emulation engine is just a red herring.
I created a few fifo logs now, but when I play them back there isn't any flickering in there. I have dual core enabled and the DSP HLE Emulation enabled. If you can use the fifologs, I will send them to you, because they are bigger than 5 MB. I uploaded another video showing what happened after I changed some video settings. https://www.youtube.com/watch?v=85oyMpyxD1o&feature=youtu.be
Updated by Leonsa almost 6 years ago
- File Metroid prime trilogy glitch.7z.005 Metroid prime trilogy glitch.7z.005 added
- File Metroid prime trilogy glitch.7z.004 Metroid prime trilogy glitch.7z.004 added
- File Metroid prime trilogy glitch.7z.003 Metroid prime trilogy glitch.7z.003 added
- File Metroid prime trilogy glitch.7z.002 Metroid prime trilogy glitch.7z.002 added
- File Metroid prime trilogy glitch.7z.001 Metroid prime trilogy glitch.7z.001 added
- File GFX.ini GFX.ini added
- File Dolphin.ini Dolphin.ini added
- File Metroid prime trilogy log.7z Metroid prime trilogy log.7z added
Leonsa wrote:
JosJuice wrote:
The DSP emulation engine shouldn't affect the graphics other than through its impact on performance, which in combination with dual core is known to cause issues like the black bar issue. Turning off dual core will likely help. If turning off dual core makes DSP HLE act the same as DSP LLE, the DSP emulation engine is just a red herring.
I created a few fifo logs now, but when I play them back there isn't any flickering in there. I have dual core enabled and the DSP HLE Emulation enabled. If you can use the fifologs, I will send them to you, because they are bigger than 5 MB. I uploaded another video showing what happened after I changed some video settings. https://www.youtube.com/watch?v=85oyMpyxD1o&feature=youtu.be
I don't know if this can help, but I created a savestate of the glitch happening, but in dolphin 5.0-9215. I already saw graphic glitches on starting up the trilogy and this time with a small black bar flickering on top of the screen. I also created one new fifolog and uploaded my configuration files.
Updated by JMC4789 almost 6 years ago
You have dualcore on, right? Turn that off and the flickering won't happen. That's a dualcore desync issue in the Prime Trilogy engine.
Updated by Leonsa almost 6 years ago
JMC4789 wrote:
You have dualcore on, right? Turn that off and the flickering won't happen. That's a dualcore desync issue in the Prime Trilogy engine.
Ok, I will try turning that off now.
Updated by Leonsa almost 6 years ago
JMC4789 wrote:
You have dualcore on, right? Turn that off and the flickering won't happen. That's a dualcore desync issue in the Prime Trilogy engine.
As to be expected you was right about the dualcore as far as I tested it now. But I still found 2 graphic bugs that are relatively minor. 1. the loading screens for the games are purple and 2. on the game select for a character the difficulty isn't displayed, but it's replaced with two black squares.
Updated by JMC4789 almost 6 years ago
Turn on XFB2RAM to fix the purple loading screens.
Updated by Leonsa almost 6 years ago
JMC4789 wrote:
Turn on XFB2RAM to fix the purple loading screens.
Ok, that fixed the issue, but the black squares aren't gone. Sorry, they aren't being displayed instead of the difficulty, but instead of something else, I think. I don't have access to the Wii right now, so I can't confirm if that is something that is diplayed instead of something else. I hope I'm not annoying, but I want to make dolphin perfect and that includes the removal of these black squares.
Updated by JMC4789 almost 6 years ago
I don't know what they are either so I can't really assist with that. It's all good, every bug is worth reporting.
Updated by Leonsa almost 6 years ago
JMC4789 wrote:
I don't know what they are either so I can't really assist with that. It's all good, every bug is worth reporting.
Ok, I searched for some proof of these black squares being a graphic bug, but it looks like it's intended. But I still have one question, why do the dual cores desinc?
Updated by JosJuice almost 6 years ago
- Status changed from Questionable to Invalid
Updated by JMC4789 almost 6 years ago
Because Dualcore is a hack to make things go fast at the expense of accuracy. Some games need better accuracy.