OpenTTD

Tasklist

FS#6607 - Stations: additional animation triggers

Attached to Project: OpenTTD
Opened by Michael Blunck (mb) - Tuesday, 15 August 2017, 13:03 GMT
Last edited by andythenorth (andythenorth) - Friday, 01 September 2017, 10:35 GMT
Type Feature Request
Category NewGRF → NewStations
Status New
Assigned To No-one
Operating System All
Severity Medium
Priority Normal
Reported Version trunk
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

For stations it is (near?) impossible to set up *multi-tile* animations using triggers which are only happening on platforms "where the train is" (bits 3 .. 5), since the animation will only being run for those platform tiles. Since prop18 (animation triggers) is a WORD and only 7 bits are being used today, it would be feasible to add those three platform-restricted triggers for the whole station as well?
This task depends upon

Comment by andythenorth (andythenorth) - Tuesday, 15 August 2017, 16:32 GMT
So change to 'whole station' for bits 3-5 in the table here? https://newgrf-specs.tt-wiki.net/wiki/Action0/Stations#Animation_triggers_.2818.29

Does it need any toolchain update, or just OpenTTD and docs?

Does it break any existing grf behaviour?
Comment by Michael Blunck (mb) - Tuesday, 15 August 2017, 19:44 GMT
> So change to 'whole station' for bits 3-5 in the table here?

Nah, I was talking about introducing 3 new triggers, e.g.:

7 80 Train enters station (starts loading/unloading) whole station
8 100 Train leaves station (done loading/unloading) whole station
9 200 Train loads/unloads cargo whole station

> Does it need any toolchain update, or just OpenTTD and docs?

Probably 3 new constants in m4nfo and NML, besides implementation in OTTD and adding it to the specs/docs.

> Does it break any existing grf behaviour?

I donĀ“t think so, because "The remaining bits are reserved for future triggers, they must be zero for now."

Loading...