Jump to content
HyperSync, HyperList and FTP are now back online ×

Archived

This topic is now archived and is closed to further replies.

thatman84

OpenBOR

Recommended Posts

3 hours ago, Honosuseri said:

There's more to life mate lol

tenor.gif

3 hours ago, Honosuseri said:

P.S You can update the OP about 2 player controls now...do your job Mr. Admin man ;)

Done......and careful I have the power now 

Agent-Smith-Evil-Laugh.gif

 

Share this post


Link to post
Share on other sites
19 minutes ago, thatman84 said:

Done......and careful I have the power now 

Not that much power...your Kung Fu is weak! I had to click the links to see the images! :rofl:
international karate plus gif

Share this post


Link to post
Share on other sites
2 minutes ago, Honosuseri said:

Not that much power...your Kung Fu is weak! I had to click the links to see the images! :rofl:

Lol its a better surprise

Anyway I said power not knowledge

Share this post


Link to post
Share on other sites
Just now, thatman84 said:

Lol its a better surprise

Anyway I said power not knowledge

I hate surprises! And knowledge is power ;)

Thanks for the laughs guys. See you around

Share this post


Link to post
Share on other sites
1 minute ago, Bungles said:

Image result

Go on then share the knowledge...im getting into this gif thing now. What with you and diskmach

Share this post


Link to post
Share on other sites

In Chrome for me its Right click the picture and choose copy image, then paste in your message.

tenor.gif

 

Share this post


Link to post
Share on other sites

I just wanted to chime in to mention the way I had open BOR working by mapping player 2 controls to keyboard keys. Here is a link to the thread:

http://www.hyperspin-fe.com/index.php?/topic/26643-Openbor

I ended up using a root method using sixaxis controller. I did manage to get it working with a non root app, I just can't remember exactly what I did.

Formatted my shield shortly after and never messed with it any after that.

So after this...... Mugen?!? ¯\_(ツ)_/¯

Sent from my SM-N950U using Tapatalk

Share this post


Link to post
Share on other sites
20 minutes ago, BiZzAr721 said:

I just wanted to chime in to mention the way I had open BOR working by mapping player 2 controls to keyboard keys. Here is a link to the thread:

http://www.hyperspin-fe.com/index.php?/topic/26643-Openbor

I ended up using a root method using sixaxis controller. I did manage to get it working with a non root app, I just can't remember exactly what I did.

Formatted my shield shortly after and never messed with it any after that.

So after this...... Mugen?!? ¯\_(ツ)_/¯
 

Thank you! Yes I had seen that a while back, however I refuse to root my Shield TV. If I keep it as stock as possible my friends can easily "emulate" (pun intended) what I have done with my box.

I was actually looking into Mugen. I saw Pouteur was starting out on OpenBOR so chimed in to help him out, then Thatman84 took up the mantle to move things along. I was trying to use Exagear to run Windows software on Android to do Mugen BUT the app doesn't seem to be compatible on the Shield TV. Pity as I would have enjoy playing Diablo 2 and a few other PC games on the Shield TV too.

Share this post


Link to post
Share on other sites

Also I know nothing about MUGEN other than being another similar 2D engine 

Google turns up the paintown app as an alternative. Guessing some of the games are converted for it maybe

Share this post


Link to post
Share on other sites

Everything vs Everything is an interesting title from Mugen..

The character selection screen is massive haha.

Image result for everything vs everything mugen

 

Share this post


Link to post
Share on other sites

Hey Guys!

I'm back after a century of hell to drop my info! lol

So i was able to get DOS Mugen  to work with Doxbox Turbo and custom editing the cycles over 100000 to make it playable, but it has weird slowdown issues sometimes.

Also DOS Mugen games are either broken to the sky or extremely hard to find. I only had a few demos running.

But its mugen on android.

I spoke to the Paintown devs a year or so back, they were working on a new version that would let you use 1.0 and pre 1.0 builds of mugen but i haven't seen anything since, and its basically broken on current Android devices.

Share this post


Link to post
Share on other sites

Hey fella's, been a while!   @thatman84 Congrats on the shiny new admin badge!  I've been away from the scene for a while. Just life in general. Read the occasional update on Tapatalk, but after I removed Tapatalk (for creating & signing me up to their forum chatrooms without my consent), I didn't get those updates anymore.    Back in December I got to researching Raspberry Pi and mini console cases, and was impressed with what it was capable of.  Once I got to setting up RetroPie, well, you know how it goes.........

Which brings me back to here.  I have been messing around with OpenBOR on the Raspberry Pi.  (More than one controller is recognized!) The user darknoir created a Command Line Interface to directly load a OpenBOR game (aka mod).  I am not going to get into the whole story of the progress but you can read it over here (tutorial-openbor-the-complete-guide) or here (openbor-6xxx-openbeta-testphase). You will even get some insight as to the resentment thatman felt over on Chrono Crash forums.

With that said, we now have OpenBOR 3400 with CLI &  .pak support (unsupported version - explanations in posts in the links above), as well as the latest (still unsupported, but duly noted) compiled from source, and patched with CLI, and OpenGL support (GL4ES for emulation station).  All mods can be individually loaded from command line.   I believe it may be possible to carry over those patches to the android version, but I'm no expert.

Since we were previously confined to OpenBOR 3400 version, I went through approximately 200 games, seeing which ones worked on OpenBOR v3400. (OpenBOR is very version specific - backwards compatibility is only by chance).  With the latest release, between the two versions nearly every mod is playable.  Darknoir has taking my list a step further by creating a comprehensive list including file size, play status (working, not working, crash logs, and even personal opinions of the game), CRC, aspect ratio, players.     I think OpenBOR compatibility is due for a major overhaul, and along with that, an updated database and appropriate artwork/metadata.

Since the mods are so version specific, we figured an appropriate naming convention would be like this:

GAME NAME [v0.0] [build version]

Example:  Teenage Mutant Ninja Turtles - Shell Shocked [Rev. 5853][v.3.0 Build 4394]

Darknoir had already started creating metadata, logo's, screen shots, boxart, and video's.  Here's a couple box art created by darknoir

1539271884340-streest-of-rage-zombie-ver.2.1-2017-v.3.0-build-4153.jpg.b95135b3065abc62d5649db453e5f58d.jpg:1539271898180-avengers-united-battle-force-ver.2.7.4-v.3.0-build-4432.jpg.ca4cc1f017bafe0d2fec7eece3652e14.jpg1539271875445-street-of-rage-2x-ver.1.4-lite-v.3.0-build-6330.jpg.4dab29fba03f1f634695ef7ef7c8878f.jpg

@Circo I would like to recommend a long overdue overhaul to OpenBOR. I volunteer to take on the task of recording videos to your latest standard.  

@THK @Metalzoic @Rain @relic @KlopjerO @Kondorito @BunglesI also would like to shine the HS Content Creator spotlight in the air to anyone that would be interested. Hyperspin has some of the most talented content creators, and absolutely the most dedicated! Hyperspin, and the talented artists involved created a new era of front end, helping to pave the way for this "retro revolution" we are seeing!  (I entered the arcade scene starting to set up Mame Wah!, when I came across HS beta!)

Thank you!

Here are the games I have personally gone through, which will painstakingly get a proper rename: pastebin - OpenBOR Games List

Share this post


Link to post
Share on other sites

Thanks for your message @BiZzAr721 :)
You only write a mistake, like we can see on your compatibility list, on PI we have two OpenBOR version, one for the old games, 3400 and one of the last build for the newest games the 6315 ;)

My list in development is here : https://docs.google.com/spreadsheets/d/1h2c9Aa_s6rGUejR0AiZgx29byNBWBReW5PK30bZcago/edit?usp=sharing

Like he write, i search for help for this part of my project ...
I know i will do it, i already do it for 3DO, Daphne, PCE-CD, a big part of the NES, JAGUAR, ... but it's long and on OpenBOR there is nothing for help, i must create all the stuff from scratch ?
You can found my mail on GIT, on write me on Google Docs :)

Thanks every one for your work here, some time i have use a part of it and it same me many days of work ❤️
You are one of the best community ever !!!

Share this post


Link to post
Share on other sites

Hi chaps,

its great to see some OpenBOR work going on and fingers crossed someone can update the android app to include the cli launching feature.

I am in between setups right now as lots of DIY on the go.

I had an ask about and it seems the thread below is this communities best offering into OpenBOR games lost setups. It was done in 2014 so not sure how much help it would be.

If you want to get setup over here for projects like artwork and things I would suggest making a thread in the relevant sub forums. There are not many artwork creators about right now but it’s the best way to find them

good luck and please keep us updated if your work completes away from the forum.

Share this post


Link to post
Share on other sites

@thatman84 I will be creating a thread soon in the appropriate sub forum. Just wanted to make an initial post here since my post was all over the map lol   @marxkemp's happens to be what I used in my HS setup an gave me a base to start from. 

Share this post


Link to post
Share on other sites

I finally created an official OpenBOR thread here. I'm hoping there is enough interest to really get the ball rolling. Many users have created media / videos, but they are so scattered throughout the web.

Share this post


Link to post
Share on other sites

  • Similar Content

    • By therourke
      I have a fully working build for Commodore Amiga now on my NVIDEA Shield (2017 model). It took me a good while to get it up and running.

      I thought it might be useful to post an 'all in one place' tutorial. Thanks go to Honosuseri over in this post for convincing me it was possible.
      Commodore Amiga is infamously painful to configure on any and all emulation setups. Retroarch takes the pain out of some of this, since we don't need individual .uae files for every single game now. But there are still some hoops to jump through.
      Onto the tutorial
       
      1. Find/setup your own Hyperspin
      Hyperspin is free and available on this very website. Install the app on your NVIDEA Shield, and compile your roms and Hyperspin setup on an appropriately sized external harddrive/USB.
      As for the ROMs, videos, wheel images and all the aesthetic stuff you need to get your setup running, you will have to source that yourselves. The Hyperspin website is good for some material, emumovies for videos, and Google and Archive dot org for everything in between. 
      For this setup I used a properly named romset for Commodore Amiga in .zip format, but you can also use .lha or .hdf format. .lha is smaller in size, but all of these run pretty much the same on Retroarch now. 
      There is no need for those pesky .uae files anymore!!!!!!!!!!
      Once you have all your roms, you will need to allocate them to the right videos and images and build your .xml database. The info for how to do this is available elsewhere on this very website. I used HyperspinChecker to do this.
      Now, onto the part where we make Hyperspin and Retroarch play nicely so you can finally play your Commodore Amiga games 
      2. WHDLoad and kickrom setup (bios file preparation)
      I obviously can't link to kickroms or WHDload.hdf and some other stuff, but Google is your friend.
      You can get kickroms legally as part of the Amiga Forever app on Google Play Store for only £1.79.
      You ABSOLUTELY NEED to get hold of these EXACT kickroms:
      kick34005.A500 kick37175.A500 kick40063.A600 kick40068.A1200 Some info on kickrom file names and how to match them up correctly can be found here.
      MAKE SURE THE FILENAMES ARE PRECISE! I left one of those As in lowercase and Retroarch didn't like it.
      You also need a properly prepared WHDLoad.hdf file: ADD THESE EXACT KICKROMS TO YOUR WHDload.hdf file (guide to do this here using ADF Opus)
      Copy all these file to the external drive you are keeping your Hyperspin setup on (I made a 'bios' folder in mine for safe keeping).
      3. Retroarch Setup
      Install the latest Retroarch on your NVIDEA Shield (probably works on other Android setups too). You can do this through the Google Play store, but as of writing this, version 1.8.9_GIT definitely works.
      You will need to make sure you have setup a way to load the Retroarch main menu from within games. Go to 'Settings', 'Input', 'Hotkeys' and set the 'Menu Toggle Gamepad Combo' to something like 'Select + Start'.
      Download the latest Commodore - Amiga (P-UAE) core from within Retroarch (use 'Online Updater' menu)
      Now 'Load Core' and choose the P-UAE Core. Start the core, then immediately go back to the Retroarch menu (Start + Select). From the 'Quickmenu' select 'Options'. Change the 'Model' here to something with plenty of power like the 'A1200 (2MB + 8MB)'. Scroll down to 'Global Boot HD' and 'WHDLoad Support' and make sure both of these are marked as 'Files'.
      One other thing from within Retroarch: having a way to 'Quit' from within games is useful for Hyperspin. So go to 'Settings', 'Hotkeys' choose a button for 'Quit Retroarch' (I use the click of my Left Analogue, but anything will do). You may also need to mess around with button mappings, but most of this should work fine if you have a NVIDEA Shield compatible gamepad. Mouse and keyboard are also, obviously, nice additions for Amiga stuff.
      Go back to 'Quick Menu', 'Overrides' and select 'Save Core Overrides' to make sure your Retroarch Amiga setup is saved.
      Lastly, and very importantly...
      Leave Retroarch. You will need an Android directory viewing program like 'FX File Explorer' for this step. Copy the EXACT kickroms listed above and the WHDload.hdf file you created into the /Retroarch/System/ folder on the INTERNAL drive of the NVIDEA Shield.
      4. Commodore Amiga.ini Commands
      In your Hyperspin setup you should now have all your roms, videos, images, menu setup, and a Commodore Amiga.xml database file all neat and tidy.
      You now need to get Hyperspin to talk to Retroarch properly.
      Back on your PC, load your Hyperspin folder and go to the /Settings_Android/ folder.
      Create or open the Commodore Amiga.ini in a text editor. Most of the stuff in here will be the same as other systems, but you can find my ini file attached here.
      Make sure the top lines in your ini read like this:
      [exe info] path=H:\hyperspin\emulators\Commodore Amiga\ rompath=Roms/Commodore Amiga/roms userompath=true exe=com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture romextension=zip,hdf,lha,HDF,ZIP,LHA parameters=cores/puae_libretro_android.so searchsubfolders=false pcgame=false winstate=HIDDEN hyperlaunch=true Each of these lines corresponds to your setup. So if you have your roms folder somewhere else, you need to tell the file. If you are ONLY using .zip versions of your roms, then you don't need the entire 'romextension=zip,hdf,lha,HDF,ZIP,LHA'  line - you can change this to just 'romextension=zip' and it will work fine. (But my line here covers all the possible rom extensions, so you can leave it). The 'exe' and 'parameters' entries are really important, as this tells Hyperspin to load Retroarch, and then Retroarch which core to load for Commodore Amiga.
      Save your file, and hook your Hyperspin external drive back to your NVIDEA Shield.
      5. Play some games
      Everything *should* be working now. If you are having problems with videos and roms matching up, or entries showing in the Amiga menu on your Hyperspin, then that is an issue with your original setup. There are many tutorials out there.
      I can vouch that THIS EXACT setup works great, and loads and plays most Amiga games I have thrown at it without too many glitches.
      6. Now, please answer me a Q 
      When using an external mouse in Retroarch and playing a game like Lemmings, I get TWO cursors - the in game Lemmings cursor, and the NVIDEA Shield arrow.
      Does anyone know how to get rid of this for good? Thanks
      Commodore Amiga.ini
    • By Honosuseri
      Right guys as some of you are aware Google changed how things work on the Google Play Store a while back, when we install an app it will use the 32 or 64 bit version depending on what's native to the device. As we're mainly focused on the Shield TV here on the Android part of the forum, it is a 64 bit device. This has proved to be a bit of an issue for those of us who love Retroarch as there are some serious differences between the 32bit and 64bit versions. In a nutshell currently we have access to more cores for us to play our retro systems on the 32 bit version. RetroArch provide a RetroArch_ra32.apk which is a dedicated 32bit version we can sideload/install and use, however Hyperspin is NOT setup to use this version as some of the paths changed.

      So...I decompiled the Hyperspin.apk and made the necessary changes (yes including the config path) to solely use RA_32. I've done some limited testing with RA_32 (1.8.7) and it seems a okay to me (even the Daphne test core works) however I don't use screen overlays or really bother with alternate config setups (in truth I've not used the STV in many months!). Feel free to download it and test yourselves, obviously backup your essential files AND do remember the .ini files need to be adjusted to use RA32....

      exe=com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture
      becomes
      exe=com.retroarch.ra32/com.retroarch.browser.retroactivity.RetroActivityFuture

      It's easy enough to open all your .ini files with notepad++. Use the Search and replace feature to find com.retroarch/ and replace to com.retroarch.ra32/ do this for all opened files then save all.

      Those who use adopted storage it's wise to move the Retroarch_ra32 app to internal storage after installing AND before running it for the first time. Let me know how it works for you, I'll do a Youtube video to help those less experienced with setting up Hyperspin when I know it's working 100% and I have the free time.

      Mega Link for Hyperspin_0.1.8_Hono.apk (https://mega.nz/file/zQNBCYKI#QVrG4uVVmvXHshl8LbosQi7LAjQmUA09R5k_YqhcMBI)
      RetroArch_ra32 (1.8.8) newest stable version at time of posting (http://buildbot.libretro.com/stable/1.8.8/android/)
    • 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...