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
Breadboard or specific Engine name control ACB.
Instead of an all in one control you can have sets of engines activate as needed.
You just gotta dig into ACB control or learn Breadboard.
Theres some Breadboard builds for engine control on the Discord.
Place copy and name and your ready to go.
Me i would suggest breadboards. They can control not only output and where it goes. But also RPM and whos on and off under what circumstance.
All in one block. Plus many many other features all tied into a crazy cluster buck of controls commands and parlor tricks to amaze and confound anyone who witnesses your builds.
This will run something like this:
if battery level is below x then:
set fuel engine battery fraction to x
if battery level is above x then:
set fuel engine battery fraction to x
Alternatively, there's a simpler method: set the engine to operate at 100% battery fraction continuously, but assign it a lower priority in the Vehicle power menu (V).
A good method for redundancy is to have it so that engines only get fired up as needed by setting the cutoff/startup points for each engine to be different, and having more engines than you need even under max load.
There are no rules that you can't have many bread boards, each only controlling a local system.