oh yeah, you are right about the corner thing the reason I'm using jumper rather than polygon pathfinding is that I haven't really been able to work out how to derive the underlying polygons from the map data - the collision is done by ray intersection checks on 2d constructed solid geometry i.e uni...

all in all pretty good you can see the top path sadly has a kink in it, but it's quite a lot better than what I was doing before.

This works great Thanks!

Hey, thanks again for this; it's really nice to have a simple and fast pathing thing to drop in. I'm wondering if you can provide any input to a problem I'm trying to solve - I want to try and smooth the path afterwards. One way of looking at it is that I want to allow any kind of movement between n...

I really hope you will reconsider removing the seeding of math.random from the default love.run. I know there's love.math.random now but I don't really care to use it when math.random is sufficient and it's pretty ingrained in me to type that. I don't think there's anything to lose by also seeding m...

haha i love the chaotic visual/audio

based on this paper http://www.dgp.toronto.edu/people/stam/ ... /GDC03.pdf

implemented this to prototype a game idea but I don't think it's going to work out - kinda cool nonetheless. feel free to use it for whatever if you have any ideas

the new joystick stuff is great!

Thanks. I was planning on improving the interface a lot, adding some randomization features, and then using it as a display in our computer science department's outreach event (intended to make kids interested in computer science). It also turned out to be a useful debugging tool for the non-shader ...

right-click + drag to connect things as inputs to others. connect the input variables at the top to the outputs at the bottom (x, y, time -> r, g, b)