Видео

You should be able to follow the same steps, the tools will just be in slightly different places: Create a selection/mask from the blue channel. Delete the bad pixels. Make a copy of the layer. Blur the bottom layer. Use curves on the alpha channel to make semi-transparent pixels opaque. Repeat until the holes are filled.

You can set the resolution as high as your pc can handle, and all of the modifiers tile. That being said... I'd say that getting results that look like gaea might be difficult, it will always have a slightly different feel to it, and I've definitely done most of the testing with smaller scales in mind, i.e. a few hundred meters across rather than several miles.

@@looseEdges what are your thoughts on PC specs that could handle it?

@@graphguy I have a pretty old pc, 4 core i5, 16Gb ram, and GTX1070. That can generate a 1 million vert terrain with erosion (which is the slowest part) in ~30 seconds. Once it's generate the viewport performance is fine. Hopefully that gives you a point of reference.

Thanks! Yeah, I thought about it, but was rushing to get it published yesterday evening... this way you can play whichever tunes you like best in the background :)

No!

Wanna know this as well

Technically, yes it could all be converted to a mesh and imported. However for performance reasons...depending on the scope of what you're doing... it my be better to export the terrain as height and attribute maps, the export addon that comes with TerraNode does this. I'm afraid I don't have much experience with the Godot engine, I have been told that terrain can be imported from heightmaps using an addon but isn't supported in Godot by default. A custom terrain shader might also be needed, unless the scope is small enough that the blender shaders can just baked into a texture. I've been asked about Godot and TerraNode a lot, so I think I'll look into it again and see if I can't write something to make exporting to Godot an easy process.

@@looseEdges I don't mind doing most of the stuff myself to export to godot as long I can bake and save objects and so on. I see this more as a level editor that I can later export and do the necessary hard work myself. Even as a isometric render would be useful. Imo I think you should work on the add-on and not worry to much about the export to godot part.

@@webinatic216 For sure, and I might decide it's not worth the time it would take to learn, but it doesn't hurt to look into it either. I also use Blender kinda like a level editor, and I've make several tools that transfer data from Blender to Unity, so it's sort of half done already if I can make a Godot importer for those same files.

You're welcome!

Correct, the blender addon saves a .basset file which is a list of mesh names and transforms, and the unity importer for that file type loads gameobjects for each mesh, places them at the instance transforms, and then saves it as a prefab which should match what was in blender.

Krita: krita.org/

I don't have a modifier for that in the strands collection. It's a good idea, I'll try to add something for custom meshes in the next update. If you have my GeoNode Assets, Deform Match Curve is pretty close to what you're describing, but it doesn't have start/end caps and can't make use of the strand tags.

@@looseEdges Thanks ! :)

Thanks! Glad you're enjoying.

Yo! That's sick. I must have missed that in the release notes.

You have some control over it actually, you can adjust the trunk/branch resolution, and it mostly depends on the resolution of leaf meshes, plus how many times you instance them. For the example trees, you can see at the bottom that the w̶h̶o̶l̶e̶ ̶s̶c̶e̶n̶e̶ ̶a̶v̶e̶r̶a̶g̶e̶s̶ ̶~̶5̶0̶0̶0̶ ̶T̶r̶i̶s̶,̶ ̶t̶h̶a̶t̶'̶s̶ ̶a̶ ̶p̶r̶e̶t̶t̶y̶ ̶g̶o̶o̶d̶ ̶a̶p̶p̶r̶o̶x̶i̶m̶a̶t̶i̶o̶n̶ ̶s̶i̶n̶c̶e̶ ̶t̶h̶e̶r̶e̶ ̶i̶s̶n̶'̶t̶ ̶m̶u̶c̶h̶ ̶e̶l̶s̶e̶ ̶i̶n̶ ̶t̶h̶e̶ ̶s̶c̶e̶n̶e̶.̶ Turns out the scene is not a good approximation, the example trees are 1500-2000 tris.

@@looseEdges Cheers! So, to be specific, each tree, on average would be around 1500-2000 tris?

@@tarekwayne9193 Yes, 1500-2000 for one tree.

If I understand correctly, you have two objects with the same topology, so vertex 0 on one is equivalent to vertex 0 on the other, and you want to move the verts in one of the objects to the position of the verts in the other object. You can do that with a Sample Index node using the Index node as the Index value. Here's an example file: danielhickox.com/uploads/morph_example.blend

@@looseEdges Thanks so much for sharing this sample file! This isn't exactly what I was trying to do, but it's very interesting to see the setup you used none the less! I am extremely close to what I was going for. I was originally trying to flip the index ordering, without moving the starting point (index 0), which I was able to figure out. What I am not sure about is if you want to set some other index (index 7 for instance) to be the starting point 0, so that you can better align the indices for a shape morph, what is the best way to offset your indices? I am also very curious about the samples you used in this video, is there any chance I can get the project file(s) somewhere to dissect your setups further? I am following along on my own but there are definitely still some gaps and I really want to understand this stuff to the core. Thanks again for sharing!!!

@@SJ98296 Sure, I think I still have the file, I'll see if I can find it. I guess I'm not quite following what you're trying to accomplish. Do you want to join my discord server so you can share an image or drawing of what you're going for? discord.com/invite/6rdD5jQtNn

@@SJ98296 Here's the index examples file: danielhickox.com/uploads/djh_index_node_examples.blend

@@looseEdges great, thank you.

To learn how to make node setups like the one in the video? I don't think it's essential to learn a specific language, I think a basic knowledge of programming concepts helps a lot with understanding what nodes are doing under the hood. But, if you have some interest in programming, (as opposed to viewing it as a necessary evil) and your main focus is Blender related, I'd recommend learning python and the blender python api, which would enable you to make scripts and addons and opens up possibilities beyond just Geonodes. Regarding courses and tutorials, I'm afraid I may not be the best source for specific recommendations. I am self-taught and have been trying to learn whatever I could get my hands on about 3d graphics, programming, game development, proceduralism, etc for a long time, in my spare time. I've learned a lot of what I apply to nodes from GDC talks, articles about code architecture and design patterns, Catlike-Coding's Unity tutorials, scene breakdowns, and honestly just setting a goal and experimenting. I haven't followed tutorials about GeoNodes much at all, I started experimenting with them when there were only a couple of nodes, and have kept up with all the changes and additions as they were made. I think I'd recommend a similar approach to anyone starting now, with the caveat that I was already familiar with the core concepts from dabbling in adjacent fields. I recommend mastering the basic nodes first, Math, Vector Math, Selections. Then use those as tools to solve simple problems, each problem you solve is another 'tool' that you can pull out and reuse in the future. As you acquire more and more tools to work with, the ways in which you can combine and apply them to problems should expand so you can make more and more interesting things. Also, beware of mistaking copying for learning, sometimes following a tutorial might enable you to 'build a house', but if it doesn't teach how to hammer a nail, or cut with a saw, it isn't helpful long term. Sorry for rambling, hope that helps a bit!

@@looseEdges awesome, thx for the detailed answer! I'll focus on hammers and saws now ;) btw bought ur geo node house assets and learning more n more now! great stuff!

You're welcome!

Hmm, I think you can do that from preferences -> themes -> 3d viewport -> theme space -> region background.

You're welcome! Although I don't think it will work with the extrude node, because the extrude node doesn't offset the UVs on new side faces and they will have a width of zero which cannot be scaled.

Are you asking about scattering something to render as a seamless texture? Yes, you just need to make the scatter slightly larger than the texture so that the edges will overlap a bit and then copy it 9 times similar to how the tiling part of this setup works.

@@looseEdges I mean like lets say you have model of a leaf and you want to scatter that seamlessly.

@@NicCrimson Hmm, I guess I'm not sure what seams you're thinking of. On its own, scattering doesn't have seams. In the case of a texture the seam is the edge of the image in 2d. You can also make a mesh that tiles, by intersection booleaning it with a cube in 3d. In either case you can make the edges match by copying 9 times into a grid.

@@looseEdges I found a video that does what I mean. ruclips.net/video/VWGtpxs18OU/видео.html

You're welcome!

Thanks! I am not planning to add tools for creating road geometry to the TerraNode library. I do have some unfinished modifiers that will be for making roads, but I think they'll be a separate library or an optional addon to the TerraNode library. I was making them in this series of videos, but that makes progress slow, so I may just finish them off camera at this point: ruclips.net/p/PLid29DRBYBBOvdazcLSbm6YSpdIMD4hPd&si=oRMepw2gXqgMWdeL

Hmm, scrolling the description works for me. I've added some more padding to bottom of the description box, hopefully that will give it room to scroll up if it was getting cut off at the bottom.

Glad to hear it! You're welcome!