Holy S**T that's clever. You've exceeded me on the math.

Yeah it clobbered my PC too. I got it to work be using a much smaller cylinder and reducing the Magn (magnitude) to 1.

But if you can render with those huge magnitudes, super. My PC/Poser combo can never deal with displacements greater than about 36 inches. You are using more than 70 inches!!!!

However, the problem is the minimum displacement bounds. You need to raise it a little above the value you are actually using. Poser is stupid, it looks at the actual number that is in the Displacement input to the surface, and assumes that is the max. It isn't, because the nodes you plugged in can produce a value greater than 1, so sometimes it is wrong.

If you look closely at your render, you can see the square patches (buckets) that are missing - and you can see through them to the inside of the cylinder. The funny thing is it rendered the other side (through the missing patch) pretty well huh?

I covered this in the manual. Since you are doing really advanced stuff, you should read the "Displacements - Issues and techniques regarding complex displacements" section. The file is WritingScriptsDisplacements.html.

Here's the relevant exceprt.

If you are using displacements larger than 1 inch, Poser needs to be told. In the render settings, set the Min displacement bounds to the largest displacement value in your scene. Alternatively, you can set the Displacement Bounds on individual objects. The latter is preferable, as universally increasing the min displacement bounds slows the renderer down unnecessarily, as it assumes large displacements for all objects, even those that have no displacement.

Here's what it looks like when you forget to do this - you get holes in the prop.

---

Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)