Model/Group Name Conflict Crashing Issue

[tkw1969]

I downloaded the latest version .46 and had opened a few sequences when I opened a old sequence that had conflicting names. I then had the pop up window open and went thru and changed the names that were conflicting. after making the changes x-lights crashed and closed out. I tried reopening x-lights and all I get is the pop up window (Model/Group Name Conflict) If I go thru and change the names again after finishing it closes the pop up and x-lights closes also. I tried reloading X-light and the same results. What Now?

I dropped back to version .42 and it allowed me to change the names and open up correctly.

[tkw1969]

I now have tried version .45 and it will open up, but when I try to open version .46 it will not open.
I'm at a loss.

[Gilrock]

We are at a loss also.  All we can do it day dream about it until we see some files.

[tkw1969]

Gil what files do you want? When version .46 crashed it closed out on its on and it won't open back up.
Now I can open version .45 and do the Package log files but I don't think they are what you want Correct?

[Gilrock]

Yes package log files includes what we want but I'd like the xlights_rgbeffects.xml and sequence.xml you're trying to open BEFORE you fixed the naming issues.

[tkw1969]

Gill here is the files. I hope these have what you need.

[Gilrock]

I'm not at home but did a quick look.  If you inspect all your model groups in Notepad++ you need to delete any of the models inside the group that have the same name as the group because its a causing a recursive loop.  That's really not a legal group and you shouldn't be able to create that situation.  You must have done it way back before we put the naming checks in the code.  See how these two lines the first model in the group is the same as the group name.  And if you really have a single model with that name then that's also a problem.  I think what happened is we forced you to rename the model a while back but the code that fixes the model name doesn't go find it in all the groups and rename it there also so you ended up with these invalid group members.  Previously the names were just ignored but with the new code it's trying to recursively load the group members so if you use the same name inside the group it gets stuck in and endless loop.

    <modelGroup name="Cascade" models="Cascade,Cascade2,Cascade3,Cascade4,Cascade5,Cascade6,Cascade7,Cascade8" selected="1"/>
    <modelGroup name="Icicles" models="Icicles" selected="1"/>