OpenBOR 6xxx OpenBeta Testphase
-
Unless I'm misunderstanding, the 6xxx OpenBOR script should be renamed to not conflict with rofl0r's OpenBOR which will stay. If that is true, and it's for sole purpose of keeping them unassociated, then maybe OpenBOR 6xxx could be named in a way that it would not conflict with the depreciated version, and can be run along side as we do.
I absolutely respect openbor team's requests of not continuing Rofl0r's work, but since that version of OpenBOR is no longer available, and Rofl0r's version is the only option, I actually think it detrimental to the creators of older, completed mods that do not work on newer versions of OpenBOR. We all already agreed we would much prefer an official source, but it's just not available.
That said, if OpenBOR 6xxx is to be a seperate script and Rofl0r's depreciated version is to remain, then I see no reason not to update it to a more functional version that you created where .paks can be used, and most importantly save states.
I found good handfull of games not working on 6xxx that worked on 3600. (Also, didn't play any enough to know if there will now be new bugs)
Also, just so I'm not mistaken, I just realized you have 3600, not 3400. Your enhanced 3600 is based off Rofl0r's build, right? And if source is found it can be compiled from original?
Thanks for your time reading all this!
-
Unless I'm misunderstanding, the 6xxx OpenBOR script should be renamed to not conflict with rofl0r's OpenBOR which will stay.
Yes, the script will be renamed to
openbor-6xxx
just to show branch development.
The resulting binary will be namedopenbor-6xxxx
just to avoid confusion
The emualtor call will be namedob6xxx
But binary and gl4es wrapper will be setted to old location
/opt/retropie/ports/openbor
The only thing I will change to old script is the location of LOG-files....
I will link to/dev/shm/
as votaile memory. This is because some modules run mad and give endless error outputs. I want avoid sd-card corruption.The old version with unpacked files can be left untouched. Some people here know how to transform the old binary to a working one with pak-support. So I think it's a way to go.
You should go to chronocrash forum, say have realy nice game developers here and some mod developers help to give weaker devices a good gaming experience.
-
@bizzar721 said in OpenBOR 6xxx OpenBeta Testphase:
rofl0r's OpenBOR
I really don't understand why do you want to take in Retropie this old version of rofl0r's OpenBOR, with or without my hack ...
It's deprecated and must be remove from Retropie-Setup, i think...On Retropie-Setup we should have OpenBOR alone, with normal name, because it is the officiel OpenBOR today and compiled for PI.
And almost all the games are working fine with it.
We should only have also the 3400 version, compiled for PI with save and pak support for some old games that works only with it and we can't update for 6xxx version ourselves ...You can make two binary installation, and two source installation for each engine compatible with all Retropie versions.
The user can install the one or two versions if he want, and when he launch his game use the runcommand menu to choose the good engine for the game.
I think it is the easier solution for everyone ;) -
@cyperghost I noticed at the OpenBOR logs were in
dev/shm
last night. I updated @darknior 's post with a good size selection of games I tested that work - most of which were unable to play on the 3600 version.I also was very pleased to see when I saved system.cfg through OpenBOR settings, those settings carried through to new mods that did not already have a config! (also noticed joypad setup on gamelist in your video) ;)
Back to what I mentioned at the end of my last post, 3600 binary you made - is that based off Rofl0r's or completely from an official source? I thought it was just an enhancement to Rofl0r's for until I realized 3600, not 3400.
I definatly think the 3600 should be considered to be installable through retropie setup - maybe not together as I was originally thinking, but there are definitely mods that run better on an older version, if they run at all. (Asterix and Ceasar's challenge crashes during gameplay in 6xxx) I found a bit more but didn't document them yet.
If your new 3600 has in fact no association with Rofl0r's, then I think this should be available as OpenBOR - 3600 and made installable from binary. I also strongly agree Rofl0r's should be removed. Anyone who already has it, nothong changes. Anyone new, will be ushered to the new 3400 & 6xxx - therefor slowy choking Rofl0r's version out of use.
-
@bizzar721 said in OpenBOR 6xxx OpenBeta Testphase:
is that based off Rofl0r's or completely
It is complete based on Rofl0r's branch. Therefore I'm not very pleased to support this. Only the 6xxx is an official branch.
-
Sorry to ask guys but after reading all of this and the other link with the experimental packaged Openbor release I can't understand at all about the installation about Openbor 6xxx version. I'm a Mod maker actually in Chrono Crash, I'm Mr.Q, and I'm working in a SNES Double Dragon based game. Can you give me the steps to get this working so I can test my beta version in my Pi3?
-
There are two ways
- If you have RetroPie 4.4 then you can install preinstalled binaries. For RetroPie 4.3 I have also a binary precompiled.
Just enter with SSH and type
wget "http://raw.githubusercontent.com/crcerror/OpenBOR-63xx-RetroPie-openbeta/master/openbor_openbeta.sh"; bash openbor_openbeta.sh galina; rm openbor_openbeta.sh
The version is installed to
/home/pi/openbor_openbeta
PAKs files can be placed to/home/pi/openbor_openbeta/Paks
if an older instance of OpenBOR was already installed then the PAK path is likely/home/pi/RetroPie/roms/ports/openbor
A script that just launches OpenBOR graphics menu will be added to PORTS section.
- Follow instructions from here: Beta scriptmodule then PAK files are placed to
/home/pi/RetroPie/roms/ports/openbor
and OpenBOR 6xxx is compiled on your own mashine. A script for selection PAK files will be place to PORTS section
Please use @ sign and write name like @mahcneto to tag people, then they will be informed of being mentioned to a post.
Welcome to our forum ;)
-
@cyperghost said in OpenBOR 6xxx OpenBeta Testphase:
It is complete based on Rofl0r's branch. Therefore I'm not very pleased to support this. Only the 6xxx is an official branch.
I know you don't want to support this release but can you share me your 3600 binary compiled for RetroPie 4.3 please ?
I really want to try it with some games to complète the 3400 and 6315 games :)
More OpenBOR version i have, more games i have a chance to launch on pi :)
Thanks -
@darknior Sorry for misunderstanding ... it's 3400 with PAK support.
Download here, you can just exchange current RetroPies OpenBOR with this one in location/opt/retropie/ports/openbor
-
@cyperghost Thank you! Just tested my WIP game and it works flawlessly! If someone wants to give it a try, it's here: https://gx-openbor.blogspot.com/2018/08/billy-lees-moveset.html
-
@mahcneto You are welcome ;) Which way for installation did you have used?
-
@cyperghost said in OpenBOR 6xxx OpenBeta Testphase:
@darknior Sorry for misunderstanding ... it's 3400 with PAK support.
Download here, you can just exchange current RetroPies OpenBOR with this one in location /opt/retropie/ports/openborOk thanks, i already have and use it :)
-
Hi, i just tried the latest build and i can see the paks listed in OpenBoR menu, however i have no input, my controller doesnt work, im using 8bitdo SF30 pro via bluetooth, any help on this?
-
@dishins Is the game selection screen your seeing the OpenBOR loader screen (red lettering, game art on top right) or @cyperghost 's script which has the blue background (like retropie setup menu)? How did you install?
-
@bizzar721 I installed as said in this post:
@cyperghost said in OpenBOR 6xxx OpenBeta Testphase:
There are two ways
- If you have RetroPie 4.4 then you can install preinstalled binaries. For RetroPie 4.3 I have also a binary precompiled.
Just enter with SSH and type
wget "http://raw.githubusercontent.com/crcerror/OpenBOR-63xx-RetroPie-openbeta/master/openbor_openbeta.sh"; bash openbor_openbeta.sh galina; rm openbor_openbeta.sh
The version is installed to
/home/pi/openbor_openbeta
PAKs files can be placed to/home/pi/openbor_openbeta/Paks
if an older instance of OpenBOR was already installed then the PAK path is likely/home/pi/RetroPie/roms/ports/openbor
A script that just launches OpenBOR graphics menu will be added to PORTS section.
- Follow instructions from here: Beta scriptmodule then PAK files are placed to
/home/pi/RetroPie/roms/ports/openbor
and OpenBOR 6xxx is compiled on your own mashine. A script for selection PAK files will be place to PORTS section
Please use @ sign and write name like @mahcneto to tag people, then they will be informed of being mentioned to a post.
Welcome to our forum ;)
I have 3 Openbor entries in my ports menu, one says ¨beta¨ and the other two are the old ones which have the selection screen or directly launch the game, neither of these my controllers are working.
Edit: i just uninstalled everything and started from scratch, now i have just 1 OpenBOR entry but my controller still not works :(
-
@dishins said in OpenBOR 6xxx OpenBeta Testphase:
t: i just uninstalled everything and started from scratch, now i have just 1 OpenBOR entry but my controller still not works :(
OpenBOR is not a libretro emulator. You need a keyboard to configure it first. There are some scripts to automate this but for now manual setup is needed
-
@dishins You could also use @cyperghost 's script module to install through experimental in retropie setup
https://retropie.org.uk/forum/topic/19326/openbor-6xxx-openbeta-testphase/35
If you are using the older OpenBOR, it will overwrite it. This will allow you to run games from a script menu that can be navigated with a controller.
-
@bizzar721 I think he tried it already. About the scriptmenu ... I think I found a why to get good results. Need just some time to test.
But I don't know if the module will be accepted in the code review ;) -
@cyperghost said in OpenBOR 6xxx OpenBeta Testphase:
But I don't know if the module will be accepted in the code review ;)
Unless you submit it, you'll never find out :).
-
@mitu Well you're right! I already asked for reference. The challange is that the description name of the script module is responsible for all pathes.
As the function are all called by local I should strip pathes. I think it's better to set all OpenBOR versions in one directory.# $1 string, $2 length function strip () { echo "${1:0:$2}" } md_id="openbor-6xxxx` md_id="$(strip $md_id -5}"
This would be my solution to strip away
-6xxx
;)
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.