Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13
On the last unofficial build (I think it was like 3663?) I got 60 fps constant in zelda wind waker. Now with 3971 it's back down to 30 fps like the build before 3663. The sound is working much better now, but I'm wondering why 30 fps is gone again?
(08-14-2009, 04:25 AM)Diddy Kong Wrote: [ -> ] (08-14-2009, 04:23 AM)Runo Wrote: [ -> ]Yeah, I'm playng it for about 3 hours no crash, no error, it's really the most stable version so far, even the save/load state are working better, and Im doing a backup and a virus scan in background, but still the performance is more than playable, thanx again Chaoscode and all the team!
With the Virus Scan and backup, really??
Which game are you running & how many FPS are you getting
Im running Smash bros melee and Super Mario Sunshine PAL
For Melee im getting 40 - 50 in one on one battles all time and in team battles 30 -40 Im sayng this version is incredible.
Sunshine im getting like 20 fps all time (PAL works on a max of 25)
And without Virus Scan and Backup I get Fullspeed in both games.
(08-14-2009, 04:08 AM)Diddy Kong Wrote: [ -> ] (08-14-2009, 04:05 AM)Chaoscode Wrote: [ -> ] (08-14-2009, 12:15 AM)joaquimserrote Wrote: [ -> ]very bad this version:
-is more slow comparate of r3950 (with same configurations)
-appears sounds when I click on buttons of keyboard in game
-i have games are broken in start, mario tennis, mario golf, super monkey ball 1 appears without head since version r3661
i use version 32
sorry for my english
you just have no idea what your doing. don't come here and say its a bad version. if you dont like it dont use it. try another gamecube/wii emulator. O wait were the only one...
Don't worry about the Idots Chaoscode, well done one the new release. 
LOL, sorry
I explained bad because my english is very bad, not my intention are severe in words, I wanted say as last revisons have some failures (any games broken in last version but not r3661).
You made a great job with this emulator
I'm having a strange problem with
Little King's Story.
When I start the ISO the Wii warning screen comes up fine and so do the first few game screens but then an FMV plays and the screen starts flashing between pure gray and the actual game screen extremely quickly. (eg. flicker)
It then continues doing that and there is no way to stop it and continues even at the main menu.
Is there a fix for this?

Try playing your game on an actual Wii.
Huh? It plays fine on my Wii of course.
(08-14-2009, 12:44 AM)THELUKESTIR Wrote: [ -> ] (08-14-2009, 12:35 AM)Ultimate Wrote: [ -> ]I'm getting a "Failed to grab 1gb of continuous memory" and it's not only in this build (3661 have the same problem, but i can play on 3505)
How can i fix that?
if you have ati downgrade to catalyst 9.3 also search the forums next time please
Ehrm... Can you explain it better to me? I didn't understand... What do i have to downgrade?
(08-14-2009, 01:54 PM)Ultimate Wrote: [ -> ]Ehrm... Can you explain it better to me? I didn't understand... What do i have to downgrade?
If you have an ATI graphics card and a version of Catalyst over 9.3, then you should downgrade because there is a memory leak issue with Dolphin when using Catalyst drivers.
And that is NOT the source of the problem because Dolphin has grabbed well over 1GB of contiguous memory before you run out of memory from the leak... I think.
So, where I can download version 3972 ? On the site there is only 3971...
(08-14-2009, 02:00 PM)Core2uu Wrote: [ -> ] (08-14-2009, 01:54 PM)Ultimate Wrote: [ -> ]Ehrm... Can you explain it better to me? I didn't understand... What do i have to downgrade?
If you have an ATI graphics card and a version of Catalyst over 9.3, then you should downgrade because there is a memory leak issue with Dolphin when using Catalyst drivers.
And that is NOT the source of the problem because Dolphin has grabbed well over 1GB of contiguous memory before you run out of memory from the leak... I think.
Well that's weird... I use a Nvidia GeForce card, and the build 3661 used to work before and i haven't installed any program that made it do that error, it just do it on it's own
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13