79,221
edits
Metroid Prime: Trilogy: Difference between revisions
m
Text replacement - " x64" to ""
m (Text replacement - "({{VersionCompatibilityVersion\|[^\|]*\|[^\|]*)}}" to "$1|}}") |
m (Text replacement - " x64" to "") |
||
| Line 67: | Line 67: | ||
<!--Use this template for test entries: {{testing/entry|revision=|OS=|CPU=|GPU=|result=|tester=}}--> | <!--Use this template for test entries: {{testing/entry|revision=|OS=|CPU=|GPU=|result=|tester=}}--> | ||
<!--Please only provide entries for the Metroid Prime: Trilogy LAUNCHER. Please visit the sub-game pages to add entries for individual games--> | <!--Please only provide entries for the Metroid Prime: Trilogy LAUNCHER. Please visit the sub-game pages to add entries for individual games--> | ||
{{testing/entry|revision=3.0-141 ES_LAUNCH|OS=Windows 7 | {{testing/entry|revision=3.0-141 ES_LAUNCH|OS=Windows 7|CPU=Intel Core 2 Quad QX9650 @ 4GHz|GPU=ATI Radeon HD 5870|result=[http://www.youtube.com/watch?v=mylfKlqaEGc Metroid Prime: Trilogy on Dolphin - Wii Emu]|tester=Foxcor}} | ||
{{testing/entry|revision=3.0-720|OS=Windows 7 | {{testing/entry|revision=3.0-720|OS=Windows 7|CPU=Intel Core 2 Duo E7600 @ 3.06GHz|GPU=NVIDIA GeForce 9800 GT|result=Metroid 2 runs at 30-40FPS very playable with Direct3D9 EFB Copies=Ram for visor scanning Must use dol method for each game. Metroid 3 runs 30-40FPS EFB Copies to RAM for visor scanning|tester=GodsSins}} | ||
{{testing/entry|revision=3.5-268|OS=Windows 7 | {{testing/entry|revision=3.5-268|OS=Windows 7|CPU=Intel Core i5-3570K @ 4.7GHz|GPU=NVIDIA GeForce GTX 275|result=ES_Launch merger. Successfully launched Prime 3, used the home button to go back to the main launcher, and then launched Prime 2. Everything works correctly. There are some minor issues, such as the FMVs lagging behind audio, but that's not new.|tester=MaJoR}} | ||
{{testing/entry|revision=3.5-379|OS=Windows 7 | {{testing/entry|revision=3.5-379|OS=Windows 7|CPU=Intel Core i5-2500K @ 4.3GHz|GPU=NVIDIA GeForce GTX 680 x2|result=100% emulation, there's no stuttering or lagging. Minor problems, such as 3 pixels at the middle of the screen. It's a bit annoying but easy to ignore. NVIDIA GeForce 3D vision isn't working, possibly a Dolphin problem. Settings used: Direct3D9, no AA, no Anisotropic filtering, HLE audio (seems to work right, without any problems), 1440x900 full-screen resolution. For more info click [http://www.youtube.com/watch?v=cWp5M9TKSpo here]|tester=Megamew28}} | ||
{{testing/entry|revision=4.0-3532|OS=Windows 7 | {{testing/entry|revision=4.0-3532|OS=Windows 7|CPU=Intel Core i7-4770K @ 3.5GHz|GPU=NVIDIA GeForce GTX 750 Ti|result=Game launches fine, but I'm unable to play anything. Prime 1 and 3 claim that the Wii Remote has disconnected, Prime 3 simply goes black and freezes, with some odd pixels in the center of the screen. Prime 2 gets as far as some sort of menu but it's impossible to input using Wii Remotes. Disabling Speaker Data has no affect. Running OpenGL, XAudio2, and using the DolphinBar.|tester=BillyAlt}} | ||
{{testing/entry|revision=4.0-5550|OS=Windows 8.1 | {{testing/entry|revision=4.0-5550|OS=Windows 8.1|CPU=Intel Core i5-4670K @ 4.4GHz|GPU=NVIDIA GeForce GTX 970|result=One small issue - The Wii Remote gets disconnected every time I load my save game, which is easily fixed with alt+f5. Prime 2 runs flawlessly, completed the game without any issues. Prime 3 runs well in the latest builds, gone are the audio issues from earlier revisions. Currently just got Plasma Beam in Prime 3, and everything is working just fine now. Mouse and keyboard controls work well enough to enable a full play through without an actual Wii Remote. Not sure about Prime 1 as I refuse to play the trilogy version due to removal of sequence breaking.|tester=Andr0idOS}}{{testing/end}} | ||
== Gameplay Videos == | == Gameplay Videos == | ||