Lockup on science collection? #12
Description
There appears to be a situation of instability that arises after collecting and transferring several data loads as a transmit all group to various targets which can cause crew reports or other science collection GUI buttons on parts to trigger a CTD with no event log to the ksp.log file. I have managed to repeat this error.. and at first thought it simple data corruption, however verification of the drive indicates now flaw and a reinstall of the science relay mod from source appears to reset the error. I suspect this is being caused by how the data is being buffered and tracked by the core KSP game interacting with the mod, but cannot pin it down due to the lack of a log and the lockup of the interface that prevents checking history.
Data not being transferred to KSC is also periodically completing base game records as to what data has been collected, without actually having been sent there and this may be related. My most recent twitch stream's end demonstrates the error and may be seen here at its end.. as well as the end of the one before it: