For information and discussion about Oolite.
https://bb.oolite.space/
I think that Tianve OXP does an excellent job of simulating a nebula.pagroove wrote:I like what you've done with the space colors. Is that feature easy to implement for oxp-makers? Could you even make it yellow/red/green?
Then you could simulate that the planet in question lies within a nebula.
I like to see nebula's included one day in Oolite.
The colour values at the moment are part of the source code, but it probably wouldn't be hard to have it referenced in planetinfo.plist instead. Problem is at the moment the code in the source controls all space so it would have to be changed to reflect on what galaxy number and what system number the player is currently in. But I don't see why not I will look into this.pagroove wrote:I like what you've done with the space colors. Is that feature easy to implement for oxp-makers? Could you even make it yellow/red/green?
Then you could simulate that the planet in question lies within a nebula.
Exciting times, eh? My guess is it will be a boy or a girl!Pleb wrote:Also same day finding out sex of the baby!
I don' know about any of that technical stuff, but I know I accidentally created a galaxy with 257 systems last week (using unhacked 1.76.1).SandJ wrote:If system -1 is interstellar space, then the system number is not an 8 bit unsigned integer.
That means the 256-system limit is not a fixed limit; there could be up to 32767 systems per galaxy!
The numbers 255 and 256 keep coming up in 8-bit games because you can either store 256 numbers in 8 bits: either the values 0..255 in 8 bits ("unsigned") or the values -128..+127 in those 8 bits ("signed").Wildeblood wrote:I don't know about any of that technical stuff, but I know I accidentally created a galaxy with 257 systems last week (using unhacked 1.76.1).SandJ wrote:If system -1 is interstellar space, then the system number is not an 8 bit unsigned integer.
That means the 256-system limit is not a fixed limit; there could be up to 32767 systems per galaxy!
From OOTypes.h...SandJ wrote:The numbers 255 and 256 keep coming up in 8-bit games because you can either store 256 numbers in 8 bits: either the values 0..255 in 8 bits ("unsigned") or the values -128..+127 in those 8 bits ("signed").
An Oolite galaxy has 256 systems because that was an easy thing to handle on those old 8-bit BBC, Spectrum, etc. computers.
But Oolite has a system number of -1 to represent interstellar witchspace, so the system number cannot be being stored in an 8 bit variable. The next size limit is 16 bits and since it must be signed (to hold -1), that would allow -32768..+32767.
Code: Select all
typedef uint8_t OOGalaxyID; // 0..7
typedef int16_t OOSystemID; // 0..255, -1 for interstellar space (?)
enum
{
kOOMaximumGalaxyID = 7,
kOOMaximumSystemID = 255,
kOOMinimumSystemID = -1
};You have a 2560-pixel wide monitor? Sigh.SandJ wrote:(Since we are all running on 32-bit machines or better, it may well be that 2,147,483,647 systems per galaxy is possible... which would mean about 655 systems on every point of the 2560x1280 point galaxy!)
This doesn’t actually follow. It would be entirely possible for the game to store an eight-bit galaxy ID but return -1 to the scripting interface if there’s no sun in the current system.SandJ wrote:If system -1 is interstellar space, then the system number is not an 8 bit unsigned integer. :twisted:
Not strictly true; it could just as easily be four or sixteen regardless of the bitness of the system. Eight is a design decision. Other numbers would be much more expensive on eighties systems because they didn’t have hardware division. (Well, technically, to divide by a constant quickly it’s sufficient to have hardware multiplication, which is much cheaper than division.)Wildeblood wrote:The other number that keeps coming up, because of Elite's 8-bit origin, is eight. There are eight government types and eight economy types.
No it is not an 8bit unsigned integer it is in fact a 16bit integer, as you can see from the code below:SandJ wrote:If system -1 is interstellar space, then the system number is not an 8 bit unsigned integer.
Code: Select all
typedef uint8_t OOGalaxyID; // 0..7
typedef int16_t OOSystemID; // 0..255, -1 for interstellar space (?)
enum
{
kOOMaximumGalaxyID = 7,
kOOMaximumSystemID = 255,
kOOMinimumSystemID = -1
};This is something else I wondered about, adding more governments, economies, etc... The first problem with this is that it would change the government types for Galaxies 1-8, which is a big no-no in my book. The second problem is how to go about having Galaxies 1-8 populated using the original/current algorythum and the newer Galaxies 9-16 using a different one. If this was possible, then other features could be added such as changing the way system names are generated to include the missing letters.Ahruman wrote:Not strictly true; it could just as easily be four or sixteen regardless of the bitness of the system. Eight is a design decision. Other numbers would be much more expensive on eighties systems because they didn’t have hardware division. (Well, technically, to divide by a constant quickly it’s sufficient to have hardware multiplication, which is much cheaper than division.)Wildeblood wrote:The other number that keeps coming up, because of Elite's 8-bit origin, is eight. There are eight government types and eight economy types.
The obvious solution is to define the information through planetinfo.plist rather than using seeded random generation at runtime. (Generate the planetinfo.plist using a RNG to get the first 8 galaxies the same as before, sure...)Pleb wrote:The second problem is how to go about having Galaxies 1-8 populated using the original/current algorythum and the newer Galaxies 9-16 using a different one. If this was possible, then other features could be added such as changing the way system names are generated to include the missing letters.
My mistake. What I mean is, the systems are located on a 256 x 128 grid, where the points are in steps of 0.1 - but they are in steps of 1 so there are 256 x 128 possible locations, not 2560 x 1280.Wildeblood wrote:You have a 2560-pixel wide monitor? Sigh.SandJ wrote:(Since we are all running on 32-bit machines or better, it may well be that 2,147,483,647 systems per galaxy is possible... which would mean about 655 systems on every point of the 2560x1280 point galaxy!)
Actually it's a 256x256 grid, but the spacing between grid points is larger in one direction than the other, so 65536 possible positions.SandJ wrote:My mistake. What I mean is, the systems are located on a 256 x 128 grid
[...]
Gelegeus (253,159)
And I even provided the evidence to prove myself wrong.cim wrote:Actually it's a 256x256 grid, but the spacing between grid points is larger in one direction than the other, so 65536 possible positions.SandJ wrote:My mistake. What I mean is, the systems are located on a 256 x 128 grid
[...]
Gelegeus (253,159)
), but after a small amount of tweaking I've figured out how to create a reversible Galactic Hyperdrive...well a piece of equipment that is single use like the Galactic Hyperdrive itself. Two source files need to be edited to achieve this, and a new entry needs to be added to the equipment.plist file. I used the source code from version 1.76.1.Code: Select all
OOINLINE int rotate_byte_left (int x) INLINE_CONST_FUNC;Code: Select all
OOINLINE int rotate_byte_right (int x) INLINE_CONST_FUNC;Code: Select all
OOINLINE int rotate_byte_left(int x)
{
return ((x << 1) | (x >> 7)) & 255;
}Code: Select all
OOINLINE int rotate_byte_right(int x)
{
return ((x >> 1) | (x << 7)) & 255;
}Code: Select all
galaxy_number++;
galaxy_number &= 7;
galaxy_seed.a = rotate_byte_left(galaxy_seed.a);
galaxy_seed.b = rotate_byte_left(galaxy_seed.b);
galaxy_seed.c = rotate_byte_left(galaxy_seed.c);
galaxy_seed.d = rotate_byte_left(galaxy_seed.d);
galaxy_seed.e = rotate_byte_left(galaxy_seed.e);
galaxy_seed.f = rotate_byte_left(galaxy_seed.f);Code: Select all
// Check if the GH Reverse Unit equipment is present:
if ([self hasEquipmentItem:@"EQ_GAL_DRIVE_REVERSE_UNIT"])
{
// Decrease galaxy number and do it in a safe way:
if (galaxy_number > 0)
{
galaxy_number--;
}
else // we are at galaxy 0, now we need to cycle to 7
{
galaxy_number = 7;
}
// Rotate Galaxy Seed right instead of left to change to previous Galaxy Seed:
galaxy_seed.a = rotate_byte_right(galaxy_seed.a);
galaxy_seed.b = rotate_byte_right(galaxy_seed.b);
galaxy_seed.c = rotate_byte_right(galaxy_seed.c);
galaxy_seed.d = rotate_byte_right(galaxy_seed.d);
galaxy_seed.e = rotate_byte_right(galaxy_seed.e);
galaxy_seed.f = rotate_byte_right(galaxy_seed.f);
// Remove the GH Reverse Unit equipment:
[self removeEquipmentItem:@"EQ_GAL_DRIVE_REVERSE_UNIT"];
}
else
{
galaxy_number++;
galaxy_number &= 7;
galaxy_seed.a = rotate_byte_left(galaxy_seed.a);
galaxy_seed.b = rotate_byte_left(galaxy_seed.b);
galaxy_seed.c = rotate_byte_left(galaxy_seed.c);
galaxy_seed.d = rotate_byte_left(galaxy_seed.d);
galaxy_seed.e = rotate_byte_left(galaxy_seed.e);
galaxy_seed.f = rotate_byte_left(galaxy_seed.f);
}Code: Select all
(
10, 50000, "GH Reverse Unit",
"EQ_GAL_DRIVE_REVERSE_UNIT",
"A single use device that forces the Galactic Hyperdrive to enable travel to a previous galaxy.",
{
available_to_all = true;
}
),