Page 1 of 1
Distinguish Oolite and Oolite Debug version?
Posted: Sun Aug 22, 2021 9:33 am
by hiran
If you just know the path to some Oolite installation, is there a secure way to tell whether it is the 'normal' or the 'debug' version just by looking at the files?
Re: Distinguish Oolite and Oolite Debug version?
Posted: Sun Aug 22, 2021 9:49 am
by Cody
I've probably misunderstood*, but debug versions have odd numbers (1.91), whereas normal versions have even numbers (1.90).
It's Sunday, and I ain't had my morning caffeine fix yet!
Re: Distinguish Oolite and Oolite Debug version?
Posted: Sun Aug 22, 2021 9:51 am
by another_commander
Regarding Windows 64-bit and Oolite version 1.90:
1. The debug version installs the folder <gameInstallFolder>/AddOns and inside it the folder Basic-debug.oxp along with all its files. The "normal" version does not install these folders.
2. The game executable of the "normal" version has a size of 5,472,768 bytes. The debug release executable has a size of 6,234,112 bytes.
Re: Distinguish Oolite and Oolite Debug version?
Posted: Sun Aug 22, 2021 9:57 am
by hiran
another_commander wrote: ↑Sun Aug 22, 2021 9:51 am
Regarding Windows 64-bit and Oolite version 1.90:
1. The debug version installs the folder <gameInstallFolder>/AddOns and inside it the folder Basic-debug.oxp along with all its files. The "normal" version does not install these folders.
2. The game executable of the "normal" version has a size of 5,472,768 bytes. The debug release executable has a size of 6,234,112 bytes.
Number one sounds like a good criteria. Number two looks a bit volatile as future builds will definitely modify file sizes.
I will try the first one then...
Edit: I can confirm the Linux version behaves the same way.
Re: Distinguish Oolite and Oolite Debug version?
Posted: Sun Aug 22, 2021 10:40 am
by Cholmondely
hiran wrote: ↑Sun Aug 22, 2021 9:57 am
another_commander wrote: ↑Sun Aug 22, 2021 9:51 am
Regarding Windows 64-bit and Oolite version 1.90:
1. The debug version installs the folder <gameInstallFolder>/AddOns and inside it the folder Basic-debug.oxp along with all its files. The "normal" version does not install these folders.
2. The game executable of the "normal" version has a size of 5,472,768 bytes. The debug release executable has a size of 6,234,112 bytes.
Number one sounds like a good criteria. Number two looks a bit volatile as future builds will definitely modify file sizes.
I will try the first one then...
Edit: I can confirm the Linux version behaves the same way.
So I've three versions on my desktop which I use: Oolite 1.77, Oolite 1.90 & Oolite 1.9TR (debug version) all labelled accordingly. The old version is good for old OXP's (before cim's changes), and Spara had me add the debug version for his tutorial on the SothisTC oxp.
Re: Distinguish Oolite and Oolite Debug version?
Posted: Sun Aug 22, 2021 10:43 am
by hiran
Cholmondely wrote: ↑Sun Aug 22, 2021 10:40 am
hiran wrote: ↑Sun Aug 22, 2021 9:57 am
another_commander wrote: ↑Sun Aug 22, 2021 9:51 am
Regarding Windows 64-bit and Oolite version 1.90:
1. The debug version installs the folder <gameInstallFolder>/AddOns and inside it the folder Basic-debug.oxp along with all its files. The "normal" version does not install these folders.
2. The game executable of the "normal" version has a size of 5,472,768 bytes. The debug release executable has a size of 6,234,112 bytes.
Number one sounds like a good criteria. Number two looks a bit volatile as future builds will definitely modify file sizes.
I will try the first one then...
Edit: I can confirm the Linux version behaves the same way.
So I've three versions on my desktop which I use: Oolite 1.77, Oolite 1.90 & Oolite 1.9TR (debug version) all labelled accordingly. The old version is good for old OXP's (before cim's changes), and Spara had me add the debug version for his tutorial on the SothisTC oxp.
...and the Oolite Communicator requires the debug version to be launched - the others do not contain the Debug Console protocol and thus would never speak to the communicator.
Since the current version is able to automatically launch Oolite (it just needs to be configured where Oolite is installed) in future it checks and warns the user if no debug version is found.