just switch from network operator, now on (i had to wait 5 days for the previous operator release my number!)

Evolution of module: now its time to link boids with a shader reading animate baked into textures. There is still quite a lot of work to have correct speeds and contact with ground...
videolog: polymorph.cool/wp-content/uplo

@polymorphcool

it's starting to become interesting in module: after hours of debugging of memory management, it's possible to explain to yellow cubes to follow spheres, and to spheres to avoid yellow cubes.
To have something smooth, there is a lot to params to adapt: inertia (affects acceleration), steer (affects rotation) and so on
video devlog: polymorph.cool/wp-content/uplo

Evolution of module in : i finally managed to master the memory creation in a consistent way => no more hard crashes (double free, malloc_consolidate & other funny stuff). Result: i'm now able to construct complex reaction of boids, with modification of plenty of parameters depending on the environment

just finished a serialisation of behaviours: [{"class":"test" , "active"1, "after":0, "attr":0, "eval":0, "event":0, "jumpto":1, "param_bool":0, "repeat":1,,...
It's possible to copy/paste the object + generate + edit it manually, I think it's a cool feature, even if documentation is necessary...

@polymorphcool

The integration of new objects in is quite tricky: there is no documentation of the editor classes and process (why & when "_node_removed" is called for example), so integration is a lot of trial & errors + searching in full text in sources. It's time consuming, but i start to have a better idea of how things works. Today i turned behaviours from spatial nodes to resources, and here is the result.

Working on a naming convention to quickly read the logic of the behaviour. This behaviour describes a boid randomly linked to 1 of 2 targets, afraid of anything in group 11 & 12. If in neghborhoud of group 11&12, a timer is set to 5 seconds, boid accelerates and runs. When timer stops, the speed is reset to default (5)
If you have advices on pseudocode langages that would make this "better" or easier read, please comment!

behaviour editor on its way!
@crickxson ce dont je te parlais l'autre jour: l'organisation de panneaux de contrôle, un gros kif :)

in module, i'd like to be able to define the way agents reacts. To do so, i defined a test/action chain (a behaviour)
the test editor is almost done, i think that previewing the actual code executed is useful for developers :)

is just marvellous: to develop the boid's behaviour, i have to design a new panel with a custom creation logic (using a tree is overkill). To preview and organise the , i just opened a new scene, built a mockup and place it above the editor. And voilà! Compared to QTdesigner and other UI tools, it fast and super simple to style.

@polymorphcool

graphical ID proposal for UBVA, united belgian visual artists, a collective currently emerging in
any critic is welcome!
no website to point to yet...

update on module for : you can use a "layer" system to group them with attractors, colliders and targets -> if not in the same group, boids do not floow each other, don't "see" colliders, etc.
in video, there are 3 groups: red, green & cyan
the big shaking dots are the barycenter of each group

@polymorphcool

Show more
Mastodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!