argent77 Posted March 31, 2013 Share Posted March 31, 2013 After randomly crashing my BG2 game while testing a mod character I have found out that the script action InActiveArea(O:Object*) is the cause for the crashes if the specified object isn't an NPC or otherwise globally registered creature and the object is not in the same area. Can anyone confirm that behavior? Link to comment
Wisp Posted April 1, 2013 Share Posted April 1, 2013 Can anyone confirm that behavior? Possibly. InActiveArea() is also the strongly suspected cause of why MESSEN.CRE would crash SoA games when he EscapeArea()ed, with older version of the Fixpack. Link to comment
argent77 Posted April 1, 2013 Author Share Posted April 1, 2013 I've tested InActiveArea(O:Object*) a bit more thoroughly in different configurations and the game always crashes if the specified creature isn't globally registered and not in the active area or doesn't exist at all. The similiar script action InMyArea(O:Object*) is much more reliable and didn't crash the game, no matter what parameter I've specified. So it could be used as a valid alternative in many cases. Link to comment
Wisp Posted April 1, 2013 Share Posted April 1, 2013 My mistake. Fixpack used to use InMyArea() for MESSEN, not InActiveArea(), so that's a separate issue from this one. Link to comment
Ascension64 Posted April 2, 2013 Share Posted April 2, 2013 You would be correct. If the game find the creature, the creature gets a NULL pointer, and the game tries to get NULL pointer's current area = crash. Worth reporting on BGEE forums. Link to comment
Avenger Posted April 5, 2013 Share Posted April 5, 2013 This is already fixed in BGEE Link to comment
igi Posted November 12, 2013 Share Posted November 12, 2013 Local copy updated, thanks. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.