"m is null" is false when "m == null" might actually be true. Probably because MonoBehaviour has an overridden "==" operator.
In any case, according to my tests (when there is a separated craft/debris that is far away), trying to access m.transform throws a nullref even though "m is null" is false.
related: #74
dkavolis
commented
4 years ago
"m is null" is false when "m == null" might actually be true. Probably because MonoBehaviour has an overridden "==" operator. In any case, according to my tests (when there is a separated craft/debris that is far away), trying to access m.transform throws a nullref even though "m is null" is false. related: #74