I never used cheat before but I will try.
Edit2:Oops forgot to say something. Thank You!
Sorry,I am a little late,I can try the builds,but it will make me uninstall since the signature is different,but oh well.
Not done yet and barely started,but dayum,build 9095 is FAST! Full 60fps Metal Heavy Fast Brawl Bowser Jigglypuff on custom stage.
Such a shame cheats don't work in that build.
Edit: The pinpoint where it stopped working is
9090 with
9089 as the last version cheats worked on.
I just knew it would come down to a faster one being the one where cheats stopped working.
But I wanszs dah speed!
7b017c6 - JitArm64: Use a register as PC argument for the dispatcher.
What would cause that to break cheats?!?
Should I try the few other builds 9091,9092,and 9093?
trying build 9105 right now under Marshmallow.
I can defenitely say that its slower than when I had Lollipop.
Menus in Zelda TP go like 8-10fps, ingame overall is about 15-20 of 30fps.
So I'm barely able to reach fullspeed at all.
is the optimized JITARM64 build worth a shot maybe? I'm not sure if there is a newer version with the Android M workaround enabled.
(03-10-2016, 04:20 PM)nex86 Wrote: [ -> ]trying build 9105 right now under Marshmallow.
I can defenitely say that its slower than when I had Lollipop.
Menus in Zelda TP go like 8-10fps, ingame overall is about 15-20 of 30fps.
So I'm barely able to reach fullspeed at all.
is the optimized JITARM64 build worth a shot maybe? I'm not sure if there is a newer version with the Android M workaround enabled.
I'm in the same situation mate, and no there isn't a newer optimized build available as far as I know. Make sure you back up your ini files if your playing around with the new builds. The controller config menus are not working yet and if you go in there inadvertently its possible to delete all your controller bindings. You then have to revert to an older apk before you can put them back in. Found that out the hard way yesterday lol
I made a little gameplay video of Beyond good and Evil running with an underclock of 30
https://www.youtube.com/watch?v=6ExgIhGMTRA
Can't seem to force it into widescreen though, and I know it can run in widescreen on the PC version of Dolphin
Make a GameSettings folder and create a new file as an ini with the game ID,you can see the ID on the matching shader file.
The setting I have inside a Brawl/RSBE01 ini file.
[Wii]
Widescreen = True
As yours is a Gamecube game,it will need that equivalent part instead,but is it [Gamecube] or what?
(03-11-2016, 01:39 PM)retroben Wrote: [ -> ][Wii]
Widescreen = True
As yours is a Gamecube game,it will need that equivalent part instead,but is it [Gamecube] or what?
That setting doesn't exist for GameCube games. You will have to do something else, like forcing a stretched aspect ratio or enabling the widescreen hack.
(03-11-2016, 06:26 PM)JosJuice Wrote: [ -> ]That setting doesn't exist for GameCube games. You will have to do something else, like forcing a stretched aspect ratio or enabling the widescreen hack.
Thanks but I can't see an option to do that in the settings.
I have however looked in the desktop ini files and I can see a setting called "wideScreenHack" so I'll try enabling that in the android GFX.ini file
Its just strange because on the desktop version with the aspect ration set to auto and the wideScreenHack set to false the game defaults to widescreen.
OK I've worked it out, I think.
I had to edit the GFX.ini file to add the following line.
[Settings]
AspectRatio = 1
Thats the same as in the desktop ini.
If you set it from within the android app it puts the setting under
[Hacks]
AspectRatio = 1
and that doesn't seem to work for some reason.
Sounds like a bug. Can you file that on the tracker?