1
[Max] General Discussion / Re: Autobump concerns and 2d displacement ala vray
« on: 2018-12-03, 13:54:24 »They have some obvious negatives as universal solution but are still superior when they apply. This is why I don't believe in single solution and it was smart for Vray to retain both algorithms.
Vray2D only takes memory as high as the bitmap footprint so 16k+ maps will obviously no be its forte. But let it sample 4k maps and it will reign supreme.
The algorithm is therefore highly suitable for tiling maps, because there the memory is minimal and the effect is sharpest.
I believe Corona shouldn't so strictly adhere to single option, most users will not be confused by being given two clearly explained solutions. Just like EdgeMap already has two modes of operation, so can displacement.
And I don't think this is anyhow terrible to be solved in UI, one checkbox could be in advanced options inside CoronaMTL, another checkbox would be added to modifier. Really simple,non-confusing additions. Those who don't want to touch it, won't need to. No hassle, no confusion, everyone wins.
Indeed, I adore Fstorm displacement until I want to get creative with procedural work and then you come to a stop. So having two displacement options for two different purposes makes perfect sense ie. Bitmap Disp (so called 2D) and Procedural Disp. Voila :) So easy to say when you are not a programmer hahaha.