Jump to content
Site is currently back up for stability test, we think we have isolated the issue. If the site starts crashing again we will take it offline to continue repairs ×

zerojay

Platinum Member
  • Content Count

    1,283
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by zerojay

  1. Here's the updated 0.1.8 build: https://zerojay.com/nextcloud/index.php/s/3QfPqYM4A6ymjr4 It gives me problems, likely because my configs aren't in the proper places anymore judging from the changelog for 0.1.8, so my controllers aren't recognized as they used to be, for instance. Once I figure this out for myself, I may move on to trying to update the CONFIGFILE part of the launch intent so that 32 and 64 bit will have their own configurations respected. I can say that MAME-2013-plus seems to play Killer Instinct far smoother on 64-bit than 32-bit.
  2. Hmm, you're right. The version on the store is more up to date than what apkpure gave me. I'll fix this.
  3. A few days ago, I decompiled and edited the Hyperspin APK to allow users to use 32-bit and 64-bit installations of Retroarch together. It's been confirmed working by the community and you can find that edited APK here: https://zerojay.com/nextcloud/index.php/s/3QfPqYM4A6ymjr4 It works as you would have originally expected using a 32-bit or 64-bit version of Retroarch to work, so in your Settings_Android system ini file, change the exe to com.retroarch to use the 32-bit version or change it to com.retroarch.aarch64 to use the 64-bit version. 32-bit Retroarch: exe=com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture 64-bit Retroarch: exe=com.retroarch.aarch64/com.retroarch.browser.retroactivity.RetroActivityFuture Currently, both 32-bit and 64-bit versions of Retroarch will be called using the 32-bit configuration files, however I will likely be updating the APK to allow you to use the 64-bit configs as well for those who may wish to use different settings for both. When that happens, I'll keep both versions of the APK available so that you can decide what you want to use. So now that the community has solved the Retroarch 32-bit problem, it would be really helpful to compile a list of cores and the version of Retroarch that it works best under. In some cases, certain cores currently only function under one or the other, but not both. In some rare cases, cores stopped working like Daphne, so again, these are things that we would like to call out. (By the way, for anything like Daphne where more recent cores no longer work, I can host them for the community if needed. Just let me know (and I do myself still need to get that working Daphne core myself). I'll update the top post here to reflect the community's findings so that people only need to come to one place to find the info they need. --- Core Information ---- atari800 - non-functional on 32-bit due to Android security changes, use 64-bit Retroarch core. mame - Latest version of MAME core only recently started compiling on 32-bit, not available yet on 64-bit. EDIT: Updated link for latest updated build.
  4. Uh, yeah... none of that has ever been true. Lol AAE is very prone to crashing, can't handle most resolutions and is based on ancient MAME code. MAME now is better in every way. Sent from my SM-N920W8 using Tapatalk
  5. You really shouldn't be bothering with AAE anymore.
  6. Version 20140405

    302 downloads

    Nintendo WiiWare - Main Menu (4:3)
  7. Version 1.0

    203 downloads

    Small scripts used for disabling and reenabling Bluetooth when running Taito Type X games to avoid problems caused by having Bluetooth enabled.
  8. Version 1.0

    343 downloads

    Quick and simple database of the few Namco System 22 games.
  9. No releases here will ever include ROMs.
  10. I'm guessing you have the tilt controls mapped for New Super Mario Bros to something on the controller then?
  11. If a game starts up telling you that you need to use the Wiimote in horizontal mode, it most likely will work well on a 360 controller.
  12. When a database cannot be found for a system, HyperSync spits out "Cannot find proper database for system" as an error. The error isn't remotely informative enough because there's no way of knowing *which* system is missing the database in question.
×
×
  • Create New...