We currently stopped investigating UE4.23 previews, it is too buggy for us to proceed… however about the new Rendering module, we collected enough information to determine the state for this project and if it will worth the headache of developing and supporting it. There are some game studios asking for pricing on having this feature available for them as primer with an added amount of money as incentive for us to finish it soon, but while the offer is tempting, it will make this product to be not available for the UE4 Marketplace concurrently, since they want exclusivity for quite an amount of time, so we are not considering this option, unless they agree on a simultaneous release for everyone.
We do need something working for two projects we got, so basically the best scenario will be having an average solution for our needs first, but considering the future planned expansions.
Now on when the asset will be released is the following topic, we could start saying that our goal is to have any new asset working on all APIs and rendering modes, which includes Raytracing, and the current state for Raytracing is sort of “crude” as solution. We are not a big studio, we have very limited human resources, and we have our main income from projects related to FX for film (not yet using a UE4 pipeline, something we are digging into), which we can’t put aside that to pursue one project that keeps being nuked with engine changes that makes it to not work. Right now we are at a limit on time to invest on this project without hurting other major projects we got. While the UE4 engine keeps getting better release by release, it pushes us to have more and more dedicated time on it to adapt to the changes, something we just can’t right now. We will get back to the development in August, but not in an exclusive pace, unless something changes for the better in our plans.