Likely related to code put in place to handle some null-refs; instead of early exit, should just catch the exceptions if they happen; dirty/ugly, but no other way around it.

Have added additional checks to see if the current flight/editor state is valid, and also added a try/catch block around the actual update code to locally catch the exception if/when it occurs. Will test this to see if I can spot the original problem before I compile and test the 'fix'.

Confirmed the base bug; and confirmed that the 'fix' fixes the problem. Need to test if the 'fix' still works under the previous crash-inducing-conditions (initializing resources on a -new- part while initializing flight scene).