Hi Andy. As it seems the Brazil team is "back", i have a slew of unfulfilled feature requests to resubmit :)
That's it for now, but I'll be back :)
well, it's not "not working" :) It just doesn't work well. We have a recent jewelry product line which i used V4 "New Displacement" plugin to develop a wood texture (using black/white image) on those parts and got very nice results from it. I tried it also on V5 displacement and had major issues with "slashing" artifacts and the mesh tearing apart. No such problems on V4. Now i tried that same model using Brazil displacement with procedural wood texture and the same type of problems appeared. All surfaces on the model are G1 at every seam (and no polar singularities, either) but render-time displacement still gives poor results. If i can get authorization to send you the model file then i will, but i don't think the upper-crust will allow it. I'll probably have to recreate the process on another file... Also the ideal is to be per-pixel displacement, not some type of remeshing (?) at render time...
Ok, you're right i see now it is per pixel. But what i said about it being choppy is still true, using either procedural or image based textures. I also would prefer to have individual distance settings for black & white levels. Currently what is considered to be the baaseline, a pixel brightness value of 127 ?
Well, that makes no sense Andy. So you can only displace "up"? Compared to other render engines, that's pretty limited in scope isn't it? Wasn't aware of the per-object pixel displacement because I'm not using Brazil in V5 yet. I'm on Win7 but still doing all my rendering & modeling work in V4 using Brazil, so i can't install Brazil 64-bit onto my system at same time its installed in 32-bit V4. Hmmm, i guess i need to make a choice to make the jump fully to V5/64 for rendering... The problem i was seeing was using the displacment under "Surface Deformations" in the BAM shader of V4. Can you do me a favor and post an image of the per-object pixel displacement dialog?
Andrew le Bihan said:
No - 0 is the baseline. 255 is the top. If you want control over black/white, use per-object displacement (also render time per pixel) and set the offset.
AH!!! I hadn't even noticed that addition. Will play around with it and see how it goes... :)
Andrew le Bihan said:
Jonah....remember...this is *all* beta. You don't need V5 for any of this - you only need SR3 Beta 1. And the per-object displacement is on the Brazil Object Properties page
OK, i tried it.
These are obvious when depending on the per-object displacement which i hope will be addressed...
I don't think we've set up the mapping channel stuff yet. I'll put that in the pile.
Masking? Use an advanced blend.
Billboard objects will be in Rhino 5.0 SR2 - the command will (probably) be called "Cutout"