Marleys Ghost

Thanks Mack, I am sure I can squeeze a little more out of it though, which is on that never ending to do list.

Thanks RP, Mack wrote the function(s) for the random visible waypoints. Not sure what hes working on now as we are not working to a plan just each having ideas in this area, writing scripts and then adding them to "the" pile. We have an A* pathfinding library that we have been using thats written in Lua which is showing promise for quite a few things I have in mind.

To prevent non Leadwerks Engine specific entries from my Blog being automatically published here via the Blog Feed, I have removed that functionality, and will simply add a new entry title and link here for all Leadwerks Engine specific entries. Leadwerks Specific Blog Entry. AI, Waypoints, A* Pathfinding, Lua & Leadwerks.

I am currently "playing" with some ideas in lua, can anyone confirm if ForEachEntityInAABBDo() is exposed to it, or if it has a different syntax? I am working from the assumption its a syntax error on my part.

Its your friend

@NA : Looks great, shall keep my eyes open on Steam for it. Nice Job. @Pixel : "Hoodwink should be out end of the year/christmas trough Steam, episode 1 and Hidden Dawn feb next year after GDC" . http://www.leadwerks.com/werkspace/topic/3533-user-interface-shots-from-my-new-game/

The emitter editor was written way back when LE2.3 was only a few months old ... there has been a lot of changes to LE since, not sure Von04 ever updated it.

As I said Mika, "yada yada .... for a second I forgot who I was talking to "

yada yada .... for a second I forgot who I was talking to

Not sure why you call it cheating ... the whole idea behind game AI, is to create an illusion.

ADN Does all that and more ...

Well, Pathfinding is just the bus the NPC's catch to get to a fight.

ADN Lots of tools about.

To prevent non Leadwerks Engine specific entries from my Blog being automatically published here via the Blog Feed, I have removed that functionality, and will simply add a new entry title and link here for all Leadwerks Engine specific entries. Leadwerks Specific Blog Entry. 3rd Person Movement & Animation Control Rig Test

Repeat If KeyHit(KEY_ESCAPE) Exit If AppTerminate() Exit UpdateAppTime() UpdateWorld(AppSpeed()) SetBuffer(gbuffer) RenderWorld() SetBuffer(BackBuffer()) RenderLights(gbuffer) DrawText (UPS(), 0, 0) DrawRect MouseX(), MouseY(), 250, 250 Flip(0) GCCollect() Forever

like a material using the skin shaders maybe?

None, but then I had to cast a vote ... to vote in the other two sections. maybe a none option would have been prudent?

franck22000 originally posted a bug in the tracker about the impact on FPS when getting closer to decals. It was lost in the data loss. He needs to re-state the issue as Josh cant remember what it refers to. http://www.leadwerks.com/werkspace/tracker/issue-171-issue-with-decals-reloaded/

Try: texture0="abstract::shot1.dds" alphatest=1 overlay=1 clamp0=1,1 castshadows=0 shader="abstract::mesh_diffuse.vert","abstract::mesh_diffuse_alphatest.frag" for your decal .mat file ... you may need to adjust 20.0/16.0 in the creation of the decal .. to scale it.

I think the webhosting company Mark uses for Blitzmax had a bad crash on Tuesday evening, seems its taking a while to sort out.

Hi Aggror, So far I have avoided models with interiors that include an upstairs. My approach to making the node data was at best limited and quickly thrown together as proof of concept. Navmeshes/waypoints and a square on a grid are basically just ways of generating the node data. With different floors, you need to remember the new degrees of freedom, not just x and z but y as well. Which is why, IMHO, a navmesh would better serve this purpose. Or more basic, a collection of pathnodes.

No probs, glad you got it sorted.

Its version 5.6 .... try redownloading I think (cant be sure) thats all I did ...

I Think there was an update to 3DWS for the .gmf export option but it may have been lost from the forum after the 6 month data loss.

Thats just a variation on a theme with the same outcome and pitfuls. The only way to truly cripple functionality is to not have it present at all.