Jleehunter

Such a simple thing to have missed! Thank you very much for that. Duly noted!

Hello, I am attempting to use the displacer to create displacement using a very high res (8k) greeble map on a simple plane. I've attempted grayscale Tiffs, PNGs, and jpeg (didn't expect much on that one). The geometry of the plain is 100 segments by 100 with an additional subdivision surface object- so everything is Hi res. I know how to accomplish displacement in the native shader, but I would like to get to the bottom of why my results are rounded and blurry in the viewport. There is a miniscule blur on the map to reduce jagged edges, but the result in the map execution is much softer than it should be. If more detail is needed, here are links to the map and C4D file. is the displacer just not optimized/meant for importing custom maps? https://drive.google.com/file/d/1e2DQ2ps4NuGZxPLAjxh7HW5NojNEddru/view https://drive.google.com/file/d/1kbIcv7NSIKj2UMHF8le2uj2k8SnbioQy/view thank you, Jerry

I've read this to be a known issue but it was with previous iterations of C4d. Does anyone have any idea what would be causing Rigid bodies to cache but NOT the collider body? It's giving me serious render issue and i'm sure i'm missing something.

Good day all, I've just completed an expensive and grossly incorrect render. I've got simple geometry in a rigid bodies dynamic simulation. I've run the simulation, and have cached all the rigid bodies, and have a separate version with alembic files for all the rigid bodies (and collider bodies). I sent the file to a renderfarm (garage render) but the final render features the rigid bodies with all the wrong timing, suggesting that the cache nor the alembics were read. I received no errors in my uploading process but there was a point when the render paused because I needed to purchase additional credits. Does this sound familiar? I'm sure it's basic but even after crawling the documentation, google, and youtube I've missed it somewhere. thanks, Jerry

Hello All, I've exhausted my ideas on how to remedy this situation- two actually. I'm rendering out my AOV's via redshift and for one, my cryptomatte, rendered as a separate file outside the multipass option, is not showing up in the selected file destination when the render is completed. I don't see it anywhere at all. Also, my AOV's render out with a heavily color burned look - this is both with apply color processing checked, and then unchecked. I'm convinced it's somewhere in my settings bc I set up a different 'dummy' scene file and I'm able to get a separated cryptomatte and properly colored AOV's. I've attached what I hope are helpful images. Would rather not have to start from scratch with a new file. thank you for any help.

I have managed a little improvement by blurring but I still get some artifacting. I'm beginning to think I may be expecting too much from the displacement map alone- i'd intended to get smooth sides and sharp corners but maybe that's more suited to vector displacement ?

Good day all, I'm wrestling with a simple issue and am baffled as to how to fix it. Is redshift's displacement node known for being temperamental? My displacement maps continue to render out with bizarre artifacts and stepping. It's almost as if no matter how large a map I use, C4d is zooming and picking up on the pixels on the edges- but surely I needn't produce a 10k map just to avoid that, yes? -I've been sure to use maps both in hi-res PNG and Tiff form. -Grayscale, both 16 and 32 bit. -The dimensions of said maps have been up to 8k, and have matched the dimensions of my UV's. I've seen plenty of excellent displacement maps online that are PNG's at far less file sizes, so I don't think it has to be huge, right? -The UV's are definitely clean and without distortion Kind of out of ideas here. Plenty of videos out there showing how to use redshift displacement nodes but none that I've found on how to fix bad maps or even generate a good one (outside of having Zbrush) Any leads as to what I've missed? Settings and Test render attached. thank you, Jerry