# How to get over point count restrictions in PCG?

**URL:** <https://forums.unrealengine.com/t/how-to-get-over-point-count-restrictions-in-pcg/2842341>\
**Category:** World Creation\
**Tags:** unreal-engine, Blueprint, question\
**Created:** [October 19, 2026, 8:19am UTC](https://forums.unrealengine.com/t/how-to-get-over-point-count-restrictions-in-pcg/2842341 "2026-10-19T08:19:59Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![papa335678](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@papa335678](https://forums.unrealengine.com/u/papa335678)\
**Post date:** [October 19, 2026, 8:19am UTC](https://forums.unrealengine.com/t/how-to-get-over-point-count-restrictions-in-pcg/2842341/1 "2026-10-19T08:19:59Z")

</div>

Trying to generate grass with PCG but the surface sampler keeps throwing an error about too many points. How can I increase the number of points the surface sampler can output? I need a lot of points for grass, it currently caps at around 1.5 million. I am attempting to generate grass for a reasonably sized landscape.

---

<div class="post-metadata">

**Author:** ![Stolcjan](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/stolcjan/32/1213449_2.png) [@Stolcjan](https://forums.unrealengine.com/u/Stolcjan)\
**Post date:** [October 19, 2026, 8:44am UTC](https://forums.unrealengine.com/t/how-to-get-over-point-count-restrictions-in-pcg/2842341/2 "2026-10-19T08:44:49Z")

</div>

Have you tried splitting the landscape into smaller sections and running the Surface Sampler on each section separately? You could then generate the grass in batches instead of trying to generate all the points at once. This might help you get around the point limit without having to increase it.

Also, are you using the standard PCG Surface Sampler or a custom setup? It would be interesting to know whether the limit comes from the sampler itself or from memory/performance constraints.

---

<div class="post-metadata">

**Author:** ![ChenDong](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@ChenDong](https://forums.unrealengine.com/u/ChenDong)\
**Post date:** [October 19, 2026, 10:39am UTC](https://forums.unrealengine.com/t/how-to-get-over-point-count-restrictions-in-pcg/2842341/3 "2026-10-19T10:39:54Z")

</div>

The Surface Sampler cap is there to protect you from one giant point set, so rather than raising it, the usual approach is to not generate everything in one go:

1. Make the PCG Graph run on a partitioned component (enable “Is Partitioned” on the PCG Component / use a PCG World Actor) so generation is split per grid cell. Each cell then only generates its own points.
2. Turn on Hierarchical Generation (HiGen) and put the dense grass on the small grid size (e.g. 12.8m or smaller), with runtime generation enabled so cells generate around the player and get cleaned up behind it.
3. Lower Points Per Squared Meter, and use a Density/Self Pruning filter so you aren’t spawning points you never see. For grass, the Static Mesh Spawner with a culling distance helps a lot.
4. For truly huge landscapes, Landscape Grass Types (Landscape Grass Output material node) are built for this, because they spawn grass in the render streaming area instead of as pre-generated points.
5. Also check whether the Surface Sampler bounds are the whole landscape; limiting it to the partition bounds keeps the count per cell small.

1.5M points in one cell is usually a sign the graph should be partitioned.

---

<div class="post-metadata">

**Author:** ![papa335678](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@papa335678](https://forums.unrealengine.com/u/papa335678)\
**Post date:** [October 27, 2026, 6:13pm UTC](https://forums.unrealengine.com/t/how-to-get-over-point-count-restrictions-in-pcg/2842341/4 "2026-10-27T18:13:07Z")

</div>

Seems to come from the sampler itself, it does say to increase it’s memory but there isn’t any variable for it on the node.
