Looks like back in 2016 a similar problem was attempted: Accessing landscape's min and max height from within material but Object bounds and Object position nodes apparently only apply to a single quad so using those to find the max and min height of a landscape yields component specific results. The only workaround that seems to work is to manually find them by dropping a plane into the landscape and manually bringing it up and down to find the values. This manual approach is non-viable for my use case as I want to calculate a great deal of things about landscape behavior based on these values and errors compound.
1 Like