http://205.196.122.122/7wu3f39hfiig/bp6w...for+mh3.7z
My specs:
Core 2 Duo E7400 at ~2.8 Ghz
8 GB RAM
Nvidia GTX 560 Ti
Using latest build, I get 20-24 FPS in town, 17-23 when in Moga Forest.
Using THIS one that I just stumbled on, I get to play full speed 30 FPS 90% of the time. Exception is when there are lots of people in town(Argosy) and lots of monsters in other maps.
This is an old build. Not sure if someone revised it and I haven't tested the actual corresponding build from here(R5474).
Follow the readme included. (It was already there when I found it)
This build will have 2 major bugs. One of them has already been discussed thoroughly in the past. The other one, I had to figure out the fix myself.
*** Bloom(too bright and crappy graphics)
- Thankfully this version already comes with the bloom patch. All you need to do is PRESS 7(not numpad) when you're in the actual game. Please note that when you toggle this on, there are a few graphical glitches:
1. Might seem too dark. Don't worry, you get used to it. I did. And it's not that dark. I don't even bring torches in caves.
2. On occasion, you're character model will just be pitch black. Thankfully, it doesn't include the armor and equips, just the character model, so it won't be a problem.
3. When this is activated while in the title menus, you won't be able to navigate through them because a lot of details will disappear. So make sure you toggle on only when you're in the game already.
4. Loading screens will be pitch black, only the quest introduction text will show. Don't worry, it's loading.
NOTE: 7 is a toggle switch. You can toggle it anytime to see the loading screens, or the horrendous bloom effect when you're out doing quests.
All in all, the game will be delightfully fast and playable for those with similar rig as mine.
And never mind my video card. It's high end, but not necessary. The game only uses around 30% of gpu grunt while running when I checked.
*** Savestates
On occasion, when you load a state, it's either:
1. It won't load(freeze screen, black, stuttering audio only, just audio playing, etc.)
2. It does load but you can't use your emulated wiimote.
3. When you load a state that's in a quest, suddenly the quest time is up and you failed the quest.
Simple fix:
1. Completely close Dolphin.
2. Change your system time to approximately when you last saved it, or even before you saved it. Change the date, too, if necessary. If you're using Windows, just click on the time itself at the bottom right corner on your taskbar then click "Change date and time settings". I'm sure you can figure it out at this point.
3. Open dolphin again and load state. It should load now.
4. While your game is still running,
- pause it(F10).
- if you're running on fullscreen, press Alt+Enter so you can see your desktop again. The Dolphin game window will on occasion be just black. That's normal.
- change system time back to the correct time.
- click the Dolphin game window to return to your game and unpause(F10 again.)
- wait for the game screen to appear again first.
- if you prefer running your game fullscreen, NOW is the time to go back to it. Alt+Enter again. Otherwise, if you toggle to fullscreen while the game window is black, it stays black even after unpause.
- save the state again for good measure.
I'm not entirely sure why wiimote connection fails on some of the load states. It seems to happen arbitrarily.
TIP: If you're saving a state while in a quest, make sure you open the Quest Info screen and note the time left. Countless times it's happened to me, losing 20 minutes quest time and even fail a quest just because I had to save state and exit Dolphin. Then when I came back, it's like Dolphin keeps track of the time you were gone and updates your savestate respectively. So if this happens, you may need to do this process.
Hopefully people who have had the same problem, or still do, find this post.
What happened to my post?
My specs:
Core 2 Duo E7400 at ~2.8 Ghz
8 GB RAM
Nvidia GTX 560 Ti
Using latest build, I get 20-24 FPS in town, 17-23 when in Moga Forest.
Using THIS one that I just stumbled on, I get to play full speed 30 FPS 90% of the time. Exception is when there are lots of people in town(Argosy) and lots of monsters in other maps.
This is an old build. Not sure if someone revised it and I haven't tested the actual corresponding build from here(R5474).
Follow the readme included. (It was already there when I found it)
This build will have 2 major bugs. One of them has already been discussed thoroughly in the past. The other one, I had to figure out the fix myself.
*** Bloom(too bright and crappy graphics)
- Thankfully this version already comes with the bloom patch. All you need to do is PRESS 7(not numpad) when you're in the actual game. Please note that when you toggle this on, there are a few graphical glitches:
1. Might seem too dark. Don't worry, you get used to it. I did. And it's not that dark. I don't even bring torches in caves.
2. On occasion, you're character model will just be pitch black. Thankfully, it doesn't include the armor and equips, just the character model, so it won't be a problem.
3. When this is activated while in the title menus, you won't be able to navigate through them because a lot of details will disappear. So make sure you toggle on only when you're in the game already.
4. Loading screens will be pitch black, only the quest introduction text will show. Don't worry, it's loading.
NOTE: 7 is a toggle switch. You can toggle it anytime to see the loading screens, or the horrendous bloom effect when you're out doing quests.
All in all, the game will be delightfully fast and playable for those with similar rig as mine.
And never mind my video card. It's high end, but not necessary. The game only uses around 30% of gpu grunt while running when I checked.
*** Savestates
On occasion, when you load a state, it's either:
1. It won't load(freeze screen, black, stuttering audio only, just audio playing, etc.)
2. It does load but you can't use your emulated wiimote.
3. When you load a state that's in a quest, suddenly the quest time is up and you failed the quest.
Simple fix:
1. Completely close Dolphin.
2. Change your system time to approximately when you last saved it, or even before you saved it. Change the date, too, if necessary. If you're using Windows, just click on the time itself at the bottom right corner on your taskbar then click "Change date and time settings". I'm sure you can figure it out at this point.
3. Open dolphin again and load state. It should load now.
4. While your game is still running,
- pause it(F10).
- if you're running on fullscreen, press Alt+Enter so you can see your desktop again. The Dolphin game window will on occasion be just black. That's normal.
- change system time back to the correct time.
- click the Dolphin game window to return to your game and unpause(F10 again.)
- wait for the game screen to appear again first.
- if you prefer running your game fullscreen, NOW is the time to go back to it. Alt+Enter again. Otherwise, if you toggle to fullscreen while the game window is black, it stays black even after unpause.
- save the state again for good measure.
I'm not entirely sure why wiimote connection fails on some of the load states. It seems to happen arbitrarily.
TIP: If you're saving a state while in a quest, make sure you open the Quest Info screen and note the time left. Countless times it's happened to me, losing 20 minutes quest time and even fail a quest just because I had to save state and exit Dolphin. Then when I came back, it's like Dolphin keeps track of the time you were gone and updates your savestate respectively. So if this happens, you may need to do this process.
Hopefully people who have had the same problem, or still do, find this post.
What happened to my post?
So much to learn, so little time...