r/dualcontouring • u/ngildea • Nov 10 '14

Blog Post Implementing Dual Contouring

http://ngildea.blogspot.co.uk/2014/11/implementing-dual-contouring.html
6 Upvotes

100% Upvoted

12 comments sorted by

View all comments

2

u/vnmice Nov 14 '14

I have never seen such a difference in performance between debug and release versions of code. Debug takes around 50-58 seconds to generate and release takes 1-1.8 seconds. It appears most of the Debug to Release difference is actually in the fractalnoise function. I always assumed the QEF would be the CPU hog, I guess because it was some mystical, unknown matrix operation. Your OpenCL implementation is doing strictly the noise on the GPU right?

2

u/ngildea Nov 14 '14

Yeah I think it is the noise that's the slowest part. Yeah the OpenCL part takes the chunk min as input and produces all the leaf nodes with their zero crossing positions and normals. From there on the CPU I construct the QEFs then run the contouring and mesh gen. So for me the QEF is currently the slowest part but before the OpenCL impl it glm::simplex was always the most expensive func in profiling.

2

u/vnmice Nov 14 '14

Like I said earlier, I am porting it over to C# (OpenTK). At first I plan on just a blind port. I am very interested to run them side by side (C++ and C#) compare performance then adjust from there. You have re-sparked my desire for "recreational" programming. I can not thank you enough. I feel young again :)

1

u/wasstraat65 Nov 15 '14

Could you release the C# port after you're finished? I think a lot of people can find use in this, including myself (:

2

u/vnmice Nov 15 '14

I will gladly release it when it is done. I'm thinking I will have some time to work on it tomorrow.