Dolphin, the GameCube and Wii emulator - Forums

I'm using this build an Xenonblade works Flawless without crashes.

Thought I'd drop by to say thanks...

Just completed Xenoblade flawlessly (sometimes with minor problems like Wiimote getting disconnected after saving to states) using this emulator (EDIT: your builds), and the game ran fast, too, at 4x native without any AA. This game looks great even without AA though.

Nah, i'm not as lucky as you, guys, just loaded the game, reorienting the camera and Dolphin freezed.

10 seconds.

:\

hi Filthy, can you pls re-upload the 3.0-71 SSE3 with mylek´s 3.1 build? this build works better for me, than your current build.

Filthy, could you compile an ICC optimized build of GCMemcardUpdates branch?

if you want to test the changes in my branch (GCMemcardUpdates) there is a build here -> http://www.emucr.com/2011/09/dolphin-gcmemcardupdates-git-30-98.html
nothing is really different when it comes to actually playing the games, just a bugfix (formatting from the memory card manager), small fixes for less noob confusion (auto formatting the card when first used) not writing the sram.raw file)

(09-23-2011, 02:02 AM)Trevlec Wrote: [ -> ]hi Filthy, can you pls re-upload the 3.0-71 SSE3 with mylek´s 3.1 build? this build works better for me, than your current build.

I never actually deleted it, just removed the links.
SSE3
SSE4.1
SSE4.2
SSE3 + Mylek's Patch
SSE4.1 + Mylek's patch

Somebody else mentioned that the 71 build was working better for them as well. Now I am curious as to whether or not the difference is between something committed between the versions, or the optimizations used. The 3.0-96 builds I put up don't have IPO or optimized headers turned on, as I found they didn't help in my xenoblade fps tests.

The 96 build is using /O3 instead of /O2 as well, as I found it was giving a slight FPS boost. In my professional experience, I've found /O3 to usually be a risky optimization though. I've had it break proper code operation before. If people find it isn't working well, I might go back to /O2. Please let me know if that is the case. I can always revert to my older build settings.

As for the memcard branch, I think I'll pass on it for now. At the moment, I am more interested in nailing down solid settings for the main branch. I am sure that Emucr's builds are fine for that.

Somebody on another forum had suggested I consider profile guided optimization, and that is what I am looking into at the moment.

AUIU all the different parts are built to static libraries which can't be profiled. You'd only be profiling the GUI code in the Dolphin project.
Another small but harmless compiler optimization you can add is /Qauto-ilp32 since >4GB of memory isn't needed.

Filthy, are you going to compile the new builds?

Can't believe there's not a x86 (32-bit) version of this build.

Any plans on a 32-bit version? I believe the demands are high, they are just shy and don't post in forums.