Hi thanks for the reply, Markus!
Thanks for looking that up for me, I had actually seen that link before and was what I was referencing. The link to the generic make your own engine style VXGI framework does indeed still work, but the ue4 github linked on that page does not return the VXGI github, which I understand might even have been removed from github entirely?
Regarless, that link only goes to the current RTXGI builds and caustics ue engine builds.
I think the ue build specifically was very deeply integrated, with correct ui elements in correct menus and modifications to both engine and VXGI implementation to work specifically with UE4 and some of its idiosyncrasies for rendering (how it handles emissive materials with specific shading types and whatnot).
So I suspect that even if I were to climb that mountain of integrating it myself I think it would probably not work regardless, or be significantly inferior to what even the very old engine builds that still exist can do.
All that said, I strongly suspect that just getting that code with all the work done and throwing it into the new engine would probably compile without too much hassle, perhaps? If not too much happened in the back end pipeline? I’m really hoping that might be the case.
I understand the project is dormant and not the direct focus of the company, as you guys are (largely rightly) pushing your RTX stuff right now, but this tech has a lot of promise, so if I could push you to make that contact on my behalf when you are able, it would really mean a lot if you could do so.
As i’ve learned from some very large source code releases from microsoft of late, sometimes things are just a simple ask away at many awesome companies, they just dont get to the right desks.
Much love and thanks for everything you do in these forums, very busy bee! -Ben