Steam'i Yükleyin
giriş
|
dil
简体中文 (Basitleştirilmiş Çince)
繁體中文 (Geleneksel Çince)
日本語 (Japonca)
한국어 (Korece)
ไทย (Tayca)
Български (Bulgarca)
Čeština (Çekçe)
Dansk (Danca)
Deutsch (Almanca)
English (İngilizce)
Español - España (İspanyolca - İspanya)
Español - Latinoamérica (İspanyolca - Latin Amerika)
Ελληνικά (Yunanca)
Français (Fransızca)
Italiano (İtalyanca)
Bahasa Indonesia (Endonezce)
Magyar (Macarca)
Nederlands (Hollandaca)
Norsk (Norveççe)
Polski (Lehçe)
Português (Portekizce - Portekiz)
Português - Brasil (Portekizce - Brezilya)
Română (Rumence)
Русский (Rusça)
Suomi (Fince)
Svenska (İsveççe)
Tiếng Việt (Vietnamca)
Українська (Ukraynaca)
Bir çeviri sorunu bildirin
COUNTWORKING -> same as COUNT, but excludes not working (off, incomplete) blocks
ANTENNARANGE -> Shows selected antenna Range in % to max
COUNTITEM -> add also tools and other items that are not included yet
Graphs:
Horizontal Bar, alternative designs (segmented etc), Percentage as Text
Others:
Fix Text alignment...
Radiation, Antenna, Landing Gear, Jump Drive
Fixing the "WORKING" to work with not only IMyFunctionalBlock but all IMyCubeBlock types (where it inherits from)
Also if a weapons or cargo container is damage beyond functionality should show inventory as zero. Maybe you can add a bool value to enable or disable the feature.
I missing the ability text from other scrips on the same display as the graphs from InfoGraphx. Example: I like to have flights speed, breaking speed on my flight seat https://ibb.co/JsNxP8j
@VirtualGaming: Airpressure is lready built in. UPDATE:AIRPRESSURE:.... does the trick. read the manual for the different states represented by the %.
PS: I have already implemented a few things like items and update modes, but I need a bit more time for the rest of the features. A release is likely for next weekend - but that's not a promise :)
In this variation, only one display will update per execute. This result in a latenz by the visualization. But it safes a lot of execution time. Now the execution time is only by up to 1ms/frame. And the execution time is undependend from the amount of used lcds.
Maybe it helps :)