Open shadowmage45 opened 5 years ago
Apparently this is being caused by a call to 'update part resources' from the ModularRCS part-module, which normally interacts with a 'VolumeContainer' on the part. When VolumeContainer is not present, it assumes that RF/MFT integration has been activated, and attempts to use that code-path.
So the real question is why does this part/module try to interact with resource/volumes? (it doesn't try to change fuel-type or anything; it just issues an update call to recalc volumes..)
It is not so much of an 'error', as nothing bad will happen, but more of a 'not all code works as expected' thing....
Reported on forums that SSTU's RF/MFT integration spams the log with errors when using the MRCS part (the stand alone RCS part?)