Chaos Corona for 3ds Max > [Max] Daily Builds
Caustics playground!
aaouviz:
Thanks for the feedback guys.
Another issue discovered (though its working pretty damn well and I'm loving this!).
I'm using displacement map for the waves in this pool. It's working well, very fast. However, I'm guessing the calculations of the displacement are causing problems with the projection of the caustics. See two attachments - the first (camera) is incorrect, the caustics stop (near the black line - coincidental), however, if I change the view slightly (so more of the pool is visible) and restart the render, the caustics renders properly. If I then switch back to the camera view (without restarting the render) the caustics renders properly from the camera.
I hope this makes sense - happy to share scene if helpful. Any suggestions how I might overcome this problem?
soso:
Don't get me wrong, this features is one of the killer features, and it's so useful in many cases. But, because of the overwhelming NaNs pixels and slow render time, it is kinda useless in animation productions...
Tanakov:
Without wasting time I started working with caustics, so my results were weird at the beginning.
The issue you see on "Test 02" was caused by a missing texture, on a network path that wasn't even part of this shot.
Other than that MAN can't wait to try my water splashes now!
maru:
--- Quote from: aaouviz on 2019-04-24, 09:46:43 ---Thanks for the feedback guys.
Another issue discovered (though its working pretty damn well and I'm loving this!).
I'm using displacement map for the waves in this pool. It's working well, very fast. However, I'm guessing the calculations of the displacement are causing problems with the projection of the caustics. See two attachments - the first (camera) is incorrect, the caustics stop (near the black line - coincidental), however, if I change the view slightly (so more of the pool is visible) and restart the render, the caustics renders properly. If I then switch back to the camera view (without restarting the render) the caustics renders properly from the camera.
I hope this makes sense - happy to share scene if helpful. Any suggestions how I might overcome this problem?
--- End quote ---
Either switch to "World size" displacement in the Performance tab (this will calculate displacement globally, not just for the camera view, but may be slower and more RAM-consuming), or use this string option:
float geometry.displace.maxSizeScreenOutFrustumMultiplier = 1
More on string options: https://coronarenderer.freshdesk.com/support/solutions/articles/5000518663-string-options
maru:
--- Quote from: soso on 2019-04-24, 09:52:32 ---Don't get me wrong, this features is one of the killer features, and it's so useful in many cases. But, because of the overwhelming NaNs pixels and slow render time, it is kinda useless in animation productions...
--- End quote ---
Please send us any scenes where you are getting NaNs and slow rendering. We will do our best to fix it!
Also, we have not encountered any NaNs in our internal tests, so your help is invaluable!
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version