Search the Community

Showing results for tags 'locomotion'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • HTML5 Game Coding
    • News
    • Game Showcase
    • Coding and Game Design
  • Frameworks
    • Phaser
    • Pixi.js
    • Babylon.js
    • Panda.js
    • melonJS
    • Haxe JS
    • Kiwi.js
  • General
    • General Talk
  • Business
    • Collaborations (un-paid)
    • Jobs (Hiring and Freelance)
    • Services Offered

Found 1 result

  1. Hi guys I'm writing the locomotion algorithm for a character I created in blender. What I'm trying to achieve is a blend tree that will allow me to blend between the "walk-front", "strife-left" animations according to the velocity of my character (something similar to https://www.youtube.com/watch?v=Xx21y9eJq1U&feature=youtu.be&t=1263). I've been able to blend between two frames, by calculating a weighted average of the transformation matrix for each bone, so far so good. Now before going on with my development I'm asking myself the following design question. Supposing I will have a state machine to control the character, should I write an update(dt) method called at each engine tick and reposition its bones individually or rather bake at run-time a new animation with frames each time the direction/velocity changes? I just do not know the pros/cons sticking with Babylon Animations versus going on with my own update method. What I like of using Babylon Animations is the fact that I can fast up / slow down my walk cycles so to simulate faster/slower velocities. Thank you in advance for any feedback, Joez