OpenBOR finally working fine on RETROPIE with ES

cyperghost

@darknior said in OpenBOR finally working fine on RETROPIE with ES:

No i don't have access to the runcommand user menu. I can't see the grey launching box screen and press a button. It's why launching a game is really really faster for OpenBOR.

That's strange. I see the grey box always if I use my script. As the calls from ESs es_systems.cfg and my script are the same I don't understand why in your setup is no box. You can see the selection box right in this posting here
Annother question, do you see the grey box if you are using my script?

When i write ES XML i want to explain that if i activate the ES option that only show games in XML, i will not see in ES the other games and i can't launch them. With you menu i can.

Okay understood! So you set "Parse XML gameslist only".
Nevertheless there is a solution.... a bit hacky but it might work well.

We can use runcommand now. So we have access to runcommand-onstart.sh ... we edit the file and add codeblock from below. We edit runcommand-onstart with:

nano /opt/retropie/configs/all/runcommand-onstart.sh
and add code from codebox below ;)
~~Before we add a new BOR-game "Access Selection Menu", so we type mkdir "/home/pi/RetroPie/roms/ports/openbor/Access Selection Menu.bor"~~
edit: Much better solution - ES can't define between files and directories. My script does so this entry won't appear in my selection menu
- We add a new file "Access Selection Menu" with
- touch "/home/pi/RetroPie/roms/ports/openbor/Access Selection Menu.bor"

### Access to Selection Menu
## 
# $1 = systemname > openbor
# $3 = full path of ROM-file

if [[ "$1" == "openbor" && "${3##*/}" == "Access Selection Menu.bor" ]]; then
    # pkill runcommand.sh # Maybe needed to prevent first runcommand from being messed up
    bash "/home/pi/RetroPie/roms/ports/OpenBOR - Beats of Rage Engine Selection.sh"
fi

##
### Access to Selection Menu

Please consider to change pathes and filenames as you want. I didn't test the codeblock!
may the farce be with you ;)

darknior

@cyperghost said in OpenBOR finally working fine on RETROPIE with ES:

Okay understood! So you set "Parse XML gameslist only".
Nevertheless there is a solution.... a bit hacky but it might work well.
We can use runcommand now. So we have access to runcommand-onstart.sh ... we edit the file and add codeblock from below. We edit runcommand-onstart with:
...

Ok now i understand where to put your GIT .SH file lol
I have modified PATH with mine to feet my system and try it.
I works perfectly !!!

Now I see the grey box every time. Your script fix it.
Now the configuration key is auto for all games, so excellent
And the FAKE FILE.BOR i can launch your menu <3

But i found some bugs ... maybe i'm alone to have them :

On your BOR GAMES menu i can't move with my Jostick ... only with Keyboard.
I have a 8bitdo joy, and i see you use Joy2key ... maybe i must configure something her but what ?
EDIT : Sorry only player one Joystick working, not the second player. On port one i have a Xbox One USB controller.
And if i understand fine you map it like a keybord ? It can really help for some other homebrew that not use joystick.
When i launch the original OpenBOR.sh file from ES Ports, if i understand fine it must also launch your menu because there is no specified FILE.BOR in %ROM% ... but it not launching it for me.

#!/bin/bash
"/opt/retropie/supplementary/runcommand/runcommand.sh" 0 _PORT_ "openbor" ""

EDIT : But it's not a real problem because now i have made a Menu.cfg by copying an other one that works fine with my Joystick. You must only put resolution and filter to disable because it don't like them ;)

cyperghost

@darknior said in OpenBOR finally working fine on RETROPIE with ES:

Now I see the grey box every time. Your script fix it.

Now the configuration key is auto for all games, so excellent

And the FAKE FILE.BOR i can launch your menu <3

Yes, that's like I expected. Excellent!

The joystick selection is fixed to 1st Joystick only if you want your wirless controller to work you can set iz to js1 instead of js0. I just ripped that part out from runcommand (script kiddie way). It's possible to fix that.
So not a bug ... just didn't take time to investigate.

OpenBOR.sh

No you misunderstood the way it works - the original OpenBOR.sh is useless (imho). It's not able to launch my menu becasue it isn't feed with any argument. It just calls OpenBOR binary and will likely show you the OpenBOR intro graphics. I deleted it and use always the menu script. You can also rename my script to OpenBOR.sh if you want.

I hope it's more clear for you now ;)

But it's not a real problem because now i have made a Menu.cfg by copying an other one that works fine with my Joystick. You must only put resolution and filter to disable because it don't like them ;)

Can you explain this please? Can we change the OpenBOR intro screen with menu.cfg?

darknior

@cyperghost said in OpenBOR finally working fine on RETROPIE with ES:

The joystick selection is fixed to 1st Joystick only if you want your wirless controller to work you can set iz to js1 instead of js0. I just ripped that part out from runcommand (script kiddie way). It's possible to fix that.
So not a bug ... just didn't take time to investigate.

Yes i have understand it's not a bug when i edit my post, i read your code in your script

    "$ROOTDIR/supplementary/runcommand/joy2key.py" "/dev/input/js0" kcub1 kcuf1 kcuu1 kcud1 0x0a 0x09 &

But i don't know Joy2key, like you write we can replace js0 by js1 but we will lost the first controller. And like you map the gamepad to the keybord keys UP DWN LEFT RIGHT, i think we can't do it on the two gamepads.

Can you explain this please? Can we change the OpenBOR intro screen with menu.cfg?

When you lunch OpenBOR for the first time the problem is that the Gamepad is not working. You only have Keyboard.
When you are in game you can configure it, and after you can use Gamepad on games.
I understand the menu.cfg is the controller configuration for the OpenBOR games launcher menu.
I take a game CFG that working with my controller, replace it and it rocks now perfectly :D
But the MENU don't like the graphic options, like X2 640x480 and filters, it's why on this config you must disable them.

NOW the last BIG BUG we must understand, is why OpenBOR create games save file at start, and when you are playing games Never save any progression :(
With this bug we can't finish any games to unlock new options ...

cyperghost

@darknior

But i don't know Joy2key, like you write we can replace js0 by js1 but we will lost the first controller. And like you map the gamepad to the keybord keys UP DWN LEFT RIGHT, i think we can't do it on the two gamepads.

I assume not. The joy2key works (afaik) only for terminal programms. And with a change of the joypad you won't loose a setted controller. Because the controller are added as device in unix filemenus.

I understand the menu.cfg is the controller configuration for the OpenBOR games launcher menu.
I take a game CFG that working with my controller, replace it and it rocks now perfectly :D
But the MENU don't like the graphic options, like X2 640x480 and filters, it's why on this config you must disable them.

Thanks that worked best!

NOW the last BIG BUG we must understand, is why OpenBOR create games save file at start, and when you are playing games Never save any progression :( With this bug we can't finish any games to unlock new options ...

Yes it's a pitty even highscores are not saves. I think there is an error in the binary are an error how save files can be accessed again. So maybe you can fix it as you made it possible for commandline parameters ;)

But to recapitulate the whole thing of coding and posting.
Nicely done and a great step into further development for OpenBOR.

darknior

@cyperghost said in OpenBOR finally working fine on RETROPIE with ES:

Yes it's a pitty even highscores are not saves. I think there is an error in the binary are an error how save files can be accessed again. So maybe you can fix it as you made it possible for commandline parameters ;)

Yes i will try if a friend can help me. I'm not a C expert... It's hard for me and it's why i wish a real C developer come her to help us with this :p

But to recapitulate the whole thing of coding and posting.
Nicely done and a great step into further development for OpenBOR.

Yes it's really excellent :)
I have write all my stuff and your stuff in the first post ;)
Thanks a lot

cyperghost

@darknior Ah... yes saw you've updated the script. But you forget to reference to the script ;) - I think you set link to this.
https://retropie.org.uk/forum/topic/13784/openbor-finally-working-fine-on-retropie-with-es/64

Then users will see the pictures and can get download location and the description how to autoconfigure joypads is also available ;) Thanks anyway.

Yes i will try if a friend can help me. I'm not a C expert... It's hard for me and it's why i wish a real C developer come her to help us with this :p

Yes this would be fine ;)
It's really sad the development is stuck to an old engine. I think the Pie is powerfull enough even for newest addons. Maybe you revitalise the whole fork ;)

darknior

@cyperghost said in OpenBOR finally working fine on RETROPIE with ES:

Then users will see the pictures and can get download location and the description how to autoconfigure joypads is also available ;) Thanks anyway.

It's ok i have updated and add your link :)

It's really sad the development is stuck to an old engine. I think the Pie is powerfull enough even for newest addons. Maybe you revitalise the whole fork ;)

Yes it's bad :(
I see the last OpenBOR comme on Switch last week !!! WTF !!! It's an console, no many people will use it ...
And on PI where we are many many users nobody port the last source code :(
Yes the PI3 is enough powerful to make it works perfectly, for sure :D

I think the dream can come if one day some one have the idea to port OpenBOR engine to RETROARCH !!!
Like some other Homebrew, it's possible, and doing it make OpenBOR working fine on any system ;)
And maybe add some new feature with Savestate, Rewind, ...

BiZzAr721

@cyperghost I went ahead and made the scripts for all the games I had listed as working (+ asterix & obliqe). The the last thing to do is make it use the default master.bor.cfg. I realized there is nothing on the individual scripts to call for it. Could you please help me (again) with on exactly what I have to pull from your script to add to the individual game scripts to keep full function? I'll adjust the script I hacked together with the amendments. I'll be out of town for a few days but I'll get right back into it on my return. Thank you!

Edit: extra points if it can be rolled into the emulators.cfg, kind of like dosbox does!

cyperghost

@bizzar721 Sorry I don't get you. You want to copy default configuration for every called script? Then insert just a copy command

[[ -f "destination.file" ]] || cp "default.file" "destinatation.file"

The [[ ]] is a testcommand if file already in place if not then copy it.

@darknior
About the load/save feature ;)
It's all written here. Some lines later you will find entry // OMG! Fix that! So I assume there are some errors in.
I think some file handling is broken. Maybe some more experienced coders can help here.

BiZzAr721

It sounds exactly like what I'm looking for. I want it to work just like your script, which is to look for a cfg file. If none exist copy master.bor.cfg to the save folder and rename it to match the game name.

I'm thinking I could either add this to the emulator.cfg to be run before evey game loads, or must it be included in the start of each script, named with the full path & proper file name?

cyperghost

@darknior Improved the script menu a bit. Now it's sorting to ABC (sort command) and I resolved a small bug with array sorting - from my old function-snippet. I think I found a way to solve the joypad problem, too ;)

@BiZzAr721 I would rather modify the scripts from ports before modifing the emulator call. Btw: we have runcommand access now. That offers much entrypoints. Read more about here - I would use User Menu entry.

@zerojay Can we modify the emulator.cfg for openbor like done here in code box?. The adding of %ROM% does nothing to the regular compiled binary as it can not be called with command line parameters. But it will prepare users for the modified version from @darknior

So in scriptmodule openbor.sh the change would just be

function configure_openbor() {
addPort "$md_id" "openbor" "OpenBOR - Beats of Rage Engine" "pushd $md_inst; $md_inst/OpenBOR %ROM%; popd")

zerojay

@cyperghost said in OpenBOR finally working fine on RETROPIE with ES:

@darknior Improved the script menu a bit. Now it's sorting to ABC (sort command) and I resolved a small bug with array sorting - from my old function-snippet. I think I found a way to solve the joypad problem, too ;)

@BiZzAr721 I would rather modify the scripts from ports before modifing the emulator call. Btw: we have runcommand access now. That offers much entrypoints. Read more about here - I would use User Menu entry.

@zerojay Can we modify the emulator.cfg for openbor like done here in code box?. The adding of %ROM% does nothing to the regular compiled binary as it can not be called with command line parameters. But it will prepare users for the modified version from @darknior

So in scriptmodule openbor.sh the change would just be
function configure_openbor() {
addPort "$md_id" "openbor" "OpenBOR - Beats of Rage Engine" "pushd $md_inst; $md_inst/OpenBOR %ROM%; popd")

When that modified version is ready, let me know and I'll make the switch.

cyperghost

@zerojay You may read the first posting in this thread. Only @darknior's version of OpenBOR includes CLI calls. So we have to change the git, too. And I'm not familiar with the git-system.

In this state the %ROM% switch is harmless and would just help users if they want to use @darknior binary - so addons can be directly loaded like the other emulators behave. By using the regular binary the ROM call is left empty and the user is kicked to the OpenBOR selection screen.

I think we better wait before making quick changes. Thank you ;)

cyperghost

@darknior Consider to recompile the OpenBOR binary. Mine is just 900kB, your is 1300kB ... That's the size rofl0r predicted for his build.
That should give the engine a boost ;)

BLOAT:
  OpenBOR (anallyst edition) x64 binary           :  750 KB
  OpenBOR (lavalit edition, rev 3320)  x64 binary : 1250 KB
  OpenBOR (lavalit edition, rev 3600+) x64 binary : probably 1.5 MB+

I post binaries compiled on Pi3 on my github account

@BiZzAr721 I've written a script that will setup config via UserMenu ... type in SSH
cd /opt/retropie/configs/all/runcommand-menu && wget "https://raw.githubusercontent.com/crcerror/RetroPie-OpenBOR-scripts/master/OpenBOR - Setup GamePads.sh"

darknior

@cyperghost said in OpenBOR finally working fine on RETROPIE with ES:

Consider to recompile the OpenBOR binary. Mine is just 900kB, your is 1300kB

Thanks a lot, how do you do this ?
I know when i compile my binaries are always bigger than suggested ...

cyperghost

@darknior Well I rely also on the great coders here in the forum. So i just changed two lines in my version of openbor.sh install scriptmodule and let it compile as is it used to be. But I think this binary runs much better. The tearing in "Nightslashers" for ex. is significantly reduced with this.
I think the NO_GL=1 parameter makes the difference.

I hope someone will port newest engine to Raspberry ... OpenBOR offers really great gameplay and I don't understand why there is so less attention from the developers from chronocrash. They don't consider the Rasperry as chance for wider audience and for further development for their addons (imho!). The smoothest thing would be an integration into libretro.

Second I just want to test the scriptmodule for a later PR - and yes it works, the %ROM% is written to emulator config instantly. So it may be possible to use your fork .... But I'm not sure if this is allowed.
Maybe @zerojay can answer this... (Sorry for tagging you)

darknior

@cyperghost said in OpenBOR finally working fine on RETROPIE with ES:

I think the NO_GL=1 parameter makes the difference.

Ok thanks, it's a good idea :)
I will try your binary if it works better :)

I hope someone will port newest engine to Raspberry

I hope too ... i think it can be interesting to show OpenBOR on pi on the Chronocrash forum ... showing it works fine on pi and that we stand for an update ...
I have plan to make a beautiful ES menu with media and make a video to show them ... but it will take me some time to release media...

Second I just want to test the scriptmodule for a later PR - and yes it works, the %ROM% is written to emulator config instantly. So it may be possible to use your fork .... But I'm not sure if this is allowed.

Yes if Retropie can be updated with my fork and your script it can be really cool for every one :)
With the two mode, launch OpenBOR from port and a new ES section with all the games.
But we must also give some CFG already configured with pad for MENU and DEFAULT.

cyperghost

@darknior said in OpenBOR finally working fine on RETROPIE with ES:

Yes if Retropie can be updated with my fork and your script it can be really cool for every one :)

Agreed! But not our buisness.

With the two mode, launch OpenBOR from port and a new ES section with all the games.

Well therefore we have the Docs section or the thread here

But we must also give some CFG already configured with pad for MENU and DEFAULT.

I don't think so. That should still be a user decission

cyperghost

@darknior There seems annother version of OpenBOR for RetroPie spreading around. It is also build 3016 but I was not able to get it running.

install script is here - a user named ulysess seems to have compiled it for several models. But I can't get it running. So it seems not to be the same version we are using.