>>43631
>Are there any open-source robowaifu skeletons or skeleton software already out there?
Oh sure. Probably many of them (though I myself haven't investigated this thoroughly).
Blender is probably the most famous/well-known.
Redot surely has this too. Basically any DCC package (cf.
>>415 ) that supports character animations would need such a facility.
OTOH, apart from the meticulous process of teasing out the integrated skellington support, who would want to include Blender within our robowaifu's runtime systems? Madness. Same for basically any other major system's libraries (YMMV).
We need something simple, lightweight, and fast-as-lightning. Given the safety-critical nature of such a system literally driving the motions of human-environment-adjacent humanoid robots...it also needs to be reliable & secure. Given that I've already started the process of going down this path to meet all these needs simultaneously (cf.
>>14409, et al), it just makes sense to roll our own. "NIHS" is a concern that IMO is mostly-irrelevant for our ultimate contexts here on /robowaifu/ (cf.
>>10000 ).
Daily reminder that none of this has ever been done before. Our closest corollary industries are aerospace & automotive, and no one from these industries is passing out such IP for free AFAICT. *
>tl;dr
Using general, bloated, (usually) controlled-by-
(((corporations))), "may change or die tomorrow at the drop-of-a-hat" frameworks for writing a webapp? Sure. Using them for writing
human-lives-are-now-hanging-in-the-balance-systems-software? Lol, nope. :D
<--->
Here's the library I'm considering studying for lifting simple & fast functionality out of, then integrating that within our
RW Foundations framework:
https://gitlab.com/eidheim/Skeletal-Animation-Library
I know this developer and have been using one of the programs he helped create (juCi++) for about a decade now. He values the same things that make C++ suitable for us here, and uses SFML for visualizations (which I'm also currently leaning towards). It's also MIT licensed, which means we can use it here with no restrictions.
I hope all that makes sense, Anon(s). AMA if not. Cheers.
---
* One notable exception to this is the C++ language's creator Bjarne Stroustrup and the coding standards he personally collaborated on crafting; for (what became) the F-35
Lightning II fighter jet.
https://www.stroustrup.com/JSF-AV-rules.pdf
There are also premium paid-for coding standards for automotive available. Finally, the
C++ Core Guidelines is a well-known & extensive resource for developers writing mission/safety -critical, reliable systems code:
https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines
Edited last time by Chobitsu on 01/13/2026 (Tue) 16:25:38.