Yes, my wording was not great in that regard. I have updated the manual to clarify this.I think this is incorrect. Without including an Octane Override I'm able to add an image layer in the shader group (baked from procedural noise) and can control the displacement via the material settings. The displacement automatically updates as I adjust the displacement amount. It seems there's no need for an Octane Override in order to adjust the amount of displacement as this is being sourced from the material displacement settings native to Modo. 'Use modo render cache' and 'displace polygons' are both off.
This is due to a bug in the Render Cache. I have updated the manual to add....Again, I have to disagree here. I'm seeing very strange results (as I've been saying since the beginning of this thread). I have attached another two screen captures illustrating the point. One uses the baked version of the procedural noise layer and the second uses the actual procedural noise layer. The stunted displacement occurs in both, even when the Octane preview is stopped and restarted. 'Use modo render cache' is enabled. 'Polygon Displacement' is enabled.
My apologies for not mentioning this previously. I thought TheFoundry had fixed this issue in SP3.IMPORTANT: There is a limitation with the Modo Render Cache (as at Modo901 SP3), where the normals are NOT displaced for displaced vertices. So the normal for a displaced vertex will be the un-displaced normal. This issue has been reported to TheFoundry. This is impacts the usefulness of approach 2).
Paul
