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
https://imgur.com/CRvVO5G
For example: Q = {100, 0, 0, 100} → Q = {10000, 0, 0, 10000}.
When active sonar detects a target it actually has a range to target and it displays that target for a certain amount of time... for passive it shows a smaller box (possibly a different/customizable color) for targets that are detected (but obviously it has no distance information).
i'm using a medium camera but it doesn't allows me to connect it
I figured it was a me-issue at first but other workshop entries work just fine. I've tried both restarting my game and re-subscribing. Any ideas?
target1 (1~3 local x,y,z, 4 speed), target2 (5~7 local x,y,z, 8 speed) ...
>using this many lua scripts leads to bad tick delay