Dolphin, the GameCube and Wii emulator - Forums

Full Version: r7714 - Windows [x86/x64] Frequently updated Dolphin SVN builds by Xtreme2damax
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
(07-07-2010, 03:33 PM)obscured Wrote: [ -> ]Thanks for the build. For some reason your was faster then Araris's build. I thought I had a performance hit of 10% speed with the new commits.

Interesting, I just got the base SVN + Hyrule Speedup Hack...if he's building his with SSE4.2 support it's probably faster, otherwise I have no idea what might be wrong.
(07-07-2010, 10:06 AM)Xtreme2damax Wrote: [ -> ]There is no other way, you need to update DirectX.

If bandwidth is a problem, just download and run the web updater, not the full DirectX redistributable package. This should only update necessary runtimes, and will only use between 10 MB - 15 MB compared to the 100+ MB redistributable package. It is the quickest and easiest way to update your DirectX runtimes.

I downloaded and installed the latest directx9 through torrent (june), now it can see the direct3d plugin.

Your build is better in term of graphics, the grass looks normal , the horizon , everything.

But the problem of slowdown remains the same, once I quit kokoriko village to the next destination , my frame rate in the field drops down to 20 fps and farther to 15fps. The rates go back to normal once I enter smaller areas like the city or the lake , the problem seems only in the open fields. I see no difference between the official dolphin 2.0 and your build regarding this problem.

Is there any specific config to improve this in your build?

I am using EFB to texture (i tried to RAM, it ruins the graphics and makes no speed up) with EFB copy scaled on , Fog on or off is making no difference.

And oh, the rumble didn't function in your build.


I have a Quad Core Q6600 2.4GHz and Radeon 4850 + 4GB RAM.
Did you enable the hack in the DX9 configuration? Refer to my screenshot in the following post to find where the option is located:

http://forums.dolphin-emu.org/thread-2176-post-98761.html#pid98761
(07-08-2010, 02:20 AM)Xtreme2damax Wrote: [ -> ]Did you enable the hack in the DX9 configuration? Refer to my screenshot in the following post to find where the option is located:

http://forums.dolphin-emu.org/thread-2176-post-98761.html#pid98761


Still, same symptoms, just a little improvement in speed.

I am getting 20 fps in the twilight around hyrule castle. Is this normal for this build? or it can be better?
no good, the more I venture in that part of the hyrule field , the slower it gets, now i am getting 17 fps.
That's normal, idle skipping can be enabled for an extra boost. The hack won't give you full speed, but your speed will be much better than without the hack. For example on my system I have 12 FPS - 15 FPS in Hyrule Field without the hack, with the hack I have 22 FPS - 25 FPS. I enabled idle skip when I tested on my end since this option offered a 3 FPS - 6 FPS speedup. You can enable idle skipping in the plugin options or the game list configuration by right clicking a game and enabling the checkbox for idle skipping.
(07-08-2010, 05:33 AM)Xtreme2damax Wrote: [ -> ]That's normal, idle skipping can be enabled for an extra boost. The hack won't give you full speed, but your speed will be much better than without the hack. For example on my system I have 12 FPS - 15 FPS in Hyrule Field without the hack, with the hack I have 22 FPS - 25 FPS. I enabled idle skip when I tested on my end since this option offered a 3 FPS - 6 FPS speedup. You can enable idle skipping in the plugin options or the game list configuration by right clicking a game and enabling the checkbox for idle skipping.

and the rumble? Tongue
My build has nothing to do with the rumble, you must have not properly configured rumble or the feature was broken by a specific commit, nothing to do with my builds. You should track down the commit responsible and report this regression to the developers providing everything is properly configured on your end. Wink
(07-08-2010, 05:57 AM)Xtreme2damax Wrote: [ -> ]My build has nothing to do with the rumble, you must have not properly configured rumble or the feature was broken by a specific commit, nothing to do with my builds. You should track down the commit responsible and report this regression to the developers providing everything is properly configured on your end. Wink

it was natively not working before changing anything , I am trying to select Motor L or R but still no effect.
I can assure you it wasn't my build that broke this, I never messed around with game pads so it's impossible for me to have broken rumble. When I just tested my build, rumble was working fine, so my bet is that something wasn't configured correctly on your end.
Could you compile a built using nvidia cuda sdk? Tks.