Pathing and Collisions

[Herman]

I was working with a function for JASS that involves movement, the way I was using it was to re-create "Jump", so I set the pathing to false to the unit does not collide with other units, and looks nice and uniform

But the unit doesn't move properly when it flys above other units...

It moves to the sides as if it still had its pathing turned on

Does anybody have any experience with unit pathing + movement bugs and possibly some information that could help me out?

 

[Kwah]

. . . set collsion size to 0??

This is just a suggestion. It might not workbut it is the best that I can come up with. Also order the unit to move to point using triggers and see how that works. . .

Hope this helps.

 

[spiwn]

Umm... he did that and it did not work correctly. That is why he wants help.

 

[Kwah]

He said pathing no collision size. . . two different things.

 

[spiwn]

Turn Collision On/Off is GUI.
SetUnitPathing(unit, true/false) is the Jass/actual.

 

[Herman]

Aye, I did the pathing to false, what spiwn is saying is exactly correct

Yeah, I can't think of anything else

I was pondering using triggered movement, but that wouldn't work with the function I am using

 

[Kwah]

Triggered units eliminate the problem.

You could make it so that when a unit orders itself to move to location have a trigger move it to that location instead.

Hope that this helps!

 

[Herman]

Thats what I am doing at the moment

I am currently triggering the movement, whilst turning collision false, I thought perhaps ordering the unit rather than moving it bit by bit via JASS would affect the in-game movement coding, but it would not suit my needs

I don't believe you can help me if you don't have any JASS knowledge, as it is a fairly advanced function I am working with

 

[Kwah]

Meh, no JASS (well just starting)

Could you not do it in GUI?

 

[PurplePoot]

Use SetUnitX/Y instead of SetUnitPosition, I'd say.

They're faster anyways.

 

[Kwah]

Why, PurplePoot why?

(Yup Sean I am learning JASS!)

 

[PurplePoot]

SetUnitPosition takes pathing into account, and I assume it's ignoring the fact that SetUnitPathing was called.

SetUnitX/Y ignore everything except... setting the unit's x/y, respectively. You can even move units off the map, and things of that sort (Though I suggest you don't, it tends to cause game crashes).

 

[Kwah]

Ok, thanks for the clarification!

 

[Herman]

SetUnitPosition takes pathing into account, and I assume it's ignoring the fact that SetUnitPathing was called.

SetUnitX/Y ignore everything except... setting the unit's x/y, respectively. You can even move units off the map, and things of that sort (Though I suggest you don't, it tends to cause game crashes).

Ohhhh

That helps alot

+rep