yeah man!
i was waiting for something like this long time ;)

Hi,

nothing works on my computer... (WIN7, big GPU and CPU). I have no idea why...

Black or white screen only.

wow!!!!

too bad...
strange, i compiled both VS and PS with model 3.0, but seems the problem is not this for sprites...
did you tried to set a lower number of particles? like 64 instead 512 (the default value in 2d sprite patch)
... i don't have any ATI card here, keep on with this updates, hope we'll fix it at the end.

uhm...strange, none of the library patches should work then, because in each particlesGPU shader there is texture access in VS...
...maybe the problem reported by aze has to do with Sprites draw function in hlsl (see the two lines in the technique of the shader), maybe ati has a different sintax...

Yes, sprites not work on my ati mobility 5650.

PointSprites.fx is working on mine.. (mobility 5850)

Looks great, thanks for posting those!

I noticed that when I moved render window to second screen it freezes and I get a "range check error" come up in tty.
Moving it back to the first screen lets it start up again. Not sure why?

SBAM

yay for teh update!!
mindblowing stuff, natan! :)

oh nice update, I've got an odd problem though. In the new 3d Transform patch if I have OVER 9000! cubes the scaling is wrong, for instance if they're at uniform scale in xyz, and I have OVER 9000! then the Pitch input starts to affect scaling. Any ideas? I'm guessing it's to do with texture formats?

@Bitminster: i have to say that that patch is really an experimental one i did just before posting. i didn't tested it enough and i know there are problems with it. i'll check it if have time. now I have other priorities... you will see...

@Noir: wait for SBAM PT.3 ;)

SBAAAAM PT.3
BIG UP DOTTORE FOR THE XMAS PRESENT

yea awsome sbambam! thx a lot mister

Hey Dottore,

there is any way to make textured surfaces?

thanks for the release, and waiting for more ;)

Hi Dottore,

i´ve tried it but maybe (for sure) i´m missing something,
could you check the pixel shader code?
thanks again

-----------------------------------------
// PIXELSHADERS:
// --------------------------------------------------------------------------------------------------
float Alpha <float uimin=0.0; float uimax=1.0;> = 1;
float4 PS(vs2ps In): COLOR
{
   // float4 col = PhongDirectional(In.NormV, In.ViewDirV, In.LightDirV)*Alpha;
   float4 col = tex2D(Samp, In.Tex2Cd); 
   col.rgb = PhongDirectional(In.NormV, In.ViewDirV, In.LightDirV);
   col.a = Alpha;
   return col ;
 
 
 
}

your code is wrong:

• you create a float4 and assign to it the color from texture;
• but then you overwrite the rgb channels with the phong component. in this way there will be no blend between these and your texture.

this is the correct way:

// PIXELSHADERS:
 
float Alpha <float uimin=0.0; float uimax=1.0;> = 1;
float4 PS(vs2ps In): COLOR
{
   float4 col = PhongDirectional(In.NormV, In.ViewDirV, In.LightDirV);
   col *= tex2D(Samp, In.Tex2Cd); 
   col.a *= Alpha;
 
   return col ;
}

make shure the sampler (samp) is the one from your texture.
and the texCoord are the same of the position texture.

ParticlesGPU release 0.21
@catweasel: now transform works on surfaces
@lasal: surfaces have texture now. look into the code to see your error ;)

Hello again,

i don´t know if i´m doing something wrong but the new shaders doesn´t show the texture and alpha pins, but they are in the code...
weird

i´ve cleaned the cache and they are still with this problem.

i will try with my version and your code.
thanks again

of course

The same in the other computer,
has anybody the same problem?

Resolved, there was a conflict between the old and the new shaders.
thanks

Hi Dottore,

only a question,
in the 2d Dynamic field texture, is there any way to transform all the system? like in the new bicubic surface? or add to the shader a transform all pin?.

i want to make a symetrie and the only posible solution that i´ve found is to make the transform in the camera.

thanks again for your fantastic contribution.

Thanks a lot Natan,
you are very didactic, very apreciated your usefull comments.
i´ll try it.

:)

Good to ear you did it ;)
btw, the first Out.Pos is useless. this is better:

vs2ps VS(
    float4 Pos : POSITION,
    float4 TexCd : TEXCOORD0,
    float4 TexCdCol : TEXCOORD1)
{
    //inititalize all fields of output struct with 0
    vs2ps Out = (vs2ps)0;
 
    //get the position info from the Position-velocity texture:
    float2 particlePosition = tex2Dlod(SampData, TexCd).rg;
 
    Pos = mul(Pos, tW);
 
   //now apply the position taken from the texture
    Pos.xy += particlePosition;
   //apply the post mesh transform
    Pos = mul(Pos, tPost);   
 
    //then apply the tVP
    Out.Pos = mul(Pos, tVP);
    Out.TexCdCol = mul(TexCdCol, tTexCol);
 
    return Out;
}

bye! :)

fantastic work!!!!

in my ParticlesGPU_3d_Dynamic_PosCycle help patch some connections seem to be broken. i tried to fix it, but it does not work...

allthevvvverybest,

dd

@sinus: strange, is this happening with beta25 plus addons pack?

@hrovac: because we are using directly the GPU, there are many problems related to each graphic card.
in general i saw that ParticlesGPU on multiscreen is problematic: seams there's no way to share a rendered texture between two different screens; so if we evaluate the position texture (in your case the Queue shader+renderer) on the first monitor, we can't send this texture to the second screen (where there's the final render).
Try to keep all the renderer in the same screen (moving the renderer windows), also if just one goes to fullscreen.
As i said, it could also depend on your specific graphic card...
hope this will help you.
best

Natan

Hello Dottore,
only a question, in the 3d surface shader, would it be possible to adapt it for using flat shading instead phong?

how?

thanks

ari.

@natan

thank you for explaining the graphiccard issue.

i have another question:
can you please explain why the fogis not working?

thanks_alex.

ahhaha guys, there's a lot of requests coming on here... :D
the problem is atm i have no time to customize particle Shaders for every one... that's why in these days i started to write a proper guide to this library and i hope will be ready in few days. in this way you will understand how everything works and will be able to modify and try new things without my help in every step. I thing it's better, it's also more rewarding for you.
keep updated!

@sinus: i really don't know how is it possible.. try to reinstall vvvv and check if there's something missing (last directx,net 3.5,...).

Natan

hi,
for of all, vvvvery nice library, amazing. I'm triyng to use it in a multiscreen setup but it work only on the first monitor. I think it's something dx related, anyway, do you thing there's a workaround or something i can do to see the particles in all my monitors/projectors? i've tried to make a texture of the final rendering and use it splitted in 2 quads with different transforms, but nothing to do.
thx for any hint ;))

@screamer: the only thing comes in my mind is to duplicate the particlesGPU system for each monitor you need. this means duplicate the whole patch containing all the shader cycles and the final renders and to place these duplicated patches one for each screen you need (also with the relative render window).
It's not at all the optimized way (and if your particle system it's already heavy in single screen, the whole renderes could be really slow...)but you can try if it works. it would be a clear clue.

hi, i write here because this seems the much similar contribution to what i'll want to do. so probably dottore is the best one to tell me if it's possible (i tried for a day, then abandoned for my poor ability in hlsl).
there's a fantastic fluidsolver (navier stokes) in the amd/ati collection (just a sample in rendermonkey). But the problem is that this shader is a complex multipass shader, with something like 50passes. Should be fantastic to split this passes in a patch with multiple shaders (something similar to the gpu transform approach i think).
anyway rendermonkey can be downloaded here: http://developer.amd.com/archive/gpu/rendermonkey/pages/default.aspx#download

bye :)

thanks again!

Sbaaam!

so badass man thankyou so much!

magic stuff !

When are we getting this then Vux :)

Vux for president!

is there a way to add a alpha-texture to "ParticlesGPU_SplineMesh" to control the opacity of each spline-geometry?

thx

@everyoneishappy:

you have to change 2 shader:

inside bicubic_yresample:
all double to float

inside particleGPU_SplaneMesh:
change the name of the techniques (PhongPoint, PhongDirectional)(as mentioned here:beta-26-shader-syntax-error)

@Screamer; I fixed the second monitor output by opening all render windows, moving to second monitor, and then minimising back to patch.
With changing 'double' to 'float' and changing 'point' to 'pointy' and the other naming fixes, everything now appears to work perfectly on an ATI 4850.
Fabulous stuff.

Edit : The first way I tried to fix second head output was DX9Texture > AsVideo > VideoTexture. Worked, halved the frame rate.

Edit 2 : No it doesn't :o/ At least I am having a good look at the actual shader code :oD

indeed, and also the multipoint attractor would be great...

@photropik; could you please share your knowledge (or code ;) how you got to work the sprites functions on your ATI?

I am struggling since a week on my HD4870...

cheers

Hi
is it possible to spread the emitter ON/OFF ? Or do I need to create a single shader for each instance?
S>

Hi, just a shout to bring this contribution on the top of the list...

Browsing youtube I found this video:http://www.youtube.com/watch?v=eSWm_VImgFQ

the behaviour of particles is simlar to vux "ParticlesGPU_2d_Dynamic_Attractor_Bounce"

I invite you to download the binary or the source code from the description or below and testing by yourself.
http://www.craigmouser.com/random/cudaparticles.ziphttp://www.craigmouser.com/random/ParticleEngine.zip

The fact is that this program works across mulpiple heads and multiple cards!

It would be possible to make this library multi-head?
Is this a limit of shader architecture in VVVV?
Is this a limit of VVVV?

Just to know
Thanks for reply.