Відео

I don't understand the question. If you want to make it not-infinite, change the Material / WorldBackground to None. Look at Tips in the docs to make it smaller.

Hterrin work without genrate heavy mesh in project?

@@vRV379 I'm sorry, I still don't understand. HTerrain is a different plugin written in gdscript. Our mesh is lighter but our shader is probably heavier.

@@TokisanGames i am trying to say can i use your terring in directly on my game?(without genrating any heby mesh(Terrin 》Generate mesh(heavy) )

@@TokisanGames i have one more dout when i trying to add Texture in Godot 4 it was shoing Wariing The working is:- core/io/image.cpp:2496 - Loaded resource as image file, this will not work on export: 'res://matirials/terrin/sand/DefaultMaterial_BaseColor.png'. Instead, import the image file as an Image resource and load it normally as a resource Plase slove it or make Full tutorial For make terring and How to use all options.

In Material/Debug Views, enable Texture Rough. It should be mostly white. The default roughness texture is middle grey, which is too glossy for ground cover. Best practice with textures is to experiment, learn, and think about the textures so you can develop experience and understanding. Dirt or ground cover should not be shiny unless it's wet. Adjust your textures however you like before packing them.

​@@TokisanGames Thanks for the quick answer! I tried replicating the changes you made in gimp but without success. Now that I know for sure that you adjusted the textures, I am way more confident in playing around. I didn't expect at first that a material ready for download had to be adjusted to not be that shiny. Congrats on the new release btw! The detiling works great compared to the UV rotations, and the mesh instancing looks promising, especially with the future plans mentioned in the docs!

You'll have to look through the code to understand how, or chat with Zylann. I haven't worked with him on voxels for a number of years. I'm working on Terrain3D and Out of the Ashes.

The original several implementations were garbage. In 0.9.2 it finally detiles properly and has been renamed.

Enable debug collision. Our foliage instancer will be out in a few weeks.

What?

Materials blend using the height texture if height blending is enabled (default) and you've put height textures into the files, and you're blending with the spray brush using a moderate value. If you're referring to blend based on Y-axis value, they don't. They blend based upon slope using the autoslope setting, which also has a height reduction to reduce by Y axis.

No, there's already a road plugin for Godot. Won't take much work for it to snap to the ground if it's not already native. We already have a slope tool for sculpting flat, angled ground and paths.

@@TokisanGames Gotcha thanks! I'll have to look into the snap to ground feature for making roads/paths as it would make it a lot easier.

Thanks. There's also a built-in tool in the Terrain3D Tools menu now.

Oh, I didn't know that. Thanks for the info.

Core devs often break the engine during development. 4.3 is not supported until it is stable. Development branches are only for advanced devs capable of self support. This is likely due to clayjohn inverting the depth texture.

The whole Godot editor is a Godot game. Our editor.gd is a script running 'in game" that you can look at. All of our classes are documented in the online docs. Built in documentation is not possible with GDExtension at the moment.

A foliage instancer is currently in development. The docs/project status offer 3rd party tools in the meantime.

Sure, or use the Godot Road Generator, but neither have anything to do with Terrain3D. Enable our editor collision so whatever other utility can snap to the ground.

​@@TokisanGames the "Snap funktion" only works with the CSG Polygon and not with the path 3D :(

@@TokisanGames wish I had the same raycast funktion like Beau Seymour in his Godots Roads Video by 5min

@@JohnStonexDj If you want to use Path3D you of course need additional code. I assumed you knew it's just a barebones math class. It doesn't generate meshes. You'd need to generate your own mesh, and provide snapping functionality. Eg Waterways does this, uses Curve3D, generates meshes, snaps to ground colliders. If you want a no code option, use CSG or the plugin I mentioned. Regardless these are independent of Terrain3D. They'll just query the terrain via code, the same as any mesh, though we provide more options in our Integrating with Terrain3D documentation.

@@TokisanGames Thanks for answer so quickly.Yes I know that path 3d dont generate a mashes. I built a CSG around my path 3d so I have my street network template for painting it on the terrain. I`m a coding newbie but I saw Terrain 3D brings extra library for raycast stuff. Will read the documentation about it one day. The KI told me when I want to use the Terrain 3D library I have to write "Import Terrain3D" but Godot marks this red because Terrain3D and my path3d are not in the same folder ... I dont get it <- I`m a big newbie

Frankly it's such a common gamedev practice across all engines that it behooves you to learn it. Every 3D model or asset pack you've bought or downloaded has come with channel packed textures. Photoshop doesn't handle alpha channels well, but there's a built-in tool for packing in the Terrain3D Tools menu. Texture packs come as individual files so you the gamedev can pack them how you want for the material you are creating. Our selection of maps and packing is different than might be used in another environment. It's not the texture creator's job to guess how you want your textures packed or pack them 5 different ways to cover every possibility. It's a reasonable expectation that the gamedev will spend 2 minutes and pack them as they need.

@@TokisanGames I'll just have to do it a few times to get used to it. I'm just glad there are tutorials like yours that put it in plain English for people like me. Thanks so much.

@@PastaMaster115 Use the built in tool in the menu, now that its available.

It tells you the exact problem. All textures must be the exact same format per the docs. Your albedo texture format of the third set (ID 2) doesn't match the first (ID 0). You can lookup formats 19 and 22 in the Godot Image docs. We can help more effectively on discord.

@@TokisanGames I have the same problem as him but i used exactly the same settings that you have shown here, tried with both png and dds it gives same result. When i try to use it in new project it works without problem.

@@vranigavrani Then you have the same cause for the problem. You've added a new texture that doesn't match the existing format. If you are adding textures to the demo, they are currently using BPTC, not DXT5. You can see that in the inspector, and the Import settings. Check HQ on the import panel. Read the docs and come to discord for help.

@@TokisanGames I misunderstood at the first i tho my texture is the problem but after some time i figured it must be Godot import settings. Thanks man, after some tweaking in import settings i got it to match existing textures and it worked. Great tool, going to try build something out of it and see how it goes.

Probably both, but I'm not targeting low poly worlds so am not an authority on the subject. I'd say try them both out and let actual experience guide you.

Out of the Ashes is an adventure game we are developing. Look at the channel for a development trailer from a few years ago.

Enable the plugin in project settings. Listed in the Installation instructions.

@@TokisanGames Yeah, I started a new project, and it is showing up now, but its not letting me paint any texture onto the white terrain.

@@SovereignVis Come in to the discord server for help. And look in your console for error messages.

ok

It wasn't Godot's choice, it was mine. In UE, you spend time wiring up texture channels to create your material. Here you spend that time directly packing the files. Every game engine uses channel packed textures, and every gamedev needs to learn how to do it, for far more than terrain. We've had a built in channel packer for months so you don't even need to use Gimp. If you can't be bothered to spend the 2 minutes and are going to be rude, use one of the other inferior terrain systems, write your own, or use UE5; it's a great engine.

​@@TokisanGames Im happily using heigh terrain with zero issues and drop in textures. lol sorry if i came off grumpy.

See my other answer.

The documentation has a section for mobile/web. Opengles support in gd4 is lacking features. We can't support it until Godot builds out opengles.

@TokisanGames oh okay, thank you for your response! Also, sorry for asking on two videos 😂 I must have gotten confused

First understand what you need by reading the texture doc and this video. Albedo+Height, Normal+Rough. Then this tool should be self explanatory. Add albedo and height textures to be combined, and normal and rough. Come to discord for help.

Settable in Godot, or in your GPU driver, nothing to do with Terrain3D. Read comments on godot proposal 8607. You're not seeing actual FPS. Also look at a monitor like taskmanager to see how much GPU is actually utilized.

I wouldn't for terrain. It's a waste of vram. But you can look at tips in the documentation.

That's what is currently implemented. You can access more right now with vertex spacing. We're using texture arrays, which support up to 2048 layers on modern cards. With a 1k region size, 45km^2 could be supported without much work, and 90km with 2k region sizes. However, to be practical, Godot needs to finish supporting 64-bit ints, and working above 16km you really need a double precision build. Follow issues #77 and 159.

Did you enable the plugin? Read the written installation instructions.

@@TokisanGames ahhhh ok I'll try again tomorrow

This is very important to me

You get exr or r16 heightmaps from other third party tools and import them here. Or you can draw your own terrain here and export them. Read the import/export document.

Can you give me the URL of a third-party tool? Thank you very much.@@TokisanGames

The documentation explains what is needed in detail. BPTC is needed only for the demo because the existing two textures are BPTC. When you create your own project you can put in any textures. The requirement is that all subsequent textures match size and format of the first.

@@TokisanGamesokay cool

It was merged in January.

It loads all terrain data at start. There's no streaming in Godot or our plugin. There's a bug in Godot that prevents saving more than around 8k^2. But it could be imported at runtime up to 16k^2.

@@TokisanGames so if i want to uses that to make a massif terrain for airplane it's kinda a no? Would be around 50km by 50km

@@mirtir472 Current heightmap maximum size is 16km^2. You can scale the distance between vertices say up to 10x. But to run a 50km world you'll most likely need to build the engine and plugin with double precision.

@@TokisanGames make sens loading a 250k height map in the gpu would probably eat a large amount of vram. Is it possible to use multiple terrain node with our system? I will try to make it work! Thanks for your answer ! I will also keep you updated if i found good idea !

@@mirtir472 not simultaneously, at the moment. We use multiple terrains in different scenes.

Look at your console. It probably tells you that you're using inconsistent formats or sizes. Then read the texture docs that tell you the specs that must be identical.

Set world background to none. Look at Tips in docs.

Baking the autoshader is worth considering. The user can already alter the autoshaded parts with settings or manual painting.