Hmm, that makes a lot of sense actually. One could say too much sense. <img src="smileys/smiley17.gif" border="0" align="middle" />

Hope you get it figured out soon! It's a brilliant plugin. Many props to you!

Sorry didn't realise how bad that sounds lol <img src="smileys/smiley2.gif" border="0" align="middle" />

The Canvas plugin makes it really easy for shadow casting. Thanks — Can anyone attempt a distance blur shader? Where at a designated point the blur is none and then increases with distance from the designated point. That would make shadows look really good (attenuation I think). I want to attempt this when I have time and learn more about GLSL..

Hey there! So I'm having an issue with the Pathfinder behavior. I have it set up for some NPCs to follow the player around after some interaction. There's a checkpoint system in place, and when the player dies the game recreates the positions of all the NPCs and inventory, etc...

However, after dying and having the stage restart, when the NPCs try to set their path to the player, the game gives this error:

Javascript error!

Uncaught TypeError: Cannot read property 'ts' of null

http://localhost:50000/RezPathfinder_behavior.js, line 141

and a little bit about it being a bug in Construct 2 or a problem with the plugin.

This occurred in both the latest and previous releases of your behavior.

I'm working on fixing this issue or at least making it clearer what is occurring. The problem is when you create a new object it loses its association with the "astar" plugin so you need to do that again. If this doesn't make sense then I can upload an example for you.

Thank you, Rez, it seems like it's all working as expected now!

I've done some tests here and the overlapping now happens on a predictable way, so I can adjust my blockers and art to it. Your suggestion of using the blocker bigger than the art was already my approach, but it was not working since the path's behavior was kind of unpredictable.

Even a minor misalignment between the path's end and the object seems solved now, that's nice! I did not bring it up since for my project it was just some minor issue, not so important.

I'll be back to my project in the next week, so will let you know if any problem arises. Thank you very much for the ace work! <img src="smileys/smiley20.gif" border="0" align="middle" />

PS: I really liked the new example and possibilities, will think about them when doing my project.

Thanks! The new GetBlockAt would help to create a push out at solid type behavior for real time movement.

New version (0.24, see first post) of the pathfinder and astar plugins. Object blocking now works correctly. New expressions: GetBlockAt and GetCostAt - useful for debugging or whatever. New example showing these new features and fixes.

Methods can be used to provide almost real time path finding with blocker movement (see new example).

Check it out! And as always let me know of any bugs and issues.

Thanks.

> Sorry been very busy lately, new job, family, work, courses, etc. When I get chance I'll look into this.

Hi 00Rez, no problem at all, I imagined that you might have been busy! I myself had been busy the last couple of days and I did not push my project far, so there were no reason for me to try to hurry you.

I've tested the project a little, and it seems that it is something related to "diagonals", not sure if it is of any help. If I choose "no diagonals", it behaviors as expected, never entering any of the blocked paths. Unfortunately, the "no diagonals" path tends to form very long, and ugly, stair-shaped paths on many situations, so I was avoiding it.

I am also using "moveto" behavior, might have hit some corner case with the use of both together, I dunno.

Anyway, thanks for you attention!

Make the blockers invisible then use a smaller object which is visible as the perceived blocker. The player will only see the smaller objects so it will look OK to the player. This is quick fix. I'll look into it.

Quite a fail with this one precision is difficult and I think the offerings from Rex and others will be far better...

Hi, first of all, great plugins! Unfortunately I'm running into some problems.

I'm not sure if I'm doing something wrong, but I created a simple logic for a moving NPC using Astar and Pathfinder plugins, it works, but as the "simulation" goes the NPC starts to "cut corners", moving inside the collision sprite. I've tried to increase the resolution of the cell size, but it keeps going inside as time passes.

I've attached a simplified capx to make my point clear, you can see that as simulation goes, the block starts to ignore the corners more and more, but not all corners. Any ideas?

My NPC astar test

Sorry been very busy lately, new job, family, work, courses, etc. When I get chance I'll look into this.

mix

Here is the amended test3.

Thanks 00Rez, works fine! )

If in real time to create obstacles, Pathfinder can find a way?

example, added DragDrop .capx

Kinda. You want to have a period before they start where you can move the blocks then calculate the paths again. You could get it to work real time to certain degree but it would involve some more checks.

I'll upload that test with a few changes... hold on.

Thank you.

You have not forgotten about my little example ? )

Here is the fixed capx.

One last thing you will need to edit the Pathfinder behavior runtime.js file.

Change this.blockSelf to false instead of true. Let me know if you get stuck doing this and I'll upload the file for you instead.

P.S. I changed the wave time to 3 seconds so change it to whatever you had.

Thank you.

You have not forgotten about my little example ? )

Sorry mix I'll link it later!