There isn't much talk about this game or it's sequel, but Conduit in particular gives my system the flux, and it has only gotten slower with newer dolphin builds. The actual wii game has auto frameskip that doesn't seem to work properly in the emulator, instead the gameplay slows down with the framerate. Anyway, this game actually works properly framerate wise on a really old build of dolphin, one of the old multithreaded fifo attempts, r4937 (which I found on a old build database a while back).
The only conditions are that the debug menu must be initiated. Google will provide the know-how. Once you have your image ready with debug, set dx9 renderer to efb ram, not texture. This actually forces the emulator to become gpu limited (the speed will change depending on the options you set in debug). Now, in the conduit debug menu, turn on depth of field. The framerate will lock at twenty but the game speed will be full. Basically, this old build compensates for slow gpu render thread by skipping frames to keep up with cpu thread, something I've seen others post about before. The Conduit has pc-like settings in debug that actually swamp the gpu thread and change how the emulator functions. This doesn't work on any other build I've ever tested. Also, in debug menu, turn off "blur on reload". That setting forces depth of field off and turns off the frame skip.
This probably works for conduit 2 (it has the same debug menu I think), and any other game that is severly gpu limited in the render thread. Note that changing settings in the dx9 plugin won't work to swamp the gpu thread. It has to be the game doing it. I'm sure nobody cares about these old builds, but at least for conduit, a really hard game to emulate, it works wonders. I don't know the tech or why this build compensates like this in efb ram, but i'm glad it does.
Jay
The only conditions are that the debug menu must be initiated. Google will provide the know-how. Once you have your image ready with debug, set dx9 renderer to efb ram, not texture. This actually forces the emulator to become gpu limited (the speed will change depending on the options you set in debug). Now, in the conduit debug menu, turn on depth of field. The framerate will lock at twenty but the game speed will be full. Basically, this old build compensates for slow gpu render thread by skipping frames to keep up with cpu thread, something I've seen others post about before. The Conduit has pc-like settings in debug that actually swamp the gpu thread and change how the emulator functions. This doesn't work on any other build I've ever tested. Also, in debug menu, turn off "blur on reload". That setting forces depth of field off and turns off the frame skip.
This probably works for conduit 2 (it has the same debug menu I think), and any other game that is severly gpu limited in the render thread. Note that changing settings in the dx9 plugin won't work to swamp the gpu thread. It has to be the game doing it. I'm sure nobody cares about these old builds, but at least for conduit, a really hard game to emulate, it works wonders. I don't know the tech or why this build compensates like this in efb ram, but i'm glad it does.
Jay