Animation Property and Collision Development
- Thread starter DCurrent
- Start date
Piccolo
Well-known member
Just tried to run my old code with OpenBOR 4.0 today and portions of code related to this are causing issues.
I checked the engine code to see how to adapt the code so that it works, but from what I understand some parts are missing.
It seems since then you removed attack property from animation, and moved it to an intermediary frame struct.
But this frame struct seems unaccessible from script as of now (it seems planned to be accessible through set/get_animation_frame_property but those are not implemented yet).
Collision code seems complete though, only the intermediate frame code seems to be missing. Though as dropv is now a struct I think it might be missing a script getter/setter.
I checked the engine code to see how to adapt the code so that it works, but from what I understand some parts are missing.
It seems since then you removed attack property from animation, and moved it to an intermediary frame struct.
But this frame struct seems unaccessible from script as of now (it seems planned to be accessible through set/get_animation_frame_property but those are not implemented yet).
Collision code seems complete though, only the intermediate frame code seems to be missing. Though as dropv is now a struct I think it might be missing a script getter/setter.
Yes, this is unfortunately still in development. Collision is a MODEL property, not an entity property (as are a lot of things the old script properties erroneously threw under "entity" property, and there was just too many spiderweb structures for me to get them all done before I could release.
Furthermore to that, I don't know if you saw my explanations elsewhere, but there is no such thing as a frame in OpenBOR and never has been. Well, obviously there is, but not as in there being a frame object. OpenBOR uses the SoA approach, rather than AoS. What you might think of as frames are actually parallel arrays of certain animation members.
As an example, consider delay. This is what you'd probably assume:
C:
animation->frame[frame index]->delayBut it's actually this:
C:
animation->delay[frame index]So by the same logic, collision looks like this:
C:
animation->collision[frame index]->collision_attack[collision_index]It seems like an insane layout at first, but saves a massive amount of memory and CPU by avoiding allocation of unused members. It does however pose a bit of a challenge when it comes to making script access intuitive, and I was still working on it as of 4.0 release. This semester has been thesis writing time so I haven't done much of anything, and I also took time away from engine code to work on my own projects, but I hope to get a lot more done over the Summer.
HTH,
DC