» SceneGraph
This site relies heavily on Javascript. You should enable it if you want the full experience. Learn more.


plugin assets 3d mesh FBX assimp
Credits: v.1.0 to a great part sponsored by decode.io - - - vux for dx11 pack & the assimp wrapper - - - elias for some vvvv-sdk treasures


convenient handling of complex 3d scenes (DX11 & EX9)

  • easy transformation handling: don't worry about cascaded transformation hierarchy in the back
  • efficient resource handling: loads meshes and textures of the model only once



Ever got tired of binsized SetSlice, Sift, * (Transform) mayhem when using the collada/assimp nodes?
This contribution aims to solve these issues.

Collada and Assimp are both great at doing what they were intent to: loading 3d scenes. They just don't natively provide a vvvv-friendly way to actually make use of all the info they load. The mere spread outputs of transforms, meshes, textures, etc. obfuscate the hierachical relation, and forces you to juggle binsizes while keeping the differnt types in sync.

so decode.io and I put our heads together, thinking about a patcher-friendly way and came up with this.


load the scene, apply some transforms and one 'Split' like node which outputs everything nicely for a shader.

1. Load any 3d file format that Assimp can handle. (Thank vux for the assimp wrapper which is in use here to read the data.) The Scene also handles memory allocation of meshes and textures. They are uploaded once, even if used by many nodes.

2. Convenience Node displaying a browsable SceneGraph tree with all the relational info in it's place.

3. Apply transforms by specifying which part of the graph/tree should be affected. Accumulation and propagation to all children is automagically handled in the back.

4. Model outputs all the drawing relevant data of the (sub)graph in nice little spreads to use connect directly to a shader without further ado. Each meshpart has its corresponding transfrom and material in place. For not textured parts a default white texture is inserted to avoid bin sizing. Check the config pins to configure the node to do just what you need (e.g. multiple textures, bouding box, bone tranforms...)

(numbers correspond to the ones in the pic above in case you didn't notice)

techier details

The Scene (=loader node) outputs the type GraphNode which is a reference copy of the whole scene hierarchy, namely SceneGraph. Transformation can be applied on any node (or group or spread of nodes) within that graph.
in case you can draw everything at once with the same shader. you're done at this point.
If not the Selector lets you move a 'pointer' in a GraphNode another descendant than the root, thereby you select just parts of the whole model for drawing and further transformation downstream.

(more implementation details on demand)


Free for non-commercial use.
'Pay as you can' licensing model for commercial usage.

Change Log


  • fixed bug, where node names would prevent loading due to incompatibility with xml
  • fixed faulted loading with directly nested meshes


  • initial release


possible further development features

  • more details on Light & Camera
  • Animations (keyframe)
  • glTF loading adapter (that would give materialdescription by PBR parameters)
  • resource (async) preloading

Known Issues

  • toggling textures pins off will not destroy them in the EX9 version
  • Deleting the Model nodes will show an exception in the tty, don't worry
  • download

    16.10.18 [15:35 UTC] by woei | 82 downloads
    Show 1 older revisions

    Older Revisions

    20.07.18 [01:54 UTC] by woei | 137 downloads

timpernagel 20/07/2018 - 08:25

Superb! Thanks WOEI and DECODE!

readme 20/07/2018 - 11:15

This is huge and provides a solution to a problem that's been a pain in vvvv, while environments like Unity offer way smoother and integrated asset handling/scene explorers.

Exactly what I had in mind when writing this:

Still, it doesn't solve the problem that these approaches don't ship with vvvv/don't integrate well as there's no proper interface to load those modules up but to manually place them in your patch.

Anyway, I very much welcome this. Finally something that aims to provide high level user friendliness.
Just a couple of vvvv nuisances left in this regard. I will address this at the summer camp.

Thank you!

microdee 20/07/2018 - 12:04

noice! this should be pull requested into the DX11 pack

u7angel 20/07/2018 - 15:59

that saves some tedious patch work, cheers!

mburk 20/07/2018 - 16:30

Awesome, thanks! glTF support with PBR parameters would be great! any way to support this?

eno 20/07/2018 - 18:26

Chapeau guys!!!

Noir 20/07/2018 - 19:25

well done!

tgd 17/10/2018 - 21:49

Looks very useful :)

anonymous user login


~3d ago

ravazquez: @catweasel it was late when I wrote that, it's probably not the case, will test and report

~3d ago

catweasel: @ravazquez in separate instances of vvvv? Awesome if so!

~5d ago

ravazquez: @karistouf you can use my Global S&R contribution for this purpose

~6d ago

joreg: yes, no S/R. OSC is one way to communicate btw. instnces.

~6d ago

karistouf: @joreg: between 2 differents instances of VVVV on same computer,no S and R (values) possible ? only OSC way ?

~8d ago

tonfilm: glad to share the second update on the #vl #xenko #3d library: #vvvv #visualprogramming #creativecoding vl-xenko-3d-engine-update-2

~10d ago

joreg: rather toot then tweet? follow the hype and us on mastodon: https://mastodon.xyz/@vvvv #vvvv

~10d ago

ggml: any recommendation for renting visuals-grade pcs in berlin ?

~10d ago

metrowave: Structure Sensor Core now for Windows: https://store.structure.io/buy/structure-core cool features, could be useful in vvvv