Because many times people asking the same thing, I think a own topic is necessary now.
Action 0B will be GRF Action code for a new eye candy graphics.
It's the concept to give the ability to show TTD objects with different sprites (sets),
for rail station the sets can be adjusted by the user.
This should make things possible you see here:
http://www.ewetel.net/~michael.blunck/t ... albox2.png
http://www.ewetel.net/~michael.blunck/t ... actory.png
http://www.ewetel.net/~michael.blunck/ttd/cargo.png
This pics were made with a proof of concept hack of 1.9.1 exp-alpha 49a
The current Draft for the new action is this (a copy of the text on my site):
Code: Select all
TTDPatch-RFC Eye-Candy Action B
Version: 0.2a
Date: 2003/08/07
Author: Oskar Eisemuth
Action B: Defines new eyecandy set
~~~~~~~~~
May appear anywhere in the .grf file.
Data is <num-version> <set-type> <num-set> <bit-cap> <num-sprites> <pointers>
B num-version versionsnumber
0 eyecandy alpha
B set-type Type of set.
(Basenum will be used in the calc later,
if no basenum, this stuff isn't currently supported)
0 rail stations (basenum = 18)
1 road stations
2 airports
3 ship
4 railways
5 roads
6 bridges
7 tunnel
6 town buildings
7 industry buildings.
8 company headquarters
9 lighthouses
255 rail station placement array (special see annotation)
B num-set The set number which can be in the range of 0-7
following grf can overwrite a set...
B bit-cap capabilities of this set
bit 0 snow sprites
all others to zero!
W num-sprites How many following sprites this set use
W pointers Word pointers to the sprites, the size can be calculated with this:
basenum (* 2 for snow)
set-type = 255: (Station placement array)
Data is <num-version> FF <num-set> <num-bytes> <byte stream of station arrays of 777 Bytes>
W num-bytes = 777
Currently no build year, (when a set becomes available)
How station size could be limited (so it could be work with signal boxes Michael has drawn)
How random sprite selection in a set could work.
Comments, Ideas welcome.