(07-26-2017, 03:06 AM)Admentus Wrote: [ -> ]I don't think Dolphin is meant to be used on a Android phone to play GameCube and Wii games for the foreseeable future as you might hope it should. Perhaps lightweight games or for experimentation. Perhaps in 10 years time from now. Still, underclocking can cause a lot of issues. So the question is what you rather have: a lot of issues but decent FPS or perfect-compatibility with lower speeds. I know what I want. Higher FPS can always be gained by upgrading your hardware. Faster and better hardware is being released with each year. Issues are only resolved through improving upon Dolphin itself.
There is no need for removing underclocking as far as I care. The reason lies more with fewer people complaining about why Dolphin is having issues. Each time someone states that underclocking improves your experience I just slam my forehead into my wall.
I don't think upgrading your hardware will help for smartphones. They have so much catching up to do in terms of performance that we'll probably never see a phone that can handle Dolphin without speedhacks like underclocking. Even if all that plays on Android are lightweight games like Pokemon Colosseum or Smash Bros Melee, I'd rather have those work with underclocking than not be playable at all.
That said, perhaps you could prompt users with a warning box saying that it will break their game. I know it says so down below already, but clearly no one's stopping to read it.
(07-26-2017, 04:40 AM)Guilherme Wrote: [ -> ]Overclocking feature can be useful if you don't reduce too much, 22% of clock is crazzy, depending on the game you'll have a bad experience, for games that use the max of console CPU, theorically half clock should give about half FPS, so 20% of clock should give 20% of FPS,which is crazzy, 20% of 30 FPS is 6 FPS.
This feature also helps me when I have low framerate in some games I tested here, to get full speed I must overclock the CPU to 150%, I don't know why, it's not a hardware problem as when I overclock the internal CPU (that should makes the emulator heavier to my system) makes the game run better.
Depends on the game but some games that have variable framerates, and some that don't, just do not hit a consistant framerate on physical hardware. Either the developers were too ambitious or used some poor coding, but not every GC and Wii game runs at a solid locked high framerate at stock internal clock speeds.
(07-26-2017, 07:52 AM)TKSilver Wrote: [ -> ]Depends on the game but some games that have variable framerates, and some that don't, just do not hit a consistant framerate on physical hardware. Either the developers were too ambitious or used some poor coding, but not every GC and Wii game runs at a solid locked high framerate at stock internal clock speeds.
I understand that some games will not run at full speed all the time, a 30 FPS game drop to 28 FPS or even 25 FPS for a while is normal, but I'm talking about a drop from 30 to 20, and not just for a while, drops from 60 to 35-40, it's not good for the gameplay.
I don't have played much of Dolphin, but it's one of the best emulators I've used, one the things I like is that the emulator shows the actual FPS, PCSX2 shows 60 FPS, but I know many PS2 games run at 30 FPS. Sometimes we use a lot of hacks to improve the emulation speed, we can feel that the FPS is lower, but it still shows 60 anyway. The graphic emulation is good, if we use a high resolution it looks like a native PC game, the PCSX2 graphics are blurry even on high resolution, maybe due to the complex hardware hard to emulate.
Well, since you can build a system that can handle almost any game you can throw at Dolphin at 1x internal resolution with just a mildly overclocked Pentium G3258 and its iGPU on stock cooler with a LGA1150-based motherboard (which is an old CPU/platform nowadays, also even more cheap than it already had been on launch), I don't think it's even worth trying emulated CPU underclocking on PC. On the smartphones however, it *MIGHT* be useful to debug something, but not for playing games, that's sure...