This looks really useful! The gap that this bridges is currently one of the weakest points in my workflow in terms of 1. keeping things non-destructive and 2. avoiding repeated work when updating assets from Blender. Thank you for making this!
I've heard the term "tangent space" a few times in the past, but not much. I decided to do some research and now understand that it has to do with vertices and is relevant for UVs. from chatgpt: Tangent space is defined at each point on a surface, while local space applies to the entire object. Tangent space is aligned to the surface’s texture coordinates and normal, while local space is aligned to the object's origin and axes. Tangent space is specifically useful for detailed surface operations (like normal mapping), while local space is used for positioning and transforming the object as a whole. Tangent space is a specialized local space used for surface detail manipulation. If the object has a UV-mapped texture with normal mapping (or other tangent space-based effects), the tangent space is defined relative to the object's surface. When you rotate the object, the tangent space rotates with it. This means that the normals and other surface details will continue to be correctly aligned with the texture and the surface. With these statements in mind, I'm having a hard time understanding what you meant by "rotating out of tangent space". Any thoughts on what I'm not connecting here?
The way I like to think about tangent space (in a less technical way) is that its a shared coordinate system that can be constructed both from the the 2d UV coordinates and from the 3d world coordinates. This allows you to translate a point or a direction from 3d space to UV space by passing through the shared tangent space. However, because it's 2d in nature if you rotate a point around an axis that isn't perpendicular to a face. In 3d the left verts might move closer and the right verts father away from the center of that face, or in front/behind each other... but from a flat front on viewpoint the left and right verts simply move closer together, losing that depth info in the change from 3d to 2d.
just as FYI, you could make some money providing complete training on all of them, and in different contexts (different scenes and stuff) for re-inforcement learning. Likely make more money off the training than the asset itself. It's real nice, btw. One of the best plugins out there in a lot of ways. Great idea.
Thanks! Yes, I've put a bit of thought into how I might do that. Unfortunately, making training materials can be quite time consuming, to really do it well at least, which I'd want to do.
@@looseEdges - yeah, I hear ya. I can imagine they would take a while. One other thought is a product that is a set of group nodes for geonodes to simplify some operations.
These nodes are pretty awesome. It is complicated though, but that's just 3d. At first, I thought these were grouped geometry nodes, for using within your own geonodes pipeline. Are they always used as modifiers, or are these also used inline in geonodes setups?
You can do both, I often use them in more elaborate node groups myself. I did design most of them to be used as modifiers first, because I think that is more approachable, but there is a lot you can do with them if you are comfortable combining them into your own bigger setups. I do all the time, in fact in the library you'll find many nested groups, for example, Resize nodes included inside of many of the Build modifiers.
when the planes are porjected onto the face, why does it still show the original planes? Do you make those not render, or do you get rid of them afterwards?
I think that is actually caused by the previous modifier in the stack, Face Project, that modifier can be used in two ways. One would be to project the active mesh onto a target object and then instance on those, replacing them. The other, (which your question is about) is to project a copy of the target object onto the active mesh, which leaves the original planes visible. I personally like keeping the faces visible as a kind of control to edit, and if I want to render it I'd just turn of the renderability of that object. I also am often exporting the finished mesh rather than rendering it in which case I don't include those faces as part of the export.
hello i have a question. so is it possible to change the materials for the land.? i have a potential project where i wanna use anime shaders for materials.
Yes, it is possible. I talk about how to customize the materials in this video: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-A8B5AR-R9xk.htmlsi=faGCQINaVEqrDqAz
Wow I looked at that pack hard. I rarely buy addons, I prefer to build my own but I seriously considered buying it last week. I've only bought a handful of addons ever. Not because I'm a cheapskate, I want to know how it works. I want to be able to improve or update it. I just like making my own stuff. The only addons I buy are ones that save me time and hassle when modeling. I always make my own materials, textures, effects etc. You have convinced me though. This is definitely worth the money and more actually. I'm going to buy this. I appreciate your work bro
Absolutely worth it! 100% recommend. It's ridiculous how much stuff is packed into this and it just keeps getting better. I have no affiliation, just a happy node nerd.
Hi there, how hard would it be to replace the assets with custom models and textures and how difficult do you think is it to export the terrain layers as vertex colors?
Hi! All that should be pretty straightforward. The scattering can be done with any collection of assets, so all you should need to do is import them into your .blend file and group them into collections. Making your own material slightly more involved, but not too difficult, I made a video specifically about materials here: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-A8B5AR-R9xk.html By terrain layers, are you referring to the attribute masks such as erosion or elevation? Those are all generic float attributes, so it should be as simple as packing them into RGB and storing a named color attribute. As a potential alternative, TerraNode also comes with an addon that can export all those attributes to textures.
What would be the ideal EEVEE settings in 4.2? It doesn't look anything like your video ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-bkrU_GwNxgY.html.
Hi, it has changed a bit. I released an update a couple of weeks ago that was aimed at fixing problems caused by 4.2 and EEVEE Next, so make sure you have the latest version (v5). In the video about the Update, I discuss the new EEVEE settings a bit: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-i61LDJdh0ug.htmlsi=NlW0doVi-6-H7L2n&t=435. If you have questions about more settings after that, let me know. I'd be happy to share a .blend or a screenshot with all the EEVEE settings I've been using and share that with you.
This is really amazing. I used DAZ in Unreal but this Terra Node is somewhat similar or more convenient to make terrain at your wish. Couple it with G-scatter or Ngon addon and it will give you proper exterior in no time.
@@looseEdges on default in blender if you click left batton mouse on mesh, it selects mesh, but ufter this program became another function. how I can return default function sellecting object(mesh) with click left cnob mouse?
@@vaxs3993 That is strange, TerraNode doesn't change any blender settings. Selection should always be either 'left click' or 'right click' I would check your user preferences under the 'Keymap' tab. It should be the very first setting.
This is awesome! got as soon as I discovered it and works flawlessly! The only issue I am having is that for some reason I can't make it interact properly with lights and hdri (cycles) could be that I am doing something terribly wrong
Glad to hear it! That is odd, I just did a quick test and a terrain with cycles seems to be working fine for me. Was there a specific material that was causing the issue? Also feel free to join my discord server, ( discord.gg/EuUHutzrJr ), that way you could share pictures etc.
I love your geometry nodes assets pack! I really hope you can solve the roof problem you looked at in this video. That would be a super useful tool for arch viz modeling
the problem i see is the addons offer nothing that a person who's competent in blender can't do naturally, thus profiting on peoples ignorance. you could make a new tutorial on how to do these in 4.2 if its any different than the currently available tutorials, and focus on finishing your projects rather than addons. imo it would be more efficient to learn the modifiers (like screw and follow path) and use materials and alphas than to create the topology for a roof, rope, pipes, leaves, etc. and have millions of polys in ur scene.
I agree that everything my tools can do can also be done in blender without them, but I disagree that they are not valuable simply because it could be done another way. I think that is like arguing that you shouldn't get a power drill because you already have a screwdriver. I am confident that my tools simplify certain workflows, and that saves time.
@@looseEdgesI agree with you here. Sure any technical artist could figure out their own node tree to make these things work but even in large studios there are built in tools to speed up production. Personally I do like to know how things work under the hood as this makes me a better artist but not every;one did mathematics right though to college so it can be quite difficult to decipher without some help. With your expertise you could put some tutorials together explaining how you built your tools and put it up on Patreon or Udemy to monetise your efforts. By the way I have your terrain toolset as with as your nodes set, as soon as I get some time I’m looking forward to having a good play. :)
Hey LooseEdges! Nice video, I just found out about you :) I have some ideas about how to solve the issue at 10:40, let me know if you would like to discuss them
@@looseEdges AHH my message was removed... I was saying if you want to speak in that blue social network for work (LNKDN) if you are there, you can find my name there as "aitorsr"
@@looseEdges so basically you can simplify the problem by inputting simpler geometry, so instead of having both of the ceiling combined as a Boolean, have them both "complete" without any hole/trimmed. So for the curved ceiling, the current intersection edges would end coplanar with a vertical plane. For the other ceiling, you would get to fill the intersections. What this allows you is having a ribbon-like surface, where you can now scatter tiles, and then remove the ones that end up below the roof to solve the intersections. I hope that makes sense.
@@looseEdges another option is having the geometry as you have, but procedurally get to the ribbons situation and then solve as I mentioned in the previous message. This would be more difficult but you would have an input closer to the final result.
there's this dude Bill Mollison who came up with Permaculture . ...... he liked to say that if u collect enough of _anything_ in one place, it becomes a resource. ..... apparently applies to bad ideas as well ..... =) great video, brother, thank you! ∞ <3
I cannot offhand add any ideas, but I do like the pipe stack tool - that is very neat and I can definitely see many uses for that. That shingles on any roof surface would be brilliant if you can crack it. I frequently deal with tegula and imbrex, which many texture sites just describe as 'clay roof tiles'. Thing is that what I need is more ordered, and the roof at the gable ends has to be a certain form. Then there is the horror of trying to get these onto conical and hemispherical meshes, for apses, or the roofs of apsidal ends. Very common in earlier architecture, but a devil to model. Great video though - I enjoyed watching that. I'd still call it far more successful than not with plenty of exciting ideas.
Thanks! I'll let you know if I solve the shingle problem. I certainly agree on it being successful--it's all part of the process--and I'm using 'bad' in a very loose sense most of the ideas could still be useful, I've just run into dead ends on them for now.
No guarantee that these would work but pattern one could be interesting with clothing, and the image to curve might be interesting with bump maps. For pipe topology, wouldn't the perfect seam be function of the angle? Those are my ideas.
Yes, I think the pattern idea is very cool as a fast way to add detail to anything that won't be too close to the camera. There may be a way to generate the pipe joint topology, and I'm sure the angle would play a role in that, but I haven't been able to wrap my head around it yet.
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.
@@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 :)
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.
If I understood correctly with his addon: one can take benefit of Blender's easy and intuitive interface for designing complex objects using instances and then export them to Unity as premade prefabs. Blender provides a lot of modifiers for automating tasks such as array modifiers, or geo nodes. In unity, assembling complex object can be a double work or tedius thing, (in this context). If this is so, this addon is really solving a problem.
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.
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.
Nice vid! Had the idea of making this kind of node floating around in my head for a few days now, so the timing of this video was just really fortunate. ^^ 12:52 Bit of a tip, but you can actually set Position as a default input. It's under the "Default Input" option under Min and Max. It's a 4.1 addition afaik, so that avoids the whole magic number shenanigans. Vector sockets should have Position & Normal, and Integer sockets should have Index and Index/ID available as default inputs.
