Beny Benz

Member
  • Content count

    2
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Beny Benz

  • Rank
    Newbie

Personal Information

  • Interests
    Programming
  1. DX11 FFT on GPU

    Thank you so much for your answer. I'll then try to focus on compute shaders, because they seem to have advantages in terms of usable functions e.g. bitreverse...
  2. DX11 FFT on GPU

    Hi, I'm currently trying to write a shader which shoud compute a fast fourier transform of some data, manipulating the transformed data, do an inverse FFT an then displaying the result as vertex offset and color. I use Unity3d and HLSL as shader language. One of the main problems is that the data should not be passed from CPU to GPU for every frame if possible. My original plan was to use a vertex shader and do the fft there, but I fail to find out how to store changing data betwen shader calls/passes. I found a technique called ping-ponging which seems to be based on writing and exchangeing render targets, but I couldn't find an example for HLSL as a vertex shader yet. I found https://social.msdn.microsoft.com/Forums/en-US/c79a3701-d028-41d9-ad74-a2b3b3958383/how-to-render-to-multiple-render-targets-in-hlsl?forum=xnaframework which seem to use COLOR0 and COLOR1 as such render targets. Is it even possible to do such calculations on the gpu only? (/in this shader stage?, because I need the result of the calculation to modify the vertex offsets there) I also saw the use of compute shaders in simmilar projects (ocean wave simulation), do they realy copy data between CPU / GPU for every frame? How does this ping-ponging / rendertarget switching technique work in HLSL? Have you seen an example of usage? Any answer would be helpfull. Thank you appswert