Adding to what the other people said, it is crucial that you keep in mind that the purpose of emulating something is for it to resemble as closely as possible what it is trying to emulate. The main idea here is so a pc program is able to run Wii games and applications as accurately as possible (like a Wii would) and it is not so a certain type of pc can run it smoothly, hence the strong recommendation to use the latest build.
I actually got the same thing today after updating where I was stuck at 3fps. Several versions gave me the same thing. After deleting the install directory and clearing out everything in the Docs/Dolphin but save states it is back to 100%.
Edit: Nevermind. After I tried reloading it is back to slow again. Something is up.
On 4.0-2045 both GC and Wii games are slow on OpenGL and D3D
(07-07-2014, 07:24 AM)jsu718 Wrote: [ -> ]I actually got the same thing today after updating where I was stuck at 3fps. Several versions gave me the same thing. After deleting the install directory and clearing out everything in the Docs/Dolphin but save states it is back to 100%.
Edit: Nevermind. After I tried reloading it is back to slow again. Something is up.
On 4.0-2045 both GC and Wii games are slow on OpenGL and D3D
I just registered on these forums to point out the cancerous problem the Dolphin client decided to spit out of it's rotten canal known as it's Config system that would make every fork of ioquake3 shed a tear for every child that died in the holocaust.
Basically no matter what, Dolphin forces Interpreter mode. Even when you set the config to read-only. Even when you deleted everything, or re-installed other versions. Even when you force a local Config, or gave it permissions, or moved, etc.
I have absolutely no idea whats going on, but having to set it back into JIT everytime is not only annoying, but disrupts anyone using Dolphin on a TV. Can you confirm this is the case for you too?
(07-07-2014, 12:48 PM)Mithrot Wrote: [ -> ] (07-07-2014, 07:24 AM)jsu718 Wrote: [ -> ]I actually got the same thing today after updating where I was stuck at 3fps. Several versions gave me the same thing. After deleting the install directory and clearing out everything in the Docs/Dolphin but save states it is back to 100%.
Edit: Nevermind. After I tried reloading it is back to slow again. Something is up.
On 4.0-2045 both GC and Wii games are slow on OpenGL and D3D
I just registered on these forums to point out the cancerous problem the Dolphin client decided to spit out of it's rotten canal known as it's Config system that would make every fork of ioquake3 shed a tear for every child that died in the holocaust.
Basically no matter what, Dolphin forces Interpreter mode. Even when you set the config to read-only. Even when you deleted everything, or re-installed other versions. Even when you force a local Config, or gave it permissions, or moved, etc.
I have absolutely no idea whats going on, but having to set it back into JIT everytime is not only annoying, but disrupts anyone using Dolphin on a TV. Can you confirm this is the case for you too?
Looks like that is exactly what is happening. I just played for about 2 hours to test it, closing the game and opening it didn't trigger it, but closing Dolphin and reopening set it to interpreter. Does it every single time.
(07-07-2014, 12:57 PM)jsu718 Wrote: [ -> ]Looks like that is exactly what is happening. I just played for about 2 hours to test it, closing the game and opening it didn't trigger it, but closing Dolphin and reopening set it to interpreter. Does it every single time.
Its like a super freak mutation of Dolphin AIDs that has the only singular goal of edging it's dolphin-dong into everyone's eye sockets, pissing and reverberating until the victim dies 2 years later in a hospital in debt.
After deleting configs, forcing portable installs, etc I'm beginning to think this may be a registry problem. Dolphin doesn't seem to use hidden files/folders and I can't fathom what kind of black magic the developers used to have the client use a forced setting across multiple multiple installs even when the global config directory is ignored. The one thing I know for sure is that this is a problem that is very recent with the master branches.
Ooookay everyone, let's have a little chat. If you are having a problem with the emulator, or anything in life, and want help from those who made said thing, attacking them is not going to be a very good idea. Congratulations Mithrot, you earned yourself a ban by being a jackass. Everyone, let's try to ignore the troll vomit and keep things civil.
jsu718 and sandrienn, thanks for the report. With some quick investigation, we discovered that the build that caused this was
4.0-2038. delroth did a quick revert, and everything should be fine as of
4.0-2051.
Take that as your occasional reminder that development builds are not stable releases. Sometimes our testing misses bugs (granted, that's partly because our automated testing sucks), and we get into this kind of situation where Dolphin defaults to use the interpreter. If we were confident that our development builds never caused regressions, we wouldn't call them development builds and have a disclaimer on the download page.
It's also partly my fault to have waited before reverting the buggy change, since we were notified of it more than 12h ago. Wanted to wait for an eventual fix but it didn't come. Oh well.