The SystemHeatBoiloff patch includes the lines:
volume = #$../mass$
volume *= 0.5
…which looks like it's intended to set the loop volume to half the mass, but the second line lacks a "@" prefix, so it's actually adding a new property, not editing the existing one. ModuleManager apparently ignores the asterisk when creating a new property, because what ends up in the MM config cache is just volume = 0.5, and ModuleSystemHeat seems to use the last volume property when more than one is present. The result is that the in-game "added loop volume" is 0.5 cubic meters for all tanks.
However, if I fix this, I get even smaller volumes: the H250-64 tank ends up with a loop volume of just 0.34 cubic meters (even less than 0.5), since mass is the tank's dry mass of 0.68 tons. (I don't know whether volume is meant to represent the actual tank volume, or just the volume of the cooling lines, so half the mass may or may not be a plausible approximation.)
The SystemHeatBoiloff patch includes the lines:
…which looks like it's intended to set the loop volume to half the mass, but the second line lacks a "@" prefix, so it's actually adding a new property, not editing the existing one. ModuleManager apparently ignores the asterisk when creating a new property, because what ends up in the MM config cache is just
volume = 0.5, and ModuleSystemHeat seems to use the last volume property when more than one is present. The result is that the in-game "added loop volume" is 0.5 cubic meters for all tanks.However, if I fix this, I get even smaller volumes: the H250-64 tank ends up with a loop volume of just 0.34 cubic meters (even less than 0.5), since
massis the tank's dry mass of 0.68 tons. (I don't know whethervolumeis meant to represent the actual tank volume, or just the volume of the cooling lines, so half the mass may or may not be a plausible approximation.)