Oolite Bulletins

cim wrote:

... A Cobra III has a bounding box volume of 2.5E5 cubic metres. A Coriolis has an internal volume of over 8.3E8 cubic metres, so you could fit well over a thousand Cobra IIIs inside the Coriolis ... A cargo pod has a bounding box volume of 3.6E2 cubic metres ...

El Viejo wrote:

Those hex(?) numbers make no sense to me

SandJ wrote:

The format may be familiar from spreadsheets

El Viejo wrote:

Smivs wrote:

There is no 'standard' template as such for readmes.

On the subject of readmes: is there any reason why .rtf shouldn't be used for a readme instead of .txt? Many OXP authors do use .rtf, but not all.
Rich Text Format is far more readable than .txt, which is a pain and doesn't encourage the reading of anything!

Shipbuilder wrote:

Is it possible to design a ship then have, depending on say the role, a different texture for each role type ?

For example design a ship which when used by pirates could have a skull and crossbones or similar themed texture while the same ship used by the police could have another texture altogether.

"my_ship" = {
  ...
  roles="pirate";
  model="my_ship.dat";
  materials = {..."pirate_texture.png"...};
  ...
}

"my_police_ship" = {
  like_ship="my_ship";
  roles="police";
  materials = {..."police_texture.png"...};
}

Shipbuilder wrote:

Is it possible to design a ship then have, depending on say the role, a different texture for each role type ?

cim wrote:

Shipbuilder wrote:

Is it possible to design a ship then have, depending on say the role, a different texture for each role type ?

For example design a ship which when used by pirates could have a skull and crossbones or similar themed texture while the same ship used by the police could have another texture altogether.

Yes. Define the ship for say, the pirate role:

Code: Select all

"my_ship" = {
  ...
  roles="pirate";
  model="my_ship.dat";
  materials = {..."pirate_texture.png"...};
  ...
}

Then define the police role using like_ship

Code: Select all

"my_police_ship" = {
  like_ship="my_ship";
  roles="police";
  materials = {..."police_texture.png"...};
}

When you use like_ship, any parameters not specified in the ship definition will be taken from the base ship definition - so here we override roles and materials, but leave the rest the same - in practice you might want to change a little more than that.

"my_player_ship" = {
  like_ship="my_ship";
  roles="player";
  materials = {..."player_texture.png"...};
}

Thargoid wrote:

Or alternatively you can do it by scripting, so on spawning/launch the ship skin gets set on the fly. Both materials and shaders are fully visible to script (hence you can have the ships skin change, for example as the ship becomes damaged - see my Swarm thargoid warship for example).

Smivs wrote:

Yes, easily done.
For a comprehensive example take a look at my Smivs'Shipset (the Adder is probably as good a one to look at as any)...

Smivs wrote:

It's "EQ_HARDENED_MISSILE"

Aaaargh! Ninja'd

PS please consider moving to OpenStep