Dolphin, the GameCube and Wii emulator - Forums

isn't it that you have to keep pausing and resuming the game when its suddenly getting slower for no reason otherwise it crashes?
I'm pretty sure that has something to do with how the cpu power managment is handled OR a memory overflow that it fills up cache or memory with more than it can hold.

I wonder if the issues for this phone will eventually be fixed. It doesn't affect me personally but I'm interested to see how well it could perform without the current issues it has. I think next year phones will finally be good enough to play dolphin properly, but I guess it still comes down to the video drivers. Maybe I'm a bit optimistic though, especially when my expectations are pretty much baseless.

(04-11-2016, 04:31 AM)Grey1213 Wrote: [ -> ]I wonder if the issues for this phone will eventually be fixed. It doesn't affect me personally but I'm interested to see how well it could perform without the current issues it has. I think next year phones will finally be good enough to play dolphin properly, but I guess it still comes down to the video drivers. Maybe I'm a bit optimistic though, especially when my expectations are pretty much baseless.

It could happen tomorrow or in 5 years from now, we reached a moment when hardware isn't that important, drivers are. Dolphin is moving forward, once there'll be mainline ES 3.2 and Vulkan drivers we'll see how it stands but for now it's pretty hard to predict anything, I mean unpredictably hard. Even Snapdragon 820 appears to have some issues, why would you think Snapdragon 920 won't have them? I'm running Dolphin on Snapdragon since driver v14, I still remember v53 bugs and v84 bugs and regressions, now it's v154 (S7/G5) they always messed up something so you start thinking of Nvidia as of gods from the Olympus.

Just tried Twilight Princess on my S7 (exynos version) again, opening works with fullspeed if I keep tabbing out and back in but I can't make it past the menu until it crashes again.
There is defenitely some potential here performance wise since I'm almost getting the same fps as on my Shield TV in the opening scene.
I just hope that the crashes are getting fixed soon.

(04-11-2016, 11:06 AM)nex86 Wrote: [ -> ]Just tried Twilight Princess on my S7 (exynos version) again, opening works with fullspeed if I keep tabbing out and back in but I can't make it past the menu until it crashes again.
There is defenitely some potential here performance wise since I'm almost getting the same fps as on my Shield TV in the opening scene.
I just hope that the crashes are getting fixed soon.

twilight princes is also unplayable in shield tv when you arrived to faron wood 7 fps or worse hyrule field.

exynos can not match the X1 nvidia, so it would work even worse in that part

(04-11-2016, 12:13 PM)brujo5 Wrote: [ -> ]twilight princes is also unplayable in shield tv when you arrived to faron wood 7 fps or worse hyrule field.

exynos can not match the X1 nvidia, so it would work even worse in that part

Just copy the GameSettings directory from your desktop to your device, and enable the ZTP speedhack. So this game should run much better

(04-11-2016, 07:55 PM)degasus Wrote: [ -> ]Just copy the GameSettings directory from your desktop to your device, and enable the ZTP speedhack. So this game should run much better

Ahhh before only 2fps after applying the patch up to 18fps in faron woods. Thank you!!!!





Another question for paper mario game: Is the new bbox emulation supported in Mali t760?

Can someone be so kind enough to post the text needed for the better fps pretty please?

After a lot of stuff,I evnetually found the actual code itself and enabled it with the OnFrame code type it was.
It looks like the wiki picture with the map border gone.
I really want this "proper" version of the fix with Faron running 16fps faster.
I have played up to the inside of the Zora temple with brutally slow fps on the wagon escort part prior to it.

I would sacrifice the map for a chunk of fps any day.
Hint: You can hide the map by pressing d-pad left,but that doesn't fix performance without the speed hack.

At the PPSSPP forums I discussed why the emulator was working in RetroArch's PPSSPP Core, while the official PPSSPP app don't. Unknown thought it had to do with RetroArch's core being 32bit and newer PPSSPP builds being 64bit. Maybe it's the same problem with Dolphin, might be worth looking into.

yea the pppsspp issue as been resolved by using the 32bit recompiler. its still fast enough for most PSP games.
I'm guessing there still is no fix for the 64bit recompiler of dolphin?