alright, so OS sapien and I aren't good friends, and I've never actually gotten it to work. but after about 3 months of working with it I got it to open (but then it swiftly crashes). however, unlike previous crashes, this actually yields exception data for once.

04.03.12 19:57:14 EAX: 0x00000000
04.03.12 19:57:14 EBX: 0x0000CF01
04.03.12 19:57:14 ECX: 0x0012EC60
04.03.12 19:57:14 EDX: 0x00000110
04.03.12 19:57:14 EDI: 0x0012F340
04.03.12 19:57:14 ESI: 0x00000000
04.03.12 19:57:14 EBP: 0x0012F218
04.03.12 19:57:14 ESP: 0x0012F208
04.03.12 19:57:14 EIP: 0x77A65CD4, C3 8D A4 24 ?????
04.03.12 19:57:14 EXCEPTION halt in \halopc\haloce\source\cseries\profile.c,#442: parent_timesection->self_msec >= child_timesection->elapsed_msec

this is the exception error ^^^^

I seriously am in dire need of some assistance because if I can't open OS sapien I won't be able to work on any new mods or heavily edit any of my current months. I've been dealing with this for a long time and might have to just create non-OS replacements for all the tags and edit them all my mods in normal sapien, then switch to os tags before compilation (which would be very painstaking and redundant)

so please, if anyone can offer assistance or just throw in two cents I'd be very much obliged. this is basically me issuing an SOS right now, seriously!
Edited by Delicon20 on Apr 3, 2012 at 09:09 PM

i don't know for sure seeing this is OS
but is the .exe set to 1 cpu?

if it is then that's all i can think of right now.

where would I navigate to see if it was?

nah forget what i thought at first, i don't usually use OS,
but just installed it there to check it out, it runs fine on more than 1 cpu.
might even have been mentioned in the doc i read ages ago.

ally is right, you need to set sapien to only use 1 core.
something about set affinity to 1 or 0 for the processors, i dunno.
oh lol oops.
but seriously that is pretty much always what that error is, so maybe OS is not playing nice with your dual/quad/w/e core.
Edited by Maniac1000 on Apr 3, 2012 at 10:10 PM

holy crap, it actually worked!

YES!!!

thank you guys!

haha i knew sapien had issues with some machines running more than 1 cpu,
and was sure that this was the case with OS_sapien too.
but when i ran the OS_sapien on my own pc and checked that more than 1 cpu was checked,
i just thought i was wrong, and thought i slightly remembered something about OS_sapien having the cpu issue fixed.
was shattered man, sure i was talking to you on xf maniac, but i had to log off and go to sleep
you know that part where the eyes start rolling? LOL