Jump to content

Assertion failure with ConflictAllForElements when script is run on multiple records


Recommended Posts

Posted

Exception in unit userscript line 49: Assertion failure (D:\Projects\TES5Edit\wbImplementation.pas, line 3698)

 

When I run the script on only one record, this error doesn't produce.

elements := Tlist.Create;
elements.Add(ElementByName(m, e_name));
elements.Add(e);
elements.Add(element);
c := ConflictAllForElements(elements,false,IsInjected(m));
elements.Free;

Usage is as above.

Version is 3.1.2

 

Bug report: http://pastebin.com/5E1pKj3j

 

Any help is appreciated.

Posted

Problem solved by using ElementByIndex instead of ElementByName. No idea why it would fail on multiple instances though.

 

EDIT: found out element can be nil when it doesn't contain that record and accessing it through index will return the next element.

Posted

Great! and welcome to AFK! :) The topic you want is here I trow.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...