Results 1 to 4 of 4

Thread: 12.04.08 15:34:26 EXCEPTION halt in \halopc\haloce\source\memory\data.c,#495: tag i

  1. #1
    "Think Different" Masterz1337's Avatar
    Join Date
    Sep 2006
    Posts
    4,405

    12.04.08 15:34:26 EXCEPTION halt in \halopc\haloce\source\memory\data.c,#495: tag i

    12.04.08 15:34:26 EXCEPTION halt in \halopc\haloce\source\memory\data.c,#495: tag instance index #65535 (0xffffffff) is unused or changed

    I've seen this before but I can't recall what it is or how to fix it. Anyone else know?
    Reply With Quote

  2. #2
    Banned
    Join Date
    Oct 2008
    Posts
    58

    Re: 12.04.08 15:34:26 EXCEPTION halt in \halopc\haloce\source\memory\data.c,#495: ta

    what was the last thing you added?
    Reply With Quote

  3. #3
    "Think Different" Masterz1337's Avatar
    Join Date
    Sep 2006
    Posts
    4,405

    Re: 12.04.08 15:34:26 EXCEPTION halt in \halopc\haloce\source\memory\data.c,#495: ta

    Errors don't always have to be things you add or edit. There's lots of other things that can do stuff like this.

    I found the problem anyway though.

    When we added the new elites in, I renamed the elite biped we use to use, since we have liek 16 elite biped tags, each one with different primary and secondary colors, as well as their armour perm set. Whe I transfered my tagset over to my laptop when my desktop was down, I told it to overwrite the old tagset. The old tagset still had the elite.biped tag in it, which refers to the new model, but a different animation and collision model. This is what was causing sapien not to open and the map not to compile.

    So for future referances, delete a tagset before overwriting it.
    Reply With Quote

  4. #4
    For Gnomejas sevlag's Avatar
    Join Date
    Oct 2008
    Posts
    1,875

    Re: 12.04.08 15:34:26 EXCEPTION halt in \halopc\haloce\source\memory\data.c,#495: ta

    Quote Originally Posted by Masterz1337 View Post
    Errors don't always have to be things you add or edit. There's lots of other things that can do stuff like this.

    I found the problem anyway though.

    When we added the new elites in, I renamed the elite biped we use to use, since we have liek 16 elite biped tags, each one with different primary and secondary colors, as well as their armour perm set. Whe I transfered my tagset over to my laptop when my desktop was down, I told it to overwrite the old tagset. The old tagset still had the elite.biped tag in it, which refers to the new model, but a different animation and collision model. This is what was causing sapien not to open and the map not to compile.

    So for future referances, delete a tagset before overwriting it.
    now if it was only a tag problem that was the cause of my sapien not working :/
    Reply With Quote

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •