ProceduralGraphMover doesn't adjust Bounds Y position

Hi Aron, So I’ve got the PGM working but something I noticed is that it only updates on the XZ axis.

I have another script that is adjusts the Y value so it matches the players, otherwise the scan doesn’t work properly on my terrain.

I had a look in the code and it suggested that the Y value isn’t important. Would it make more sense to increase the size of the bounds height value and does that increase the scan cost because the volume is larger?

My terrain is a custom mesh generation system with deep oceans and high mountains. I am scanning an area that is 256x40x256.

Yeah, just increase the bounding box height. It has no effect on scanning speed.