I think I have my brain around how the XNA game execution flows but correct me if I have this wrong.

When you start the game the <yourgame>Game.StartGame() is called from the Program.cs class file which creates a new <yourgame>Game object(all of the variables get assigned initial values and the constructor creates a new Graphics Device Manager, and a new Content Manager) then calls game.run().
This calls Initialize() and executes all the code there and at the end calls base.Initialize() and this calls LoadGraphicsContent()
(base.Initialize() I assume is something within XNA framework behind the scenes?) then it returns to Initialize() and goes on to the Update().

From what I could tell stepping through it with the debugger, this is where the loop starts. Update() runs it's code and at the bottom base.Update() calls Draw() runs it's code and then at the bottom base.Draw() calls Update() and the loop continues until the game is exited.

Please let me know if I got something wrong in that flow.
Thanks

jnbutler

__________________
jnbutler

I believe what happens is after your game has initialized itself, the application enters loop like below.
Inside that loop calls to Update() and Draw() are made. Now depending on what type of game timing is established will determine how often the Update() and Draw() methods get called. This is hidden by the framework.

The base.* versions of these methods are only responsible for executing the base functionality of the base class. I do not believe they make calls back and forth to each other. For example, base.Update() calls Draw() and vice versa.

Does that make sense?