Fixed controller running updateai before update happened, which could cause radius problems

AI will now only start running after the first actual update run

Author: garethyr

Entities/Actor.cpp

@@ -1371,7 +1371,8 @@ void Actor::VerifyMOIDs()
 
 void Actor::Update()
 {
-    // Update the controller!
+    //TODO This should be after MOSRotating::Update call. It's here because this lets Attachable scripts affect their parent's control states, but this is a bad, hacky solution.
+	//See https://github.com/cortex-command-community/Cortex-Command-Community-Project-Source/commit/ea20b6d790cd4cbb41eb923057b3db9982f6545d
     m_Controller.Update();
 
     /////////////////////////////////

System/Controller.cpp

@@ -162,7 +162,7 @@ namespace RTE {
 			}
 
 			// Update the AI state of the Actor we're controlling and to use any scripted AI defined for this Actor.
-			if (m_ControlledActor && !m_ControlledActor->UpdateAIScripted()) {
+			if (m_ControlledActor && m_ControlledActor->ObjectScriptsInitialized() && !m_ControlledActor->UpdateAIScripted()) {
 				// If we can't, fall back on the legacy C++ implementation
 				m_ControlledActor->UpdateAI();
 			}