SC2Mapster Forums

Development > Data

Destroy actors

  • 10 posts
    #1 Feb 26, 2013 at 21:28 UTC - 0 likes

    Hi,

    I have a question that may be very... stupid and simple. :-D

    How do I destroy actors?

    Because: in my map there is that strange behaviour that after about an hour of gameplay new models are not shown anymore (new spawned units are invisible, projectiles are invisible, not eben the minimap icon of new units are visible).

    Because it occurs after some playtime I thought its because of some sort of memory limit etc!? I never really understood how to destroy an actor after its occurence. Is there some way to track the number of actors? Or has anyone an idea why this is happening? :)

    If you like, test my map "Desert Tankbattle BETA" and please report bugs you find/ suggestions you have here in the forum:

    http://tinyurl.com/Tankbattle

    #2 Feb 27, 2013 at 08:55 UTC - 0 likes

    No idea regarding your main problem, but actors are destroyed through the Destroy Event+ action, if it has no additional terms it will destroy the actor running the event.

    All actors created by Blizzard have destruction triggers by default, so unless you deleted them or created your actors from scratch using a bad source they should destroy themselves.

    Is this problem occuring only for you or for all players? Does it affect everyone simultaneously? Could you play the map with some friends, with at least one using a high-end PC and another using an outdated one/crappy laptop?

    #3 Feb 27, 2013 at 11:35 UTC - 0 likes

    The problem occurs for all players simultaneously and with various hardware combinations. I experienced it yesterday the first time but other players had reported the problem bevore, so I guess it has something to do with the game "engine" itself.

    Its only my first thought that it may have something to do with actors - I cant think of another mechanic that might cause such behaviour... I dont know how to verify this though...

    #4 Feb 27, 2013 at 19:44 UTC - 0 likes

    How many instances of this actor are occuring at once?

    #5 Feb 27, 2013 at 20:18 UTC - 0 likes

    Which actor? That was also one of my questions: Is there a possibility to track the number of active actors to find out why the bug appears?

    #6 Feb 27, 2013 at 23:26 UTC - 0 likes

    Some triggers might be able to.

    Still how many times per second is the ability being used? are there any persistents? Are there any timers used by the events? How many units use it?

    #7 Feb 28, 2013 at 20:52 UTC - 0 likes

    There's a lot of debug stuff for tracking actor memory leaks like this, but they can be confusing. Check out Blizzard's actor cheats tutorial: http://us.battle.net/sc2/en/game/maps-and-mods/tutorials/actor/

    That's what you probably need to do to figure out for sure your problem. Other than that, go through any actors that you have created or edited and make sure that they contain proper destroy events. The new patch modified a lot of base unit actor data (specifically with buildings) and this can cause your own events to get messed up. Make sure the new patch didn't add anything to an actor event's "Target" field that shouldn't be there.

    #8 Feb 28, 2013 at 22:51 UTC - 0 likes

    @DrSuperEvil: In fact I dont know why this strange behaviour of the map occurs - only the visible (or better: not visible) consequences. :-D

    There are several abilities, triggers, timers and also persistent effects in the map, yes. I thougt someone might have an idea how to track the source of the problem... are we talking about the same thing? :)

    @TrenchaunT: Thx for your link.. I'll look over it.

    Does any actor need an destroy event? Or may it be enough to set its lifetime (if the option is available)

    #9 Mar 01, 2013 at 21:35 UTC - 0 likes

    Destroy event actions destroy the actor if you want it gone use it. Depending on use sometimes the built in orphan event kicks in destroying it prematurely. Other times it just does not destroy when you need. Save your map and try to simplify it without saving until the problem stops.

    #10 Mar 04, 2013 at 21:38 UTC - 0 likes

    Okay the actor cheats were very helpful. Seams I figured out the problem - one actor was not destroyes. Thanks!

  • 10 posts

You must login to post a comment. Don't have an account? Register to get one!