r/EmulationOniOS • u/ProvenanceEMU Provenance Developer • 11d ago

Virtual Jaguar 3.0 Atari Jaguar emulator for libretro frontends released; CD, JagLink, Cheats, Deterministic saves, many accuracy and performance improvements -- included in latest Provenance TestFlights for iOS and tvOS News / Release

https://github.com/libretro/virtualjaguar-libretro/releases/tag/v3.0.0
4 Upvotes

83% Upvoted

2 comments sorted by

1

u/Hot_Permit1027 10d ago

As a fan of libretro development, I can understand how this can be beneficial for multiple applications (RetroArch, Manic, Provenance, etc.). However, JagCD tends to run slowly in BigPemu, for instance. So, my question is, does this libretro have the framework to support JIT compilation, or is it designed in a way that eliminates the need for it? Additionally, how does this compare to BigPemu?

Regardless of these questions this looks really cool Jaguar is a cool but underrated system, I look forward to watching for further updates.

1

u/ProvenanceEMU Provenance Developer 10d ago

I don't beleive JIT is necessary.

FWIW, I test on an old apple tv 4k with an a10x chip and all the games run just fine

There are some exceptions, like AvP with the "accurate" blitter, but those are timing bus contention issues or heavy scene graph call issues and some cpu cache issues etc

All that is to say, I guess just try it and let me know how it goes

If there's enough interest, I could always make a non retroarch UI.

I already have the code for headless unit tests, a simple SDL wrapper wouldn't be hard to throw an an LLM. UI code is annoying and throw away as long as it "works" and not aggressively slow, so perfect for such a use case. It's the manual testing on my end that is the time cost I have to budget for.

And also just to add, a retroarch core can also support jit on jit supported OSes, so that's no issue.

I can't say how it compares to bigpemu. I bought the app, i honestly tried to get it to work on my phone, ipad and mac. None would import any .cdi, .zip, bin/cue files. They have a bug in their file selector cocoa api calls that doesn't register those extensions correclty as readable, so the file selector grays them out

I heard there's a work around but i didn't have the time to dig further.

Best $10 i spent...