Hey guys ever since I upgraded to OS to play the new firefight maps and SPV3 I noticed ever since then my Tool has stopped functioning correctly...

Literally every time I try to add something new to my scenario (shows up fine as usual) Tool will give me that unknown error every time (which everyone claims has to do with corruption). Well that is total BS because I tested it with my working tags that I purposely re-imported and I'm sure they don't magically corrupt whilst sitting in a folder.

How do you downgrade from OS?

I want to get back to my modding but OS has killed my Tool and I cannot continue adding my previously working tags nor anyone else's I download.

Further edit: Literally every tag on this site, every tag I extract, even my own tags that I add to a scenario that I haven't yet done prior to the OS upgrade will cause Tool to give me that stupid error... (I just upgraded CE not my tools by the way)...
Edited by Halo Noob Modder117 on Jan 2, 2017 at 07:37 AM
Edited by Halo Noob Modder117 on Jan 2, 2017 at 07:38 AM

What is the error?

OS does nothing to tool.

uninstall HEK, delete the tags folder and reinstall the HEK. This will fix your issue.
Edited by DeadHamster on Jan 2, 2017 at 08:48 AM

Yeah what is the error because I had that problem before too but it was only for the tags that used the old versions of OS

He didnt even install the OS HEK, just the end user OpenSauce 4.0.


The user version of OS doesnt modify the editing tools in any way.

a scenario made with os_guerilla or os_sapien needs to be compiled with os_tool because it is incompatible with the normal tool.

Also please note that opensauce tags will be corrupted when ripped using hek+, so those can also be the source of your error.

Please do show the error though.
Edited by SBB_Michelle on Jan 2, 2017 at 10:58 AM

The error (note- this is the same error I get every time regardless of what I compile):
01.01.17 10:18:25 tool pc 01.00.00.0609 ----------------------------------------------
01.01.17 10:18:25 reference function: _write_to_error_file
01.01.17 10:18:25 reference address: 42ca20
01.01.17 10:18:25 Couldn't read map file './toolbeta.map'
01.01.17 10:18:53 WARNING: 1 clusters in structure_bsp levels\custom\tagtest\tagtest have no background sound or sound environment.
01.01.17 10:18:53 EAX: 0x00000000
01.01.17 10:18:53 EBX: 0x000B0000
01.01.17 10:18:53 ECX: 0x0002918A
01.01.17 10:18:53 EDX: 0x0017D838
01.01.17 10:18:53 EDI: 0x19EA1000
01.01.17 10:18:53 ESI: 0x19DC7DF0
01.01.17 10:18:53 EBP: 0x000754AC
01.01.17 10:18:53 ESP: 0x0019A4B0
01.01.17 10:18:53 EIP: 0x00436131, F3 AB 8B CA ?????
01.01.17 10:18:53 EXCEPTION_ACCESS_VIOLATION

And no guys, I'm not stupid. I've been using this for a while now, nothing but my Halo CE game is using OS, I don't extract tags from .yelo files nor do I use OS tags. I've tested this on multiple tags that have worked from this site, from maps that have previously worked and even my own tags.

Now can someone please answer my question: How do I remove OS from my CE? I uninstalled CE and reinstalled it and for some magic reason it automatically turns into OS. WTF?

You need to uninstall OS via add remove programs or via the installer. But I am pretty sure your error is unrelated to it. Have you tried completely eliminating any variables that could cause tool to crash? You should try compiling tutorial with no custom weapons or changes to your globals.

I'll be very surprised if your problem is OS.

Trust me it is. I did no alterations to my mods. Now after using OS to play your masterpiece I got bored and decided to continue where I left off and now Tool is dead.

I make personal, lore friendly, non-os things. I just alter existing maps and maybe a few textures here and there (gold plasma rifle anyone?) AND RESTORED THE JACKAL MAJOR ;).

Everything was working fine. I stopped modding briefly after my final test and installed OS for CE. Now going back to continue modding Tool no longer compiles anything.

I tried the variables. I even deleted my entire tag folder and used the default one I first used back in the day with just a few multiplayer scenarios. THAT DIDN'T EVEN WORK.
Edited by Halo Noob Modder117 on Jan 2, 2017 at 07:04 PM

Uninstall everything and install on a clean slate. This is the simplest solution.

You know what? I did and guess what?

Just started up HCE (haven't done my HEK yet) and BAM! Still OS!!! WTF I completely removed it!!!

Screw it I'm going to play some Halo TMCC. I'm not touching this for a month this is doing my head in.

Did you run the OS installer to remove OS?
E: I think you misunderstand.
Reinstalling HCE however many times will not uninstall OS. They are separate things, simply working in conjunction.
Edited by Spartan314 on Jan 2, 2017 at 09:31 PM

Oh my god I'm so dumb how did I miss this...

This never crossed my mind. I literally forgot all about the installer...

"OS installer was where OS came from, I'm going to uninstall H:CE and HEK to remove OS" -rip derp moment 2017

EDIT: WELL WELL WELL... TOOL is working now.
Edited by Halo Noob Modder117 on Jan 2, 2017 at 10:23 PM

Yeah well, I'd have to agree with you, that was pretty dumb.

On a side note however, I still don't understand how having OS installed would affect normal HEK tool. As DeadHamster has stated, there shouldn't be any hampering in that sense in any way.

If you could do me a favor, can you reinstall OS, but this time with HEK tools too and see if it works? It be helpful to know if this is just a weird issue with having HEK installed with no OS and the game with it.

I get that problem sometimes when I add an pelican from CMT. Check your files because sometimes it may have something invalid like bipeds, weapons, shaders, etc

Master: I'll do that when I finish with my mod. I didn't use OS HEK because I thought my old tags wont work. If I upgrade my HEK to OS can I still use my non-os tags and compile scenarios into maps?

Or do I have to make a new set of tags and compile .yelos? <This is what I didn't want the hassle of finding out. I wanted to play .yelos but stick to making my basic non-os mods.

Fox: This is why I bothered posting this silly thing. There was not a single red line in Guerrilla and Sapien did not complain like it does IF something IS corrupted. It baffled me that Tool just kept repeating the same error over and over with any new tag I added until I removed OS... So odd.

By invalid do you mean the red stuff or is there another thing I should look out for?

For now, I'll just be getting back to that sentinel beam issue...
Edited by Halo Noob Modder117 on Jan 3, 2017 at 07:54 PM

If you upgrade to OS all your tags will work with stock HEK, unless you use a new field in a tag that wasn't there before, then it is automatically upgraded. Even with upgraded tags, tool can strip any new data and compile a regular map for anyone to use.

01.09.17 15:20:10 EAX: 0x00000000
01.09.17 15:20:10 EBX: 0x00000001
01.09.17 15:20:10 ECX: 0x00000000
01.09.17 15:20:10 EDX: 0x00000000
01.09.17 15:20:10 EDI: 0x0019EE28
01.09.17 15:20:10 ESI: 0x00000000
01.09.17 15:20:10 EBP: 0x0019ED00
01.09.17 15:20:10 ESP: 0x0019ECF4
01.09.17 15:20:10 EIP: 0x7763F43C, C2 08 00 90 ?????
01.09.17 15:20:10 EXCEPTION halt in \halopc\haloce\source\tag_files\tag_groups.c,#3157: #-1 is not a valid animation_block index in [#0,#3)

I get this now gg. -.- time to fix

do you have an extracted tank of monitor in your tagset? That error often happens when an animation tag is extracted improperly.

I'm moding B30 it was working fine in till I started working on my wounded marines concept

Then clearly it is the wounded marines.

You have an empty block field somewhere within the tags you extracted. For some reason Halo doesn't like this.

01.11.17 17:08:07 tried to add more elements for a actor_variant_transform_collection_entry_block @20AD9BD0 #32 than allowed
01.11.17 17:08:07 EAX: 0x00000000
01.11.17 17:08:07 EBX: 0x00000001
01.11.17 17:08:07 ECX: 0x00000000
01.11.17 17:08:07 EDX: 0x00000000
01.11.17 17:08:07 EDI: 0x0019F180
01.11.17 17:08:07 ESI: 0x00000000
01.11.17 17:08:07 EBP: 0x0019F058
01.11.17 17:08:07 ESP: 0x0019F04C
01.11.17 17:08:07 EIP: 0x7763F43C, C2 08 00 90 ?????
01.11.17 17:08:07 EXCEPTION halt in \halopc\haloce\source\tag_files\tag_groups.c,#3157: #-1 is not a valid actor_variant_transform_collection_entry_block index in [#0,#32)

RIP

you can only have 31 transformations

RIP revives in flood missions

By type or how many actors?
Edited by ScarFOx on Jan 11, 2017 at 05:46 PM

Actors that can change I think.... I've yet to fully push it as I was able to do everything I wanted in all missions other than c40 which I am currently working on.