| Commit message (Collapse) | Author | Age |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
something
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This was a pain... but all the coords make much more sense now and a lot of mystery negation has disappeared.
|
| |
|
|
|
|
| |
Encompasses determining a route and a distance to travel
|
| |
|
| |
|
|
|
|
|
| |
This makes more sense when you realise that the existing navigation
workings work on exactly the same type!
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
I think it's fair to make all vehicles uses links and nodes to navigate... even if those links, nodes are
private to that vehicle
|
|
|
|
| |
Has the main window provide some control over our test train
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Derives lots more info directly from the model
|
|
|
|
| |
Not an instance of the vehicle.
|
| |
|
|
|
|
| |
Rails in this case.
|
|
|
|
| |
Simpler, unbinds the transformation matrices for location, now done just in the shader.
|