That error message looks helpful.
Also, going by the signature of the 2 people with crashes as well, i think it might be CPU related. All those CPUs, E6700, Q6600 and Phenom II X4 955 are apparently missing the following CPU features(compared to an i7):
- SSE4 and up(edit: clarification that none of those processors support SS4)
- AVX and AVX 2.0
- FMA3
- EMT64
- F16C
- AES
(05-20-2014, 06:52 AM)mimimi Wrote: [ -> ]That error message looks helpful.
Also, going by the signature of the 2 people with crashes as well, i think it might be CPU related. All those CPUs, E6700, Q6600 and Phenom II X4 955 are apparently missing the following CPU features(compared to an i7):
- SSE4+
- AVX and AVX 2.0
- FMA3
- EMT64
- F16C
- AES
did you try the build in *_2.zip that is only with the dialog box or *_3.zip with a probably fix ?
dolphin_d3d_20140519_3.zip did not work either, and it's not showing the nice error message anymore.
According to their sigs, the user StripTheSoul has this rig:
Core2Quad Q6600@3400MHz (+Scythe Mugen) / Abit IP35 Pro / 2GB RAM / Geforce GTX 460 OC (1GB) / X-Fi XtremeMusic / Win8.1 Pro 64bit / 2x WiiMote+MotionPlus+Nunchuk.
And Gir this one:
AMD Phenom II X4 955, ATI AMD Radeon 5770 4 GB DDR2 1066, Windows Blue
Which is why i figure this might not be one specific AMD GPU problem. Well, that is if the infos in the sigs are up-to-date.
Here's the crash dump from test version 4(3800).
So, i did a 1st test with dual core deactivated and LLE activated to get results that tell how much the total CPU load improves. For now i'm just looking at how well the start menu island zoom in Wind Waker works. When i get a stop watch or stop watch app, i'll do a test with a 2-3 min recording and compare how long it takes in the different versions, and check if the fps logs are worth posting. Since i can get the game to run at less than full speed with these settings, measuring the time it takes for an island run seems like a good benchmark to me.
4.0-1601 and DolphinLTCG with D3D give me 19 fps in a specific scene over 5 seconds, 4.0-1601 with opengl gives me 19-20 fps in the same scene, and the version 20140519_working gives me 23 fps there. Those results are pretty consistent and are the same, no matter how often i repeat the test. So considering rounding, i'd say it's a 15.5% to 26.9% improvement in that scene. Hopefully the improvement will be the same overall and not just in that scene. Will report later when i have better results.
Also, the stutter beahvior is the same for all D3D tests, so my very 1st impression that this might introduce stuttering, was wrong.
mimimi: Could you also try this test without LLE? By adding a new bottleneck, the speedup isn't shown that hard
But I'm fine with single core.
(05-20-2014, 07:01 PM)degasus Wrote: [ -> ]mimimi: Could you also try this test without LLE? By adding a new bottleneck, the speedup isn't shown that hard
But I'm fine with single core.
And dual core is a must have option too. As a 50% speed up in the video thread is a 25% speed up if it runs in the same thread than the cpu one ( if cpu thread was of duration equal or less than the video thread in dual core mode ).
galop1n: This isn't always true. Eg for some games, we're bottlenecked by the cpu emulation, so your speedup won't be noticed at all.
(05-20-2014, 07:30 PM)degasus Wrote: [ -> ]galop1n: This isn't always true. Eg for some games, we're bottlenecked by the cpu emulation, so your speedup won't be noticed at all.
That's why i said "if"
The recording idea did not work, the input unsyncs, so link is running against walls etc. So i went back to that one scene from Wind Waker's start menu for now. The fps numbers are the min/max values from 2 runs.
D3D, dual core, HLE, version 20140519_working:
Scene 1: 44-46 fps
Scene 2: 74-77 fps (displaying the wind waker logo in front of the sea, before the screen turns black)
Time it takes until screen turns black: 41 sec
D3D, dual core, HLE, DolphinLTCG:
Scene 1: 32-34 fps
Scene 2: 75-76 fps
Time it takes until screen turns black: 43 sec
=> Up to around 36% improvement on dual core + HLE.
D3D, single core, HLE, version 20140519_working:
Scene 1: 25-26 fps
Scene 2: 45-46 fps
Time it takes until screen turns black: 64 sec
D3D, single core, HLE, DolphinLTCG:
Scene 1: 21-22 fps
Scene 2: 41-42 fps
Time it takes until screen turns black: 69 sec
=> Up to around 19% improvement on single core + HLE.
D3D, dual core core, LLE, version 20140519_working:
Scene 1: 36-37 fps
Scene 2: 55-57 fps
Time it takes until screen turns black: 51 sec
D3D, dual core, LLE, DolphinLTCG:
Scene 1: 30-31 fps
Scene 2: 53-57 fps
Time it takes until screen turns black: 53 sec
=> Up to around 20% improvement on dual core + LLE.
So in some places there's basically no change at all, while there's some good improvement in others.