Reported Version: v0.1.4 (latest) | Mods: none | Can replicate without mods? Yes
OS: Windows 10 | CPU: Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz | GPU: NVIDIA GeForce RTX 2070 | RAM: 16.0 GB
Severity: med (can lead to unexpectedly running out of fuel/practically infinite fuel)
Frequency: low (fairly hard to replicate in controlled environments, but once triggered the effects are obvious)
Description: Transferring fuel between different fuel tanks on the same craft using the resource manager may result in more/less fuel than you start with, even when no engines are active.
Screenshots from a controlled test:
A craft with only X200 tanks, two -32s, one -16 and one -8. Only one of the -32s are full. Engines are only used to drain fuel.
After a series of random fuel transfers between the tanks, it ended up with more methane and less oxygen than before, all without activating the engines.
Consistent order of actions that trigger this bug haven't been found yet, but here are some suspected triggers:
1. Having more than 2 fuel tanks of different sizes present in the transfer tab.
2. Not setting in/out for every one of the fuel tanks, or when the automatic setting doesn't kick in.
3. Setting in for full tanks and out for empty tanks.
4. Just using the = button in general
Typical symptoms during the occurrence of the bug:
1. Tank filling while no other tanks are draining.
2. Tanks that haven't been set an operation participating in the transfer.
3. Reversed fuel flow, from in tanks to out tanks.
4. Fuel level change rate in one tank is bigger than every other, happens often when transferring between different sized tanks.
5. Oxygen tanks draining to fill methane tanks and vice versa.
6. Transfer stopping when fuel level equalizes rather than after target tanks are full or source tanks are empty. Basically acting like the = button instead of in/out.
