[Wii] Metroid Prime 3: Corruption
|
02-16-2013, 06:02 AM
(This post was last modified: 02-16-2013, 06:24 AM by NaturalViolence.)
Well after reading this post (post #20 at the bottom of the page): http://forums.dolphin-emu.org/Thread-how...ays?page=2
I figured I would try out MP3 to confirm that the crashing is fixed. I haven't played the game in a very long time because of the crashing. In fact the last time that I played it was well before 3.0 was released (r72xx). I tried the latest revision 3.5-397 Unfortunately I didn't even make it in-game before discovering two new bugs. That weren't present in 3.0. 1. A constant beeping sound from my wiimote regardless of HLE/LLE, OpenAL/DSound/XAudio2, Audio framelimit on/off, and wiimote speaker volume set to 0 or not. The problem is not present in 3.5. I also tested some other games and it is not happening in them. 2. This: http://i.imgur.com/kxM1QRk.jpg Take a look at the middle of the image between the I and M. See that little black bar? It appears as soon as the wrist warning fades and never goes away even when in-game. It happens with all three video backends and every graphics settings. And trust me I have tried all of them. It is impossible to get rid of. The issue is present in 3.5 so it occurred somewhere between 3.0 and 3.5. I want to confirm that other users are having this issue. I'm not sure how an issue that has been around for over a year went unnoticed or unreported but it's not in the issue reports section of the googlecode page, the wiki, or the old gamethread. I won't put it in [img][/img] tags since it's too big. And I won't rescale it since it needs to be fullsize for you to easily see the issue. Also unrelated to dolphin but I noticed that my wifi becomes unresponsive when my wiimote is active. The BT radio waves must be interfering with it. Interesting because I don't recall having this problem before. It's going to take a really long time to bisect such an old issue and I really hope that I don't have to do it. Edit: Ok I'm doing the bisect now. It is present in 3.0-805 and 3.0-750. Edit 2: Ok I kept going back and the issue is still present so I went back and tried 3.0 to double check. And it's apparently in 3.0 as well. Which is odd because I don't remember it being there the last time I tried. Perhaps it's a problem with my drivers or win 8. I can't imagine an issue like this going unnoticed for 1.5-2 years. Also the wifi issue does not occur in 3.0. How weird is that?
"Normally if given a choice between doing something and nothing, I’d choose to do nothing. But I would do something if it helps someone else do nothing. I’d work all night if it meant nothing got done."
-Ron Swanson "I shall be a good politician, even if it kills me. Or if it kills anyone else for that matter. " -Mark Antony
That "dash" goes away for me. It turns into the "dot" that's on the wiki page. Oh, and for me that bar doesn't appear at 1x native even at the main menu, just like the dot. I saw a pic from DefenderX playing this game a few months ago, and it had a dot instead of a dash as well... *shrug*
I've been trying to play through the game, now that the micro-stuttering and crashing is a little better since 3.5-380. It's uh.... it's rough. I'm considering it more an experiment than enjoyable play at this point. I have to use OpenGL to help with the microstuttering, and it has all kinds of weird slowdowns. Plus, crashes still happen, but it's not as bad as it used to be... Even MY COMPUTER, 3570K @ 4.7ghz, gets slowdowns in large areas with OpenGL. DX9 would have better performance, but D3D9 and D3D11 have much worse microstuttering, which kills any performance gains. Fifo error, just, ugh. I'm so crazy for playing through through. Just reached Elyssia. As for the wiimote thing, I don't have that in 3.5-394. I'll get latest and check shortly. I do have something else though: Random rumble. It's freakin bizzare. I'll pause it, put the wiimote on my desk aimed away from the screen, and it will just sit through wurring at me every few seconds. Even hitting the wii menu and it will just keep going. Only way to stop it is to kill the wiimote rumble in the wiimote properties. This only started after the removal of alt wiimote timings. I've been meaning to try to pin this and get this reproducible, but it's an elusive bugger. Have you experienced this? Oh, NV, I'm playing on NTSC. What are you playing on? I've heard PAL in 50hrz mode doesn't have all the Fifo errors, so worth pointing out. Intel Xeon w7-3465X OC | Asus Pro WS W790-E Sage SE | NVIDIA GeForce RTX 4090 FE | 8x16GiB G-Skill Zeta R5 DDR5-6000 | Windows 11 22H2 | (details)
MacBook Pro 14in | M1 Max (32 GPU Cores) | 64GB LPDDR5 6400 | macOS 13
02-16-2013, 06:34 AM
(This post was last modified: 02-16-2013, 06:37 AM by NaturalViolence.)
Issue occurs all the way back in 6505 as well. At this point I am positive that this issue is with my system somehow. I have never seen the black bar before and I know I have played this game on 6505 before. Since you're running win 7 I can rule out win 8 as the cause. We are both running nvidia cards but from different generations. Stranger still is my last card was a GTX 260 C216 from the same generation as your card and it didn't have this problem. Maybe it's just an issue with recent nvidia drivers? How the fuck.
Also the beeping issue is present on 3.0 and latest but not 3.5. The wifi issue does not occur with 3.0 but does occur with 3.5 and latest. Quote:That "dash" goes away for me. It turns into the "dot" that's on the wiki page. Oh, and for me that bar doesn't appear at 1x native even at the main menu, just like the dot. I saw a pic from DefenderX playing this game a few months ago, and it had a dot instead of a dash as well... *shrug* It appears at all IR for me and never changes. Quote:As for the wiimote thing, I don't have that in 3.5-394. I'll get latest and check shortly. I do have something else though: Random rumble. It's freakin bizzare. I'll pause it, put the wiimote on my desk aimed away from the screen, and it will just sit through wurring at me every few seconds. Even hitting the wii menu and it will just keep going. Only way to stop it is to kill the wiimote rumble in the wiimote properties. This only started after the removal of alt wiimote timings. I've been meaning to try to pin this and get this reproducible, but it's an elusive bugger. Have you experienced this? I don't use wiimote rumble and the game always crashes within 5 min anyways so I can't say that I have. I'm also running the NTSC version.
"Normally if given a choice between doing something and nothing, I’d choose to do nothing. But I would do something if it helps someone else do nothing. I’d work all night if it meant nothing got done."
-Ron Swanson "I shall be a good politician, even if it kills me. Or if it kills anyone else for that matter. " -Mark Antony 02-16-2013, 06:40 AM
Crashing is no where near that bad for me... I mean, it used to be back in late 3.0 era, but since 3.5-380 I can usually play for an hour or two without interruption. I have no idea what the difference is...
Intel Xeon w7-3465X OC | Asus Pro WS W790-E Sage SE | NVIDIA GeForce RTX 4090 FE | 8x16GiB G-Skill Zeta R5 DDR5-6000 | Windows 11 22H2 | (details)
MacBook Pro 14in | M1 Max (32 GPU Cores) | 64GB LPDDR5 6400 | macOS 13
02-16-2013, 06:43 AM
Well I haven't tried it since 3.5. Like I said above as soon as I saw the black bar I starting trying to fix it before going in-game.
"Normally if given a choice between doing something and nothing, I’d choose to do nothing. But I would do something if it helps someone else do nothing. I’d work all night if it meant nothing got done."
-Ron Swanson "I shall be a good politician, even if it kills me. Or if it kills anyone else for that matter. " -Mark Antony 02-16-2013, 06:54 AM
Oh I thought... gah. I thought you said it was crashing after 5 minutes. My mistake. How's the crashing for you?
Intel Xeon w7-3465X OC | Asus Pro WS W790-E Sage SE | NVIDIA GeForce RTX 4090 FE | 8x16GiB G-Skill Zeta R5 DDR5-6000 | Windows 11 22H2 | (details)
MacBook Pro 14in | M1 Max (32 GPU Cores) | 64GB LPDDR5 6400 | macOS 13
02-16-2013, 07:38 AM
(This post was last modified: 02-16-2013, 07:48 AM by NaturalViolence.)
It was crashing after 5 minutes back when I played it (pre-3.0). I really don't feel like playing through it right now with these two issues to try and determine how long it takes to crash post 3.5-380.
Edit: After a quick test I can confirm that the rumble issue is present for me as well. I also updated my graphics drivers but to no avail.
"Normally if given a choice between doing something and nothing, I’d choose to do nothing. But I would do something if it helps someone else do nothing. I’d work all night if it meant nothing got done."
-Ron Swanson "I shall be a good politician, even if it kills me. Or if it kills anyone else for that matter. " -Mark Antony 02-17-2013, 10:08 AM
More testing reveals that the only way to fix it is to use openGL or d3d11, turn off MSAA, and set IR to 1x.
If IR is set to anything but 1x it appears. If MSAA is enabled it appears (even at 1x). If d3d9 is used it appears (even with 1x IR and no AA).
"Normally if given a choice between doing something and nothing, I’d choose to do nothing. But I would do something if it helps someone else do nothing. I’d work all night if it meant nothing got done."
-Ron Swanson "I shall be a good politician, even if it kills me. Or if it kills anyone else for that matter. " -Mark Antony 02-17-2013, 12:19 PM
(02-17-2013, 10:08 AM)NaturalViolence Wrote: More testing reveals that the only way to fix it is to use openGL or d3d11, turn off MSAA, and set IR to 1x.Try enable Accurate Vbeam emulation, it works very well here, it will prevent those damn black bars, but if you didn't has all shadercache until the end of the game (I mean you need play it from the "new game" until the "ending" to get the MAX shadercache possible), there is a high chance for the black bar appear if you didn't has any shadercache.
CPU: Intel Core i7 3770 3.4 GHz (3.9 GHz with turbo boost) 4.23GHz with OC
RAM 16GB DDR3 [color=#009900]NVIDIA[/color] GTX 1070 [color=#000099]Asus[/color] Windows [color=#3333ff]10[/color] Pro 64bit Currently using Driver [color=#00ff00]WHQL[/color] |
« Next Oldest | Next Newest »
|
Users browsing this thread: 1 Guest(s)