Видео

Yes you can :) I showed how to set them in a BP, you just have to call the set function when your slider change. As for doing a slider, that's out of the scope of this tutorial, but I'm sure you'll find other tutorials for that.

@@adrienlogut3482 can you explain a bit more detailed how i would create the function to set treedensity in a blueprint pls :c ? think i know how to do the slider when i got the function

It's in the video ;) ruclips.net/video/0NQAQPaJ8ko/видео.html

you are a goat!

Perhaps :)

@@adrienlogut3482 are you directly working with epic ?

Yes :p

@@adrienlogut3482 alors c'est prévu ces améliorations ? :p

@@Dhieen Pour des trucs plus complexes, ca va se passer avec des data assets (mes dernières videos en parlent). Pour le drag and drop, oui c'est prévu pour 5.6

Landscape is now retrieved with a Get Landscape Data node

With the gather node and the pin Dependency only

I randomly found the solution somehow. There's something called PCG Volume (which I had never heard of or don’t remember), and I didn’t use it to generate objects. It’s a strange thing because I don’t recall using something like this before. But it could be that I used it once, and then when I made a sample of that map for other projects, I completely forgot about the existence of this PCG Volume, which is why nothing was working. But I feel great that I found the solution myself after struggling with it for almost a day, haha.

PCG volume is the simplest way to have PCG working :) in the video I drag the graph in the map which automatically create a PCG volume with this graph assigned. If you tried with a custom actor, that's different ;) PCG needs bounds to generate that's what I explain in the second part!

Yes it's possible though a bit more complex. You can convert level instances to PCG data assets. The selection process is the same as meshes, but to spawn them you have to use the Load PCG data asset node and use the copy points node. From there you can spawn the associated meshes. I don't know if you can spawn level instances directly as actors too, if that's another possibility

@@adrienlogut3482 Ye its weird, I have the exact same setup but instead of meshes a PCG data set in my structure, no matter what I do the Load PCG data node keep throwing a "unable to load PCG data" ? - I already found a way to do it by using a int multi selection node but this way you have all the PCG data assets loaded in the graph at all times. So doing it with data assets would be more beneficial haha. Anyhow, thanks for the quick reply! Your work is impressive

@@adrienlogut3482 After a bit more trouble shooting I actually got this to work! Thanks for the guidance! Funny enough, I was watching the advanced PCG vid from Unreal fest and they went over the same approach, i just skipped it lol

Not easy in 5.4 but feasible. You can try to extract the path to the static mesh using Get Actor Property and pass it into a Mesh Sampler. In 5.5, there will be an option "From Input" on the mesh sampler that will allow you to sample an actor directly, utilizing the Geometry Script API to convert a Scene component to a Dynamic mesh. This will on top of that allow for Vertex Instanced Color.

The logic I show there works for any Object, as I'm working with paths. It would work with Actors, or any object actually.

​@@adrienlogut3482 Thank you very much for your reply. The problem I encountered was that pcg setting assets needed to be instantiated before it could be used normally, and this operation was completed automatically when I dragged pcg setting into pcg graph. I could not find a way to create pcg setting instance manually. And what I get through the path is only a pcg setting path reference, not the model and material path in it

IIRC you can right click on a node and create an instance out of it

I found the answer, just use PCG Data Assets instead of PCG Setting, right click the Asset operation in the level to create PCG Data Asset from the level, then use Load PCG Data Asset node in PCG Graph, use blueprint variable to override the asset input, You can freely change the Data Asset you use

It depends where you want to do it. If you want to do it in the loop subgraph, you could use a Branch node and use a compare node to compare your ID to the one you want to work from (like Tree) and plug it in the Output to B override of the Branch node (like I did with the debug node). Then you can work from there with only the tree points (you can even add those points to the Previous Points data, to take them into account into the difference nodes for the other IDs. Or if you want to do it in the main graph after all is spawned, you could add an "Add Tags" node just before plugin the data into the Out pin of the output node, the tag being the ID. Then in the main graph, you can use "Filter data by Tag" -> Tree for only getting the point data associated with the trees.

@@adrienlogut3482 I did as you said in the second version. It turned out brilliantly. I did: Trees -> Boulders -> Grass. Thanks to this additional change, I also added Mushrooms around the trees. After adding "difference" and connecting the "outside filter" there, mushrooms don't grow on the rocks. Perfect. Huge thanks!

No you can't you have to prune it before. Once they are spawned they can't be removed. So you have to assign the meshes before hand, partition your points on the mesh attribute, pass it into a loop subgraph to extract the bounds. This video might help you ruclips.net/video/Q_NoeoPP3zE/видео.htmlsi=pd8jFPhvXQl3LdIX

@@adrienlogut3482 That was perfect! I've implemented this and it's doing exactly what I needed. Thank you so much for the help!

Check the follow up video ;)

@@adrienlogut3482 ok ty!

We don't interact with the landscape system, so you won't be able to remove intersection with PCG. You'll have to do all in PCG. But grass (or any highly tight and dense mesh placement like foliage) is not fully ready with PCG as it generates a lot of points and can quickly reach Out of Memory or tank your framerate.

@@adrienlogut3482 oooh ok so pcg is not perfect yet lol, but if its a grass clump (multiple blades in one mesh, nanite), its ok no?

The main issue comes to the fact that each grass position will be a point, on the CPU that would then be added into an instanced static mesh component. But the first phase of creating the point might overload your RAM (depending on how you do the generation, you will need to partition the component to be sure you don't get OOM and benefit naturally of the streaming system). But try it, that's the best way to verify :D

Basically is there a way of achieving this with Spawn Actor node instead of Static Mesh Spawner?

Spawn actor can also use an attribute for spawning, it's Spawn Attribute setting on the node. The rest of the logic is the same, you assign a path to an actor to spawn to each point.

@@adrienlogut3482 Thank you so, much I finally did get it working with Packed Level Actors. I did notice one issue is that when I use the Spawn Actor node in a blueprint with splines, and I want to add a point on the spline with normal ATL-Drag method in editor it crashes unreal. This doesn't happen with Spawn Static Mesh node. If I clear the pcg I can then add the spline points and regenerate without crashing, so is their a small setting I am perhaps missing? Using UE 5.4.4.

You're not the only one that reported that, I have this on my stack will try to fix it for 5.5

@@adrienlogut3482 Oh great, thank you so much again :)

What do you mean, "after a specific chunk"?

@@adrienlogut3482 It just looks like only a small square is being generated when the pcg volume is much larger than what is actually being generated

@@NorwinLabs So if you increase the size of your volume (while not changing your mesh) it doesn't update correctly? If you are changing your mesh, you will need to force regen (Ctrl + Click generate) because we can't catch changes to meshes sampled with the World Ray Hit.

You probably want to do the difference after the landscape projection but before spawning.

Do you have a landscape? If not, and you are using the World Ray Hit query, there is a limitation that the bounds of the actor needs to overlap with the meshes you wanna project on. So you have to add a box collision on the BP actor that would encapsulate the spline and the mesh you want to project on.

You have to select the component you want to inspect in the bottom left!

@@adrienlogut3482 Found that already.

@@WillemGrooters 👍

Indeed input pins are deprecated now, you can have access to the landscape with Get Landscape data node. Have a look to later videos, PCG is in active development so a lot have changed between 5.2 and 5.4

Hey! It's pretty easy, it means you don't have an attribute named "Mesh" in the incoming point data of you static mesh spawner. In the tutorial, meshes are assigned to point with the match and set attribute, and you can inspect the result of the match and set to see the name of the attribute :) just use that one in the static mesh spawner!

It's pretty easy actually! If you uncheck Constant Threshold you have a new pin Filter that appears. That's for another data that will be used as the threshold. So if you plug an attribute set (like with a Graph Parameter or a Create Attribute node) into the filter pin, you can set the threshold attribute to @Last or the exact name of your attribute in the attribute set for it to be used as a filter

@@adrienlogut3482 Perfect - "@Last" was the part I was missing - thx a lot, worked like a charm!

Found: I use default floor instead of landscape

Hello! The default behavior for the difference node is to do an union, so implicitly we have a union done. You can add a union node before if you want to be explicit. Note also that those videos are from me when I was less knowledgeable about the system, so there might be some places I did something not useful or optional!

I didn't create it, it already existed :)

Indeed things have changed!

There are some on the Unreal site. Otherwise it's a beta plugin, it comes with less documentation that's the contract.

Change the mesh in the mesh and ID struct by an actor reference, and change the static mesh spawner by a Spawn actor, with no merging option, and in actor attribute reference the name of your attribute containing the actor reference

@@adrienlogut3482 any idea how i could spawn it as a mesh and have it change to the bp when i interact with it? cheers love the channel

That's not PCG related then, you'll have to add another system that replace the instanced mesh by actors when the player is close.

@@adrienlogut3482 cheers! Your channel is brilliant

Yeah it's the first videos, learning it the hard way. You could always try to use a plugin to zoom on the video. Though watching it in 1440p, it's pretty sharp to my eyes.

Answered you on Discord too but for the other I'll post it there: If you add a priority value to mesh and Id, you'll just need to add that priority value as a weight attribute on the match and set attributes (like in the first video)

You can check other videos, such as episode 2, for bounds and exclusions

@@adrienlogut3482 cheers mate

@@adrienlogut3482 hey sorry for all the questions how do i filter slope for pcg?

Solved it... Just need to do another Loop...😅 and the Loop logic of PCG is very hard to understand... Lack of a clear cut direction to something like index and loop content as traditional programing language...

That's unfortunately a big limitation of a graph approach for programming. The best way to do what you want is to partition the data, so that all points in a given data has the same mesh. Then loop on those data. You can use Get Attribute from point index, index 0 because you know all points have the same mesh.

Yes of course, you can use another spline with the same sampling method and add that to the difference. Or another primitive and get it with Get Actor Data

​@@adrienlogut3482 Thank you for the advice! I somehow used a volume sampler to filter out that area!

That would work but it is very inefficient ;)

@@adrienlogut3482 Thanks for your great tutorials! How would you go about doing this? I am trying to use a difference node on two surfaces from spline before I send the surface into the recipe spawning loop, but the conversion returns a grayed out line. Debuging the difference looks correct, I have my original surface with a hole where the other surface is.

PCG doesn't support reading maps in the graph. Though if you want it to be in order from the array of meshes, you can use Copy Attributes. It will copy mesh 1 to point 1, mesh 2 to point 2 etc... Looping on the meshes.

We deprecated the input pins, so you'll have to use Get Landscape Data and Get Actor Data for the equivalent :) Have a look to more recent tutorials!

@@adrienlogut3482 great! ty for your quick answer :) I'll definitely follow your serie for PCG

i get the correct projection replaced "World Ray hit Query" with "Get Landscape Data“.

Living on the edge, no time to waste! Most of what is described here can be found in later videos, with the up to date way of doing it. You can check the Ep 1 and 2 about new features ;)