Specs:
i7-720QM 1.6ghz (2.8ghz turbo boost)
NVidia GeForce GT 230M
There are two major problems (other than how slow it goes using only 25% CPU on an i7 mobile processor.. but that's not a WW specific issue, that's another topic.)
First and foremost, there is a problem with smoke/heat effect. In normal fire smoke (lanterns, torches, etc), things get distorted/reflected in the heat effect. In the Dragon Roost Heat, it is insane, it looks like the screen is being torn apart with sharp edges rather quickly.
OK, I have tried 3 builds (2.0, 6331 (crawls for some reason), and 6441). I have tried D3D and OpenGL Plugins, all setting combinations, and I mean I played with them for hours and hours, notably the EFB settings. I have them on EFB->RAM (tried texture, turning off EFB pretty much breaks the graphics), EFB scaled copy (tried turning it off), EFB->CPU access (yes, tried turning that off too,) tried enabling Safe Texture Cache (I don't think this had any effect on anything) and XFB both modes (IIRC this broke things.)
(I am also using TP Bloom Hack to eliminate blurriness on the crappy resolution I have to use to get decent speed... native in a few places including Dragon Roost where the heat effect is going on and any place with fog, at least on 2.0 where it is an option. Still looks kinda crappy - AA doesn't seem to do anything on native/640x480 - unless I turn it up to at least 800x600.)
So I am of the conclusion that this is a problem with Dolphin and the card... or the drivers :/ (anyone got any ideas on the drivers I should use perhaps?) I have found that a couple other people reported this problem.
The other problem is the pictograph. It goes click-click-click-click-etc and does that for a good minute before it either A) crashes (64-bit builds) or B) goes to a sometimes black sometimes correct picture and continues (32-bit builds). I tried messing with the graphics settings for this too... luckily I have zero interest in the Nintendo Gallery and can just handle it for the few I actually need to take for some stuff.
Im having an issue with wind waker. im stuck in dragon roost level. beat the level, but when i try to teleport out of the boss room, it freezes
OK SVN 6441 x64, I got to the main room in the Forsaken Woods and the giant flower wasn't there, left and re-entered, and it was there, then I went and got a key and came back and the entire room was gone, Link went into a door into an abyss of nothing and the screen went to black
Many problems with this game, grr.. it's not even that great a game, not sure if it's worth all this..
No need for a new thread:
http://forums.dolphin-emu.org/showthread.php?tid=40&page=97
about the core i7-720QM 1.6ghz using only 25%, are you right?? I have the same processor and a nvidea gt330m and I didn't notice that 0_o the game runs at full speed.
the smoke/heat problem is an issue yet to be fixed. Just have to be patient ;-)
Ah ok, how come no one else seems to mention it?
We have very similar specs, open up a task manager and see how much CPU Dolphin is using. Windows 7? What resolution, graphics settings, Dolphin build?
(12-11-2010, 04:59 AM)xenofears Wrote: [ -> ]Ah ok, how come no one else seems to mention it?
We have very similar specs, open up a task manager and see how much CPU Dolphin is using. Windows 7? What resolution, graphics settings, Dolphin build?
windows 7
1366x768
Dolphin svn6543 right now.
only 25-28% of the cpu is being used :-s . I don't know if it is because Dolphin only uses 2 cores and i7 have 4 cores (4cores = 100 in task manager
)
(12-10-2010, 09:16 AM)xenofears Wrote: [ -> ]Specs:
i7-720QM 1.6ghz (2.8ghz turbo boost)
NVidia GeForce GT 230M
There are two major problems (other than how slow it goes using only 25% CPU on an i7 mobile processor.. but that's not a WW specific issue, that's another topic.)
First and foremost, there is a problem with smoke/heat effect. In normal fire smoke (lanterns, torches, etc), things get distorted/reflected in the heat effect. In the Dragon Roost Heat, it is insane, it looks like the screen is being torn apart with sharp edges rather quickly.
OK, I have tried 3 builds (2.0, 6331 (crawls for some reason), and 6441). I have tried D3D and OpenGL Plugins, all setting combinations, and I mean I played with them for hours and hours, notably the EFB settings. I have them on EFB->RAM (tried texture, turning off EFB pretty much breaks the graphics), EFB scaled copy (tried turning it off), EFB->CPU access (yes, tried turning that off too,) tried enabling Safe Texture Cache (I don't think this had any effect on anything) and XFB both modes (IIRC this broke things.)
(I am also using TP Bloom Hack to eliminate blurriness on the crappy resolution I have to use to get decent speed... native in a few places including Dragon Roost where the heat effect is going on and any place with fog, at least on 2.0 where it is an option. Still looks kinda crappy - AA doesn't seem to do anything on native/640x480 - unless I turn it up to at least 800x600.)
So I am of the conclusion that this is a problem with Dolphin and the card... or the drivers :/ (anyone got any ideas on the drivers I should use perhaps?) I have found that a couple other people reported this problem.
The other problem is the pictograph. It goes click-click-click-click-etc and does that for a good minute before it either A) crashes (64-bit builds) or B) goes to a sometimes black sometimes correct picture and continues (32-bit builds). I tried messing with the graphics settings for this too... luckily I have zero interest in the Nintendo Gallery and can just handle it for the few I actually need to take for some stuff.
Ok im going to be a bit blunt dude most if not all the issues were fixed in the latest dolphin res
The flame/smoke issue is still there i think but its a lot better of then it used to be
I played the game flawlessly on a shit quad core processor
Fact is if you keep up to date with the latest revs most issues will be fixed
As i matter of fact i clocked wind waker on dolphin 2.0 standard
And im telling you now it was still playable regarless of the errors
he errors that other people are having like the missing rooms and shit though that you own issue this wasn't really directed a you
(12-11-2010, 08:09 AM)kazaazak12 Wrote: [ -> ] (12-10-2010, 09:16 AM)xenofears Wrote: [ -> ]Specs:
i7-720QM 1.6ghz (2.8ghz turbo boost)
NVidia GeForce GT 230M
There are two major problems (other than how slow it goes using only 25% CPU on an i7 mobile processor.. but that's not a WW specific issue, that's another topic.)
First and foremost, there is a problem with smoke/heat effect. In normal fire smoke (lanterns, torches, etc), things get distorted/reflected in the heat effect. In the Dragon Roost Heat, it is insane, it looks like the screen is being torn apart with sharp edges rather quickly.
OK, I have tried 3 builds (2.0, 6331 (crawls for some reason), and 6441). I have tried D3D and OpenGL Plugins, all setting combinations, and I mean I played with them for hours and hours, notably the EFB settings. I have them on EFB->RAM (tried texture, turning off EFB pretty much breaks the graphics), EFB scaled copy (tried turning it off), EFB->CPU access (yes, tried turning that off too,) tried enabling Safe Texture Cache (I don't think this had any effect on anything) and XFB both modes (IIRC this broke things.)
(I am also using TP Bloom Hack to eliminate blurriness on the crappy resolution I have to use to get decent speed... native in a few places including Dragon Roost where the heat effect is going on and any place with fog, at least on 2.0 where it is an option. Still looks kinda crappy - AA doesn't seem to do anything on native/640x480 - unless I turn it up to at least 800x600.)
So I am of the conclusion that this is a problem with Dolphin and the card... or the drivers :/ (anyone got any ideas on the drivers I should use perhaps?) I have found that a couple other people reported this problem.
The other problem is the pictograph. It goes click-click-click-click-etc and does that for a good minute before it either A) crashes (64-bit builds) or B) goes to a sometimes black sometimes correct picture and continues (32-bit builds). I tried messing with the graphics settings for this too... luckily I have zero interest in the Nintendo Gallery and can just handle it for the few I actually need to take for some stuff.
Ok im going to be a bit blunt dude most if not all the issues were fixed in the latest dolphin res
The flame/smoke issue is still there i think but its a lot better of then it used to be
I played the game flawlessly on a shit quad core processor
Fact is if you keep up to date with the latest revs most issues will be fixed
As i matter of fact i clocked wind waker on dolphin 2.0 standard
And im telling you now it was still playable regarless of the errors
he errors that other people are having like the missing rooms and shit though that you own issue this wasn't really directed a you
Sorry if I wasn't clear, but I was using SVN 6441. I WAS clear that I tried 2.0 for these issues. I had to go BACK to 2.0 (used 32-bit, didn't try 64) to avoid the Forsaken Forest crashes (it crashed again entering the mini-boss chamber, just went to black,) and that's too slow on my rig. Sorry, I stand by my issues.
Don't pay any attention to him.
Whatever, SVN 6441 = Wind Waker crashes on my machine. Sorry if you are not happy with that. And it played Tales of Symphonia just fine beginning to end (like 70 hours), save the known ghosting issue.