[Wii] Metroid Prime 3: Corruption

[paraemuladores]

(01-17-2012, 01:02 AM)lord_al Wrote: For me the game crashes unless Enable dual core is unchecked. When I finally do manage to get it to play it runs at what seems to be half speed. Seems really buggy.

Running it on 3.0-371
I5-2500k @ 4.5ghz
4GB RAM
560TI @ 1000mhz clocks OC

What settings should I try? Should I try a different version?

Apologies if this has been asked I have read some of the thread but not all.

Try this:

EDIT: in fileserve now

File name: Dolphin ZEROx.zip File size: 11.69 MB

It's the version 3.0-216 with the exe of ZEROx and the configuration of hyperspeed (without the Xbox360 configuration), you can start reading about them here if you need any more information:

http://forums.dolphin-emu.org/showthread.php?tid=3583&page=20

From there, you should have plenty of information on how to configure the emulator, if this version does not work.

[Arcadia288]

I'm having severe problems with Metroid Prime 3. I have searched almost the entire forums and come across many helpful comments, but NONE of them are working for me.

The problem is that the game will only run at 27-49FPS, regardless of internal resolution. The build that I use seems to make no perceptible difference whatsoever, and the game crashes within a matter of minutes after starting up. This catastrophic performance makes the game almost unplayable, bearing in mind that Super Smash Bros Brawl runs almost flawlessly at 54-60FPS UNDER THE EXACT SAME SETTINGS.

The control system does not allow any reliable use of the cursor on the main menu, as it renders the topmost option (Sensitivity) in the Controls tab inaccessible, as the cursor can't reach it. Tinkering with the settings for the emulated Wiimote makes no difference to this. This problem also carries over into the simple matter of controlling Samus, as the controls system won't allow normal turning, it only allows either turning at half the normal speed for about 1 second, or does nothing at all. Whether I'm using the keyboard or an XBox 360 controller, the problem does not change at all.

As far as I can tell, the emulator has no reason at all to be doing this to me.

Hardware specs:

CPU: Intel Core i5 2.80GHz Quad-Core, not overclocked
Video Card: NVidia GeForce GTS450, 1024MB
RAM: 4GB.
OS: Windows 7 Home Edition 64-bit

Primary version of Dolphin: r7687M (runs all other titles flawlessly)
Dual Core on, Idle Skipping on, Framelimit 60FPS, JIT Recompiler selected, DSP HLE audio selected, DTK Music enabled, XAudio2 backend selected at 48KHz, emulator is using EuRGB60 mode for Wii titles. All other options are turned off.
Graphical backend is Direct3D11, which is rendering to main window at 3x native resolution. EFB copies has no slider on this version, only three tickboxes, Virtual and Ram are on. Ignore format changes, Disable XFB and Disable Per-Pixel Depth are turned on, all others are off. Nothing in Advanced window is turned on.
Control system in use: Emulated Wiimote.

The long and short of it is that the lag and the unresponsive IR section of the emulated Wiimote both make Metroid Prime 3 unplayable on my computer, and they both need to be fixed. Nothing I've tried has worked, and I've tried everything I could think of, and at least 6 different suggestions from the forums. Please respond ASAP.

[MegaJump]

(02-01-2012, 12:04 AM)Arcadia288 Wrote: I'm having severe problems with Metroid Prime 3. I have searched almost the entire forums and come across many helpful comments, but NONE of them are working for me.

The problem is that the game will only run at 27-49FPS, regardless of internal resolution. The build that I use seems to make no perceptible difference whatsoever, and the game crashes within a matter of minutes after starting up. This catastrophic performance makes the game almost unplayable, bearing in mind that Super Smash Bros Brawl runs almost flawlessly at 54-60FPS UNDER THE EXACT SAME SETTINGS.

The control system does not allow any reliable use of the cursor on the main menu, as it renders the topmost option (Sensitivity) in the Controls tab inaccessible, as the cursor can't reach it. Tinkering with the settings for the emulated Wiimote makes no difference to this. This problem also carries over into the simple matter of controlling Samus, as the controls system won't allow normal turning, it only allows either turning at half the normal speed for about 1 second, or does nothing at all. Whether I'm using the keyboard or an XBox 360 controller, the problem does not change at all.

As far as I can tell, the emulator has no reason at all to be doing this to me.

Hardware specs:

CPU: Intel Core i5 2.80GHz Quad-Core, not overclocked
Video Card: NVidia GeForce GTS450, 1024MB
RAM: 4GB.
OS: Windows 7 Home Edition 64-bit

Primary version of Dolphin: r7687M (runs all other titles flawlessly)
Dual Core on, Idle Skipping on, Framelimit 60FPS, JIT Recompiler selected, DSP HLE audio selected, DTK Music enabled, XAudio2 backend selected at 48KHz, emulator is using EuRGB60 mode for Wii titles. All other options are turned off.
Graphical backend is Direct3D11, which is rendering to main window at 3x native resolution. EFB copies has no slider on this version, only three tickboxes, Virtual and Ram are on. Ignore format changes, Disable XFB and Disable Per-Pixel Depth are turned on, all others are off. Nothing in Advanced window is turned on.
Control system in use: Emulated Wiimote.

The long and short of it is that the lag and the unresponsive IR section of the emulated Wiimote both make Metroid Prime 3 unplayable on my computer, and they both need to be fixed. Nothing I've tried has worked, and I've tried everything I could think of, and at least 6 different suggestions from the forums. Please respond ASAP.

Hey, trying using a newer build. Like 3.0 or newer. Game runs just fine using 3.0-363 for me.

[Arcadia288]

MegaJump, I tried using the newest build I could find (3.0-408), and it made no difference at all. The controller's unresponsiveness hasn't been fixed, since I still can't enter the security code in Samus's gunship at game start (the controller doesn't allow me to bring that part of the ship's console into range of the aiming cursor, don't know and don't care what's causing that problem), and it still won't do 54-60FPS in battle. I need a solution that fixes both of those problems, and the unfortunate thing is that using a newer build doesn't solve either problem.

[Luiz]

(02-03-2012, 09:51 PM)Arcadia288 Wrote: MegaJump, I tried using the newest build I could find (3.0-408), and it made no difference at all. The controller's unresponsiveness hasn't been fixed, since I still can't enter the security code in Samus's gunship at game start (the controller doesn't allow me to bring that part of the ship's console into range of the aiming cursor, don't know and don't care what's causing that problem), and it still won't do 54-60FPS in battle. I need a solution that fixes both of those problems, and the unfortunate thing is that using a newer build doesn't solve either problem.

I'm sorry to say this, but you need more power to run it well. You need at least 3.8 Ghz to run in a stable way and you need to use the latest builds. You'd better use a real wiimote, because there are some movements that are very hard to do with the 360 controller ( like grapple attack and the push and pull).
At least i was able to complete this game 100% using the 3.0-305 build without a single crash, but i was using an overclocked i7 at 4.1 Ghz and a real wiimote and nunchuk.
Good luck any how

[Neeshka]

Finally got the lasso to work, bind all the shake buttons (the main controller+nunchuck) to 1 button. Bind Tilt up/down to another button.
While keeping up/down held press the shake button. Works almost all the time.

[DefenderX]

Hey there, i have a little problem.



In the middle of the screen, there is a very small white dot. I've tried many settings, but the dot won't disappear.

btw: I use the normal graphic settings (Direct3D9) plus OpenMP Texture Decoder, Cache Display List, Disable EFB Access from CPU and EFB Copies to RAM with Cache. (needed for scanning the environment)

[Duke Nukem]

Uhh I don't know if it's the liquor that speaks now, but I can almost guarantee that the white dot belongs to the game even on the real console.
I have a strong memory that there is white dots on MP1 and MP2 too.

However if I'm wrong I would gladly be flamed!

[MegaJump]

No, the white dot is not normal and shouldn't be there. Disable OpenMP, and try using Auto(Window Size). Oh, you don't have to use EFB to RAM, Dolphin automatically switches it when the game launches. I just keep it on Texture, and it works just fine. even for scanning.

[DefenderX]

don't work.

btw: i have to set EFB Copies to RAM manually. my version don't switch this setting automatically