It's fast enough that the incomplete JIT core is now the limiting factor in almost all games.
(07-16-2013, 06:25 PM)Sonicadvance1 Wrote: [ -> ]It's fast enough that the incomplete JIT core is now the limiting factor in almost all games.
Forgive my ignorance, but does that mean that the bottleneck at this point with Open GL ES 3 enabled is now CPU? And optimisation obvioulsy?
The bottleneck is the lack of implementation of the CPU emulation core.
Once that is completed, the bottleneck will be the CPU itself.
Are you still running / developing this on your chromebook?
I am yet to get OpenGL ES running on chrubuntu.
Running automatic platform detection
Using EGL Native Display Platform: x11
libEGL warning: failed to create a pipe screen for armsoc
libEGL warning: DRI2: failed to open armsoc (search paths /usr/lib/arm-linux-gnueabihf/dri:${ORIGIN}/dri:/usr/lib/dri)
Chrubuntu doesn't have hardware acceleration on the ARM chromebook. I haven't run dolphin on it for quite a while. This is mostly due to the fact that the ARM chromebook still doesnt have OpenGL ES 3 drivers despite being out for nine months. I do know our EGL backend is broken in Unix as well. Mostly just been testing on the Galaxy S4
SonicAdvance1, can you elaborate why GLES 2 isn't supported? What crucial features are missing?
It isn't completely unsupported depending on how you look at it, if/when sonicadvanced gets a nVidia shield (or any tegra 4?) he'll add support for that afaik and that only supports GLES2, but I'd guess it also supports some extra extensions.
OpenGL ES 3 will be supported by default on new 4.3 JB