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


pack FBX asset
Credits: Special thanks to: Eno Henze @ nsynk; Beta testers: Boris Vitazek, Roy Datom, Antokhio, Sebl, Sune Petersen, Marko Ritter, Andres Alvarez, Constantine Nissidis, Gegenlicht, Johannes Lemke, Eno Henze, Zsolt Korai



is an advanced FBX importer using the official Autodesk FBX SDK 2018. It might be a better choice instead of the Assimp importer if you want to use a feature specific to FBX like:

  • Embedded media
  • Blendshapes
  • Triangulating NURBS, or higher order faces than triangles
  • Using multiple UV layers
  • Handling node transformation hierarchy properly
  • Instantly use rigged meshes (skeletal animation) coming right from the main SkeletalMesh node
  • Having a more shader oriented pipeline


If you haven't already, Get vpm

Install via vpm

Read the EULA and on the bottom you'll find a toggle button for example assets.
Open girlpower.v4p for more information ;)

Known issues:

Consult girlpower.v4p for known issues


You can read the EULA during installation. In a nutshell FBX4V is free for Non-commercial only and this fact is emphasized with a blocking popup window. There are 2 ways currently to get rid of that:

  • Request a quote at info@uberact.com for Commercial version which comes with priority support and an annoyware-less version
  • For university or hobby projects where vvvv have to start in an embedded system without human help, you can write some info about the project to info@uberact.com and we can provide you annoyware-less version if it's indeed not for commercial purpose.

microdee & Uberact


  • Fixed vpm install script not dealing with uninitialized Pack.InstallDataFromJS
  • (mp.dx/PBRIBL) Worked around nasty bug with Renderer MRT not initializing correctly inside PBRIBL in and after vvvv beta 35.5

sebescudie 09/06/2017 - 12:02

Yo md! Thanks for this release :)

Seems there's something wrong during installation : all packs install successfully (mp.dx, mp.essentials, mp.fxh) but FBX4V isn't there. Prompt says :

Installing FBX4V
Data :
VVVV Architecture seems to be x64
Removing vpm temp folder
All good in theory.

Also, VPM tells me that Message is already installed, but it doesn't seem to see I also already have dx11, and downloads it anyway.

Any clue?

u7angel 09/06/2017 - 12:07

very nice indeed. but a standalone download without packs dependencies would be awesome. i'm very willing to introduce this into our workflow and buy licences but please make it a compact, dependency free contribution.

and you might add this to the STORE ? store


u7angel 09/06/2017 - 12:10

yeah , FBX4V is not there via VPM

but you can get it here https://f001.backblazeb2.com/file/uberact/FBX4V/FBX4V-17.06.zip

microdee 09/06/2017 - 17:46

@sebescudie: If you update vpm to the latest version does it still won't install? https://github.com/vvvvpm/vpm/releases/latest
@u7angel: FBX4V depends on couple of nodes inside mp.dx and mp.essentials to generate the geometry and in mp.dx there's already a rendering pipeline which can use the ID semantics coming from SkeletalMesh. Without the new skeleton nodes in mp.essentials you wouldn't be able to drive rigged meshes, and without its generic Expand node you wouldn't be able to read many data coming from FBXFile or the raw Mesh (FBX) node. The plugin itself can exists without them but it would be a uselessly barebone thing for the average vvvv patcher. If I wouldn't have dependencies I would have to rewrite so many things postponing release and consuming my time while in fact nothing improved. So vpm takes care of installing them for you so you don't have to get braincancer.
Also please remove that link as I don't want people to download it standalone while dependencies not being there correctly and asking me about why it doesn't work.

u7angel 09/06/2017 - 18:23

i have updated vpm and it doesnt install.

when i manually install the missing fbx4v pack and put in the assets, most of the girlpower patches don't work. just some blurred background, kinda chaotic and massive patches to find the error. and yes, i hit the reload pin.

microdee 09/06/2017 - 18:27

@sebescudie, @u7angel: vpm not installing FBX4V was caused by a logical error in the installation script, you don't have to update vpm. My bad, try it now!

microdee 09/06/2017 - 19:03

@u7angel: I was using an alpha version of vvvv during development. Probably a version prior beta 35.5 because I didn't have any issues with the 3 girls showing up. Something went horribly wrong in that version apparently as Renderer (DX11 MRT) stopped initializing correctly since beta 35.5 and latest alpha. There is something dodgy with enums in general anyways nowadays. ANYHOW I introduced an ugly quick fix which hard-resets Renderer MRT with CreateNode into PBRIBL.
Try it now. Overwrite mp.dx and mp.essentials in vpm

sebescudie 09/06/2017 - 19:39

@microdee : ty, installs fine now !

tonfilm 09/06/2017 - 21:11

hello @microdee you said

Something went horribly wrong in that version apparently as Renderer (DX11 MRT) stopped initializing correctly since beta 35.5 and latest alpha. There is something dodgy with enums in general anyways nowadays.

can you be more specific? is there any patch that shows the problem? would be suuuuper helpful as we just have a release candidate out that should help us all to get rid of any of these buggers...

microdee 09/06/2017 - 22:08

@tonfilm: never managed to isolate the bug or come up with precise reproduction steps I can try it now. More specific symptom maybe in inspector all unconnected enums flash red at opening inspector, but that's it, it's a nasty one. I can try to reproduce it in an isolated patch maybe

guest 10/06/2017 - 14:27

Nice! (vpm disconnected on first attempt, slow net connection)

matka 12/06/2017 - 10:50

Wow, this is so next level microdee!
...and I've got it all working on the first attempt also
see you at NODE17

u7angel 13/06/2017 - 19:05

just had a look again, got it working after an hour of vpm downloading ;)

i wonder if it's possible to revise the node concerning performance hit. loading a scene and supplying a mesh is a simple task but kinda hefty on the cpu.

and i'd prefer simple girlpower demos, showcasing not how nice/slow something can be rendered but a concise example of the fbx plugin / features.

xxxlalala 13/06/2017 - 22:03

that assets toogle !!
Thank you very much
tha node comes at the right time for my diplomverteidigung

microdee 14/06/2017 - 04:07

@u7angel: good find! I know about performance, when I find time and motivation I will convert the whole module to a plugin. The high cycle count comes from the fact that it has quite some nodes inside which increases graph preparing time even when 80% of those nodes are not evaluating just on the frame when static data is ready. That Mesh node though is not working, and that's a honest mistake by me not removing it. Hotfix is coming. Nobody noticed that in Beta though including me forgeting about it. Only SkeletalMesh module exposes the complete and animated geometry. Even when dealing with static meshes just turn off processing.
A subjective comment on your phrasing: loading and supplying a geometry for the widest variety of possible systems is not a simple task. especially when it have to be supplied from FBX SDK where you have to deal with 5 separate matrices to get an inverse binding transform just for a single example out of many. if that would have been the case FBX4V would have been released in 2016 autumn and it wouldn't be closed source :P
Girlpower patch wise: that's exactly what's happening actually. Showing off and explaining specific features/use cases with meaningful data. girlpower.v4p for character animation, oldman.v4p for blendshape manipulation, city.v4p for animated rigid transforms and large scenes (camera movement), sponza.v4p for materials, which also contains a major mispatching so it will be provided in that hotfix. All of them indicating clearly which part is necessary for FBX4V and which is for showing off. I'm actually thinking about how to break it down better while maintaining functionality.

u7angel 14/06/2017 - 08:54

@microdee, concerning the phrasing. i wasn't refereing to the inside of the nodes. i'm talking from the users perspective. 90% of my cases is just loading meshes without materials / skeleton. so i would expect as few nodes as possible and a low cpu hit. and talking about the girlpower patches, do you really need all that stuff inside to show the tech? its kinda noisy. but i guess we both follow different concepts. i like things to be as compact as possible, small releases without module/pack noise, tidy patches showcasing only the essence. it comes down to specialized vs. multipurpose

anyway, keep up your good work.

velcrome 14/06/2017 - 21:58

when I was running xcountry and long distance in my youth, I learned about the importance of doing the last click, but also about the effect of bystanders cheering along it, so let me just join in with chris, while you just try to maintain pace for the last kilometer:
go, david, go! you just go, man! not far any more, the worst shit's already behind you. just fkin finish and you're golden!

hrovac 15/06/2017 - 14:24

@velcrome: youre good at cheering!

let me join!
@microdee: great work, so much needed and really cool, finish it!

@u7angel: jump over your shadow :) and show a little bit more appreciation for this good work(even if youre a nordic cool guy i guess)

u7angel 15/06/2017 - 14:48

@hrovac, i care a lot for such marvelous work. that's why i give feedback in the hope to see a flawless product at some point. something i'd really love to use and happily buy licenses. not sure if that is a nordic point of view ;)

microdee 15/06/2017 - 15:50

thanks people I really appreciate it, feedback like what Chris is giving is very useful, my long comment was just to clear up the situation and "calibrate" expectations

tekcor 16/06/2017 - 00:39

Hey realy amazing, awesome that face demo. Has a lot of potencial. Cant check the files now. But are there alzo exporters???

microdee 16/06/2017 - 15:39

there is no exporting unfortunately. exporting geometry from vvvv done perfectly via obj. I can't see use cases for anything more complex. In the future though I'm planning material data editing including assigning shaders to materials and assigning textures to properties and maybe editing names, but it's a long term plan.

anonymous user login


~9h ago

tonfilm: server is an IP in the network. @vueno type: \\ into windows explorer

~12h ago

vueno: where can i find the fileserver from NODE17?

~14h ago

microdee: new vpm version is out 1.2.7 https://github.com/vvvvpm/vpm/releases/latest now you can select folder with a gui (+ drag and drop folder onto the text-box)

~23h ago

vasilis: Have a great time guys at Node17!!

~1d ago

matka: @marlonossiliere have a look here topographic-phong-shader

~1d ago

metrowave: the livestream is great...big thx!

~2d ago

Damien Rave: new small project from today: piano + midi + vvvv = love https://www.youtube.com/watch?v=KS5MZ5_KRb8

~2d ago

herbst: @tonfilm no stream here. I guess you know that and are frantically working on a solution? ;)

~2d ago

tonfilm: the #livestream URL is on: vvvv-keynode-livestream