so I tried opening os_sapien after about 3 days of not using it and I started getting this error:

05.31.13 14:21:52 EAX: 0x00000000
05.31.13 14:21:52 EBX: 0x00BD4E01
05.31.13 14:21:52 ECX: 0x00000000
05.31.13 14:21:52 EDX: 0x00000000
05.31.13 14:21:52 EDI: 0x0018F1E0
05.31.13 14:21:52 ESI: 0x00000000
05.31.13 14:21:52 EBP: 0x0018F0B8
05.31.13 14:21:52 ESP: 0x0018F0A8
05.31.13 14:21:52 EIP: 0x76EB0C22, 83 C4 04 C2 ?????
05.31.13 14:21:52 EXCEPTION halt in \halopc\haloce\source\memory\array.c,#130: index>=0 && index<array->count

three days prior I could open maps no problem, yet now I am all of a sudden locked out of sapien. I haven't changed anything since then, and to double check that it wasn't a tag related issue I tried sapien on a fresh set of tags, it crashed. To triple check, I made sure tool was able to compile my tags, and I never got a single error.

I've been adjusting sapiens compatibility settings and nothings working. Anyone know what the problem is? I tried using the thread search tool but couldn't find a thread with a solution.

I'm running windows 7, if that information helps.

So yeah, if anyone could assist me I'd be much obliged. Thanks in advance

Once again, os_sapien isn't coded right and keeps adding to sapien.cfg until it is too big to read, rendering os_sapien useless.

Whenever os_sapien starts not opening and it gives you that .c,#130: error, just delete sapien.cfg.

It won't ruin your window-placement! I swear! :)

Well I'll be a drunk monkey's uncle, it worked!

Thank you sir, you win the Delicon20 seal of approval, it looks like this: E(:

I had this happen years ago too. Sorted halo root by size and was surprised to see a 4gb heapdump in there.