Two big CTD issues stand right now for the Build Mod 13:
<a href="http://swankyplace.com/potcbugs/view.php?id=152" target="_blank">http://swankyplace.com/potcbugs/view.php?id=152</a>
<a href="http://swankyplace.com/potcbugs/view.php?id=273" target="_blank">http://swankyplace.com/potcbugs/view.php?id=273</a>
These may or may not be related, as they both happen during 3d sailing mode and ship battles. However one happens on the top of the hour change (as reported by Hook when fighting the French invasion fleet), and the other happens whenever you hit F1 (and possibly F2 as well).
PLEASE, if anyone wants to help do the grind of finding out when this occurs with more precision pinpointing, and possibly suggest ideas on what may be causing this, please help.
If you help, TURN ON LOGGING to aide in trying to find the problem. When these two CTDs occur, there is no error.log entry for them. They simply quit the application with no reasoning whatsoever. However the compile.log will contain more information on what occurred 'before' the CTD.
If anyone wants to edit your files to add a ton more trace lines (and you know how), then that may help even further. Hook has reported to have put in a ton of them on his own testing, and still cannot find when this happens. THESE CTDS ARE VILE!
I would help play test, but unfotunately my access to my home gaming rig is near to non-existent right now, and for at least another few weeks. However when I do get a chance to try, I will. I have my work Mac with me at all times, which has internet access, and all the code files, so I can whip up code changes, and work on code ideas to fix the problem. I just cant test the shtuff!
So, if anyone is willing to help, please do. These last two CTD's (or the same one), are basically the last really nasty problems left in Build 13 !!!
<img src="style_emoticons/<#EMO_DIR#>/dunno.gif" style="vertical-align:middle" emoid="
" border="0" alt="dunno.gif" />
The classic bomber "DeleteAttribute" of an attribute that has an aref made to it, for which you use the aref after the delete, was my first guess. However after looking over all some 1200 instances of DeleteAttribute, and looking at what they deleted, and tracing the attribute within the action, so on so forth... I didn't find anything that raised an eyebrow <img src="style_emoticons/<#EMO_DIR#>/sad.gif" style="vertical-align:middle" emoid="
" border="0" alt="sad.gif" />
So, that inital hunch, didn't pan out.
I know of another CTD causer, and thats doing a calculation with a number that is way too friggen big. This type came to my attention with the Donating to the Church when you were level 100 and wanted to raise up to "Hero" status. The number got so ungainly large, that a float operation on it caused a CTD.
Now, trying to find one of THOSE is next to impossible on a grand scale. There is really nothing you can search by. The only way to find those, is to pinpoint the 'area' of crash, and then go through the code with a fine toothed comb.
<a href="http://swankyplace.com/potcbugs/view.php?id=152" target="_blank">http://swankyplace.com/potcbugs/view.php?id=152</a>
<a href="http://swankyplace.com/potcbugs/view.php?id=273" target="_blank">http://swankyplace.com/potcbugs/view.php?id=273</a>
These may or may not be related, as they both happen during 3d sailing mode and ship battles. However one happens on the top of the hour change (as reported by Hook when fighting the French invasion fleet), and the other happens whenever you hit F1 (and possibly F2 as well).
PLEASE, if anyone wants to help do the grind of finding out when this occurs with more precision pinpointing, and possibly suggest ideas on what may be causing this, please help.
If you help, TURN ON LOGGING to aide in trying to find the problem. When these two CTDs occur, there is no error.log entry for them. They simply quit the application with no reasoning whatsoever. However the compile.log will contain more information on what occurred 'before' the CTD.
If anyone wants to edit your files to add a ton more trace lines (and you know how), then that may help even further. Hook has reported to have put in a ton of them on his own testing, and still cannot find when this happens. THESE CTDS ARE VILE!
I would help play test, but unfotunately my access to my home gaming rig is near to non-existent right now, and for at least another few weeks. However when I do get a chance to try, I will. I have my work Mac with me at all times, which has internet access, and all the code files, so I can whip up code changes, and work on code ideas to fix the problem. I just cant test the shtuff!
So, if anyone is willing to help, please do. These last two CTD's (or the same one), are basically the last really nasty problems left in Build 13 !!!
<img src="style_emoticons/<#EMO_DIR#>/dunno.gif" style="vertical-align:middle" emoid="

The classic bomber "DeleteAttribute" of an attribute that has an aref made to it, for which you use the aref after the delete, was my first guess. However after looking over all some 1200 instances of DeleteAttribute, and looking at what they deleted, and tracing the attribute within the action, so on so forth... I didn't find anything that raised an eyebrow <img src="style_emoticons/<#EMO_DIR#>/sad.gif" style="vertical-align:middle" emoid="

So, that inital hunch, didn't pan out.
I know of another CTD causer, and thats doing a calculation with a number that is way too friggen big. This type came to my attention with the Donating to the Church when you were level 100 and wanted to raise up to "Hero" status. The number got so ungainly large, that a float operation on it caused a CTD.
Now, trying to find one of THOSE is next to impossible on a grand scale. There is really nothing you can search by. The only way to find those, is to pinpoint the 'area' of crash, and then go through the code with a fine toothed comb.