Hi all!!I have some problem with this VBA Next emulator.My phone is Nexus 4 and running 60Hz refresh rate but it seem that my fps in game only have around 50 something only which make the game laggy.Any solution??(didnt have problem when using SNEX9X Next emulator only have problem in VBA Next emulator)
Surprisingly enough, it may be a simple matter of not enough CPU horsepower. Even with a fancy new phone, VBA Next is borderline. I believe an iPad 3+ is required to top 60 fps and even that is close.
Correction - you need an iPad 4 for fullspeed VBA Next emulation. The Apple A5x inside the iPad 3 is just too weak to do it.
A GBA CPU interpreter is going to be slow, sorry. An iPad 4 has at least a +25fps advantage over a PS3 - so it can run even the most demanding GBA games (Final Fantasy 5/6) at fullspeed with VBA whereas a PS3 cannot (56/55fps or so).
Anyway, the only reason things like gba4iphone (or whatever it’s called) is fast is because these are all rebranded versions of gpSP - Exophase’s GBA emu with the ARM dynarec. And really, gpSP - while being a lot faster obviously due to this - will never be as accurate as VBA for this very same reason. Also, it will never be able to run on a non-jailbroken iOS device or a non-jailbroken Windows RT/Phone device since they simply don’t allow for code generation at runtime.
So really, there is a reason why we are bundling in CPU interpreter versions of emus with our mobile RetroArch packs - so that at least there is an option to use these cores on systems that don’t allow dynarecs for security reasons. And it is pretty much unavoidable that going with CPU interpreters instead of dynarecs will require at least 2x or 4x the CPU requirements - that is a simple basic fact of life.
Anyway - a gpSP libretro port is still in the offing. For now, VBA Next is the only choice on ARM devices with libretro.
Perhaps emu developers are really going to have to start seriously considering a future where dynarecs will simply not be an option and perhaps pursue a different strategy - whether that is through strategically placed speedhacks or some other hack, I dunno. ARM64 with TrustZone extensions is going to introduce a lot of pitfalls for dynarecs to be able to keep executing in native code (on Android), so it’s obvious that the window of opportunity on dynarecs is closing, and it’s closing fast with these mobile platforms. And who knows if it will stop with the mobile platforms either and whether MS will not be wanting to impose the same restrictions in a future Windows OS upgrade (since Windows RT is their platform as well - where they disallow JITs/dynarecs from being able to function).
So nothing can do to overcome the problem??because i cant play game with laggy screen
thx for the information