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
For example:
const string RANGEFINDER_TARGET_FORMAT = "{3}";
will just output the raw range (and only the range) to all text panels in the CM Target group. You can add whatever embellishments you like, like "Range: {3} m" or (what I would use) "Range: {3:F2} m" (the latter will round to 2 decimal places)
Otherwise, check out this version of the script [gist.github.com] which outputs to text panels the same thing that is displayed in the terminal. It's untested though and I have no plans to support that modified version.
I haven't had a chance to play around with the Raycast stuff in the dev branch, but depending on how far cameras can scan, coincidence rangefinders (such as this script) may be obsolete. But I'll wait til it hits stable.
But if you want an actual GPS coordinate that appears in your list, you have to make the edit I mention above to RANGEFINDER_TARGET_FORMAT and then look at (or edit) the text panel after you get your range.
Unfortunately, that's the only way to pass GPS coordinates from scripts to players.