Ha, out of sight and out of mind.
I appreciate your good intention but what difference will it make? Feel free to do whatever you like here.
Ha, out of sight and out of mind.
I appreciate your good intention but what difference will it make? Feel free to do whatever you like here.
This forum shouldn't shut down as a mess what I'm very likely to create.Bigchillghost wrote: ↑Fri Oct 06, 2023 6:01 pm I appreciate your good intention but what difference will it make?
Bigchillghost wrote: ↑Fri Oct 06, 2023 3:07 pmand it shouldn't be a problem to tell which curve belongs to which bone if you group them one level at a time.
I was talking about reversing the nested structure. One level at a time using the chunk size to break the entire binary blob into senseful structures. The number of items in each anim group matches with the bone count so I assume they match to each bone accordingly. Or were you saying they're otherwise?
Well, I'm not in the position to say otherwise. Still fighting with the names.Bigchillghost wrote: ↑Fri Oct 06, 2023 6:38 pm I was talking about reversing the nested structure. One level at a time using the chunk size to break the entire binary blob into senseful structures. The number of items in each anim group matches with the bone count so I assume they match to each bone accordingly. Or were you saying they're otherwise?
Isn't this what you've done already? Is there a deeper nesting?Bigchillghost wrote: ↑Fri Oct 06, 2023 6:38 pm using the chunk size to break the entire binary blob into senseful structures.
Yes, that's correct. Maybe I forgot to change some naming of the elements in that template. But if you've observed the file using the template, you'd see there're 31 elements contained in each so-called animations, and under each of these elements there're 8 actual anim curves. Think of the concept that a "move" anim group consists of 4 specific anims: "move left/front/right/back". You can ignore other terms like
Yesh I was just saying it'd be clear once you got the nested structure figured out. There's no noticeable deeper nesting except for some bytes before each key count and these fields don't seem to show any hints.Isn't this what you've done already? Is there a deeper nesting?
You can just hit preview without performing individual steps as compile, execute, and convert. In fact there's no need to care about which step you should take first if you're confident about that your params are absolutely correct. The tool automatically performs the necessary steps in between. But to avoid unexpected crash it's recommended to perform these steps manually.