Trees and grasses disappear

[masscube]

Describe the bug I have a strange bug. The trees and grasses suddenly disappear when I fly over the terrain with the camera. See the video.

There are a total of 16 terrains each with a resolution of 1024 x 1024 (terrain width/height) and terrain details also of 1024 x 1024.

I use Unity 2022.3 HDRP and the Nature Renderer with the latest version 2022.0.0.

Link to the video that shows this problem : VIDEO

To Reproduce Steps to reproduce the behavior:

1. Create 16 Terrains with each Terrain 1024 x 1024
2. Add Some gras and trees
3. Add Nature Renderer on all Terrains
4. Fly around the Terrains and see the problem

Expected behavior The trees and grasses do not suddenly disappear, as can be seen in the example video.

Screenshots

(Without Nature Renderer - it works)

(with Nature Renderer - the Terrains on the right side has no trees and grasses)

Project(please complete the following information):

• Unity version: 2022.3.9f1
• Render Pipeline: HDRP
• Render Pipeline Version 14.0.8
• Nature Renderer Version 2022.0.0

System (please complete the following information):

• Platform: Windows 10

[masscube]

Here another Video: https://massive-cube.com/work/problem/natureRenderer2.mkv Is this a bug or is there something wrong with the settings? I can't get any further.

[reVirtual]

Try disable [Only Initialize Within Rendering Distance] in NR, I use then same version of unity and NR to u, it works for me. I don't really know why, most likely it's a bug.

[preble]

I encountered the same issue with my project after upgrading from Unity 2021.3 to 2022.3 and NR 2022.0.1: when moving the camera a significant distance (1000+ units) from where it started, terrain tiles near the camera would immediately stop rendering trees/details. Updating the floating world origin also seemed to temporarily fix the issue (previously this was not necessary at such a close distance).

Disabling OnlyInitializeWithinRenderingDistance seems to work around the problem altogether though.

[dongfangliu]

Disabling OnlyInitializeWithinRenderingDistance works for me too. This shall be a bug in this option.

[tony-bera]

i am facing the same issue but i do not have the OnlyInitializeWithinRenderingDistance option in my NR, did anyone find any other way to fix this?