2.9 Version, Scatter in small areas with RAM problem

My primary language is not English. I am using a translator to write.

After updating to version 2.9, a problem arose: when trying to generate grass in small areas (my test was area below X:2000; Y:2000), RAM usage increases significantly, to the point of freezing the computer. On large terrains, this does not happen.

In version 2.8, I noticed that when trying to generate grass, the density automatically increases to 30.000 ~ 50.000+ in small areas. But on large terrains, it is below 1.000, but there was no problem with RAM to the point of freezing the computer and it worked.

Will I need to increase my RAM? But this problem only occurs in small areas, it seems more like an optimization problem…

My hardware:
CPU: AMD Ryzen 5 4600G
RAM: 16gb 3000MHz (XMP profile)
GPU: NVIDIA GeForce RTX 3060 12gb

Hi there, sorry for the inconvenience. The new 2.9 Version is estimated to boost overall performance and optimization; otherwise, there might be some underlying issue in your hardware or even on our side (a possibility). A certain number of users noticed significant “slowing” of d5 after the latest update, and we suggested they update their drivers to the latest version to ensure maximum performance. Although this can be on a case-to-case basis, it is worth a shot to update your drivers.

Can you also send me the following images, which determine your System Info, RAM, and Memory Usage while running the current scene? Thank you.


The driver is the Studio version and is up to date at version 565.90. The issue happens even in empty scenes. I ran tests using a basic plane model and set its size to X:1500, Y:1500. Then I used Scatter to generate grass automatically on the plane, and that’s where the problem occurs: it goes into an infinite loop, and the RAM usage starts increasing until it fills up completely, causing the computer to freeze.

Here are some images:

Before trying to generate grass with Scatter:

After using Scatter:

When using Scatter, it gets stuck on ‘Loading’ and doesn’t move past that. This plane is small: X:1500, Y:1500. Logically, there shouldn’t be an issue in such a small space.

However, if the plane is large, this problem doesn’t occur: it doesn’t get stuck on ‘Loading’, loads normally, and it’s possible to configure the grass generation without any issues.

As you can see in the image below:

Edit:
My guess as to what might be causing the issue is the Distribution > Density setting. As I mentioned earlier, in version 2.8 this issue didn’t occur with small planes, but I could see that the Density was very high, around 50,000+. However, with large planes, as shown in the screenshot, it always stays below 1000. So, I assume that in version 2.9 the Density value might be excessively high on small planes, leading to high RAM usage.

This is more of a bug report than a personal issue. My projects tend to be smaller, but they make extensive use of small planes with grass textures. Instead of using manual Scatter, I prefer the automatic Scatter because it saves as a separate object, which I often use for ‘before and after’ views of houses. This way, I can hide the Scatter when I don’t need it.

I hope this explanation clarifies my point.

Thanks for reply.

Hello, Thank you for providing an in-depth description of the issue that you have experienced. I also tried to recreate the said environment, where I applied the scatter tool in the same dimension of the basic plane. On my end, my d5 crashes after “Loading” and would not proceed to apply compared to the scatter tool being applied in a larger plane. Hence, I have reported this bug to my team and will further fix this issue. Again, I do apologize for the inconvenience this issue has caused. :bowing_man:

hey since you guys already talked about it , I agree with this, and today reported it on support email and linked in as well , it literally boost my cpu to 100% usage and ram to 22Gb out of 32gb, I hope it will get solve asap,so we can continue enjoying this app



Hi there. The upcoming 2.9 Hotfix update already fixes this issue. Please confirm with us sooner if it has also fixed this issue on your end. Thank you.

yea last night upstairs (Oliver) confirmed hotfix coming out this friday so I guessed it should be already fixed by now , Thanks man