Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Yes. It changed in the last couple of weeks.
There is a very important difference between upper and lower case characters.
KM, M, H do not refer to kilometer, meter and hour at all. The proper and only correct units (and prefixes) are km, m and h.
There is no such prefix as K and it stead is k. The meter got m and no M. A second got s and not S. Likewise the hour got h and not H.
Thus forms like these are wrong (in the context of velocity or distance):
MS
M/S
M/s
m/S
Km
KM
KM/H
KPH
The reason for that is rather simple. It is a standard and lower as well as upper case chars often got different meanings.
The best example here is the upper case K which actually stands for the unit kelvin and either is the temperature relative to absolute zero with steps like the celsius scale or it is a temperature difference between two celsius values (the difference between 12°C and 22°C is 10K and not 10°C when being technically correct)
I know people are lazy. Some are ven so terribly lazy that even though they know they do things wrong they simply dont care and say "but context" (which works 90% of the time when you use utterly trivial cases but quickly fall apart once you use more complex situations with units like K kg s² / m)
So to convert from km to m and from m to km we use the wonders of SI prefixes which are based around 10 and no arbitrary 3, 12, 16, 18, 21 and whatever other multiplier the antiquated variants utilize.
We know that the prefix k stands for a multiplier of 1000.
If you didnt know, this small article helps: https://en.wikipedia.org/wiki/Metric_prefix
Thus 1 km = 1 000 m and 1.5 km = 1.5 * 1 000 m = 1 500 m.
If you had 1 700 m and wanted to get it in km you had to divide by 1000 and thus get 1.7 km.
Thus that kind of math should be the easiest kind. You multiply by a 10er based value and actually shift the decimal mark to the right.
If anyone comes along having an issue with the conversion from km/h to m/s, it is equally simple.
1 km / h = 1 000 m / 60 min = 1 000 m / 3 600 s = 1 / 3.6 * m / s
or
1 m / s = 3.6 km/h
I hope that clears up some confusion.
*sarcasm*
First, m/s is a valid velocity. You even use it yourself. (I think you were trying for m/S, but I can only assume.)
Second, you need to be consistent with the symbols you use. You suggest moving the comma, yet you never used it yourself. Either your numbers are wrong or you should have said "decimal point." I know it's a regional thing. Different places do things differently but you should at least be consistent.
*/sarcasm*
Sorry, I just had to do it. The only reason there was confusion in this post was because the OP left out important contextual information and not because they used improper abbreviations. Sadly, I think you wasted your perfectly good rant. My condolences.
Back to the topic.
I thought this kicked on only for really far objects. It makes sense when you're talking about being 300 million meters from an object. Even 10 thousand meters is better expressed 10km. But within only a few thousand meters I prefer it in plain old meters. I'll need to go test this all out now. Also, I wonder if they can add it as an option so you can select when it changes over. In the game options not the world options.
I indeed intended to use another example with like S for "seconds" which actually is siemens.
The comma also is the decimal mark here so you guessed correct twice.
Dont worry, that was no rant at all. It is merely an attempt to tell people what the correct way for these units is other than they use them while hoping that it improves the situation.
Maybe a few learn something new because they simply arent aware of the correct forms.
Well subjective preferences. I actually prefer 1.2 km over 1 200 m. Though i also dont care much about it being one way or another as both mean the same.
Also as there is little, if not even none at all, practical difference between 1 200 m, 1 205 m and 1 249 m for flying a ship around, i dont see much of a need to actually change it.
Though i agree that having a setting for the prefix and rounding rules would be pretty neat.
So one could apply rules like:
- round to 1, 2 or 3 digits past the decimal mark
- use the next bigger prefix with a value above 1 000, 2 000, 10 000 or 100 000 etc.
The more porper customization there is the better.