Try to measure the CPU temperature during the stuttering. You can use CPU monitor and pull down the upper bar during play to see the temperature. I don't think it's related to this but it's a try.
I played Kirby for Wii at 60 fps without stuttering. I always use 90hz setting. Obviously I guess you tried to modify some emulator options.
Try a different region setting (Pal-Ntsc) or try to redumb your rom.
(11-11-2019, 12:26 AM)Nemesis Wrote: [ -> ]Try to measure the CPU temperature during the stuttering. You can use CPU monitor and pull down the upper bar during play to see the temperature. I don't think it's related to this but it's a try.
I played Kirby for Wii at 60 fps without stuttering. I always use 90hz setting. Obviously I guess you tried to modify some emulator options.
Try a different region setting (Pal-Ntsc) or try to redumb your rom.
Temps are ok, monitoring them right from the beginning of my tests and while Dolphin is (sometimes) not stuttering @ 55° it does so @ 47°, so no throttling here - if the readouts are ok. PPSSPP while running GoW @ 5x int. resolution and 52° runs smooth "forever" ...
I tried many combinations of settings. I'm pretty sure the judder is not (directly) related to any settings, because sometimes I can drive 1-2 laps in Mario Kart with no stutter at all. I don't think I could drive a complete lap without any issues at all if the settings were wrong ?
PAL/NTSC can't be the reason, because I ONLY buy NTSC-games for more than 30 years. Only PAL-games I ever bought are C64 games and that was more than 30 years ago ^^
The stuttering doesn't really look like the typical stutter (like shader-compilation); hard to describe. The gameplay does NOT slow down and sound is still playing 100% correctly; no cracks, no pitch-shifting ... It looks like if there are too many or repeated frames. Really strange.
(11-11-2019, 08:25 AM)Locoviejo Wrote: [ -> ][color=#222222]How do you set it to 90Hz?[/color]
- If you're rooted you can install Auto90 app.
- If you're not rooted, you have to grant permissions via adb ...
Just search for "Auto90" in the playstore. adb-instructions are there, too.
Ok, so I got a OnePlus 7 (non T non Pro - just like the one in the video) and tested several MMJ and official builds @ Android 9 AND 10. It's doing the exact same thing - runs perfectly smooth for a while, begins to judder/ stutter (always at different places in game) and returns to running smoothly, stutter, smoothly ...
So it
seems to be a problem with dolphin itself (?) as no other game or emulator does this - and I have tested MANY.
There are some reports around telling the same story BUT suggest this doesn't happen using a retroarch-core.
The core has other problems and disadvantages of course but it's said to be perfectly smooth all the time.
The problem is, the only still available cores are from ~ september 2019 and up
I can't find any older versions, so I'd still be
EXTREMELY grateful if somebody can help me finding the Android Dolphin RetroArch core version "1d973f4" or one from around march 2019 !
Thanks in advance
... so I finally found the problem and a workaround:
The source of all that really disturbing (!) judder/ stutter is the cache.
As long as the cache-folder is "empty" while playing there is NO stutter at all.
I tested this in splitscreen with a file-explorer, started games, and while the games were running I deleted the .uidcache file in /storage/emulated/0/dolphin-emu/cache/ and the /shaders folder; /GameCovers can stay of course ...
Shader compilation is set to async-skipdraw and compile before starting, so there's not even the slightest lag or stutter right from the start.
I didn't notice any (or more) missing textures than before (when actually using the cache), so it seems the cache is either corrupted or can't be read correctly - It just creates stutter and does not help or work at all.
As soon as the game is running and the cache file+folder is deleted, (I was a bit amazed I was able to delete them while they were in use !?) dolphin does not create a new file or folder and just runs great. Mario Kart (Wii and GC) for example ran several full cups in a row 100% smoothly and stutter free @60fps. Soulcalibur is a nice example, too - perfectly fluid now.
This is a true hassle obviously - you have to do this every time you start a game - I made a little tasker-profile for dolphin taking care of this (yup, that's a BLOODY workaround, but totally worth it)
As I wrote before, I tried MANY old and new builds (MMJ and official) on Android 9 and 10 on Oneplus Snapdragon 855 and 855+ (OP7 and 7T).
Whats wrong here ? Oneplus ? Dolphin ?
Would be really nice if a Dev can comment on this ...
Hi mate, I played a lot of games that run at 30fps on my OnePlus 7TPro and never noticed the problem but today I played Sonic Heroes and I noticed the stutter. The game is rock solid at 60fps but sometimes there is a frame pacing problem.
I found a simple workaround.When the game stutters just use the gesture to watch open apps, then click the game. The game starts to work flawlessly. I played almost an hour without problems. Is seems a problem related to the focused window. Maybe when the emulator tries to write down the cache the game lose its priority. Watching the open apps and clicking on it will restore the focus. Give it a try.
(11-27-2019, 01:29 AM)Nemesis Wrote: [ -> ]I found a simple workaround.When the game stutters just use the gesture to watch open apps, then click the game. The game starts to work flawlessly. I played almost an hour without problems. Is seems a problem related to the focused window. Maybe when the emulator tries to write down the cache the game lose its priority. Watching the open apps and clicking on it will restore the focus. Give it a try.
Thanks for your input but this won't fix my (apparently I'm the only OP7TP user able to "see" this) problem.
This is clearly cache- and not focus related. Again, I can only speak for myself, but I have done nothing special to my device before testing dolphin, so I'm pretty sure other ppl
should have this problem as well - question is, if they really see it or dont care ...
My fix using tasker to clear the dreaded cache invisibly in the background works 100% and doesn't need any additional shenanigans, so I'm totally fine with it - and even saves space
I guess there have to be more ppl to notice this before devs even care to look into this ...