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
More details, for anyone who is interested in the behind-the-scenes work: Some people call this the "detector range" or "scan range" or "ping". The detector itself does have a range, but this problem is specific to how the playfield is configured. There are many playfield directories in the scenario. For each planet, you will see a file called playfield_static.yaml, in each planetary playfield subdirectory. For the starting planet, the directory is JS_DesertStarter. The POI's and the HV's are spawned randomly from groups. These groups have two settings called MapDistance and HudDistance, which are relevant here. Previously, I had MapDistance=500 and HudDistance=100 set for both POI's and HV's. Now I have removed MapDistance/HudDistance from POI's, and I have MapDistance=0 for HV's, in the next version. These new settings match what was in Star Salvage. Once the new version is released, give it a try and let me know what you think. I'm happy to adjust it as needed.
Your videos on creating new wrecks for SS are how I found your YouTube channel back then and wound up subscribing.
Thanks again and happy New Year!