Thanks for sharing tmp
looks great
Only one thing I haven't projector(dx11) node...

Ok i'll try to dwnld from github the girlpower and replace it
Thanks tmp

Confirm

Thanks again Tmp

Hello,

I need some help. I want to calibrate kinect with a projector so i use the "calibration (kinect setup)help.v4p".

I follow the steps and everything seems to go fine. My problem is that i can't understand how i can apply the trasnformation on the joints positions of the "skeleton". I tried to use "applyTrasform" and inserted thw joints positions and the "transform out" from the "calibration" node, but it didn't work. Could someone help me?

Thanks in advance.

UPDATE

changes in the latest version (08.05.15):

• introduced a separate node for kinect 2 that uses the kinect2 raytable to calculate world coordinates (instead of fov for kinect1).
• the texture-based building of pointclouds (kinect1/2 & layer) is a bit faster now (uses numthreads 8,8,1 instead of 64,1,1)

@cunk111: i dont't know contributions of evvvvil or everyoneishappy that are related to pointclouds. so i cannot say anything to performance.

I sense a disturbance in the Force.

Guys, you really have to check out the forces-part of the pack. Is already a lot of fun and contributing of additional stuff highly appreciated. We have the next implementations on the list (verlet + constraints, boids, connectall, sorting, etc.). But if you have already something on your hard-drive, feel free to implement it in the pack and make a pull request. Lets build a(nother) powerful particle-libary!

Ah, and don't miss the MultiEmitterWithGroupedForces.v4p-girlpower patch. Eventbased behaviour-switching!

Nice work, Luper. I love the wired canvas :)

Would you mind adding some attribution to the documentation of your project to the benefit of intolight and tmp's work? It has been quite an investment of time and work to get the pointcloud pack to where it is now, hence the creative common license obligation of

• Attribution
• Non-Commercial
• Share-Alike

I can see that this wasn't a project for the big bucks but for the arts, and we also appreciate you giving away the cellular shader as an appreciation in kind, so this might not apply to you at all, but for completeness:
If you want to earn money with it, don't want to mention our name in the context of your installation or give someone parts of the code under different licensing terms, just get into contact with us.
Easy, we don't bite. We just feel it unfair if someone takes the cake we baked without us having a share.

I uploaded a solution in your forum thread.

Unfortunately I cannot reply to your second question. Can you be a bit more specific? Or even better: upload a small patch that shows your problem.

Hello intolight team, and first of all thank you for this amazing work.

I'm doing a new project in my university (merging pointclouds from multiple kinects and send it to Cinema4D), and now I'm searching for the right tools.
I'm trying Processing, brekel and vvvv... so I'm wondering if it's theoretically possible to merge multiple kinects through bouygroup?

Like in your "MultipleKinectSetup" example, just on different mashines...
I'm new in vvvv, so I can't estimate if this is possible.

It would be great if you could give me some thoughts!!!

Best regards
neoshaman

edit: so it's for kinectV2

Hello velcrome and much thanks for the information.

I have some additional questions for this:

Do I need this one for merging in realtime? Would it be possible to record the data separately an merge it afterwards?

What else do I need.. or could you briefly give kind of workflow?

Sorry for the beginners questions... I really don't know where to start.

Best regards

sorry, i can not reproduce this problem.

did you checkout the latest version on github?
what does tty say?

I'm trying to work with the Skeleton Node for Kinect2, however I don't really understand the values delivered (PositionXYZ & JointXYZ). Shouldn't the x and y values always lie between -1 and 1 or how do I need to interpret them?

hello,

i'm not sure how to split the forcebuffer & ForceIndexBuffer to match the split of the pointcloudBuffer and keep the right forces at the right place, it's possible to filter PC id's at the Visualization stage but it's far slower!

any ideas?
thanks

Massive, cheers!

filterworld with kinect 2 seems to be doing nothing, emitter shows kinect image when connected directly, but shows nothing but pulsating help cube when connected to filterworld

wow! this is so cool
thanks

this great contrib makes my nvidia driver crash. beta35.2. x64 on win7 x64. please see report from tty. seems to be related to my system. all the other packs including particles pointclouds work fine. do i have to delete the latter? thank you.

Stacktrace

 bei SlimDX.Direct3D11.Buffer..ctor(Device device, BufferDescription description)
   bei FeralTic.DX11.Resources.DX11RWStructuredBuffer..ctor(Device dev, Int32 elementcount, Int32 stride, eDX11BufferMode mode)
   bei VVVV.DX11.Nodes.DX11BufferRendererNode.Update(DX11RenderContext context)
   bei VVVV.DX11.Lib.RenderGraph.DX11DeviceRenderer.ProcessNode(DX11Node node)

   bei SlimDX.Result.Throw[T](Object dataKey, Object dataValue)
   bei SlimDX.Result.Record[T](Int32 hr, Boolean failed, Object dataKey, Object dataValue)
   bei SlimDX.Direct3D11.Buffer.Build(Device device, DataStream data, Int32 sizeInBytes, ResourceUsage usage, BindFlags bindFlags, CpuAccessFlags accessFlags, ResourceOptionFlags optionFlags, Int32 structureByteStride)
   bei SlimDX.Direct3D11.Buffer..ctor(Device device, BufferDescription description)
   bei FeralTic.DX11.Resources.DX11RWStructuredBuffer..ctor(Device dev, Int32 elementcount, Int32 stride, eDX11BufferMode mode)
   bei VVVV.DX11.Nodes.DX11BufferRendererNode.Update(DX11RenderContext context)
   bei VVVV.DX11.Lib.RenderGraph.DX11DeviceRenderer.ProcessNode(DX11Node node)

   bei SlimDX.Result.Record[T](Int32 hr, Boolean failed, Object dataKey, Object dataValue)
   bei SlimDX.Direct3D11.Buffer.Build(Device device, DataStream data, Int32 sizeInBytes, ResourceUsage usage, BindFlags bindFlags, CpuAccessFlags accessFlags, ResourceOptionFlags optionFlags, Int32 structureByteStride)
   bei SlimDX.Direct3D11.Buffer..ctor(Device device, BufferDescription description)
   bei FeralTic.DX11.Resources.DX11RWStructuredBuffer..ctor(Device dev, Int32 elementcount, Int32 stride, eDX11BufferMode mode)
   bei VVVV.DX11.Nodes.DX11BufferRendererNode.Update(DX11RenderContext context)
   bei VVVV.DX11.Lib.RenderGraph.DX11DeviceRenderer.ProcessNode(DX11Node node)

   bei SlimDX.Result.Throw[T](Object dataKey, Object dataValue)
   bei SlimDX.Result.Record[T](Int32 hr, Boolean failed, Object dataKey, Object dataValue)
   bei SlimDX.Direct3D11.Effect..ctor(Device device, ShaderBytecode data)
   bei FeralTic.DX11.DX11ShaderInstance..ctor(DX11RenderContext context, ShaderBytecode bytecode)
   bei VVVV.DX11.Lib.Effects.DX11ShaderData.SetEffect(DX11Effect shader)
   bei VVVV.DX11.Nodes.Layers.DX11ShaderNode.Update(DX11RenderContext context)
   bei VVVV.DX11.Lib.RenderGraph.DX11DeviceRenderer.ProcessNode(DX11Node node)

   bei SlimDX.Result.Record[T](Int32 hr, Boolean failed, Object dataKey, Object dataValue)
   bei SlimDX.Direct3D11.Effect..ctor(Device device, ShaderBytecode data)
   bei FeralTic.DX11.DX11ShaderInstance..ctor(DX11RenderContext context, ShaderBytecode bytecode)
   bei VVVV.DX11.Lib.Effects.DX11ShaderData.SetEffect(DX11Effect shader)
   bei VVVV.DX11.Nodes.Layers.DX11ShaderNode.Update(DX11RenderContext context)
   bei VVVV.DX11.Lib.RenderGraph.DX11DeviceRenderer.ProcessNode(DX11Node node)

   bei SlimDX.Result.Throw[T](Object dataKey, Object dataValue)
   bei SlimDX.Result.Record[T](Int32 hr, Boolean failed, Object dataKey, Object dataValue)
   bei SlimDX.Direct3D11.Effect..ctor(Device device, ShaderBytecode data)
   bei FeralTic.DX11.DX11ShaderInstance..ctor(DX11RenderContext context, ShaderBytecode bytecode)
   bei VVVV.DX11.Lib.Effects.DX11ShaderData.SetEffect(DX11Effect shader)
   bei VVVV.DX11.Nodes.Layers.DX11ShaderNode.Update(DX11RenderContext context)
   bei VVVV.DX11.Lib.RenderGraph.DX11DeviceRenderer.ProcessNode(DX11Node node)

   bei SlimDX.Result.Record[T](Int32 hr, Boolean failed, Object dataKey, Object dataValue)
   bei SlimDX.Direct3D11.Effect..ctor(Device device, ShaderBytecode data)
   bei FeralTic.DX11.DX11ShaderInstance..ctor(DX11RenderContext context, ShaderBytecode bytecode)
   bei VVVV.DX11.Lib.Effects.DX11ShaderData.SetEffect(DX11Effect shader)
   bei VVVV.DX11.Nodes.Layers.DX11ShaderNode.Update(DX11RenderContext context)
   bei VVVV.DX11.Lib.RenderGraph.DX11DeviceRenderer.ProcessNode(DX11Node node)

   bei VVVV.DX11.Nodes.DX11MultiStructuredBufferRendererNode.Render(DX11RenderContext context)
   bei VVVV.DX11.Lib.RenderGraph.DX11DeviceRenderer.ProcessNode(DX11Node node)

   bei VVVV.DX11.Lib.RenderGraph.DX11DeviceRenderer.ProcessNode(DX11Node node)

   bei VVVV.DX11.Nodes.Geometry.NullIndirectDrawerNode.Update(DX11RenderContext context)
   bei VVVV.DX11.Lib.RenderGraph.DX11DeviceRenderer.ProcessNode(DX11Node node)

   bei VVVV.DX11.Lib.RenderGraph.DX11DeviceRenderer.ProcessNode(DX11Node node)

   bei SlimDX.Result.Throw[T](Object dataKey, Object dataValue)
   bei SlimDX.Result.Record[T](Int32 hr, Boolean failed, Object dataKey, Object dataValue)
   bei SlimDX.Direct3D11.Effect..ctor(Device device, ShaderBytecode data)
   bei FeralTic.DX11.DX11ShaderInstance..ctor(DX11RenderContext context, ShaderBytecode bytecode)
   bei VVVV.DX11.Lib.Effects.DX11ShaderData.SetEffect(DX11Effect shader)
   bei VVVV.DX11.Nodes.DX11StringShaderNode.Update(DX11RenderContext context)
   bei VVVV.DX11.Lib.RenderGraph.DX11DeviceRenderer.ProcessNode(DX11Node node)

   bei SlimDX.Result.Record[T](Int32 hr, Boolean failed, Object dataKey, Object dataValue)
   bei SlimDX.Direct3D11.Effect..ctor(Device device, ShaderBytecode data)
   bei FeralTic.DX11.DX11ShaderInstance..ctor(DX11RenderContext context, ShaderBytecode bytecode)
   bei VVVV.DX11.Lib.Effects.DX11ShaderData.SetEffect(DX11Effect shader)
   bei VVVV.DX11.Nodes.DX11StringShaderNode.Update(DX11RenderContext context)
   bei VVVV.DX11.Lib.RenderGraph.DX11DeviceRenderer.ProcessNode(DX11Node node)

   bei VVVV.DX11.Nodes.DX11MultiStructuredBufferRendererNode.Render(DX11RenderContext context)
   bei VVVV.DX11.Lib.RenderGraph.DX11DeviceRenderer.ProcessNode(DX11Node node)

thx for your fast reply! i am pretty sure, that i installed the proper architecture. girlpower does not work exept asymp geometry, but without colourfade. plugins work. modules all show the same symptoms. io boxes (string) need a long time to display content. then renderer goes black fullscreen for a second then. tty goes wild. system msg: nvidia driver disabled.
basically all the dynamic buffers make troubles. can do more analysis later. will post in issues. allthebest.

because of these strange driver errors i updated the nvidia driver. this issue disappeared indeed. nevertheless none of the modifiers of the pack work on my machine. it takes io boxes(string) quite some time to display content. meanwhile buffers receive 0, what they obviously dislike. more soon at the github/issues. thx!

thanks for the hint! will fix that asap (having no kinect2 atm)

I'm having trouble using custom resource semantics (with a 3d buffer)

Render semantics seem fine

Patch here https://www.dropbox.com/s/dl3wgw5axhp119u/Vortex.zip?dl=1

(look in psys Vortex - nothing is happening when addressing the 3d buffer values and applying them to the force variable)

Is it possible to use a different particles shader on different selections of particles in the same system?

Hi there. Amazing contribution. I'm coming from the world of C4D and X-Particles so just getting to grips with vvvv. So much potential! My question is, is it possible to use this pack to load in pointcloud data such as .xyz .ply or .asc. Big thanks!

@mrboni
you are using RenderSemantic(DX11 StructuredBuffer)

so you have to use

StructuredBuffer<float3> rndDir : RND3D;

as Custom Semantic Entry

the other way would be to use RenderSemantic(DX11.Layer 3d) and keep

float3 rndDir : RND3D;

@tmp - ooops, missed that. Easily done using the dynamic modifiers!

Btw - awesome contribution :)

Also - What's the best way to draw splines following a particle's path? I'm currently trying -

• attribute buffer (position out) > verlet (3d buffer) > spline buffered

but it's not quite right. Also I don't know how to set the spline count to only the number of alive particles..

@everyoneishappy - got you. That should work for my needs. Thanksya

is the technique of the right color node "set"?
what happens if you set the technique of the left color node to "set" instead of "add"?

cannot confirm. here all techniques work as advertised

currently on a 770 gtx

@luper. got the same problems. things work in pointcloud pack, but not in dx11 particles pack. no colors, no modifiers. no errors.

could not track down the problem. i think it is related to my win7. what version do you use?

ah btw.. luper also uses Windows 7 and has the same issue.
I tested it on Windows 8 -> everything is working.

so at the moment I can only recommend to update to win8 or higher.

ok it is definately a problem with windows 7.
it limits the count of bound rwstructuredbuffers to 8 and particles needs 9 at the moment. perhaps I can find a solution for that, but not in the next days. until then I can only recommend you to update windows to at least version 8 :)

yes, filterbuffer is the right node for that!
and yes - this node could be moved to selection category :)

can anyone else confirm that problem?

Hallo, I tried both vpm and github but nodes are missing, just to name a couple ScaleFade and ColorFade.
S.

is this something we should be aware of? if so, please elaborate!

problem confirmed with a fresh install.

I guess they are now replaced by ScaleByLifetime and ColorByLifetime, but without a diffff.xml this change breaks patches (including help patches)

How to control the number of emitting/max. particles? In the KinectSetup example patch, the amount of emitting particles can be increased by entering a lower number than the standard 100 in the Mod node (hope that’s the correct way). But with more particles, the emission stops in certain intervals. Seems that there is somewhere a restriction of the maximum number of particles. How to adjust/increased it?

Edit: Yeah, I think I understood now: The number for the Mod node is counting the points from the Kinect texture. 100 means that particles emitting from every 100th point. 1 means particle emitting from every point. There is one emitter who is fed with the resolution of the Kinect depth map, which defines the emitter size. Increasing this number extends the max number of particles.

Edit 2: Well, it seems that the performance drops down significantly when trying to make a more dense emission by emitting from every 5th point (also, I causes a kind of regular grid) . Could it be possible that multiple particles emitting from the same point and thus things getting slow? Maybe there is a way to restrict the emission my using filters on the Kinect textures? I tried with blur and masks, but it seems that the textures doesn’t work anymore when applying filters. Any suggestions?

Hey guys

im getting some red nodes, coming from DX11.Extensions.dll
I try to load the DLL on the vvvv patch to see if find the correct path, but only loads the filepath. it doesn't open the dialog to select which node u want to use from that DLL
any hint?

using win 10 64, vvvv 50beta35 clean with dx11 pack and dx11 particles

@manuel:

where did you get the particles pack from? latest github version? did you follow the installation instructions? did you download vvvv/dx11/dx11.particles in the same architecture? Please use TTY Renderer and paste error messages here.

@guest:
If you want to randomize it, you should use the mod-selector and play around with value + offset inputs.

There is no lifespan in dx11.pointcloud. So you should use the particles pack for this kind of behaviour. In general I recommend not to use dx11.pointcloud anymore ;)

Hi tmp,
adjusting the Mod "offset" doesn't change anything, even with different values on Mod "input". I tried a workaround by masking out the Kinect textures with noise, so that random pixels are black and not emitting. This works visually, but it seems that it doesn't affect the performance and the counted particles in relation to the max number. Even tried to mask out 80% on all Kinect textures, but the performance and particle dropout is similar to having no mask at all. So it seems that somehow invisible particles are around. Did a patch that illustrates the problem, but can't upload it here.

you could write a custom selector that takes a dynamicbuffer with 0 / 1 values as input.
this should be an easy task if you have a look at the existing selection nodes.

@tmp: Please help with some advise on the Kinect emission rate in the new dx11.particle version. I totally stuck when trying to emit from every Kinect pixel/point. As this worked fine in the old pointcloud version, it should be somehow possible with the current. Many thanks!

Hi velcrome,
Created a new thread here: https://discourse.vvvv.org/t/dx11-particles-kinect-emission-density/15101 with patches, if you want to have a look.

do you have the addonpack installed?

Hello again,

your particles are avvvvesome, but somehow I still have some red nodes. I've tested almost all help files and figured out that six nodes are red:

Constant(DX11.Particles.Effect) > ConstantGeometry
DynamicModifier(DX11.Particles.Modifiers) > Modifier_Skeleton
Scale(DX11.Particles.Modifiers) > Modifier_Scale
Target(DX11.Particles.Modifiers RWStructuredBuffer) >Modifier_Target_RWStructuredBuffer
Point(DX11.Particles.Effect) > ConstantPoint
Emitter(DX11.Particles.Emitter Layer) > BufferUtils_UpdateCounterBuffer

Do you know what to do?

Cheers

@neoshaman : are you using dx11 latest release ?

for all users who don't want to download the latest version via vpm or github:
I uploaded the latest version as zip to this contributions page.

changelog highlights:

• big performance improvements (especially on startup)
• experimental chunk logic (import ascii/ply/obj pointclouds and generate chunks -> stream them with LOD. have a look at girlpower folder)
• cloneable templates for emitters/modifiers/selectors
• geometry emitter (have a look at girlpower)
• better vectorfield handling and debugging
• a lot of small bugfixes

complete list here:
https://github.com/letmp/dx11-particles/commits/master

what exactly do you miss? if you are talking about the chunk example, you have to follow the instructions to generate the assets. they are not included because they would blow the filesize of the pack.

hello, is there a way to feed this particles data to noodles? cheers!

updated to latest vvvv & dx11 version

Question / Bugreport:

Emitter (DX11.Particles.Emitter RWStructuredBuffer) Help-Patch:

Why is first Emitter (EmitterDynBuffer1) affected by the "Force" connected to the "Selection" on the right? Seems the selection is not working properly. Would assume that only the Emitter RWStructuredBuffer-Particles are affected by that.

Check. Didn't see the spread in the z-input of the vector-node. Ok, now the whole pack is perfect. No bugs anymore. Anywhere. Chapeau. :)

@mrboni had this behaviour as well. as far as i remember you have to set the renderer inside the vectorfiledreader to r16g16b16a16float. should fix the bug.

FYI: I uploaded the latest version from github to the contribution page.
Changelog: https://github.com/letmp/dx11-particles/blob/master/CHANGELOG.md

Thanks for the fix and update!

Awesome and thx for the update!

age modifier seems to be broken right now, doesnt do anything

bur why does it not affect their lifespan?

the way i would expect age and lifespan modifiers work:

if i have particle of lifespan of 1 and i set the age to 0.8 on every frame, they should never die
if i have particle of lifespan of 1 and set lifespan to 10, it should live 10 times longer

right now if i set the age modifier to 0.8, the particles with lifespan of 1 still get emitted every second
and if i set lifespan to 1, particle never dies

thanks a lot! we were really scratching our heads on this one :)

Do you think there's a way to get DX11.particles to do a physical fluid simulation?

At the low end something like this
https://www.youtube.com/watch?v=2WYc8zCyG-w

At the high end...
https://www.youtube.com/watch?v=RMEUuxU-Dso

I know it's not trivial but want to see if I'm theoretically barking up the right tree. Do you think a custom modifier would be capable of this kind of dynamic behaviour?

People have already done flex in vvvv afaik. But it's Nvidia stuff, so you need to be a registered dev and are under legal restrictions etc

@io I know your comment was a few months ago but in case an answer is still useful.

You have to set a lifetime > 0 on the layer emitter. If you set it to 1 then it will read original positions from the layer every 1 second.

After that any other modifier can give the particles movement, eg the SelfRepulsion modifier. This is good for emitting trails of particles or making an object explode or slide away.

IF what you need is for the particles to always be stuck to the layer object than its a bit more complicated.
One approach is you keep lifetime at 0 so they reemit in the new positions every frame.
Then you could use a modifier in ADD mode to their POSITION property and you can create apparent movement.
Eg if you use the VF3D Noise and VF3D ParticleModifer nodes from the fieldtrip pack and then run some animation (integration) through the noise the layer object particles will appear to move.

In terms of a solution where you emit the particle and then it persistently sticks to the layer object but you can add other behaviours this is difficult because theres no trivial solution to targeting the new positions on the layer object. You can use the RW Buffer nodes to create and target particles based on the particles emitted by the layer Emitter BUT the particle count changes every frame and the layer emitter has no way to keep the order of the particles consistent from frame to frame. So whilst the particles do target positions on the object its effectively random which position they will run to so the particle-object cannot keep its shape and turns into noise.

Last potential solution is if your source for the layer emitter has velocity calculated already (Eg its a SDF+noise generated from VF3D noise from fieldtrip pack) then you could use that same velocity source as a modifier.

I just uploaded an update for Scale/ColorByDistance nodes on github. They have spreadable inputs for position and radius now.

DL: https://github.com/letmp/dx11-particles/archive/master.zip

About ColorByDistance, can get working colors properly,let's say I have 4 positions, and 5 color for each of them, actuallty can't get it working properly in order to manage colorsets separately, did u try that ? Guess ColorBuffer should be indexed within loop.

p.s.: In ColorByDistance help patch binsize pin is set to 13.

It means its' mandatory to use selection in order to use colors binsize ?

In my test, i'm not using any selection and behaviour, in a way, it's not correct, as you can see i'm passing colors spreaded, but everything is only using the first bin.
If, I use the selection it works, but I don't need any selection :)

What i'm asking is if colors can be managed directly from CBD shader,as i was expecting to work.
Another solution I can apply, is to have a lerp inside shader loop and so manage a fadeToBlack with another incoming float buffer, not elegant but working perfectly.

yes it makes sense in your application and I recommend to save it as a custom modifier.

but I think it doesn't make sense as part of the pack, since it breaks the default binsize/selection behaviour (if I get it right).

if you want, you can send me the custom modifier, so I can have a look at it. maybe it makes sense after all :) and if not, I could add it to the examples.

Hi,

When i tried to use constant node i only get red node. I installed with first manually, after that i tried vpm too.

Hi! Is it possible to export particles to PLY format? (for further manipulation in Houdini, for example)

I can confirm a small bug.
You used tab and a lot of spaces before each of your custom attributes, which leads to a messy type/variable extraction.

There a two solutions:
1) Exchange the spaces with a tab
2) Put a Clean (String) node between ExtractStruct and Register node

Hey, Geometry Buffer seems broken on beta 39. Results in things like this https://i.imgur.com/OxbC90W.png , while exactly following the DX11 particles workshop.

I haven't set any colours, don't know where they came from.

Which is weird, beacuse the AssimpGeometry example works.

Hi, is there a way to blend transparent particles with opaque geometry?After a long time searching about depthbuffer and softparticles still nothing comes in handy