In need of help figuring out an error.

[Artigo]

I've just recently got into modding Halo CE. I'm not a skilled modder in any sense, but I enjoy making AI battle it out using sapien and other such tools. Most recently I went all in trying make a large battle on Ratrace. I used a stock Ratrace map and added secenery and AI tags. Everything seemed to be working well except for the message saying:
"AI knowledge database (768 entries) is full (warns once every 30 sec)".

I was able to compile the map and play, but that's where my problems started. After about five minutes of play I got the dreaded "Gathering exception Data" message and my game shut off. So my question is: Is there any way I can find out the problem is so I can fix it?

Thank's in advance for any advice and help if you need anymore details just let me know, because I am really looking forward to playing these maps with friends.

The complete debug information from Sapien and tool follows:

Code: Select all

07.12.06 15:35:45  sapien pc 01.00.00.0609 ----------------------------------------------
07.12.06 15:35:45  reference function: _write_to_error_file
07.12.06 15:35:45  reference address: 401b13
07.12.06 15:35:45  Couldn't read map file './sapienbeta.map'
07.12.06 15:35:46  CreateDevice succeeded with refresh rate = 0
07.12.06 15:35:47  Increasing sound decompression buffer size to 1048576 bytes
07.12.06 15:36:51  local player 0, weapon (0x0), deleted unexpectedly
07.12.06 15:37:19  AI knowledge database (768 entries) is full (warns once every 30 sec)
07.12.06 15:37:55  AI knowledge database (768 entries) is full (warns once every 30 sec)
07.12.06 15:38:47  AI knowledge database (768 entries) is full (warns once every 30 sec)
07.12.06 15:39:21  AI knowledge database (768 entries) is full (warns once every 30 sec)
07.12.06 15:40:06  AI knowledge database (768 entries) is full (warns once every 30 sec)
07.12.06 15:40:37  AI knowledge database (768 entries) is full (warns once every 30 sec)
07.12.06 15:41:19  AI knowledge database (768 entries) is full (warns once every 30 sec)
07.12.06 15:41:53  AI knowledge database (768 entries) is full (warns once every 30 sec)
07.12.06 15:42:29  AI knowledge database (768 entries) is full (warns once every 30 sec)
07.12.06 15:43:04  AI knowledge database (768 entries) is full (warns once every 30 sec)
07.12.06 15:43:42  AI knowledge database (768 entries) is full (warns once every 30 sec)
07.12.06 15:44:19  AI knowledge database (768 entries) is full (warns once every 30 sec)


07.12.06 15:47:30  tool pc 01.00.00.0609 ----------------------------------------------
07.12.06 15:47:30  reference function: _write_to_error_file
07.12.06 15:47:30  reference address: 42ca20
07.12.06 15:47:30  Couldn't read map file './toolbeta.map'


07.12.06 15:48:10  tool pc 01.00.00.0609 ----------------------------------------------
07.12.06 15:48:10  reference function: _write_to_error_file
07.12.06 15:48:10  reference address: 42ca20
07.12.06 15:48:10  Couldn't read map file './toolbeta.map'
07.12.06 15:49:00  loc: Tried to add item ui\multiplayer_game_text with different size (9976) than expected (10128).
07.12.06 15:49:00  loc: Tried to add item ui\shell\main_menu\settings_select\player_setup\player_profile_edit\controls_setup\controls_binding_labels with different size (1192) than expected (1292).
07.12.06 15:49:00  loc: Tried to add item ui\shell\main_menu\settings_select\multiplayer_setup\playlist_edit\ctf_edit\ctf_labels with different size (324) than expected (380).

It seems I was able to fix my problem by deleting the flood combat forms, strange.

[boo_diddly]

it seems that you had filled up the database. As it reads, you put too many AI into the map, and thusly halo could not keep track and the few too many AI caused the exception. How many AI did you put onto the map?

[ledhedgn]

to many ai will cause the engine to crapify, then it causes the exception so it can have a break, if you are doing a simple team ai mod, have like 8 or 9 on each team, now if you are doing like what bungie did, with all those ai, what you do is you use scripts and trigger volumes to get it to do that.