Jump to content
Welcome Guest!

Join us now to get access to all our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, and so, so much more. It's also quick and totally free, so what are you waiting for?

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 😀

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.
 

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
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

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.

 

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.

 

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

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
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

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.

 

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 ;)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By thatman84
      Hyperspin Android Overview & Installation
      Credits
      BBB
      Reznate
      Thatman84
      Lilcza
      And anyone I have forgotten helped me learn this
      My guides are only an extension of Reznnate's sticky posts
      PLEASE READ the OTHER sticky posts
       
      What is it?
      An Android version of Hyperspin that works with existing themes and data directly from the Hyperspin community.   It launches both Android games and Android emulators.
       
      Why?
      Several reasons...    
      Android hardware is getting faster and faster.     Emulators for Android are getting better and better.     We wanted to play with our Hyperspin setups outside the house.     I wanted to replace the old PC in my MAME cabinet with a mobile device so I could justify leaving it on all the time.   It needed the ultimate launcher!!!  
      How?
      Since the Windows version of Hyperspin is dependent on Adobe Flash, it was necessary to build the app from scratch. With performance in mind, the Android version is highly-threaded and renders with the GPU using OpenGL.
       
       
      Compatibility
      Android 4.4+ NVIDIA OpenGL drivers ONLY Tegra4, Tegra K1, Tegra X1 Drivers  (Tegra Mobile Device List) Confirmed working device, but not limited to, Shield Portable, Tablet and TV, Google Nexus 9, MiiPad, ADT-1 Tested Emulators Release statements  
       
       
       
      Hyperspin/Android Limitations
       
      RocketLauncher is not available for use on Android but the settings files it uses within a PC setup are compatible.
       
      Vertical Systems/Wheel list only No Touch Screen Input (Controller required) Favourites list feature not supported Genre feature not supported Searching subfolders for ROM’s not supported Games list only supports launching of one emulator (multiple emulators can exist in settings line and the 1st one installed will be launched) PC based animations and themes not fully functional. See this detailed post HERE  
       
       
      Never used Hyperspin before?
       
      As Hyperspin Android was originally designed to allow PC users to have another way to experience their setup you will need to first decide how you would like to proceed with your Hyperspin Android setup
      **Skip to Installation section if NOT using a PC**
       
       
      The easiest way is to  install the PC version for testing and building your Android setup (Follow Avar’s official tutorial videos HERE or follow step by step guides HERE Alternatively build your Hyperspin Android setup from iOS computer or directly from your Android device.  
      Already using Hyperspin on a PC?
      You can co-exist your PC and Android Hyperspin setups in one Hyperspin folder by making the following additions.
       
      Optional additional database file called "Main Menu_Android.xml". Located in your Hyperspin/Databases/Main Menu folder. This will allow for a specifically tailored Main Menu for your Hyperspin Android setup
       
      Optional additional settings folder called /Settings_Android. Located in your Hyperspin directory and populated with your Android specific Main Menu.ini, Settings.ini and SYSTEMNAME.ini’s. This allows both Windows and Android launcher/rompaths to co-exist in separate .ini files within the same Hyperspin directory.
       
      **Note
      Some of your PC Themes and features may not be compatible with your Android setup so it may pay to build a specific Hyperspin folder for your Android setup. If you take this opportunity to trim unneeded files to save storage space it will likely mean some 3rd party tools (Don’s Filter list and Hypertools) may not function correctly.
       
      Also adjustments to your Android set of settings will need to be done manually with a text editor
       
       
       
       
      Installation
       
      What’s Needed:
      A file explorer installed on your Android device (ES File Explorer in this case) Optional: PC to make life easier Step 1 – App Installation
      Note: The device you are using and your chosen Hyperspin folder location (local, sdcard, external HDD or NAS) will directly affect your steps and settings file values
      All testing was done on my NVIDIA Shield TV Pro 3.2 Marshmallow 6.0, slight differences may be found on other devices
                                                                           
      On your device open Google Play Store and search for Hyperspin
       
             2. Install as any other Play Store app, accepting all permissions when prompted
       
      You will now see the Hyperspin app in you devices menu

       
       
      Step 2 – Build your Hyperspin directories
      To function, Hyperspin pulls all data from an installation folder NOT included with the app installation. Without this directory you will see the below screen when trying to launch Hyperspin

      Note: New users without a Hyperspin directory and not installing a PC version of Hyperspin please download
       
       Hyperspin Android base pack
      (Adjusted from BBB's Hyperspin 1.3.3 file)
      Existing users please locate your PC Hyperspin directory and copy this to the root of your preferred storage device (USB, SD card, internal storage or NAS) see below details.
       
       
      But First...
       
      Decide on Storage Media & Location...
       
      I will now show you how to install Hyperspin onto the internal storage of your Android device. You are free to place your Hyperspin directory on a different storage device, including SD cards, USB storage and Network Attached Storage (NAS), but please be aware Hyperspin will seek and prioritize booting 1st from
       
      /usbdrive/Hyperspin
      then
      /sdcard1/Hyperspin
      then
      /sdcard/Hyperspin
      for your data.
       
      Also note that on the Shield TV Pro /storage/Emulated/0 & /storage/sdcard are in fact the same location
       
      If you will be using a NAS to store your Hyperspin directory, please be aware that there can only be one directory level between your devices /storage directory and your Hyperspin directory. For this to work, you will need to share your Hyperspin folder from your NAS device and the map that device to you Android device through its storage settings. It should then be seen in your devices /storage folder (I will cover this in detail in subsequent tutorials)
       
      Example of correct NAS Path:-           /storage/MYNAS/Hyperspin
      Example of incorrect NAS Path:-        /storage/MYNAS/SUBFOLDER/Hyperspin
       
      My TEST path screenshot
      Is my Local device directory /storage Is the name of my NAS Drive sdcard1
       
      Next – Get a file explorer
       
      I Installed ES File Explorer (ESFE) by searching ES in your Play Store app and install as any other.
       

       
      A.        
      Launch ESFE and navigate to the 1) Local then 2) Home - option. Place your Hyperspin folder here 3)
       

       
       
      Note: For a HSA to work the ONLY required files/folders for an Android installation are as follows
      /Hyperspin
      /Databases
      /Media
      /Settings
      /Emulators (optional ROM location structure for ease of setup)
       
      B.
      Please now exit to your home screen and launch the Hyperspin App, to test everything is correct. Depending on your correct choice of Hyperspin directory you should now be greeted with the Hyperspin intro video and your Main Menu wheel of systems.
       
      The base pack download will look similar to this example.
       

       
      This is what you get with the default Hyperspin 1.3.3 version I have adjusted
       
       
      Now you have completed the basic installation there are some settings that require adjusting and reviewing to enable games to be launched.
      Also the per system/wheel settings are covered here
       
    • By thatman84
      This is the start of the WIP guide and Amiga Project thread
      DONT REPLY TO THIS THREAD
      REPLY TO THIS ONE(clicky)
       
      Database taken from this thread post
       
      More to follow
    • By thatman84
      The Libretro devs just enabled the CHD support for the SuperGrafx and PC-Engine cores on android.
      Update your cores with Online Updater.
       
      Personally I have not converted my games or have any PC-Engine CD games but its a good addition anyway.
      I hear that audio sync and quality can be an issue
    • By reznnate
       Tested Emulators -- .ini config settings   Retroarch - Various emulators   exe=com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture  parameters=<choose one of the emulator cores like below>   Examples of retroarch core parameters Atari 2600 core:  parameters=cores/stella_libretro_android.so PSX core:  parameters=cores/pcsx_rearmed_libretro_neon_android.so   libretro cores:  4do_libretro_android.so  bsnes_mercury_performance_libretro_android.so  bsnes_performance_libretro_android.so  catsfc_libretro_android.so  desmume_libretro_android.so  dinothawr_libretro_android.so  dosbox_libretro_android.so  fb_alpha_libretro_android.so  fceumm_libretro_android.so  fmsx_libretro_android.so  gambatte_libretro_android.so  genesis_plus_gx_libretro_android.so  gpsp_libretro_android.so  handy_libretro_android.so  mame_libretro_android.so  mednafen_lynx_libretro_android.so  mednafen_ngp_libretro_android.so  mednafen_pce_fast_libretro_android.so  mednafen_pcfx_libretro_android.so  mednafen_psx_libretro_android.so  mednafen_supergrafx_libretro_android.so  mednafen_vb_libretro_android.so  mednafen_wswan_libretro_android.so  mass_libretro_android.so  meteor_libretro_android.so  mupen64plus_libretro_android.so  nestopia_libretro_android.so  nxengine_libretro_android.so  o2em_libretro_android.so  pcsx_rearmed_libretro_android.so  picodrive_libretro_android.so  ppsspp_libretro_android.so  prboom_libretro_android.so  prosystem_libretro_android.so  snes9x_libretro_android.so  snes9x_next_libretro_android.so  stella_libretro_android.so  tgbdual_libretro_android.so  ume_libretro_android.so  vba_next_libretro_android.so  vbam_libretro_android.so  vecx_libretro_android.so  virtualjaguar_libretro_android.so  yabause_libretro_android.so     Dolphin - Gamecube/Wii/Wiiware exe=org.dolphinemu.dolphinemu/org.dolphinemu.dolphinemu.activities.MainActivity parameters=AutoStartFile    IrataJaguar - Atari Jaguar  exe=ru.vastness.altmer.iratajaguar/ru.vastness.altmer.iratajaguar.MainActivity  parameters=rom   NES.emu - NES  exe=com.explusalpha.NesEmu/com.imagine.BaseActivity  parameters=   MSX.emu - Colecovision, MSX, etc.  exe=com.explusalpha.MsxEmu/com.imagine.BaseActivity  parameters=   Mame4Droid - MAME  exe=com.seleuco.mame4droid/com.seleuco.mame4droid.MAME4droid  parameters=   Mupen64Plus AE exe=paulscode.android.mupen64plus/paulscode.android.mupen64plusae.MainActivity
      parameters=    Nightly builds exe=org.mupen64plusae.v3.alpha/paulscode.android.mupen64plusae.SplashActivity parameters=     Play! - Playstation 2 exe=com.virtualapplications.play/com.virtualapplications.play.ExternalEmulatorLauncher parameters=   Reicast - Dreamcast  exe=com.reicast.emulator/com.reicast.emulator.MainActivity  parameters=   Drastic - Nintendo DS  exe=com.dsemu.drastic/com.dsemu.drastic.DraSticActivity  parameters=GAMEPATH   Fpse - PSX  exe=com.emulator.fpse/com.emulator.fpse.Main  parameters=path   ePSX - PSX  exe=com.epsxe.ePSXe/com.epsxe.ePSXe.ePSXe   parameters=com.epsxe.ePSXe.isoName  * change romext=cue in settings.ini, iso did not work for me   PPSSPP (FREE version) - PSP  exe=org.ppsspp.ppsspp/org.ppsspp.ppsspp.PpssppActivity  parameters=org.ppsspp.ppsspp.Shortcuts PPSSPP Gold - PSP             exe=org.ppsspp.ppssppgold/org.ppsspp.ppsspp.PpssppActivity              parameters=  exe=org.ppsspp.ppssppgold/org.ppsspp.ppssppgold.PpssppActivity  parameters=org.ppsspp.ppssppgold.Shortcuts   uoYabause - Sega Saturn exe=org.uoyabause.android/org.uoyabause.android.Yabause
      parameters=org.uoyabause.android.FileNameEx
      Yaba Sanshiro
               exe=org.uoyabause.uranus/org.uoyabause.android.Yabause
               parameters=org.uoyabause.android.FileNameEx
      Gearoid - Sega Game Gear  exe=com.androidemu.gg/com.androidemu.gg.EmulatorActivity   Parameters=   Colem - Speccy ZX - fMSX VGBANext  Emulators from Garage Research  PAID  com.fms.colem.deluxe - Colem - Colecovision  com.fms.fmsx.deluxe - fMSX  com.fms.ines - iNES  com.fms.emu - VGBAnext - GBA/GBC/GB Emulator  com.fms.vgb - VGBc - Gameboy Color  com.fms.mg - Master Gear - Sega Game Gear  com.fms.speccy.deluxe - Spectrum Sinclair ZX  FREE  com.fms.colem  com.fms.fmsx  com.fms.speccy    Set "??" to "com.fms.emulib.MainActivity" for all products but VGBAnext.   For VGBAnext:  ??=com.fms.vgba.MainActivity for opening *.gba files  ??=com.fms.vgb.MainActivity for opening *.gbc/*.gb files   OpenBOR - 2D Game Engine (Some integration issues with Hyperspin)              exe=org.openbor.engine/org.libsdl.app.SDLActivity Parameters=   Launch android app package names in database.xml Determine Android game name through Google Play web interface. i.e. https://play.google....ure.dragonslair   pcgame=true
×