Im trying to modify a dynamic pathing blocker to only block specific units, but for some reason its not working.
The method im trying to use is to set the collide flags on the blocker to only block units with a certain collide flag checked.
What ive tried is unchecking all the collide flags exept for either an unused land or air flag and then checking the same flag on the unit i want to block. Despite this it is still blocking all ground units.
Any help on the subject would be much appreciated.
Ahh ha!, so thats the reason! I ran a few tests to verify this with my 3ps map and everything matches up.
This will definatly be a great workaround so that we can have everything ready and waiting once the bug is patched!
I have a great 3ps map done almost purely with triggers that got crippled by the function error, so I moved the trigger set to a new map and now the system works fine. What is really puzzeling me is that whenever the new map bounds are changed, the yaw function stops working again. It could be possible that there could be a relationship between the map bounds and the yaw function.
As for the people who are suffering from this issue, I would recomend copying your trigger set to anouther map to see if they work there.
0
Im trying to modify a dynamic pathing blocker to only block specific units, but for some reason its not working. The method im trying to use is to set the collide flags on the blocker to only block units with a certain collide flag checked. What ive tried is unchecking all the collide flags exept for either an unused land or air flag and then checking the same flag on the unit i want to block. Despite this it is still blocking all ground units.
Any help on the subject would be much appreciated.
0
I wonder if the editor will include all these models from the cinematic because you could make some insain ingame cinimatics with them. :D
This will be an epic release!
0
Ahh ha!, so thats the reason! I ran a few tests to verify this with my 3ps map and everything matches up. This will definatly be a great workaround so that we can have everything ready and waiting once the bug is patched!
@halthought -> Thanks for letting me know. :)
0
I have a great 3ps map done almost purely with triggers that got crippled by the function error, so I moved the trigger set to a new map and now the system works fine. What is really puzzeling me is that whenever the new map bounds are changed, the yaw function stops working again. It could be possible that there could be a relationship between the map bounds and the yaw function.
As for the people who are suffering from this issue, I would recomend copying your trigger set to anouther map to see if they work there.