Leadwerks 3.2 Indie : Animated Character Workflow Test

Testing the animated character workflow from Mixamo's Fuse software to Leadwerks 3.2 Indie. The character was created in Fuse then a whole category of animations from a TrueBones animation pack were re-targeted in Ikinema before the character was finally imported into leadwerks. There were no adjustments or tweaking performed at any stage (although it will be done in future when required), this was simply a test of the pipeline.

Read More

Leadwerks 3.2 Indie : I hate waiting in for deliveries! [HD]

  I hate waiting in for deliveries, so it's essential to pass the time "playing". What did you do today?

Read More

Leadwerks 3.2 Indie : Proof Of Concepts & Several Tests.

It's been a fair while since I updated my blog, I have just been busy. Although I am currently working with Unity 3D, I did purchase a copy of Leadwerks 3.1 Indie on Steam. Not really had much time to dabble with it other than to load it up when I first bought it. So I had a few hours and thought I'd have a tinker with it.



 This is just a quick video of that few hours work prototyping.

It also served as a test of Mixamo's Fuse that I got in the Steam summer sale at 80% off, a test of some textures, the model conversion workflow, a waterfall shader attempt and some Lua AI scripting.

The main test was for using the Navmesh functionality and Basic AI scripting to utilise it. The AI female NPC model was created in Fuse rigged and animated via Mixamo. Basically just a few hours tinkering with several different packages to see what I could come up with.

Read More

Leadwerks 2.5x + DarkBasic's Dark AI [Part 3]

I thought I'd spend a little more time on this integration, using the laptop whilst watching the Olympics. The next phase was to automate the routines for NPC update and compacting the code routines. Ultimately, the idea is that after the scene is loaded, it will be parsed and flagged Dark AI objects, NPC's, Paths and Zones will be set up automatically via information taken from the relative lua scripts. Paths and Zones will be later, collision objects are done, so I was working on how to go about NPC's using this method. As some may have noticed I am using the FPSC Model Pack 53 characters.

I converted about 5 or 6 characters to Leadwerks format and all the weapons for this exercise. I will eventually convert them all but I hand "prune" the bones of the rig and that takes longer than I want to spend at any one time on this side project. The FSM is still very basic but the first goal was to derive a current Animation state with each of those states having sub-FSM's to dictate the current behaviour based on the previous state and internal and external inputs. The framework is in place for the animation state which is derived by performing Boolean logic on returned values and strings from the Dark AI runtime and some stubs are in place nested inside for some basic behavioural sub-FSM's. First though I want to able to set up the scene and then place all the Dark AI objects, NPC's, Paths and Zones directly in the editor and then use the load routines to set all that up in an automagic way inside the application. The collisional objects were easy and are done with some simple tick box flagging functionality added to their property scripts. The NPC's a little more in depth , due mainly to the large amount of usable settings! lol. But I wanted to be able to place the model and then assign it some basic attributes to be read on load, this included what weapon to attach.

So that was the basic NPC property script setup (wasn't that painful anyway). So using the test scene from Leadwerks 2.5x + DarkBasic's Dark AI [Part 2], and placing a few enemies and some friendly's to look after the player, this is the result of the current stage reached in the integration.

Read More