OpenBOR finally working fine on RETROPIE with ES

darknior

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

Doesn't it happen when you launch it with your previous approach?

No it's work fine with .sh

But i found something strange with OpenBOR, if i launch it with :

/opt/retropie/ports/openbor/OpenBOR

It works but don't know really where is it and don't use the recorded settings, it don't find the .cfg files.
If i do :

cd /opt/retropie/ports/openbor
./OpenBOR

It works fine because i think it is in the good directory.
It's a bug in OpenBOR.

BuZz

@darknior we will move to new scummvm when it's released. Previously there were too many issues to track master

PPSSPP bins were updated the other day. From source we track bleeding edge afair

I have a WIP open or based on latest code, but have been busy on other things.

I just don't have the time now due to the size of the project to be involved in every discussion on the forum. I do read and keep track. Other developers can comment also. I'm not against tagging me in general, but it can be too much.

meleu

@darknior my new suggestion for the openbor entry in es_systems:

<command>cd /opt/retropie/ports/openbor/; ./OpenBOR rom=%ROM%</command>

darknior

I learn today why OpenBOR can't read .PAK ...

https://github.com/rofl0r/openbor/releases/tag/pak-change

But i have add PAK support to command line for future ...
And a test to very if the MOD Directory exist before launching.

	// Test command line argument to launch MOD
	int romArg = 0;
	if(argc > 1) {
		int argl = strlen(argv[1]);
		if(argl > 4) {
			loadsettings();
			memcpy(packfile, argv[1], argl);
			if(dirExists(packfile, 0)) {
				if(packfile[argl-1] != '/')
					strcat(packfile, "/");
					romArg = 1;
			}
			else if(memcmp( &packfile[strlen(packfile) - 4], ".pak", 4)) {
				if(fileExists(packfile))
					romArg = 1;
			}
		}
	}
	if(!romArg)
		Menu();

Link to DL : http://www.mediafire.com/file/5cb0zjcsd1qclqq/OpenBOR.rar

Now we can use :

    <name>openbor</name>
    <fullname>OpenBOR</fullname>
    <path>/home/pi/RetroPie/roms/ports/openbor</path>
    <extension>.bor .BOR</extension>
    <command>cd /opt/retropie/ports/openbor/ && ./OpenBOR %ROM% > /dev/null 2>&1</command>
    <platform>pc</platform>
    <theme>openbor</theme>

To launch games MOD directories :)

And i have write a bad info last day, because OpenBOR write : OpenBOR v3.0 Build 3016 2011-08-30

https://github.com/rofl0r/openbor/releases/tag/compatible-official-3400%2B

But if you read GIT it is better, we are compatible with v3.0 Build 3400 Mods !
And newer mods should work as well as now unknown commands will just be ignored.

I found this old version on my PC to try mods directly on Windows :D
I search the real v3400 if some one can help :p

https://www.mediafire.com/file/au9my6mp3dh0and/OpenBor PC v3.2637.rar

darknior

I have make a fork, if some one want help :

https://github.com/Darknior/openbor/blob/master/sdl/sdlport.c

AndyEatsCheese

Oh man I love me some openBOR!! recently I was trying to get them running on the pi by using the Dreamcast CDI versions and opening them with the DC emu.

Please keep up the good work on this!

I can't try it yet as I don't really understand this stuff, but PLEASE when you're 100% happy with the method will you write a tutorial that any noob could follow.

darknior

@andyeatscheese It's already done read before ... we can play.
I will try to fix some bugs now for save and gamepad if possible that's all.

flop

I think this post it´s a little chaotic...

I couldn´t see how to make Openborg work @AndyEatsCheese...

Keep working on it! Openborg working would be great!

darknior

@AndyEatsCheese @flop First post edited with HOW to INSTALL.

flop

@darknior what about @meleu suggestion? :/

darknior

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

<command>cd /opt/retropie/ports/openbor/; ./OpenBOR rom=%ROM%</command>

@flop I use near same if you read fine :

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

 <command>cd /opt/retropie/ports/openbor/ && ./OpenBOR %ROM% > /dev/null 2>&1</command>

I replace ; by && ... like that if the CD command is not working fine (because the directory don't exist), the script will stop.

But it's only for the moment, if i can fix the PATH problem on OpenBOR source code, we will only use :

 <command>/opt/retropie/ports/openbor/OpenBOR %ROM% > /dev/null 2>&1</command>

darknior

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

<command>cd /opt/retropie/ports/openbor/ && ./OpenBOR %ROM% > /dev/null 2>&1</command>

Oups my command is bad for XML format, use this is better :

<command>cd /opt/retropie/ports/openbor/ && ./OpenBOR %ROM% < /dev/null 2<&1</command>

ExarKunIv

@darknior

giving this a shot. im able to follow most of it, but when it came to this part.

Unpack them with the UNPACK option in PORT

i do not see that anywhere and when i try to start the OpenBOR that is in my port list it just crashes. (kinda figured)

any thoughts

darknior

@exarkuniv Yes OpenBOR don't read the PAK file you must unpack them, the option is in your PORT ES menu, i can't help you more for this, read the RETROPIE OPENBOR doc.

https://github.com/RetroPie/RetroPie-Setup/wiki/OpenBOR

ExarKunIv

@darknior

yea the unpack option is not there for me, oh well

darknior

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

@darknior
yea the unpack option is not there for me, oh well

I don't know why retropie-setup don't add it. Maybe try to make it by hands.
My file : extract.sh

#!/bin/bash
PORTDIR="/opt/retropie/ports/openbor"
BORROMDIR="/home/pi/RetroPie/roms/ports/openbor"
mkdir $BORROMDIR/original/
mkdir $BORROMDIR/original/borpak/
mv $BORROMDIR/*.pak $BORROMDIR/original/
cp $PORTDIR/unpack.sh $BORROMDIR/original/
cp $PORTDIR/borpak $BORROMDIR/original/borpak/
cd $BORROMDIR/original/
for i in *.pak
do
  CURRENTFILE=`basename "$i" .pak`
  /opt/retropie/ports/openbor/unpack.sh "$i"
  mkdir "$CURRENTFILE"
  mv data/ "$CURRENTFILE"/
  mv "$CURRENTFILE"/ ../
done

echo "Your games are extracted and ready to be played. Your originals are stored safely in /original/ but they won't be needed anymore. Everything within it can be deleted."
read var
#echo $var

ExarKunIv

@darknior

cool thx. ill give it a shot.

it is odd.
i have never got the extract.sh to ever show up for me. even back with 4.0 Retropie load.

darknior

@exarkuniv Cool if i help you :)
If you want better speak about openBOR and mods, write me on the Chronocrash official forum ;)
I wish you will found a solution to port the last LINUX version to our PI :p

maxwell

@darknior I want to thank you for your post on OpenBor. I was able to get everything loaded on my RetroPie system. While testing I was only able to get a couple of the old games to load withing any issues. I was wondering if you tried any of the new games to see if they would launch at at all? I was pretty shocked to see that OpenBor worked on my raspberry pi. I was also wondering if you could share the links where you found some of the OpenBor games you listed in your post. It seems like they are all scattered all over the place. Thank you again for creating your post. It came in handy for me.

darknior

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

While testing I was only able to get a couple of the old games to load withing any issues.

Yes they works fine ...

I was wondering if you tried any of the new games to see if they would launch at at all? I was pretty shocked to see that OpenBor worked on my raspberry pi.

It is an old OpenBOR because nobody port the new one on PI, you can only use old games made 2 3 years ago. the new games will use new scripts this old OpenBOR not understand :(

I was also wondering if you could share the links where you found some of the OpenBor games you listed in your post. It seems like they are all scattered all over the place.

No file share here sorry, you must search around the web ...

I stand a friend take time to work on PI, maybe next year he or an other dev, will port the last OpenBOR to PI.
It's possible because OB works fine on Linux.