3ICE.HU

ive been trying to make a wisp whirl were the hero enters a region and it spins him 180 degrees to another region were it turns off this trigger however ive come into alot of problems with this. does anybody have a way for me to do this in GUI?

Please Help ME!


p.s.: 3ice i know you love my pics attached =D

Actually I prefer them through imageshack or other services. My website's storage space is going to run out if we keep using it (eventually).

As for your question, the most obvious thing I'd like to point out is that moving a unit by 180 pixels every 0.06 seconds is going send it flying off the edge of the map almost instantly (in a nice arc). Try moving it by 3-5 pixels instead of 180.

not sure how im to do this, its weird because i have to enter the region 2 times (usually doesnt work first time) and the 180 is its offset

Solved in-game.

shinning_faith wrote:

helpme1.png

helpme2.png

helpme3.png

helpme4.png

helpme5.png

ive been trying to make a wisp whirl were the hero enters a region and it spins him 180 degrees to another region were it turns off this trigger however ive come into alot of problems with this. does anybody have a way for me to do this in GUI?

Please Help ME!


p.s.: 3ice i know you love my pics attached =D

The part with the move unit instantly to point, if you want less leaks use "call RemoveLocation( udg_demonp1 )" to rid of the drastic leaks that would be caused.

Thurst213 wrote:The part with the move unit instantly to point...

If you are referring to a part of his post, please quote that part of the post only. (Like I did now.)

I didn't see your post, sorry. If I did, I would of used it. Thanks anyways

What I meant is: Don't waste space by quoting a whole page of text when it is not going to mean anything.
Quote only what you need. In this case, you should have quoted the screenshot of the trigger you were talking about.

EDIT: And you gave bad advice anyway. The massive leaks are not caused by the second trigger. Nobody is going to cringe over demonp1, that is just one point leaked at the 0.1 second mark:
One leak = not important.
(EDIT2: And that is not even considered a leak, since the variable is used in the next trigger, so it needs to stay in memory.)

What hurts is the point leaks created every 0.06 seconds in the third trigger:
Thousands of leaks.
(Exactly 16.666... leaks per second, which is 1000 leaks per minute, which is 60000 leaks per hour.)

whats an easy way to solve that leak?

Follow a memory leak tutorial.