Are Compute Shaders spreadable?

vvvv beta question
#1

Hello,
a simple question:
is a Compute Shader spreadable? How?
I see that dynamic buffers can be put toghether with Cons for dynamic buffers. If I simply put a spread of dynamic buffers in a CS this will not automatically spread.
I think this is a hard subject but maybe not.

If I have to process different spreads of datas with the same CS, how can I do it?

#2

I think Renderer (DX11 Buffer) will only accept the first element count it is given.

Maybe you could build an indexing scheme in to your compute shader though?

#3

yea it’s not gonna work like that

#4

Ok, got it, thank you.

#5

how?.. no text …

#6

not a true spread, but a bin size solution, I’m working on it.
Is very specific to my implementation but if it works I will share the result, is also part of a bezier grafic implementation, sorry but I will share at the end of the work

deadlines!!!

#7

Anyone has an idea how to do this? Been writing some of the spread generator nodes as compute shaders- to get basic function is pretty straight forward, but variable spread counts is another matter entirely…

A couple not so great things I’ve tried:

  • Uniform spread counts. You can keep everything on the gpu really easily then, but not really the desired result: in this case the spreads parameters are easily spreadable, but the spreadcount is not.

  • Calculate indices and bin ID on cpu & upload to gpu. This makes having variable spreadcounts ok, but has the downside of impacting performance any time the spreadcounts change

Thoughts?

#8

lol Kyle changing spreadcounts are anti-buffer concept, since u have to recreate resource every time u change amount of data. Buffers concept is u allocate more then enough memory once then write it once on cpu then process and read on GPU discarding undesired slices, i’m not totally sure if that statement is fully true, a lot depends on the case and a correct selection of buffer…

#9

I know what you mean. But I still think GPU solution is not too hard and might be more desirable in some cases. Like in the 2nd hack above, you are making a lookup table basically, so there is really a cpu slice per thread, not so pretty if you have a HUGE buffer. The dynamic buffer nodes are nice, if apply is not on it acts same as s&h (upstream not calculated) but yeah, still doing that with a really huge count would just make the patch crash imho

#10

Just came up with this function as a proof of concept for general solution- takes a buffer of spreadcounts/binsizes & thread ID, gives back bin ID & offset.

float2 binAndOffset(StructuredBuffer<float> binsize, float id)
{
	
	uint offset = 0;
	uint count, dummy;	
	binsize.GetDimensions(count,dummy);
	
	for (uint i=0; i < count+1; i++)
	{
		if (offset+binsize[i](i) > id) return float2(i,id - offset);
		else offset += binsize[i](i);
	}
	return 0;
}