Your phrasing sounds like you agreed that you're that dumb, and offered to make a video to prove it. Is this what you intended? :confused:Quote:
Originally Posted by metsfan0908
Printable View
Your phrasing sounds like you agreed that you're that dumb, and offered to make a video to prove it. Is this what you intended? :confused:Quote:
Originally Posted by metsfan0908
Maybe the scenario file became corrupt (HEK+ loves to do that sometimes). Delete the scenario file and extract it again with HEK+.
Ummm in three pages how has no one asked for his debug.txt? He may just have a corrupted animation tag or a missing dependency in the scenario.
Mets copy the last few entrys of your debug.txt from your halo CE directory.
^Quote:
Originally Posted by ShadowSpartan
also, metsfan, delete the file your trying to open then extract. Hekplus doesn't overwrite the file unless you check the specific flag (which i don't recommend, since your recursively extracting).
As Choking showed you, I have asked for it, and have yet to get an entry from debug.txt. A corrupted animation tag or missing dependency would just make Sapien close out, not display the bad scenario error.Quote:
Originally Posted by wanksta(-=Inferno=-)
Oh my bad. I didn't see that.
I did that 4 timesQuote:
Originally Posted by ShadowSpartan
Ok, as I have said before. Open sapien, try to open a scenario, then look in debug.txt at the bottom. If it still doesn't display anything related to sapien, then try opening sapien from the sapien exe, instead of opening it by clicking a scenario tag.
ok did it still got the same error by running the .exe and still nothing in the debug.txt
i have heard of debug.txt not being dumped to under vista. Try running sapien as administrator, and then retry debux.txt