Jump to content

Leadwerks 3.2 Indie : Proof Of Concepts & Several Tests.

Marleys Ghost

2,419 views

blog-0474827001404476292.jpgTo prevent non Leadwerks Engine specific/Related 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/Related entries.

 

 

 

 

Leadwerks Related Blog Entry.

Leadwerks 3.2 Indie : Proof Of Concepts & Several Tests.



15 Comments


Recommended Comments

Hey Jorn, that was one of the "tests", there is very little information on what has and conversely not been implemented with recast and detour. Detour is a pathfinding and spatial reasoning toolkit, if memory serves (it does now an then even at my age!) I think the spatial reasoning uses entity velocities to calculate avoidence steering, hence if the player stops they will bump into him. With so little information about the intergration into LE3.x though I am just guessing.

Share this comment


Link to comment

Just out of curiosity, are you setting the player and the NPCs 'SetNavigationMode' to true? I am curious if that will make the NPCs take the player into account when following a path. Or is this command only for static objects?

Share this comment


Link to comment

Hey Mack, as far as I could workout, and could be wrong, SetNavigationMode is for static objects which will (or will not) effect the building of the navmesh, I don't think its "dynamic", I am not setting it true on the NPC's. I'd imagine its all handled via detour and however thats been intergrated into the character controller. But again with so little info on the subject I am just guessing.

Share this comment


Link to comment

Hmm good to know as like you said there's so little information available. But I vaguely remember Josh showing a video of dynamic pathfinding during the pre-LE3.0 days - dynamic meaning that objects actively finding new paths as the something new was introduced into its current path.

Share this comment


Link to comment

I think its all changed since 3.0, but how and what to is just speculation.

 

 

With the current way its done I understand the argument for a controller not being over a certain height or diameter but not being able to resize below those parameters makes no sense. There is very little control over the system. I do hope soon there will be more information on this functionality.

Share this comment


Link to comment

Interesting stuff. I have been making the steering behavior for my NPC's this week. I didn't take in to account that recast perhaps already uses steering controls.

 

As per the terrain update in 3.1, dynamic navmesh generation is disabled. You now have to generate in the editor or call the API call manually.

Share this comment


Link to comment
As per the terrain update in 3.1, dynamic navmesh generation is disabled. You now have the generate in the editor or call the API call manually.

 

Really? was that because it took too long to recalculate on terrains in general or large ones? I'd have thought rather than disable dynamic navmesh generation simply have its default as we have it now with dynamic navmesh generation an option that is selectable and not penalise those who are not using large terrains.

Share this comment


Link to comment

Agree with that statement MG. Seems a waste considering that was one of the big advantage/selling point for recast/detour. I guess we can throw a raycast check continuously in front of all our NPCs like we did with Astar... but seems a waste considering recast/detour has the ability to take care of this problem.

Share this comment


Link to comment

The dynamic nav mesh was taken out before any of the performance bugs were fixed. Maybe now would be a good time to check and see if dynamic nav mesh works better with the higher frame rate.

Share this comment


Link to comment

Luckely you can still call it though.

I would like to see an example in lua where this can be done via another thread because at the moment it causes a ridiculous glitch. And can this be done to a NavMesh that was already created in the Editor or would you have to forsake the Editor version?

Share this comment


Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Add a comment...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Blog Entries

    • By Josh in Josh's Dev Blog 8
      You might have seen this graphic comparing the size of the world in different games. I've played Fuel, and never reached the end of the world in that game. You can drive for a very long time on those roads.

      We want to use the new engine for realistic simulations of air and ground movements. At normal cruising altitude of a commercial airliner, the pilot has a view range of about 400 kilometers. The image below shows that area (800 x 800 km). You can see the areas of the biggest games ever fit neatly into the corner of just our visible area.

      The gray space above is not the total world size, it is just the area you can see at once from high altitude. The total world size is about 50 times bigger.
      This is what I am working on now.
    • By Josh in Josh's Dev Blog 26
      Gamers have always been fascinated with the idea of endless areas to roam.  It seems we are always artificially constrained within a small area to play in, and the possibility of an entire world outside those bounds is tantalizing.  The game FUEL captured this idea by presenting the player with an enormous world that took hours to drive across:
      In the past, I always implemented terrain with one big heightmap texture, which had a fixed size like 1024x1024, 2048x2048, etc.  However, our vegetation system, featured in the book Game Engine Gems 3, required a different approach.  There was far too many instances of grass, trees, and rocks to store them all in memory, and I wanted to do something really radical.  The solution was to create an algorithm that could instantly calculate all the vegetation instances in a given area.  The algorithm would always produce the same result, but the actual data would never be saved, it was just retrieved in the area where you needed it, when you needed it.  So with a few modifications, our vegetation system is already set up to generate infinite instances far into the distance.

      However, terrain is problematic.  Just because an area is too far away to see doesn't mean it should stop existing.  If we don't store the terrain in memory then how do we prevent far away objects from falling into the ground?  I don't like the idea of disabling far away physics because it makes things very complex for the end user.  There are definitely some tricks we can add like not updating far away AI agents, but I want everything to just work by default, to the best of my ability.
      It was during the development of the vegetation system that I realized the MISSING PIECE to this puzzle.  The secret is in the way collision works with vegetation.  When any object moves all the collidable vegetation instances around it are retrieved and collision is performed on this fetched data.  We can do the exact same thing with terrain   Imagine a log rolling across the terrain.  We could use an algorithm to generate all the triangles it potentially could collide with, like in the image below.

      You can probably imagine how it would be easy to lay out an infinite grid of flat squares around the player, wherever he is standing in the world.

      What if we only save heightmap data for the squares the user modifies in the editor?  They can't possibly modify the entire universe, so let's just save their changes and make the default terrain flat.  It won't be very interesting, but it will work, right?
      What if instead of being flat by default, there was a function we had that would procedurally calculate the terrain height at any point?  The input would be the XZ position in the world and the output would be a heightmap value.

      If we used this, then we would have an entire procedurally generated terrain combined with parts that the developer modifies by hand with the terrain tools.  Only the hand-modified parts would have to be saved to a series of files that could be named "mapname_x_x.patch", i.e. "magickingdom_54_72.patch".  These patches could be loaded from disk as needed, and deleted from memory when no longer in use.
      The real magic would be in developing an algorithm that could quickly generate a height value given an XZ position.  A random seed could be introduced to allow us to create an endless variety of procedural landscapes to explore.  Perhaps a large brush could even be used to assign characteristics to an entire region like "mountainy", "plains", etc.
      The possibilities of what we can do in Leadwerks Engine 5 are intriguing.  Granted I don't have all the answers right now, but implementing a system like this would be a major step forward that unlocks an enormous world to explore.  What do you think?

    • By Haydenmango in Snowboarding Development Blog 6
      So I've been researching snowboarding lately to get an idea of what animations and mechanics I need to create for my game.  I have learned lots of interesting things since I've only seen snow once or twice in my entire life and have never even tried snowboarding or any other board sports (skateboarding, surfing, etc.) for that matter.
       
      Snowboarding tricks are quite interesting as they are mostly derived from skateboarding.  Snowboarding tricks pay homage to their equivalent skating tricks by sharing many concepts and names.  For example basic grabs in snowboarding share the same concepts and names as skateboarding: indy, mute, method, stalefish, nosegrab, and tailgrab.  Something interesting to note is in snowboarding you can grab Tindy or Tailfish but this is considered poor form since these grabs can't be done on a skateboard (due to the board not being attached to the skaters feet) and grabbing these areas is generally something a novice snowboarder does when failing or "half-assing" a normal grab.  Check out this diagram to see how grabs work -
       
       
      So, after reading lots of text descriptions for tricks I was still confused by what all these terms meant and how they were actually applied.  So my next step was to look up these tricks actually being done and I found some really cool videos showing off how to do various tricks.  This video in particular is the best reference material I've found as it contains nearly every trick back to back with labeled names and some tweaks -
       
      Sadly my rigged model doesn't handle leg animations with the snowboard that well so I can't animate as many tricks as I want to.  Regardless there will still be around 15 total grab/air tricks in the game.  Now it's time for me to stop procrastinating and start animating!  
×
×
  • Create New...