06.06.12 15:45:18 EAX: 0x05691100
06.06.12 15:45:18 EBX: 0x00BD4E01
06.06.12 15:45:19 ECX: 0x02460000
06.06.12 15:45:19 EDX: 0x05680000
06.06.12 15:45:19 EDI: 0x0012F1E0
06.06.12 15:45:19 ESI: 0x00000000
06.06.12 15:45:19 EBP: 0x0012F0B8
06.06.12 15:45:19 ESP: 0x0012F0A8
06.06.12 15:45:19 EIP: 0x77677094, C3 8D A4 24 ?????
06.06.12 15:45:19 EXCEPTION halt in \halopc\haloce\source\memory\array.c,#130: index>=0 && index<array->count

this is the error os sapien gives when i try to open ANY map even the stock ones, i think its something to do with not enough memory going to sapien but i really don't know what i need to to to fix this.

How much RAM do you have? Whats your processor? How much memory left on your HDD?

4 gigs of ram (2.85 usable)

14.9 gigs of HDD space left

and here's the real kicker i only have a 2.1 GHz SINGLE-CORE processor and the hek has never given me a problem before, oh and BTW i exaggerated in the title, this is the first time ive encountered this error, sorry i was a bit PO'd
Edited by killzone64 on Jun 6, 2012 at 09:48 PM

forgot to mention that its the os hek

Edited by killzone64 on Jun 6, 2012 at 10:39 PM

Do you by mention have alot of custom tags in your tags folder? Getting rid of some could help.

i have had up to 4 gigs of tags before and i never had a problem, right now i only have 2.7 gigs of tags

i just tryed the normal hek and it give me the same error

Edited by killzone64 on Jun 7, 2012 at 05:28 PM

Do you have alot of custom tags in your tags folder?!??!

no i do not, i have recently remove 3/4 of the custom tags i previously had

Maybe a tag is corrupted? There is a very easy way how to figure out what tags are bad. Start by deleting all the tags in the map (make a copy/backup of it). Does sapien load? If so, you're on the right track. If it dosnt, idk what to tell you. In the case that it loads, make a copy of your backup. Slowly go through the tags deleting one at a time out of the map until it loads. That'll tell you what dosnt work. Good luck.

E: if sapien dosn't load, the next place is to check the files associated with the map (globals, the character tag, etc.). BE SURE TO BACK UP EVERYTHING BEFORE MESSING WITH IT!
Edited by ODST_Nick on Jun 13, 2012 at 01:33 PM

that was on a clean install idk what happened but im just using this as an excuse to toake a long break from editing

Sapien IS a complete program. And why would kornman need to do it? Are you paying him a salary to do this? And the bugs are human error or file corruption, so that's not even a flaw with sapien, that's a flaw with the users. If you hate it so badly, then its your own job to program a replacement that ignores fatal errors with files, creating files that will crash the game since the editing tools didnt prevent you from having errors, so you have fun with that.

File corruption in this case happens BECAUSE of these said editing tools that you talk about.

When has sapien ever corrupted a file on its own? In fact, I've never even seen sapien corrupt a file even WITH human aid (logically, if you quit during saving, sure, but I still havent ever seen it happen). Guerilla, sure, but that's with a person who deletes stuff they shouldn't, so again, its the users fault (And you know if guerilla prevented them from doing that, they would go bashing it for not letting them do what they want)

This attitude... *facepalm*

I'll tell you when.When you use scenarios with OS Sapien,it becomes corrupted(not 100% true but it crashes Sapien).

if it doesn't actually corrupt anything but instead just crashes then how is OS Sapien causing corrupted files? sounds like it's your fault its crashing to me lol