Hierarchical Instanced Static Mesh component culls before it is completely off screen

Hierarchical Instanced Static Mesh component culls before it is completely off screen. This only seems to happen with more than 3-4 instance elements. This also does not happen with Instanced Static Mesh Components.

1. Create a BP & open it
2. Add a Hierarchical Instanced Static Mesh component
3. In the Details panel, Add the Cube from the Engine content
4. Add 5 instance elements and space them apart
5. Compile and save
6. Add the BP to the level
7. PIE
8. Look left then right so all instances slowly move off screen

Results: The last 1 or 2 instance elements that were added will still be on screen and disappear as the blueprint is culled (attached the users repro video as well)

Expected: For all instance elements to be off screen before culling takes place

How does TextureRenderTarget2D get TArray<uint8> type data?

Why does the REMOVE method of map container remove elements have memory leaks?

Do I need to call Destory method to remove components from Actor when Destory method to remove Actor?

How do I set a material as a post-processing material?

UMG RichText not appear image when packaged

What is the cause of the packaging error falling back to 'GameUserSettings' in ue5?

Where can I download the source address of the deployment cotum service associated with the PixelStream plugin?

How to delete some elements correctly when deleting an array loop?

What is the difference between Camera and CineCamera?

How to assign a value to a member of UMG's UMaterialInterface pointer type in C++?