OpenBOR

OpenBOR 3.0 Build 3769 - 6391

No permission to download
Overview History Discussion
DCurrent

DCurrent

Site Owner, OpenBOR Project Leader
Staff member
For anyone not aware, 3.0 builds back to 3769 (the earliest official release available after migration from Sourceforge) have always been accessible via a "Legacy Build" entry in the GitHub repository. I had thought that would make builds easier to find, but apparently it had the opposite effect. My apologies. I've now mirrored 3.0 builds as a ChronoCrash resource.

Not much to say or discuss about the builds themselves. Though before anyone asks, since it's been asked ad infinitum already - I will not be making any retroactive fixes or updates. If you choose to use a legacy build for new projects, that is your responsibility.

DC
 
What about the ones older than 3769? I mean I have some older versions from over a decade ago, but we don't have to include some of the ones that break the engine's (core) system.

There may be some versions between 3769 and 6391 missing such as 3945, 4153, 4396, and 4426 (not listed as part of v3.0 builds). However, I'm aware of the mess anallyst had done in some old versions before he was demoted off from developer role due to some functions not working. That was probably back before 3769? I still remember it was around like 3711 and on until 3769, but I can't remember exactly which build had/started its system problem.

I can share some older builds (3711 and below) I have here whether they are part of the official releases or not. But I'm not asking anyone to change what older builds need to be fixed. I'm just letting this community know that I have some of them to share. We leave/let the older builds the way they are. I don't remember if they are official or not nowadays, but from the times of Lavalit, I remember they were released officially during @SX's time as well as @DCurrent's. Let me know if I misremembered. If there are builds that are deemed official for v3.0, they can be uploaded here. If they're unofficial, they shouldn't be uploaded but can be shared as attachments (I guess?). (If you don't mind, I can share 'em here.)

For anyone who asks about 6392 or 6412, I don't think either of those are official for OpenBOR. And for those of you who ask about fixing older builds for (only) your specific needs, please don't. You guys should not make/let him waste his breath on changing older builds. What's the point (of doing things unnecessary like this)? For those of you who want to port their own OpenBOR projects to very older consoles like DreamCast, you're on your own. Please don't ask the staff to help you on projects you work on with older builds, especially changing unnecessary stuff from older builds.

If I knew how to port one OpenBOR project into a specific game console like DreamCast, PSP, or PSVita, I would use a specific build that can work well for porting to a mentioned game console. But, as a result, I would need to find which part of the code can work for porting to it.

Also, no port begging, please. 🙏

I don't mean to be rude or demeaning, but I'm (just) addressing about including the remaining v3.0 builds whether they're official or not.
 
maxman said:
What about the ones older than 3769? I mean I have some older versions from over a decade ago, but we don't have to include some of the ones that break the engine's (core) system.

There may be some versions between 3769 and 6391 missing such as 3945, 4153, 4396, and 4426 (not listed as part of v3.0 builds). However, I'm aware of the mess anallyst had done in some old versions before he was demoted off from developer role due to some functions not working. That was probably back before 3769? I still remember it was around like 3711 and on until 3769, but I can't remember exactly which build had/started its system problem.

I can share some older builds (3711 and below) I have here whether they are part of the official releases or not. But I'm not asking anyone to change what older builds need to be fixed. I'm just letting this community know that I have some of them to share. We leave/let the older builds the way they are. I don't remember if they are official or not nowadays, but from the times of Lavalit, I remember they were released officially during @SX's time as well as @DCurrent's. Let me know if I misremembered. If there are builds that are deemed official for v3.0, they can be uploaded here. If they're unofficial, they shouldn't be uploaded but can be shared as attachments (I guess?). (If you don't mind, I can share 'em here.)

For anyone who asks about 6392 or 6412, I don't think either of those are official for OpenBOR. And for those of you who ask about fixing older builds for (only) your specific needs, please don't. You guys should not make/let him waste his breath on changing older builds. What's the point (of doing things unnecessary like this)? For those of you who want to port their own OpenBOR projects to very older consoles like DreamCast, you're on your own. Please don't ask the staff to help you on projects you work on with older builds, especially changing unnecessary stuff from older builds.

If I knew how to port one OpenBOR project into a specific game console like DreamCast, PSP, or PSVita, I would use a specific build that can work well for porting to a mentioned game console. But, as a result, I would need to find which part of the code can work for porting to it.

Also, no port begging, please. 🙏

I don't mean to be rude or demeaning, but I'm (just) addressing about including the remaining v3.0 builds whether they're official or not.
Click to expand...

The builds I posted were all the official builds, meaning ones we compiled and posted and are (reasonably) stable. There are plenty of other builds, but those were dev builds. The biggest problem with anything older than posted is they predate the move from Sourceforge, which I never had admin access to and so don't have any way at all to document what they are. I wouldn't even be able to tell you if they were version 1, 2, or 3.

DC
 
O Ilusionista said:
you can find them in Source Forge
Click to expand...

Oh, I forgot there was a list of builds there. Thanks @O Ilusionista. I'll try to mirror those too when I get a chance. Since they are marked version 3, that helps a lot, though as mentioned above, I don't have have any release notes for them.

*Edit for clarity:* To be more accurate, there are commit notes - kind of. Thing is though, subversion source control (Sourceforge) is very different from git source control (GitHub). Back then releases were decoupled from updates, so there's no 100% sure way to tell which release ties to what update notes.

DC
 
Last edited:
DCurrent said:
Oh, I forgot there was a list of builds there. Thanks @O Ilusionista. I'll try to mirror those too when I get a chance. Since they are marked version 3, that helps a lot, though as mentioned above, I don't have have any release notes for them.

*Edit for clarity:* To be more accurate, there are commit notes - kind of. Thing is though, subversion source control (Sourceforge) is very different from git source control (GitHub). Back then releases were decoupled from updates, so there's no 100% sure way to tell which release ties to what update notes.
Click to expand...
i know nothing of this matters but if it worth something i use 6392, and at the time it was along with similar numered builds, side worked by kratus if i recall correctly most notably(in my case) fixed an joystick maping bug, and and if i recall too they were superviced by you and eventully merged to 4.0
 
You must log in or register to reply here.
Back
Top Bottom