pack vl rendering dx11 GUI
Credits: vux, flateric
The nodes resemble the beloved vvvv drawing nodes and will make you feel at home immediately. CraftLie creates a list of draw descriptions and sends them over one output pin to vvvv. In vvvv a special node takes the descriptions and renders them into a Renderer (DX11) of your choice.
No output pin mayhem and much better performance if you want to render complex scenes from VL.
Placing the drawing nodes inside your VL data types makes much cleaner patches and shows the joy of object oriented patching. This makes it perfectly suited for UIs and other drawing tasks that have complicated visual structures and need dynamic instances.
Keep in mind that the rendering still takes place in vvvv. So you can use your vvvv shader knowledge to customize the Renderer (Craftlie) and draw the shapes in a different style. It's also possible to output many layers from VL and draw each with a different custom Renderer (CraftLie).
CraftLie is, like FeralTic the dx11 library it is based on, and anagram of the major dx11 developer @flateric. Due to the fake nature of the drawing, the name fits perfectly.
Check the folder CraftLie.1.x.x\vvvv\girlpower for:
1. An overview patch which shows all nodes in action
2. How to use instancing
3. Interactive particle patch by @sebl
4. CPU core race which stresses all cores using reactive nodes
5. Sprites particles in perlin force field
6. Dynamic UI demo that creates layered windows
If you use vvvv alpha, look here for pre-releases:
wow, what's happening...checked this late last night and thought I was already in some delusional dream state ;) great contribution!
haha, didn't want to spoil all the fun in the description... ;) thanks for testing it.
This is fascinating demo of VL, but looking through the patch, to me, it is almost incomprehensible, some VL for dummy notes would be appreciated. The gui looks to be very useful, but how to add elements to it?
I still find VL to be as transparent as mud, as poor as I am at code, it seems to make more sense, which isn't the expected result of a node based GUI, surely the data flow should be visible, it feels like the part that makes sense is somehow hidden from view and you are left with magic nodes that do something secret, maybe its just me?
that is basically why you (and every other vvvv pro) should attend this:
anyway here is a tip on how to read the DynamicUI example:
it basically follows the super classic game development pattern for mainloops. as a vvvv developer you live in that world and you only need to understand one addition to the normal 'update' processing. the mainloop is split, or sliced, into several steps in the main patch:
1. check if there are any new input events
2. process all input events and update the state/logic of all elements accordingly
3. do normal "animation updates" like you are used to in vvvv
4. output layer to output pins and render it
> start over
step 2. is the new one for a vvvv developer and itself split into two steps, HitTest to check whether an element actually needs to process the input and ProcessEvents then does the actual logic and leaves the results for the Update stored in pads. so basically the pads connect the different mainloop slices by moving data/results from ProcessEvents to Update to animate/draw it...
so go into the patches and read them like this, someone from the outside is calling HitTest, if that returns true ProcessEvents will be called where the patch processes the UI logic. finally Update will be called to render animations and other stuff that was decided on ProcessEvents.
Hey @Tonfilm I'm trying to wrap my head around another aspect of the DynamicUI example.
The DynamicUI example uses a lot of delegates, but I'm having trouble putting any of the craftLie primitives into delegates as I get 'A process can only be used in a stateful patch' errors. How did you do it?
i don't know if that helps you, but if you want to call an operation of a type in a delegate, you either need to pass the instance (state) on which you want to call the operation into the delegate as an input or create an instance on the fly when the delegate gets called.
most of the craftlie primitives are only available as process nodes (not individual Create/Update operations). that doesn't work together with a delegate out of the box... but you have two options:
reminder to self -> switch craftlie primitives from Record to Class
I've got a little workaround for craftlie that could be useful for other VL beginners used to the vvvv way of doing things.
If you want to disable drawing a craftlie primitive you'll find they don't have enable pins and you can't put them in an IF region because they are stateful. This can be a bit of an inconvenience if you are using them in a larger IF region with other calculations.
However you can put stateful nodes in a REPEAT region and disable by switching it to 0 repeats. They will not maintain state.
This is also a useful hack for making the patch neater any time you would nest a FOREACH region inside an IF region. You can combine them into a single REPEAT region and set the repeat to 0 when you want to disable it. NOTE that accumulators on REPEAT regions with 0 loops won't work as 'pass arounds' like they do with a disabled IF region. If you need this functionality you will have to manually pass any data around the region with a switch. Of course depending on your use case this may make it less neat than just having the nested regions in the first place...
the upcoming version 1.0.2 will have a Enabled node that you can insert in any layer link. so you can enable/disabe wherever you want. however the Repeat disable idea is very nice, had the problem that stateful nodes cannot be place into an IF region with other patches too.
anonymous user login