1
edit
 |
Progress Continues
We've already had 21555 updates since Dolphin 5.0. Keep up with Dolphin's continuing progress through the Dolphin Blog: February, March, and April 2024 Dolphin Progress Report. |
 |
The Dolphin Emulator Wiki needs your help! Dolphin can play thousands of games, and changes are happening all the time. Help us keep up! Join in and help us make this the best resource for Dolphin. |
Metroid Prime (GC): Difference between revisions
no edit summary
m (Text replacement - "\<s\>(.*)\<\/s\>" to "{{s}}$1{{/s}}") |
BallsOfSteel (talk | contribs) No edit summary |
||
| Line 82: | Line 82: | ||
{{testing/entry|revision=4.0-4478|OS=Windows 8 x64|CPU=Intel Core i7-3520M @ 3.3GHz|GPU=NVIDIA GeForce GT 640M LE|result= Played with D3D, 1.5x resolution. Near perfect, slows down only in very large areas or when splashing in water for some reason. FPS is constantly at around 60, VPS is stable as well. Micro-stuttering still an issue but barely noticeable; the sound is fantastic with the HLE engine, not a single error. I managed to complete the game with minor problems; the x-ray and thermal visors failed to work once for some reason, but worked again after resetting the emulator. It crashed four times in total, always in the same situation; when entering rooms where purple energy enemies are found, those that can only be killed via wave beam, the game randomly crashed. In other cases a FIFO overflow error occurred, although it didn't stop the emulation or crash the game. This is very close to perfect, and my computer is nowhere near powerful for Dolphin. Modifications to the JIT and FIFO have made a huge difference.|tester=UDEM42}} | {{testing/entry|revision=4.0-4478|OS=Windows 8 x64|CPU=Intel Core i7-3520M @ 3.3GHz|GPU=NVIDIA GeForce GT 640M LE|result= Played with D3D, 1.5x resolution. Near perfect, slows down only in very large areas or when splashing in water for some reason. FPS is constantly at around 60, VPS is stable as well. Micro-stuttering still an issue but barely noticeable; the sound is fantastic with the HLE engine, not a single error. I managed to complete the game with minor problems; the x-ray and thermal visors failed to work once for some reason, but worked again after resetting the emulator. It crashed four times in total, always in the same situation; when entering rooms where purple energy enemies are found, those that can only be killed via wave beam, the game randomly crashed. In other cases a FIFO overflow error occurred, although it didn't stop the emulation or crash the game. This is very close to perfect, and my computer is nowhere near powerful for Dolphin. Modifications to the JIT and FIFO have made a huge difference.|tester=UDEM42}} | ||
{{testing/entry|revision=4.0-5347|OS=Windows 7 x64|CPU=Intel Core i7-4770K @ 4.2GHz|GPU=NVIDIA GeForce GTX 660 Ti|result=Played through the pirate frigate section, it seems perfect and running at full speed. Using D3D, auto rescaling at 1920x1080, 2xAA 4xAF, other settings at defaults. The microstuttering is there but isn't really a problem. It was present at places like the pan over the frigate during the opening cutscene and using the morph ball for the first time. Each pause was 150ms or so. Repeating these actions did not result in stuttering since the shaders were cached.|tester=ThatBum}} | {{testing/entry|revision=4.0-5347|OS=Windows 7 x64|CPU=Intel Core i7-4770K @ 4.2GHz|GPU=NVIDIA GeForce GTX 660 Ti|result=Played through the pirate frigate section, it seems perfect and running at full speed. Using D3D, auto rescaling at 1920x1080, 2xAA 4xAF, other settings at defaults. The microstuttering is there but isn't really a problem. It was present at places like the pan over the frigate during the opening cutscene and using the morph ball for the first time. Each pause was 150ms or so. Repeating these actions did not result in stuttering since the shaders were cached.|tester=ThatBum}} | ||
{{testing/entry|revision=4.0-7816|OS=Windows 7 x64|CPU=Intel Core i5-2500k @ 3.3GHz|GPU=ATI Radeon HD 6870|result=Completed a 100% playthrough. D3D, auto rescaling, fullscreened to 1920x1080, all other graphics options set to default or auto. In certain areas there was extreme slowdown, namely the completed map screen for most sections, and the Chozo Temple, which made fighting Meta Ridley a tad difficult. There is also slowdown during special visor effects, such as when jumping into or exiting water, shooting a beam at a wall directly in front of you, or stuff splashing on it when killing Scarabs, but those were only a minor nuisance. The microstuttering shader cache issue still seems to exist here and there but the pauses were always extremely short and not too noticeable.|tester=BallsOfSteel}} | |||
{{testing/end}} | {{testing/end}} | ||