That's to be expected, the feature is actually called "skip EFB Access to CPU" and when it's checked, that means that the EFB cannot be accessed by the CPU, meaning that some features in some games won't work, especially when the CPU is accessing various data from the GPU, I guess? Someone who programs on dolphin could probably give a more technical answer.
tl;dr - Skip EFB Access to CPU is a hack and breaks things.
Hmm...I see, is this required for this game as it is suggested in the wiki compatibility rating since it says "efb access Is required" Or should I ignore? Just curious how other people are able to play with this feature on.
EFB Access being required = unchecked. It's just horrible wording + awkward positioning.
Hey guys. I have a few questions.
First, Im having a sort of stuttering issue with SMG2 and I dont know where its coming from. Im using the latest dev build 4.0 - 1386 and before now I ran the game pretty wonderfully. Even had SweetFX and a few other settings turned all the way up. Now the game doesnt really want to respond the same way. I stutter when I load into the game and theres some really bad sound issues when Im playing. Im using LLE, 3xNative, EFB Copies > Texture, No AA, and Per-Pixel lighting but thats it alongside SweetFX.
Also - should I just be using 4.0.2? I started using the dev builds when I was playing Wind Waker to deal with the heat effect problem and also see that issues are always being solved. I currently only have New Super Mario Bros. Wii, Monster Hunter Tri, and Super Mario Galaxy 2. Would it be better to run the stable version? And would using 4.0.2 stop SweetFX from crashing dolphin every other time?
Edit: Im also using the Direct3D backend and XAudio2.
Edit 2: Im also having an issue where some enemies or objects are dark or flash dark or light. Its weird. Any idea what the issue is?
The GPU requirements have gone up since 4.0-1192; I think your problem is that the GPU is getting maxed out, but I can't be sure. Try lowering the internal resolution to see if it helps.
Also, you're not having sound issues, it's correct emulation for sound to slowdown if the game slows down. We just go with the lowest latency route of letting the sound be choppy instead of masking or stretching it currently.
Mario Galaxy 2 + Wind Waker now work properly (well, Galaxy 2 still has some volume issues + and all Zelda HLE games have missing reverb) on DSP HLE on latest builds, so you could try that for a speedup as well.
So, wait, are you telling me I should be using the dev builds? And this is my system:
CPU: i5 2500k @ 4.2GHz
GPU: EVGA GTX 570 Classified
RAM: 8GB DDR3
Ill try a lower IR. Any idea why Dolphin crashes so much for me? I just installed 4.0.2 and it still crashes even without SweetFX installed.
The newer NVIDIA drivers are buggy; try using 332 drivers.
Ah alright. I had a feeling that it was the nVidia drivers. The last time I tried to downgrade things didnt turn out well but they are releasing the new DirectX 11 wonder driver soon enough. Hopefully that provides a better time.
(08-22-2013, 01:04 PM)Shonumi Wrote: [ -> ]DSP on Dedicated Thread (formerly called LLE on Thread) is known to cause freezing in games that use the Zelda ucode (LoZ:WW, LoZ:TP, Mario Kart: Double Dash, Super Mario Sunshine, SMG1&2, and a handful of others) when using LLE audio. This is most likely due to how Nintendo made the ucode, and how Dolphin emulates the DSP on a separate thread (syncing issue maybe).
So... now that Zelda ucode HLE has been fixed for the most critical parts and just recently the LLE on separate thread -option was improved (Fixed by 4.0-1413) (HLE might not have anything to do with this, or has it?), does this LLE on Thread option still cause freezes in SMG1/2 or other Zelda ucode games?
I have not tested the option at all because of those problems. But someone with some experience with those freezes (frequency? game locations? other settings?? or have they been totally random???), this might be a suitable stage to verify if the problem still exists.
And please correct me, if these recent improvements have no effect whatsoever on the main problem that causes these freezes etc.
Overall, tremendous progress lately with the overall compatibility AND performance!
(04-13-2014, 04:18 PM)bonelatch Wrote: [ -> ]So, wait, are you telling me I should be using the dev builds? And this is my system:
CPU: i5 2500k @ 4.2GHz
GPU: EVGA GTX 570 Classified
RAM: 8GB DDR3
Ill try a lower IR. Any idea why Dolphin crashes so much for me? I just installed 4.0.2 and it still crashes even without SweetFX installed.
Another thing to consider, if your overclock is not stable then Dolphin will easily crash first before entire system.