That’s is the goal indeed.
I will try to launch a funding campaign if the add on go very well
Right now they just don’t care at all
1 Like
I’ve just been doing some quick testing of the beta, and it’s already so good. I’ll try to put some renders up later, but so far this is the easiest tool for scattering in Blender that I’ve used.
2 Likes
To everyone testing out scatter right now.
An error message will probably pop when you are testing the « Demo » biomes.
This error message is totally harmless and I just fixed it. It was just an error when Getting back to user preset, as biomes will loads their own presets in the preset editor then try to te-use original preset 
If you guys could test the preset And biome creation process when you have time, it could be cool
1 Like
Hello, I am french architect and visualizer trying ti switch to Blender.
I followed this thread since beginning but finally decided today to register to BA forum.
Keep up your amazing work, we are an army behind you!
If you need extra testers let me know, me and friend of me doing visualization are just diving into Blender!
2 Likes
Hi (Salut).
As an architect you might be interested in this add-on:
1 Like
Thanks, I am looking after it for a few weeks but for the moment I keep modeling with Sketchup because I am ultrafast with it.
But let’s keep talking about Scatter here 
1 Like
If I redownload the addon will it be the corrected version?
No I will do a second beta testing phase just before the release with a corrected version of scatter
1 Like
Hi. Probably someone know.
I try to reduce the self intersection from very dense tree patterns like so
The Tiger pattern gives some design first.
The resulting scatter has to much overlap.
Reducing density results in lots of rest self intersection or big holes there where forest should be.
So there is a nature phenomenon.
Tree crown shyness – a photogenic phenomenon in which the crowns of fully grown trees do not touch each other. This looks like a Vonroi pattern. In Blender we have an procedural Vonroi texture generator included.
So when we use Groove3D we could cut with Vonroi Structures the trees or we let them grow in Vonroi Voxel Volumes. Resulting in many individual trees.) Thats not the way.
But the other way around. Could a procedural Vonroi texture be used to generate the scatter from trees on the ground?
By design there would be less overlap.
Just thinking on a 4k map.
Your terrain is 1024m.
So you have 1pixel for 0.25cm.
You generate a procedural Vonroi with parameters that every cell is around 4m.
So when you have trees on your scatter layer who have a diameter from roughly 4m you should be able to filter all trees out .
So no tree will reach roughly the other one.
With some move on the slider you could bring them closer together or give more distance. But there should be less overlap.
With the overlayed tiger pattern you generate the design afterwards.
Here some great parametric trees for umme. Also great is the automatic LOD generation.
Simply generate an AutoLOD tree and push the group to the converted particle scatter groups.
2 Likes
Thanks to @captainkirk and @stephen_leger
For finding the source of the error.
We now know that, if enabled, Jacque lucke addon will drop an error message to anyone trying to apply a biome to the target terrain
My original meadow had much more species, and the falloff on the path was easier, but I’m quite happy with effect of only one species with… alot of instances.
It took 10GB to render, with more species it would take 100GB I guess. The reason is that there are many parent particles, with less children that I would do by hand.
1 Like
heck ? that’s really really enormous.
not normal at all.
a scene like that should be 200mo maximum…
what is the cause of this ? the use of children you said ? Witouth any child’s what is the vram ?
did you apply the particle System ? Did you use an huge hdri ? Did you use micro displacement ?
It’s because of paricles. If you don’t use a lot of children - the ram usage jumps like that. I didn’t have this problem on 2.79.
Had similar problem with previous renders with Graswald, after unchecking ‘disable children optimization’ the ram usage was acceptable (I have 32gb).
It must be a bug
I highly advise NOT the use of children with scatter then.
Opposite. Using children enormously reduces render times and RAM usage. Without children the RAM goes up like crazy.
The settings on the render above, but with Emission number divided by 16:
2 Likes
1.7gig look normal
could you give me the scene in mp ?
1 Like
Fixed the two bugs related to biomes.
- no more error msg on biomes creation
- no more error message and impossibility of creating a biome if jacque lucke object scatter is enabled
code will be avaible for a second wave of closed beta testers next week
6 Likes
Just a super basic test of an exterior house scene using the demo grass:
I tried with normal settings and using children particles, without any noticeable difference in memory usage. Using children did, however, seem to speed it up by 25 seconds. I’ll try and do some more tests, also with the Graswald assets and see how big a difference it makes with those.
I’ll try to make some photorealistic meadow biomes on release
1 Like
This looks waaaay better!
the first one looks more cgi.
love this one.
mind sharing your landscape settings?
pm me if you like
1 Like