安裝 Steam
登入
|
語言
簡體中文
日本語(日文)
한국어(韓文)
ไทย(泰文)
Български(保加利亞文)
Čeština(捷克文)
Dansk(丹麥文)
Deutsch(德文)
English(英文)
Español - España(西班牙文 - 西班牙)
Español - Latinoamérica(西班牙文 - 拉丁美洲)
Ελληνικά(希臘文)
Français(法文)
Italiano(義大利文)
Bahasa Indonesia(印尼語)
Magyar(匈牙利文)
Nederlands(荷蘭文)
Norsk(挪威文)
Polski(波蘭文)
Português(葡萄牙文 - 葡萄牙)
Português - Brasil(葡萄牙文 - 巴西)
Română(羅馬尼亞文)
Русский(俄文)
Suomi(芬蘭文)
Svenska(瑞典文)
Türkçe(土耳其文)
tiếng Việt(越南文)
Українська(烏克蘭文)
回報翻譯問題
const int OnOffChance = 70; // percent
const int DimChance = 8; // percent
const int PauseChance = 20; // percent
const int PauseMin = 35000; // milliseconds
const int PauseMax = 78000; // milliseconds
as well?
When you add a light (or group of) it stores the original values and restores those values when you remove the light from the script. (but only for on/off, intensity and radius)
If you have another script modifying on/off, radius or intensity you will probably see some undesired result, but for color and blinking settings it should be fine as this script doesn't change those at all.
Will it interfere with color changing scripts?`
Can I add one or two lights out of a group of a dozen lights whose color and blinking status is changed by another script?
I really want to try it asap!
Thanks for the update letting me know it resolved.
If you're adding lights to the script when they're needed and removing them when not, the script will stop running when there are no lights to process. The script runs 6 times per second, so that's wasteful if there are no lights to process.
You only need one programmable block for many lights though, just add them seperately
-l "Light 1" -add
-l "Light 2" -add
etc.
You'll see lights currently processing in the bottom right of the programmable block screen in console
Looking forward to seeing what you make of it, Splitsie!