Bullet not spawning correctly

[Diehard@Azeroth]

I have a really annoying problem here... i used x and y intercepts and some math to calculate a bullets movement, anyhow, the spawning place of the bullet can sometimes be in the casters x and y intercept location and sometimes it spawns to the left or even right (just a bit) of the caster and goes to the angle from there. Can anyone tell me why? the bullet does have locust (collision off) and spawns in the casters x and y intercept.
Here is the trigger:

• ShootingStart
  • Events
    • Unit - A unit Starts the effect of an ability
  • Conditions
    • (Ability being cast) Equal to Sniper Shot
  • Actions
    • Custom script: local unit u = GetTriggerUnit()
    • Custom script: local real x = GetUnitX(u)
    • Custom script: local real y = GetUnitY(u)
    • Custom script: local location t = GetSpellTargetLoc()
    • Custom script: local real distX = GetLocationX(t) - x
    • Custom script: local real distY = GetLocationY(t) - y
    • Custom script: local real dist = SquareRoot(distX*distX + distY*distY)
    • Custom script: local real dx = distX/dist*udg_BulletSpeed*udg_Time
    • Custom script: local real dy = distY/dist*udg_BulletSpeed*udg_Time
    • Custom script: local real angle = bj_RADTODEG*Atan2(distY, distX)
    • Custom script: call RemoveLocation(t)
    • If (All Conditions are True) then do (Then Actions) else do (Else Actions)
      • If - Conditions
        • i Less than 8192
      • Then - Actions
        • Set i = (i + 1)
      • Else - Actions
        • Set i = 0
        • Set i = (i + 1)
    • Custom script: set udg_Bullet[udg_i] = CreateUnit(GetOwningPlayer(u), 'e000', x, y, angle)
    • Custom script: call AddFlying(udg_Bullet[udg_i])
    • Custom script: set udg_BulletMoveX[udg_i] = dx
    • Custom script: set udg_BulletMoveY[udg_i] = dy
    • Unit - Set the custom value of Bullet[i] to i
    • Set Bullet_Dist[i] = Bullet_Max_Dist
    • Unit Group - Add Bullet[i] to BulletGroup
    • Trigger - Turn on MovingBullet <gen>

cast backswing: 0
blend time: 0
maximum pitch angle: 0
maximum roll angle: 0
projectile impact z: 70
projectile launch z: 70
propulsion window degrees: 60
ms: 1
turnrate: 3 (max)
collision: 0 (also added locust)
movement type: foot

+rep

 

[Element of Water]

do

call SetUnitX(udg_Bullet[udg_i], x)
call SetUnitY(udg_Bullet[udg_i], y)

CreateUnit takes into account collision even if the unit you are creating shouldn't have collision.

 

[Diehard@Azeroth]

Element of water, i shall try it, and if it works im in love with you roflmao, Thanks a bunch dude... really thanks a fucking bunch, il try it now lol +rep checking it out
EDIT--- THANKS A BUNCH ELEMENT, I WILL PUT YOU IN CREDITS IN MAP FOR HELPING OUT IN BUGS OMG NOW IT LOOKS GREAT IN ABSOLUTELY EVERY ASPECT YAH00!... lol thanks bro
-----------------------------------
thank god for natives huh? >> setting their coords without taking collision into consideration... so good ^^

 

[The Reborn Devil]

If you set collision to 0, movement type to none and add locust to it, it should ignore collision.

 

[Element of Water]

Not when you create the unit, though. Even creating a unit with no collision takes into account whether the terrain is pathable.

 

[The Reborn Devil]

It checks the terrain, but it ignores other units.

 

[Element of Water]

I don't think so. It checks anything that could be pathable. I think this is because other units take the dummy into consideration with pathing, but the dummy doesn't take them into consideration. CreateUnit uses the units' considerations which are already there rather than the new unit's.

 

[Cheezeman]

I thought that shading locals doesn't work in 1.24?

 

[Element of Water]

It doesn't, but Diehard@Azeroth isn't shading locals. He's using them directly.

 

[Cheezeman]

So his i is refering to i, and not udg_i?
Edit: Huh no wait... i is a global and is never declared as a local in the function.
Silly me...

 

[Element of Water]

No, his i refers to udg_i, but if you look, you never see "i" used in the custom scripts, just udg_i, and he never declares a local called "udg_i". He just uses it as a global.

 

[Cheezeman]

No, his i refers to udg_i, but if you look, you never see "i" used in the custom scripts, just udg_i, and he never declares a local called "udg_i". He just uses it as a global.

Ha! I edit my post before you posted this!
Now you're the guy misreading things

 

[Element of Water]

Well, when i started posting it, I was giving you some decent information . You just have to go and ruin it like some 2-year old....

Spoiler

[/joke]

 

[Cheezeman]

Well.
Yes.

I find it amusing that this is more of a direct-chat like MSN rather than a forum.

 

[Element of Water]

Ok, stop the offtopic, this thread has been solved.

~CLOSED~

(Or would be if I was a moderator...)