Looky1173
commented
9 years ago Imported from https://bugs.launchpad.net/or/+bug/1456164/comments/1
| Property | Value |
|---|---|
| Posted by | r.roeterdink (r-roeterdink) |
| Date posted | Mon, 18 May 2015 12:11:02 GMT |
I would also prefer that the figures were given as a ratio as that is the way they are represented on published gradient profiles, (perhaps could be achieved by the reciprocal of the %age gradient).That rather depends on the country of origin. Here in continental Europe, all gradients are, and always have been, expressed as percentage (or permillige, if that is the correct word - expressed as 0/00, so 1 0/00 is 0.001). So the best way out would be a user option for the required format.
Imported from https://bugs.launchpad.net/bugs/1456164
I do not think this is a bug but perhaps more wish list or preference. There are a number of things that I consider odd about the gradient presentation in the HUD. The first is that when 'vibration' is activated the gradient alters 'in tune' with the vibration. As the gradient of the track is fixed, this ought not to happen. When the gradient is negative the negative operand is shown in black not white. This can make it hard to see against a dark background. It would be better if it was white as the rest of the digits. A second decimal point would give a better resolution as some of the gradients measure as little as 1 in 1700. I would also prefer that the figures were given as a ratio as that is the way they are represented on published gradient profiles, (perhaps could be achieved by the reciprocal of the %age gradient). This may not be relevant to MSTS routes which in a lot of cases do not follow published gradient profiles, however as Open Rails gains prominence a more accurate gradient profile may be the norm. Other than that excellent so far. Keep up the good work. The more I use it the better I like it.