OpenBOR finally working fine on RETROPIE with ES

zanac

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

@mitu no problem brother
I stay to my first opinion ... It is an unofficial port but seems maintainable

Edit
About the old 3600 port made by rofl0r ...
This is even better than the one we are using now
It has PAK support and the load and save feature is working.

But we should maintain 6k branch

@zanac Thanks for your efforts to let RetroPie run a more advanced OpenBOR engine
@BiZzAr721 thanks for testing

please note that in my "retropan" (that is a fork of retropie but for allwinner board), i choosed to have both version, the "old engine" and the "new engine", both are needed to support all games! Some games need old engine... this is the reason why in my git i put both!!!
I have a script that chose a binary or the other reading the version of the game put in the pak name.

Anyway this is not the first time that i contributed to retropie actually, i made also some patched for emulation station, if i find patch in retropan that can be useful for retropie i always prefer to merge in retropie :)

cyperghost

@zanac This is no problem!
In Retropie you can select preferred emulator
So we add both binaries and the user can choose working one.

Like here in my modified script module for open or line48
https://github.com/crcerror/RetroPie-OpenBOR-scripts/blob/master/openbor.sh

So you write openbor-3600 and launch 3600 binary
The openbor call vor newst engine looks like the one posted
So RetroPie is prepared

zanac

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

@zanac This is no problem!
In Retropie you can select preferred emulator
So we add both binaries and the user can choose working one.

Like here in my modified script module for open or line48
https://github.com/crcerror/RetroPie-OpenBOR-scripts/blob/master/openbor.sh

So you write openbor-3600 and launch 3600 binary
The openbor call vor newst engine looks like the one posted
So RetroPie is prepared

retropan is not so much cool :)
I suggest you to clean the script now that both engine support pak ;)

cyperghost

@zanac yes that was one of the reasons I entered openbor. The use of runcommand script offers solid usage of all these emulators. Man I love it if my plans are working ;)

zanac

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

@zanac yes that was one of the reasons I entered openbor. The use of runcommand script offers solid usage of all these emulators. Man I love it if my plans are working ;)
yes, you really do a cool work!

I see that sources point to https://github.com/darknior/openbor, i know that i have already said this, but please note that you will need two version of openbor, the "old engine" and the "new engine"....

Great games like "saint seiya" run only on old engine, openbor is not an emulator that will be proud of retro-compatibility, so in the future i think that we will have also more than two version :(

cyperghost

@zanac No line 48 and 49 sets preconfigured calls to a binary.

So we make following
At first we compile the two binaries
The old engine is named openbor-3600
The new engine is named just openbor

Now we write script module that compiles the two binaries and set up entries for openbor engine choice like this

# call for new engine rev 6250
addPort "$md_id" "openbor" "OpenBOR - Beats of Rage Engine" "pushd $md_inst; $md_inst/OpenBOR %ROM%; popd"

# call for old engine rev 3600
addPort "$md_id-3600" "openbor" "OpenBOR - Beats of Rage Engine" "pushd $md_inst; $md_inst/OpenBOR3600 %ROM%; popd"

Now the user can choose inside the runcommand configuration menu which pak file to load with specific openbor engine revision.

Got me now? I am writing from a tablet ;)

Edit: changed script module routine to add 2 systems in emulator.cfg

zanac

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

@zanac No line 48 and 49 sets preconfigured calls to a binary.

So we make following
At first we compile the two binaries
The old engine is named openbor-3600
The new engine is named just openbor

Now we write script module that compiles the two binaries and set up entries for openbor engine choice like this
# call for new engine rev 6250
addPort "$md_id" "openbor" "OpenBOR - Beats of Rage Engine" "pushd $md_inst; $md_inst/OpenBOR %ROM%; popd"

# call for old engine rev 3600
addPort "$md_id" "openbor-3600" "OpenBOR - Beats of Rage Engine" "pushd $md_inst; $md_inst/OpenBOR3600 %ROM%; popd"
Now the user can choose inside the runcommand configuration menu which pak file to load with specific openbor engine revision.

Got me now? I am writing from a tablet ;)

Yes, that's all right.

BiZzAr721

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

Man I love it if my plans are working ;)

Yes they are!

darknior

@cyperghost Excellent i love the idea :)

You are right, use the old 3600 port made by @rofl0r with save support and add it my command line trick if you don't already do it.
And the last OpenBOR port to use the last excellent games :)
I can't dream better solution to finally use OpenBOR on Retropie :)

When do you will release a package to try this stuff ?
Or will you add it to the official Retropie SETUP script fo all the users ?

cyperghost

@darknior welcome back!
I can write that script module indeed but I am currently on holidays till the next week.
Maybe a more advanced user like @psyke83 can take action and write that module quickly. Before doing this we may tweak the video resolution in newest openbor.

But I indeed think we should use both binaries. Rofl0rs old one with pak and save support and the newest branch brewed by @zanac

His github resp is located here
https://github.com/zanac/OpenPB4/tree/master/openbor

zanac

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

@darknior welcome back!
I can write that script module indeed but I am currently on holidays till the next week.
Maybe a more advanced user like @psyke83 can take action and write that module quickly. Before doing this we may tweak the video resolution in newest openbor.

But I indeed think we should use both binaries. Rofl0rs old one with pak and save support and the newest branch brewed by @zanac

His github resp is located here
https://github.com/zanac/OpenPB4/tree/master/openbor

in the new fork if you can try to investigate why it work only when i force a low resolution (actually i forced 384x224).... the clean way is to remove all "bad code" that i used to force lowres ;) As i said i don't own a rasbperry to try what happens... i used 384x224 'cause this is the resolution that is used in Pandora-Allwinner (the board that i use), but it's not the right thing in rasbperry ;)

Let me know if you discover this mistery, i'm very interested in for my knowledge :)

OpenBOR is missing a command line interface, a good program should implement something like....

--help
--width x
--height h
--pak /path/to/file.pak

if someone of you implement argc/argv command line in this way i think that it's the best solution to solve all problem for rasbperry but also for my crap allwinner, 'cause i can remove from my fork the 384x224 hack :)

cyperghost

@zanac see the hardcoding done in openbor.c
Maybe I can investigate

I found something.
If videomode declaration in pak file does not hit any default mode then debug video mode 255 will be used. This automatically calculates resolution. But I don't not know the source. SDL screen output maybe?

BiZzAr721

Hey @cyperghost We're all most grateful for your contributions - you go enjoy your ~~vacation~~ holiday and we'll look forward to your work on your return =p

oilusionista

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

These are games I tried that DO NOT work (but keeping them unzipped on my PC with my fingers crossed)

Avengers United Battle Force.bor

Hello there, let me introduce myself.
I am O Ilusionista, coder of the game "Avengers United Battle Force". I am also one of the administrators of the Chronocrash (the official OpenBOR community) and recently I've joined the dev team of the OpenBOR (I am just a newbie on this subject for now).

My game won't work on this custom OpenBOR version because it was built based on a VERY OLD version - build 3400. As I am writing this, the most recent version is 6412 - so you can get how old that version is. My game, as stated on the download page, needs to be run in the version 4432 specifically. I will update the game soon, and the minimum build version needed will be 6315.
Any attempt of trying to get it run on older builds will give you an instant crash, because I am using things which aren't present on those old versions.

Btw, if anyone wants to test the game, you can download it from here http://www.brazilmugenteam.com/avengers
You need to use the provided version to run the game.

@zanac as I stated at chronocrash, I saw that this is using a non-official version done by rofl0r.
There is a long story behind it but to make it short - the guy is a pain and was kicked from the dev team.

Also, we have a rule to not let any "custom" (aka non-official) version of OpenBOR to be posted there. So I am deleting your link.
please, do not post it again here - unless you remove things from that person.

Officially, there was little interest of porting and supporting (personally, I like this idea) OpenBOR to PI. But after seeing stuff from that person to be used, the interest and support had dropped to like -100. There is nothing we can do to stop you guys, but there won't be any support from the official team too.

Anyway, good luck to your project.

Edit: sorry, english is not my native language and maybe I sounded wrong. The way I worded it sounds like ports are not allowed, which is not true. You guys just need to understand ports must be based on the official version for us to support them.

oilusionista

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

OpenBOR is missing a command line interface, a good program should implement something like....

According to Damon Caskey words, "OpenBOR supports several command line arguments, though honestly I don’t recall what they are. It’s been years since anyone looked at them, including me. There are no plans for a full-scale command line interface – that’s just not something I consider worth the time. However, once I complete a current project of updating script property access, I can look into the command line arguments if it will help you out."

zanac

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

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

OpenBOR is missing a command line interface, a good program should implement something like....

According to Damon Caskey words, "OpenBOR supports several command line arguments, though honestly I don’t recall what they are. It’s been years since anyone looked at them, including me. There are no plans for a full-scale command line interface – that’s just not something I consider worth the time. However, once I complete a current project of updating script property access, I can look into the command line arguments if it will help you out."

I ported last version 6412 Read better the work that i made. Command line is a must for integration in retropie, The only problem of 6412 is the resolution that i Force on start up and pak command line, if these thing will be include even My hack for run 6412 in retropie is not useful.

zanac

Dont blame o me that i based My work from the old version. This is complete false, My work was finalized to make run even last official version that using My Little hack work like a charme. Sorry i will not help again i dont want problems i have made a clean Port of last official version and they say The opposite i have not time for flames... ;(

oilusionista

@zanac I am not blaming you, really. Calm down :)
I was just trying to explain how port works for us. If the port is made from the official version, we will try to support it. But if contains any code from that version, we won't support it, sorry.

Don't get something personal when it isn't. Nobody is here to fighting - I am just give you an explanation of what happened :)

zanac

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

@zanac I am not blaming you, really. Calm down :)
I was just trying to explain how port works for us. If the port is made from the official version, we will try to support it. But if contains any code from that version, we won't support it, sorry.

Don't get something personal when it isn't. Nobody is here to fighting - I am just give you an explanation of what happened :)

Read better what i done.
Retropie need two thing that i don't see in official version..... And if you Will add a command line will be solved without need hack source like i done.
The problems are... Resolution, we need to Force a specific resolution, see My hack i simply forced 384/224 in The sdl window. If you can start with a command line in which you pass width and height this will be solved.

Second, retropie use emulation station for start games so you need a command line to start a specific pak.

Stop no other problema in official release.

After that it seems that in git we dont have source of very old version, so for run old mods like Saint seiya Death and rebirth The stupid rotfl version is still needed, or Simple say where we can find old source?!

Yes i was very upset i try to help and i have work in official release, suggest Solution that is a Simple command line and you blame me. That s crazy!

oilusionista

@zanac I do not understand why you seem so angry. It may be a language barrier, but you seem pretty angry.
There is no need to be so aggressive - other than I have no interest in fighting, okay?

Saint Seiya game comes from the BOR (and not OpenBOR) era - it was made for the PS2 port, which was discontinued. It won't probably work on the newer versions, thanks to the changes made on the video settings. And its very outdated anyway.

I'll try to explain it one last time because I'm being polite to you but my patience has limits.

I'm not blaming you for anything. I'm explaining that whatever if a port is made using the official code, we can (it's not a guarantee) to give official support. But if there is any code, however small, that comes from that version, no. Even any mention of it in the official community will be deleted.

If you are willing to help the engine, you are welcome. As long as you use the official version and calm down, okay?