Jump to content
reznnate

IrataJaguar -- new, AWESOME Atari Jaguar emulator

Recommended Posts

From the same author of Real3DOPlayer

Fastest and most compatible Jaguar emulator I've seen.   Not bad for an initial release....

https://play.google.com/store/apps/details?id=ru.vastness.altmer.iratajaguar&rdid=ru.vastness.altmer.iratajaguar

Nearly all games run well on my Shield...   See the compatibility matrix:
http://www.arts-union.ru/node/66

 

It's $9 but worth it.     There is no launch-intent yet, he's aware we want the feature and has said he'll try to add it in the future.

  • Upvote 2

Share this post


Link to post
Share on other sites

Making some test yesterday,

Atari Karts, Power Drive, Zool 2 and Rayman

Let"s do the math !

 

Share this post


Link to post
Share on other sites

Great news..  Developer sent me a quick preview build today that addresses multi-threading of the gpu and dsp.   Tempest 2000 now runs at full frame-rate and doesn't have the audio crackles featured in your video.   I  expect him to post it soon.   

Share this post


Link to post
Share on other sites
Does rl support this emulator yet


Ptetty sure this is a android only emu atm.

Sent from my SM-G920V using Tapatalk

  • Upvote 1

Share this post


Link to post
Share on other sites


Ptetty sure this is a android only emu atm.

Sent from my SM-G920V using Tapatalk



There is a PC version too.

Android 'launch intent" is being worked on and probably a few weeks away (hopefully). 3do emu will get it too.

Sent from my Nexus 6P using Tapatalk

  • Upvote 1

Share this post


Link to post
Share on other sites
53 minutes ago, dougan78 said:

Ptetty sure this is a android only emu atm.

It's on Windows in Phoenix, it's just not a separate package like it is in Android.

Share this post


Link to post
Share on other sites
It's on Windows in Phoenix, it's just not a separate package like it is in Android.

Thanks when I looked at the site it seemed android only, will check it out.

Sent from my SM-G920V using Tapatalk

Share this post


Link to post
Share on other sites
New tests : 
 


With the latest emu build, you want to toggle both gpu and dsp in separate threads.

Gui bug makes it impossible to enter settings after populating rom list. You may need a mouse to enter settings. Or just clear data in OS app settings and redo settings.

Sent from my Nexus 6P using Tapatalk

Share this post


Link to post
Share on other sites

Yes Rez, i noticed that bug.

I have downloaded the last version on google play.

How can i toggle both gpu and dsp in separate threads ?

Share this post


Link to post
Share on other sites

In emu settings gui, toggle the two buttons that out dsp and gpu in separate threads.

Sent from my Nexus 6P using Tapatalk

Share this post


Link to post
Share on other sites

I made some new test on iratajaguar with  the option dsp and gpu in separate threads on.

 

Share this post


Link to post
Share on other sites

For next video, if you aren't speaking, turn off the microphone in Shield shadow play settings.

Developer mentioned that threaded mode can impact compatibility in certain games. So he is working on additional optimizations that should make single cpu mode faster.
 

Share this post


Link to post
Share on other sites

He added launch intent!   

exe=ru.vastness.altmer.iratajaguar/ru.vastness.altmer.iratajaguar.MainActivity
parameters=rom

  • Upvote 1

Share this post


Link to post
Share on other sites
5 hours ago, reznnate said:

He added launch intent!   

exe=ru.vastness.altmer.iratajaguar/ru.vastness.altmer.iratajaguar.MainActivity
parameters=rom

Tried it and it takes me to the games folder, it does not launch a game straight through hyperspin, any ideas?

Share this post


Link to post
Share on other sites

Sorted it out eventually, uninstalled the emulator and reinstalled it and this did the trick, now working perfectly!

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Similar Content

    • By Wandurlust
      Hi all, It seems retroarch (at least on android) has removed their Mupen64plus core and replaced it with Mupen64plus-next. My hyperspin (Nvidia shield) won't launch N64 games anymore because it's trying to launch a core that no longer exist. I have tried editing my "Nintendo 64.ini" file with multiple variations to get the new core to launch, but I cannot get it to work. Anyone know the new core parameters off hand? I've searched quite a bit and am coming up empty.  Just to clarify I'm looking for the "Parameters =" line under the exe= that determines which core retro arch will use. I have confirmed manually loading the "Mupen64Plus-Next" core works with content. I just can't seem to get the command line correct to have it launch from hyperspin. Any help is appreciated thanks! I have already switched to it launching "Mupen64 FZ" in the meantime, but I prefer the launch coming from retroarch because FZ resumes mid-game where you left off when starting from hyperspin, and I prefer the WOW factor of games loading from the title screen.
    • By Honosuseri
      I realise there is already a thread for the Commodore Amiga in the Android section. I should know, as of late I've essentially taken it over! It's one of the most viewed threads in the Android section, so clearly many of you adore the Amiga as much as I do. 
      That thread has become quite long and it's quite confusing with people choosing to emulate the Amiga in different ways. I decided it would be best to start my own thread, streamlining it to show the best way to get this done. As I do have a "proof of concept" setup working! 
      This project I've taken on is a mammoth undertaking, as the Amiga is quite a complicated system to do. I'll try to explain why and how I've decided to proceed, keeping you guys up to speed with my progress here. 
      The first real issue is the naming that Hyperspin has been using for some time now. It's based from the Whdload zip file names, which was a logical choice BUT the problem is these zip names keep changing over time as they get updated. This throws the database entries and all media assets out of whack. It's my belief that this naming is what is really holding us back doing the Amiga justice.
      Second problem for us Android users anyway, is that we can't use the zip files directly with an emulator. They needed to be extracted out and we used a bootloader to patch the files for the emulator and launch the games. All seemed well and good until I started testing games and found many wouldn't work. Very confusing as the same game files worked fine from a workbench environment I'd set up, with it's own bootloader I added in. I suspected it was the "ultimate amiga" bootloader for the Hyperspin wheel at fault, which proved to be correct. 
      So the best way to launch these Amiga games from the Hyperspin wheel, is to actually use HDF versions of the games. This removes the need for the bootloader. I decided to keep the game folders extracted from the whdload zip files. Continuing to use these with the workbench (Amiga's OS) hdf I created. Having this is a nice nostalgic nod, I'm sure genuine Amiga fans will appreciate. 
      Unfortunately we can't just point the emulator to these hdf files, it's not that simple. Each game requires a config file that points to where the particular hdf game file is, what kick-start (i.e Bios) to use, video settings, control bindings etc. These files are known as uae files, as that is the extension we tell Hyperspin to look for. We trick it into thinking these uae's are the actual "game Roms".
      Sadly uae files aren't universal between emulators. So choosing the right emulator to begin with is important. Many people had chosen to use RetroArch. Which can't do the CD32, so I'll strike it off for that reason alone (although there are other reasons). I spent a long time waiting on Amiberry to be ported to Android but the devs haven't delivered. I'm not waiting any longer, so I'm continuing to proceed with Uae4arm. 
      As I write this, the latest version of Uae4arm crashes on Android TV (i.e Shield TV) but does run fine on Android phones. The devs are aware and trying to resolve this. There is an older apk version we can install for now, which does work. Another slight annoyance is that Uae4arm is quite fussy about how the uae files are named. They can NOT have special characters in them (e.g a space) or the emulator won't launch them!
      My next complaint was that Hyperspin has "rules" about what games should be included in the xml database file. I do NOT agree with these "guidelines". I want a definitive collection of Amiga games. 
      I've decided to branch the Amiga out into different wheels, ECS, AGA and CD32. As an analogy think of Sega's Megadrive and it's hardware addons. Megadrive=ECS, Sega32X=AGA (better graphics chipset on later Amigas) and finally the MegaCD=CD32 (better audio track and FMV).
      There is a "HDF game set" floating around. However... I got to know the creator, from doing videos on my proof of concept setup. I've persuaded him to rename the files to something more sensible, that should help other frontends scrape for metadata and artwork. These names will not change over time as he updates the collection. He does release notes, so this info can be used to keep the xml database file up to date. Currently he's overhauling the hdf files so they take up less storage and even adding cheat and trainer options to the loading splash screen....very cool stuff!
      I'm working on creating missing artwork (wheel, 3D box, diskette and video snaps), keeping busy until this new hdf collection is complete. Then I can start creating the uae files needed. This will be laborious, as Uae4arm doesn't do cycle exact emulation. I need to make sure each game is configured correctly to run at the proper speed, I'll also bind commonly needed keyboard keys to the gamepad on a per game basis.
      If you're confused, that's OK! It should all make sense, once I get around to uploading some more videos. Yes I will make my assets available to you all (minus the games obviously due to Hyperspin rules), once I'm happy with the collection.

      ***UAE4ARM BETA APK LINK***

      https://mega.nz/#!TYMQQKob!9pzwooQbkxVd-__mwmqtFWNF9JSR7D7rEgY8tqu31Vg
       
    • By Honosuseri
      Retroarch (Google Play) has updated itself to the latest version 1.7.8 and it seems to have broken compatibility with Hyperspin 😕

      Having done some quick reading (https://www.libretro.com/index.php/retroarch-1-7-8-important-changes-for-people-using-the-google-play-build/) it seems under the "infinite wisdom" of Google. They're forced to build in both 32 and 64bit support for the app, so the device (Shield TV) will default to using the 64bit version as it is a 64bit device. I'm not entirely sure what's gone wrong as I haven't had time to delve further into it, although I know ZeroJay did a modded Hyperspin apk for 64bit support (that doesn't work either). Just wanted to warn users so they don't update and have any aggro.

      You can still side load 32bit versions of Retroarch, I'll do that later and test. I'm actually quite excited about some of the features that have now come in the latest version.

      ***EDIT***

      The retroarch_ra32.apk (v1.7.8) changes the path (typical). So it's now "exe=com.retroarch32/com.retroarch.browser.retroactivity.RetroActivityFuture". Hyperspin doesn't like this and it misbehaves as it did trying to load the original 64bit Google play version, which is why ZeroJay did the modified Hyperspin apk.
       
×
×
  • Create New...