Reasons for this are unknown; basically, game crashes as soon as it loads UI.map.
It doesn't happen always. I think it is somehow related to the maps I have in the folder, since it works until I compile a new map; when I do that, it can either still work or just crash until I manage to delete old maps and compile new maps to persuade it to actually work. The criteria through which it decides whether to crash or not, if any, are unknown. Does somebody know why this happens? Maps were compiled with the old build-cache-file command (only reason I use OS is because it can open the bug-free singleplayer tagset), and I use the following commands

-console -devmode -nojoystick -screenshot -no_os_gfx

Message given: "An error has occurred. A crash report for this exception has been saved to your OpenSauce Reports directory (OpenSauce\Reports\CrashRpt).
Attach the zip archive if you report this issue"

I could attach the zip archive as the message said, if needed, but I don't know if actually somebody can understand it; I surely don't.
Edited by rododoonceagain on May 13, 2015 at 02:00 PM

Did you compile the OS .scenario with non-OS tool? I believe that doing that can cause some problems. Have you tried reinstalling OS?

I compiled a map file (NOT yelo file) using OS tool, because the tags I use are OSified and vanilla Tool can't open them. My OS version is the latest available.

Have you tried compiling it as a .yelo and see if it works?

I don't mean to be "that douche bag".

But perhaps the OS team would be of a greater benefit if you had perhaps messaged them directly via their contact details.

It may also be helpful to pool all OS related errors into a dedicated thread which would in my opinion would be far easier to locate in comparison to multiple thread topics littered far throughout this site.

I wouldn't recommend using the 'bug free' SP tags on Halomaps. You should try extracting then with the HEK+. Alternately, you could open the .scenario file in OS sapien, remove al scripts from the scripts file and then recompile the scripts. After doing this, open the .scenario file in non-OS sapien, place the original campaign scipts in your data directory, recompile the scripts and then compile the map.

Its of common knowledge that the hek+ will occasionally corrupt tags such as the scorpion and forklift animations.

That is true, but I believe that the OP is trying to obtain the .scenario files for Halo CE, for compilation, (which to my knowledge, the HEK+ will not corrupt).

Also what I meant was that the OP should not use the .scenario tags included in the Bug Free SP Tag pack, as they will give the "HS syntax definition too large" error, which would not allow one to open the .scenario files in sapien, (which would obviously leave you unable to recompile the scripts).
Edited by Spartan II on May 14, 2015 at 04:57 PM

Wait what? You can't compile scripts in OS_sapien? I've done it before, what are you talking about?

All you have to do is go into guerilla, open the scenario file, take a10 for example, delete refrences scripts and something else that's around those two, open in sapien and recompile using zteam scripts and it works flawlessly for me. Now I'm really confused.


Don't kill me for my stupidity/misunderstanding of what is going on, I really am confused.
Edited by S12Spark on May 14, 2015 at 06:13 PM

I did not say that you can't compile scripts with OS-Sapien. I merely suggested an alternate method of recompiling the .scenario files scripts, so that they can be opened with non-OS sapien, and then compiled.

Spartan, hold it: you know nothing and you are making a big mess
1) HEK + corrupts tags and scripts on extraction, no matter what. I've tried what you said a whole lot of times; it did not work. Background music starts randomly, scripts are corrupted, cutscenes don't work well (when they actually work) and some levels, such as c40, are completely unplayable, because ALL the encounters after the first pulse generator don't spawn at all.

2)The "HS syntax definition too large" error can be easily overcome just by opening the scenario using OS_tool. There is no need to use your method; the problem is a crash within the engine, it has nothing to do with Sapien.

Now, the problem seemed to be caused by something not-os related, however. I uninstalled OS and it was still there; I uninstalled Halo and reinstalled it; now it works. What went wrong is something beyond my knowledge.

FrostyHEK+ Confirmed?

Just as long as it retains your cuteness and charm.

Well, at least you have it working again.

I know that there is no need for my method of solving the HS syntax error if you use OS sapien, (at the time I had suspected that there may have been a problem with OS saipen or OS tool).

I don't think that there are any perfect tagsets. To my knowledge, there are no tagsets that are free of the 'sound bug' or problems with cutscenes and scripts. Even the 'bug free' tagset.

Honestly, HEK+ works just fine for now, there are few tags that corrupt, and I've found ways to get around it. Halo tag converter will extract the scorpion tags just fine.

It would be nice to get a new tag extractor though.