Dolphin, the GameCube and Wii emulator - Forums

What "sound glitch." If you're talking about sound lagging when the game lags, then you're wrong; 3.5 is "broken" one in that case. Because if the game isn't going full speed, the sound lagging/slowing down is intended and accurate emulation. (Perhaps there is a better way than stuttering to handle it though?)

Either way, Metroid Prime 3's sound works fine for me; so I'm assuming that it's just the slowdown thing.

I do think 4.0 will be slower than 3.5; 4.0 is more accurate and has tons of new features that 3.5 didn't even care to emulate. I don't think it should be THAT much slower though. Also, I know for a long time Metroid Prime 3/Trilogy had tons of crashing issues, and those issues were fixed between Dolphin 3.5 and Dolphin 4.0. So, pick your poison on that one.

Try swapping graphics settings midgame; Metroid Prime 3 has some settings forced by INI. After the game's running, go to the hacks section and just toggle stuff. Maybe 3.5 didn't have all the correct settings so it's using certain hacks that break the game later, and are changing your results. Either way, 20 fps shouldn't be happening...

(03-05-2014, 01:40 AM)JMC47 Wrote: [ -> ]What "sound glitch." If you're talking about sound lagging when the game lags, then you're wrong; 3.5 is "broken" one in that case. Because if the game isn't going full speed, the sound lagging/slowing down is intended and accurate emulation. (Perhaps there is a better way than stuttering to handle it though?)

Either way, Metroid Prime 3's sound works fine for me; so I'm assuming that it's just the slowdown thing.

I do think 4.0 will be slower than 3.5; 4.0 is more accurate and has tons of new features that 3.5 didn't even care to emulate. I don't think it should be THAT much slower though. Also, I know for a long time Metroid Prime 3/Trilogy had tons of crashing issues, and those issues were fixed between Dolphin 3.5 and Dolphin 4.0. So, pick your poison on that one.

Try swapping graphics settings midgame; Metroid Prime 3 has some settings forced by INI. After the game's running, go to the hacks section and just toggle stuff. Maybe 3.5 didn't have all the correct settings so it's using certain hacks that break the game later, and are changing your results. Either way, 20 fps shouldn't be happening...

Sound glitch was more "all games" after Zero broke something. I'll make another thread on that just to get some ideas on what could have happened, because I'm extremely confused as to what it could have been. I mainly added that in because I didn't want to clog up the forums with question threads for simple stuff. As for MP3 I had some sound issues in 3.5, but fixed them by switching from DSound to XAudio2.

In terms of differences between 3.5 and 4.0, I'll do a few more tests over the weekend. I want to figure out which specific revision of Dolphin changed things, so you guys can figure out what might have been causing it. I know when I start up MP3 on 4.0, it logs in with a popup saying options "EFBToTextureEnable" and "SafeTextureCacheColorSamples" are overridden by the game .ini. That might be what's causing the problems, as any attempts to fiddle with the hacks/options doesn't help very much.

Currently at 50-60FPS on 3.5, and sub20FPS on 4.0. Have gotten off the Olympus on 3.5, still no issues outside of slight pop-in ( it seems to be loading the zones as the door is opening, which looks silly, but has caused no real problems yet. ).

Out of curiosity, what visors are broken due to EFB to Textures? On 3.5 the EFB to RAM setting isn't forced through the ini, and I'm able to use the Scan Visor perfectly fine with EFB to Textures. Is it a later Visor that's broken, or is it broken on key things? I'm getting the feeling EFB to RAM might be my undoing here, as it turns most of my games to mush when it's on. I'm using 8 gigs of DDR3, and no game handles EFB to RAM well, so if I had to guess what was the culprit, that'd be it. A few google searches and checking the issue lists only bring up basic Scan Visor issues, which I'm not having in 3.5.

How difficult would it be to modify 4.0.2 to not force EFB to RAM for MP3? I'd be interested in doing some tests to see if the visor issue is still around on my settings, and how playable it is with EFB to Textures enabled. If it is just the Scan Visor that has problems, I could easily swap out and set it to RAM during Scan Visor segments.

You can just edit the INI? Or you can change the settings while it's playing to override it. That's why I suggested opening the graphics menu and changing stuff while it's playing.

(03-05-2014, 02:47 AM)JMC47 Wrote: [ -> ]You can just edit the INI? Or you can change the settings while it's playing to override it. That's why I suggested opening the graphics menu and changing stuff while it's playing.

Ah yeah, now I understand.

So I fiddled with the ini on 4.0. If I set EFB to Textures, the Scanning Visor stops working, like the issues said. However on 3.5 the Scanning Visor works fine with EFB to Textures. Once I get to the weekend, I'll jump around between revisions to see if I can pinpoint which revision the Scanning Visor stopped working on EFB to Textures on. At this point it seems the game is playable for me through 3.5, so I'm not that concerned, but I'm curious what created the issue.

The GameINI forcing EFB to Ram is in 3.5. The scan visor does NOT work with EFB to Texture. I've tried deleting the gameini setting and starting fresh, it doesn't work. The only visor that works in any prime game with EFB to Texture is the Scan visor in Metroid Prime 1. All other visors, including the scan visor, do not work in Prime 2 and Prime 3.

dose anyone no if there is a way to change the brightness..for me it seems to be stuck on 100 and turning it down in the options menu dose nothing.

Brightness? Explain.

let me try to explain better sorry. Im using the Metroid prime trilogy version and i have noticed that the in game brightness level dose not seem to work. for example in metroid prime 1 and 2. the level seems to be set to the darkest were as with metroid prime 3 it visually seems to be stuck at the highest level even though it ses its at 0 in the game menu. trying to adjust the brightness level dose not take effect and trying to restore defaults dose not work either. i have tryd on all backends and same problem. tested on 4.0 and the latest 4.0 1997

guys...how's the trilogy running with u? good

If this is in the wrong place, I apologize. Just looking for game specific help with an error I may have accidentally created for myself.

I might have screwed up my save, I'm not entirely sure. I activated some gecko code.

I'm at Elysia and I had activated some items early, such as the grapple lasso, though I collected it anyways physically in game, just forgot to deactivate.
Well I was rechecking my Gecko and I un clicked the lasso because I thought: hey, don't need this now.

I move onto the spire on my way to destroy the shield on the Elysian Seed, and when I'm in the escape pod I find I'm screwed because I can't open the panel to weld the last panel. I try and recheck the stupid code and it wont work.

I even went all the way back to Norion to try and collect the item again, like maybe I didnt collect it like I thought I did? It wasn't there. Quit game and tried again...nothing.

If anyone can help me, I would really appreciate it. I'm so frustrated, and I don't want to start all over. Wii saves folder won't work...