Moderator: OpenTTD Developers
1. Train::UpdateSpeed in train_cmp.cpp says that a train can travel 3/4 cur_speed every tick.
2. TrainLocoHandler in train_cmp.cpp advances the train one pixel for each 192 accumulated speed (assuming the train is moving parallel to the gridlines).
3. TileVirtXY in map_func.h suggests that one tile is 16 pixels wide.
Now assuming there are 74 ticks in one day, a train travelling at speed 160 (which corresponds to 100mph right?) should move (74*3/4*160)/192/16 = 2.89 tiles per day. Could anyone point out what part(s) of this calculation is(are) wrong?
Squid Ate FISH (ships) (Released) | CHIPS Has Improved Players' Stations (Finished)
Iron Horse (trains, released) | Termite (tracks for Iron Horse, released) | Busy Bee (game script, released)
Road Hog (road vehicles, released)
Except classical geometry doesn't really work in TTD land. TTD's squares are actually circles.andythenorth wrote:To find out how fast they are *actually* moving I would count the number of pixels they travel per second. Because they are usually moving diagonally, you may need some help from our friend pythagoras
They're not squares or diamonds.audigex wrote:Squares don't look like squares in OTTD, you have to use diamonds instead.
If we need a diamond, we usually just tape a bunch of triangles together.
Check out how many regular-length train vehicles fit on a tile in each of the 4 orientations...
Users browsing this forum: No registered users and 5 guests