Ahoy Gareth & Elves !
Now that we threw a few grappling hooks across for the Blender Bridge I was wondering if you could demo / explain how a servo "joint" is made in InMoov.
I like the way Blender expects everything to be named .. this is a MRL mantra too.
I was hoping to capitalize on this in this way :
The MRL Blender service acts as a bridge and Blender.py is the other half in Blender.
They talk to one another all the time .. goodtimes...
I was wondering if they can agree on talking about the same things, specifically Blender Servo joints.
So, MRL Blender can say .. "hey, I got a servo here named "i01.rothead" its attached to Arduino service "i01.left" .. you got something like that in virtual land Mr. Blender.py ?"
Then Mr.Blender.py would say "Ya ! I got that .. someone imported this model with a joint/actuator which is named EXACTLY "i01.rothead" !!! What are the odds.. Lets connect them and see what happens !"
I saw some stuff on how to dynamically create an actuator - or get a reference of one by name..
The positioning of it has to be part of Blender & the Model, and the Name should allow them to bind.
Seems like this might be the way to go - but I'm pretty unfamiliar with defining such a thing in the model..
The actuator I understand a little more (but its still grey)
Thanks,
Best Regards,
Firey Pacific Rim Elves
.....same tracks.....
Yes indeed a walkthrough of the construction process is on Elves Priority list - they spent the weekend with the "InMoov Lite" ..... the little fellow found the "decimate" tool which achieved 70% reduction on things like the protective hand guards and chest plate and strangely Chin.
Am I detecting some/your thoughts on a "Mix&Match" system..... ie a box of Blender robot parts ... which will magically magnet together (however the user wishes) and if it "Virtually" works ...... an actual 3D print as good to goooooo...