Game Development Community

No MissionArea then crash when hitting F11 while in mission

by Demolishun · in Torque Game Engine · 12/24/2007 (10:05 pm) · 2 replies

This is mind boggling to me. If I create a mission without a MissionArea object and I try and start the editor by pressing F11 then the engine crashes. The mission itself runs fine. It gives me this message:
"GuiControl::awaken: failed onWake"

I cannot understand why this would be the case. I searched for everywhere MissionArea is referenced and cannot find a solid connection between the script object MissionArea and the editor in script or C++. This seems very unhealthy for this to be linked like this. As far as I knew the MissionArea object was not required, but because of some connection it is mandatory.

Can anyone shed some light on this?
Demolishun's profile picture
Torque Owner Demolishun
DemolishunConsulting Rocks!

About the author

I love programming, I love programming things that go click, whirr, boom. For organized T3D Links visit: http://demolishun.com/?page_id=67

Recent Threads

  • Setting Up Platform Specific Code in T2D
  • Would a 3D widget in T2D be practical?
  • T3D, Existing Object and Terrain System, and Terrain Paging
  • GarageGames group in Steam
  • Bug in console gui
    • NextNext Thread
    PrevPrevious Thread
    More from Torque Game Engine


    Torque Owner Demolishun
    DemolishunConsulting Rocks!
    #1
    12/24/2007 (10:42 pm)
    Well I searched through the forums and I cannot find any link that says the MissionArea is important. Most references says it is a throw back to Tribes 2. Yet in the code I find stuff like this:
    const RectI & MissionAreaEditor::getArea()
{
   AssertFatal(mMissionArea, "MissionAreaEditor::getArea: no MissionArea obj!");
   if(!bool(mMissionArea))
      return(MissionArea::smMissionArea);

   return(mMissionArea->getArea());
}

    Well if it is NOT important why is there code that Asserting against it? Is it important or not?

    Torque Owner Demolishun
    DemolishunConsulting Rocks!
    #2
    12/24/2007 (10:53 pm)
    Well, I was running the editor and there is a function called Mission Area Editor. It seems the mission area is very much hooked into the editor. I could spend a lot of time figuring out how to remove it, or I could get some work done. There is a lot of stuff in the engine that just does not make sense to me, but trying to get rid of it or understand it is too time consuming. Little things like this just go against my sense of order and drive me nuts. I may find a use for this object sooner or later. Just move on I guess.