Jump to content

Recommended Posts

This will be the home for OpenBOR discussion .

It will be my side project and next wheel.

i did have a little play a while back but @Honosuseri inspired me to start again fresh.

posted over at the official forum to see if the issues are likely to get some time from the devs

http://www.chronocrash.com/forum/index.php?board=2.0

Current Issues

Written below but better explained in this video.

 

1. Launching "direct to game" from Hyperspin (HS) wheel only supports 1 .pak file in the "PAK" games folder. When you have more than 1 game (.pak) in the "PAK" folder you will arrive at the OpenBOR game select list when launching any game from the HS wheel, then reselect the game you want to launch.

2. Controls are not intuitive and the touchscreen overlay is needed for things like exit. (Controlled by right thumb stick cursor) 

3. Player 2 controls on Shield TV are not recognised as a seperate controller. Therefore broken (needs more testing) May require 3rd party app to reprogram buttons as keyboard keys.

See this tasker profile by @BiZzAr721for changing keyboard see thread linked lower down for more details

 OpenBOR_Keyboard_Select.prf.xml

 

Setup Details

Grab up to date apk's from here

https://github.com/DCurrent/openbor/releases/tag/v4583 

Extract the release build and get the debug-apk from the Android folder.

Games

They all (I think) come as a .pak file and for now should be located on the default an local storage OpenBOR PAK folder.

Below are the details for your Hyperspin OpenBOR.ini settings file

……...............................................................

rompath=/storage/emulated/0/OpenBOR/Paks
exe=org.openbor.engine/org.libsdl.app.SDLActivity
romextension=pak,PAK

....................................................................

Another thread with tasker info from @BiZzAr721 and @badhemi

i will edit this post with setup details as and when I have time. Chip in to get us started as my time is very limited until my wreck of a house is sorted ?

  • Like 3
  • Super Like 1

Share this post


Link to post
Share on other sites

Would you like "my assets" to help you get up and going? I know your time is limited being a family man and having moved house recently.

I can try and make another video to show what's "hinky" with the OpenBOR android port. I did see you linked one of my videos to their forum BUT it wasn't really dedicated about OpenBOR.

P.S It was Pouteur who put up a video about OpenBOR on the Shield K1 which inspired me to discuss it further. He's a great guy but his videos being French probably do limit the audience some what.

Share this post


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

Would you like "my assets" to help you get up and going? I know your time is limited being a family man and having moved house recently.

I can try and make another video to show what's "hinky" with OpenBOR. I did see you linked one of my videos to their forum BUT it wasn't really dedicated about OpenBOR.

P.S It was Pouteur who put up a video about OpenBOR on the Shield K1 which inspired me to discuss it further. He's a great guy but his videos being French probably do limit the audience some what.

Yeah go for it on the assets. Maybe post the "safe" stuff here for now.

I may get a chance friday as out tonight and bolting steel aupports together tomorrow. :(

Yeah the french bit makes it hard for his stuff. Yet to find a youtube subtitles app lol

Share this post


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

Also if you do a vid i can updaye the link

Pouteur was using OpenBOR v3 build 4161(April 28 2015) in his video... I have build 4432 (Jan 25 2017).

Before I do the video, I need to make sure I have the latest version. I didn't compile it myself, I just grabbed a debug apk to download. It would be silly to talk about issues that could have already been resolved on a newer build.
 

  • Like 1

Share this post


Link to post
Share on other sites

Hi Honosuseri, my openbor build worked fine with my shiled k1, but when i use it with my satv,  i have controller issues (pad is ok but buton didn't worked) is your buid ok with the shield controler ?

Share this post


Link to post
Share on other sites

I really want to make wheel with openbor but first i have to get a build that worked fine with the satv

 

Share this post


Link to post
Share on other sites
6 minutes ago, Pouteur said:

Hi Honosuseri, my openbor build worked fine with my shiled k1, but when i use it with my satv,  i have controller issues (pad is ok but buton didn't worked) is your buid ok with the shield controler ?

I replied to your comment on my Youtube video, you must have missed it.

You have a much older build than I have. Yes the Shield TV gamepad works in the build I have (4432). Each game will need the buttons to be set in the game menu first time you play them though. I haven't tested a 2nd controller with this newer build.

It's very close to me wanting to show it off, I have no complaints about performance. Launch intent does not load the game directly, just into the OpenBOR main menu. Also bringing up the touchscreen controls so I can quit back to Hyperspin seem to be a bit hit and miss. 

Share this post


Link to post
Share on other sites

Hi guys, here is the first version of my futur openbor wheel. For now it's on my shield K1, but i will do the same on my satv

 

  • Like 1

Share this post


Link to post
Share on other sites

I cant remember when I got this Main Menu theme from as it was in my early (Collect Everything everywhere stage), but Its pretty nice with the animated background.

OpenBOR.png.60e43f2949defac7a9b29bbb292a13f7.png

There is also 221 Wheels in my folder but not sure if they are of any use.

 

  • Like 2

Share this post


Link to post
Share on other sites

Had a read on their forum this morning, I'm not going to sign up to it to participate in the discussion. I must say you were incredibly polite making your requests and queries. Had it been me inquiring I would feel like I was being "mugged off". I also tried to be polite as possible in the video trying to explain the niggling issues on the Shield TV.  It's not looking promising to be honest...

"This could be tricky. Because OpenBOR in mainly a PC software, which has some ports for sure, but the main version is the Windows one. The idea behind the ports is to be able to play on other systems, and some customizations could be needed, but it should behave as close as it is to the windows version. So if the customizations for Shield TV affects anything on the Android build (affecting its performance), it has a high chance to not be done. And I would support this - the main Android port should be the focus, not some minor and hardware based port."

"You can exit openbor from a gamepad just select quit from the main menu and openbor has always run multiple paks with a list. one day i hope we could have seperate mods on android but for now i cant see that happening."


I guess there is still a glimmer of hope as you've not yet had a reply from White Dragon, who was supposed to be the last guy working on the Android port.

Personally I don't consider the Shield TV to be "minor hardware", it is the most powerful android device/box by a country mile! But we all know that already, don't we? ;) Using Android TV as the OS might well be considered it's Achilles heel though, as it is slightly different from the mobile Android OS.

You can't JUST select quit from the main menu, I spent quite sometime trying to show how borked the controls are on the Shield TV. I've plugged in my 8bitdo FC30 Pro gamepad and the button bindings are actually different to the Shield gamepads...proving to also be equally useless.

Hyperspin is not the only frontend on android and having launch intent working in an app or emulator is actually a pretty big deal. I've had the Shield TV for quite some time and have seen Developers be incredibly accommodating to getting stuff working on it. Ranging from launch intent being added in UAE4ARM for example. To having the Shield TV's home screen wallpaper change via Recommendations Row, with SPMC (a Kodi fork) and the Arc Browser frontend (I personally requested it from the developer). So maybe the guy they have doing the Android port will be just as helpful once he is aware.

I've shared "my assets" with Thatman84. However I will now be purging them from the Shield TV, the games alone are taking up 4GB never mind the media files. In it's current state OpenBOR is useless to me, effectively being a waste of space. There are some other wheels I have that do work (e.g Microsoft MSX) but they need attention for wheel art and the like. I'll spend my time on these before I get drawn back into the Commodore Amiga when Amiberry for Android appears.

I wish you guys all the best with it. I look forward to seeing how you all get on in time.

 

  • Like 2

Share this post


Link to post
Share on other sites

Will see what happens. I may even use this project to learn a bit of app dev ? Not holding my breath though.....

updated OP with link to the GitHub release page to grab updated apk's

 

Share this post


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

Will see what happens. I may even use this project to learn a bit of app dev ? Not holding my breath though.....

updated OP with link to the GitHub release page to grab updated apk's

 

Sorry I forgot to mention, the latest .apk is 4583 dated Dec 31st 2017. I have tried it after doing that video and it's not really much better than what I was using before (4432), in regards to the controls.

I didn't like the "vibe" I was getting from their forum. A simple "Thank you for the interest, we'll chat with the Dev and see what can be done" would have been a more welcome reply. I hope the assets you now have help you along.

All the best with it guys

Share this post


Link to post
Share on other sites

Thanks for the input as always Hono,

they seem good enough don't forget I never posted over there and it was not really related to their core audience of game development. 

Hopefully whitedragon can shed some light on what's needed

  • Like 1

Share this post


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

Thanks for the input as always Hono,

they seem good enough don't forget I never posted over there and it was not really related to their core audience of game development. 

Hopefully whitedragon can shed some light on what's needed

Yeah no worries. Sorry if I seemed harsh in my replies, I'm just tired. Thing is, if you're talking about launch intent...then it should be pretty obvious you'd know what a port is lol

Launch intent is already implemented and working in a fashion, which surprised me as I said in the video it's often overlooked. If that could be sorted it would actually benefit the android port a great deal. The gamepad works in game just fine as I showed. Getting the Touchscreen controls back in the newer build seemed a little better BUT it's still far from intuitive. I'm not saying it needs to be omitted for the Shield TV, just easier to re-enable. I can't see how these things being worked on would detriment the overall performance of the app.

As I said you hadn't yet heard from the guy doing the android port. From the tests Pouteur has done with the K1, even the old builds seem to work incredibly well. White Dragon's done a very good job with it.

Share this post


Link to post
Share on other sites

Can someone post the exe line please. Not at the shield for another day to extract it. Updated the op with another thread about OpenBOR also

Share this post


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

Can someone post the exe line please. Not at the shield for another day to extract it. Updated the op with another thread about OpenBOR also

rompath=/storage/emulated/0/OpenBOR/Paks
exe=org.openbor.engine/org.libsdl.app.SDLActivity
romextension=pak,PAK

  • Super Like 1

Share this post


Link to post
Share on other sites

As said I'll be moving on to other things BUT I've done an updated video. Hopefully it's of some help regarding the controls (starts at around 2:22).

After doing that video, I can now confirm that (on the Shield TV anyway) two player controls are broken (even in the lastest apk build 4583). Essentially the 2nd pad isn't recognised as being a separate controller.

 

  • Like 1

Share this post


Link to post
Share on other sites
3 hours ago, Honosuseri said:

 

As said I'll be moving on to other things

 

Hyperspin related I hope ;)

 

Share this post


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

Hyperspin related I hope ;)

 

There's more to life mate lol

Although yes as I said before, I do want to try and tidy up my MSX wheels. They do actually work properly, unlike OpenBOR so are more of a priority. Once Amiberry is released for Android MUCH of my time is going to be devoted to that. I already have an impressive Amiga collection on the Shield TV but maybe I can make it a little better when I do the transition from UAE4ARM.

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

  • Like 1

Share this post


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

There's more to life mate lol

There is!?!? I guess I missed that memo.. :rofl:

 

  • Super Like 1

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.
       
    • By thatman84
      Please note my knowledge of this system does not run deep but everything here works and plays fine.
      What is it?
      Capcom Play System III or CPS-3 is an arcade system board that was first used by Capcom in 1996 with the arcade game Red Earth. It was the second successor to the CP System arcade hardware, following the CP System II. It would be the last proprietary system board Capcom would produce before moving on to the Dreamcast-based Naomi platform.
      How to emulate in Android (Shield TV)
      Quick and simple way is with the FBA core of RetroArch and matching FBA romset.
      At time of writing current versions are:-
      Core:- FB Alpha v0.2.97.42 (commit 6b7a701)
      FBA:- 0.2.97.42 (9 July 2017)
      Other options are MAME core in RetroArch or MAME4Droid reloaded (0.139mame romset). I believe the CHD files are needed for some games and with MAME4Droid, at least,  I had to "install" the game when it 1st launched in the emulator. That process took about 20-30mins and not all worked. Redearth was one I tested and "installed".
      Games
      JoJo no Kimyouna Bouken: Miraie no Isan (Japan 990913) = (jojoba.zip)
      JoJo's Venture (USA 990108) = (jojo.zip)
      Red Earth (Euro 961121) = (redearth.zip)
      Street Fighter III 2nd Impact: Giant Attack (USA 970930) = (sfiii2.zip)
      Street Fighter III 3rd Strike: Fight for the Future (EUR 990608) = (sfiii3.zip)
      Street Fighter III: New Generation (USA 970204) = (sfiii.zip)
       
      Note:-
      I replaced this entry in the official database with the european version as I could not get it to launch in FBA.
      Street Fighter III 3rd Strike: Fight for the Future (USA 990608) = (sfiii3u.zip)
      EDIT:- USA version is working with RetroArch core version 0.2.97.44. Make sure you have the correct RomSet version
      Setup Steps...
      1.  Open RetroArch and download the Arcade (FA Alpha) core.
                                     Main Menu -> Online Updater -> Core Updater

      1a. Transfer your games to your prefered location (You only need the six zip files listed in the database and above)

      2. Add the "Capcom Play System III" system to your Hyperspin setup with HyperHQ on a PC and transfer the files/folder to your device or by manually creating all the relevent folders to your device. (Download at bottom of guide)
      3. Add Capcom Play SYstem III to your Main Menu.xml or Main Menu_Android.xml
      4. Add these lines to your Capcom Play System III.ini file found in Hyperspin/Settings/ or Hyperspin/Settings_Android/
      exe=com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture
      romextension=zip
      parameters=cores/fbalpha_libretro_android.so
       
      PLAY SOME STREET FIGHTER .......................
       
      Extra Notes:-
      Under the FB Alpha "Quick Menu -> Options" you can select between different regions. Choosing a different region will give you the different loading screens along with other things I'm not sure about.
      Street Fighter III 3rd Strike (Default)Euro

      Street Fighter III 3rd Strike (USA)

       
      ANDROID MEDIA PACK AND DATABASE (Get your videos from emumovies.com)
      Hyperspin-CPS3Android.zip
       
       
    • By Honosuseri
      As we celebrate 25 years of DOOM! John Romero has brought us SIGIL, an unofficial 5th chapter to the original game. So as Retroarch's Prboom core has now been updated to support it...figured I should really add it to my Doom Classics wheel...
      Threw together a Sigil theme, wheel art and video snap. I was pleasantly surprised, that the prboom core now played the midi music natively. Doom 1&2 originally required me to add the music tracks as mp3 files. 
×
×
  • Create New...