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
i have a Issue though. Im trying to use it with the Small Grid Cab Cockpit and it doesn´t work.
Like, for Occupied, I want it to also show a custom line of text before and/or after it says "Occupied No/yes"
For Example:
"Left Driver Seat - Occupied No/Yes"
FYI you can gain much more performance by not using "*" in commands and instead limiting it to specific blocks (the less blocks that fit the name filter the faster the script can walk through all of them when processing command).
There are several drawbacks in usability when using TextLCD (original LCD scrolling and TextLCD not updating fast enough, TextLCD does not format text based on LCD/font size it just copies text, its updating slowly or unnecessarily faster than command output you are copying, etc, etc). The performance gain may be negligible and may be even negative.
Things I wish TextLCD had.
1. Ability to grab form multi display blocks.
Example command for grabbing a specific display might be TextLCD {Cockpit - Main:4}
2. Start line option.
Example TextLCD {Cockpit - Main:4} 2
Returns form line 2 to end of captured display.
3. Capture lines option.
Example TextLCD {Cockpit - Main:4} 2 2
Returns lines 2-3 of captured display.
4. Alignment options L, the default, C, and R.
Example TextLCD {Cockpit - Main:4} 2 2 C
Returns lines 2-3 of captured display, centering the lines.
I'd definitely love to set up the ship/station time display once; then use something like TextLCD {TimeLCD} C everywhere instead of TimeC
Just some ideas. Great script. :-)
@Leconite It all depends on the commands and how many blocks you have, strictly technically TextLCD is better performance wise, practically use what fits your needs, there are a lot of caches and optimizations in the script.
From a performance standpoint is it more efficient to used the same command set on multiple LCD's or to use TextLCD to throw the results of a single command set to multiple displays?
I think the latter, but was not sure if the script internally cached the results of running the duplicate commands.
From a reliability / survivability standpoint multiple duplicate command sets work as it eliminates the single point of failure.
I'm trying to use the PropBool command with a sensor in order to display whether the sensor has been triggered. According to Malware's API index, IsActive is available for sensors but the PropBool command doesn't seem to recognize it as a valid property. I noticed in the guide the URL you provided to Malwares list isn't the same as the API list and that IsActive isn't one of the available properties for sensors in that link. Is it safe to say AutoLCDs2 doesn't use the API members?
This is my custom data command for context: PropBool {[DEF] Sensor D3-S/A Computer Core} {IsActive} {Starboard Computer Core} {Intruder} {Clear}