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 noticed this line:
which seems to be trying to protect against this special fetch value being used by exiting early, but the "fluids_ui_open" check is false when I log it here.
It also might be worth doing something like this right after:
I added a new variable
local transfer_volume = math.min(capacity - cur_volume, max_transfer_volume)
and will be passing that instead of max_transfer_volume to lightjaCalculateFluidTransfers, which now has "max_transfer_volume" renamed to "transfer_volume" - i think the naming obfuscated the functionality here and thats why I didn't catch this.
Appreciate the assist! I've been busy so very nice to not have to start from scratch here.
Also, just for context, i just arbitrarily use that 2.12345 value so I know where the call is coming from, cant remember exactly why but I think it was needed to get the open sliders working on the fluid info UI.
Also added the asserts I mentioned, so if there is any other "leaking" it should show up as errors. As a result I found and fixed another edge case where stacking actions would cause that max transfer amount value to be miscalculated in cases where there are multiple collectors, somewhat of a concurrency issue.