Output Window

The Output window shows helpful information in text form, but nothing can be input on this window (unless you count moving it causing a freeze in the main program, then okay...)

Among the normal outputs you can expect to this window:

  • Report writing success and current epoch and day notification.

  • Important selected agent events, like death or giving birth.

  • A note about the currently playing song - specifically its filename, which includes the title and composer.

  • If a Config File was loaded, this tells you EXACTLY what variables were changed!

  • If an un-bound key was pressed. Mostly a debug feature, this is still around because I like knowing what I pressed.

  • Completion of writing saves and autosaves, if enabled.

If you have DEBUG mode enabled, then you will get a stream of event notes whenever something happens in Evagents, such as births, live mutations, or random spawns are attempted. Use this mode to provide us with more information if the program repeatedly hangs or crashes for you.

In addition, if DEBUG mode is enabled AND you are running the Debug solution in Visual C++, then the Output Window becomes VERY verbose:

  • Every tick has markers indicating start and stop of various functions. The list of the meaning of these markers is as follows:

    • "S": Syncing of live variables from GUI is happening.

    • "P": World is starting of processing periodic events not related to agents.

    • "I": Agent inputs are being processed.

    • "O": Agent outputs and movement is being handled

    • "H": Health changes are being calculated

    • "CA": Cell layer interactions with agents are being processed.

    • "AA": Agent-Agent interactions are being processed

    • "tick": The world tick has been completed and stepping to the next is beginning.

    • "D": World drawing is occurring. Will not appear if Fast Mode is enabled.

    • All "/" marks indicate the end of the previous labeled function

    • If any of these markers are missing, or if the program freezes on any of them and you cannot recover, make sure to include the exact last line of this Output window in your report! Read more on the Crashes & Debugging page.

And it's worth mentioning again: if the program crashes or freezes on you at any time, make sure to check this window if it's still open and report to us what the program might have been doing before it went kerput.