Pre-built binaries: tokisan.com/godot-binaries/ Join my discord for updates on my current game, Out of the Ashes: tokisan.com/discord See pics and details here: tokisan.com/out-of-the-ashes/
You sir are a legend. Ive hopped around several game engines for one that I am needing and its because of your tutorial and demos that led me to try Godot. If yo uhave a discord server id love to be apart of it
Awesome video! Just have to questions, 1. The only way to paint grass and water is by shaders? 2. What's the proper way to place stuff in the map if you only see it runtime? Thanks in advance!
In the video I show water. That is just a plane that cuts through the terrain and has a basic blue reflective shader on it. Not voxels at all. Took me 15 minutes to make. Grass, you could follow Bastiaan's grass tutorial, which should work fine. ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-uMB3-g8v1B0.html Probably many other methods for grass or water available. You can place objects in the editor at run time just as I moved the camera around towards the end of the video. Add an object, run the scene, move the camera where you can see, then move the object where you want.
Very neat! However there doesn't seem to be an option for blocky terrain anymore. Using the non-LOD VoxelTerrain node, it is smooth by default and there's nothing in the properties for the blocky style.
You'll have to talk with Zylann. It's been years since I built it. Looking at the code, the blocky mesher has not been removed and the documentation still shows it's an option.
Cool stuff! Is it possible to make the terrain (height map included) tileable? That way, instead of running into draw distance issues it's just repeating the landscape?
The landscape already repeats the height map. As you move toward the horizon, more sections are built. You're always in the center. With VoxelLodTerrain, you can extend the view distance very far which means the heightmap is tiled within your view many times.
@@TokisanGames Is there a way to view the terrain within Godot viewport (without playing the scene)? Would like to position polygon objects/buildings visually. Or how would you go about doing that? Really fun to play with so far, the pre-built binaries are super helpful. Is there an advantage to compiling it ourselves?
@@formaffinity The in editor option is disabled as it's not stable yet. You can run your game, reduce window sizes, switch back to the editor window and place your objects by editing the position and rotation in the editor. Compiling yourself allows you to learn more about the engine, get more up to date versions, or add other modules to it.
@@TokisanGames Thanks for the quick reply on such an old video. I haven't managed to find how to access the save function yet. So far my workaround has been to save all changes made to the map in an Array and load chunks of changes when the player reaches places he's already been
Is there a way to implement custom chunk loading? I have searched the documentation but cant find it, I also need to create custom procedural generation by applying multiple noises to the terrain (2D noise, then 3D noise removing voxels), if I am over complicating this please tell me, and thank you for your time
Search for benchmarks online. For things like voxel generation, C# has been shown to be up to 12x faster, C++ up to 93x faster. Godot can use all three. A better metric is how easily you can fix or work around the bugs in the engine. Having been working on a decent sized game in Godot, in the future, I would only make something big in UE. Not Unity. Not Godot. Not any of the new upcoming, untested engines. I would only use an engine that the developers use to produce games. UE alone qualifies.
@@TokisanGames Thanks for your response, but I have to say I don't agree UE is the only answer. Look at Unity, 7 days to die is made in Unity, so is The Forest, Empyrion, and many other open world games were made in Unity, so I think if anything, Unity is the most battle-tested engine. The beauty of Godot I think tho is the ability you have that if you are really invested in a project and there is a bug with the engine, you can take the time to dig deeper and find a way to fix it, with Unity, you will always be at the mercy of the unity developers to fix the engine bugs, it's a black box.
Thanks for this tutorial, I tried downloading the Linux x64 binaries (on debian) and I got: ./Godot_v3.2.2rc+cd8d43_x11.64: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.26' not found (required by ./Godot_v3.2.2rc+cd8d43_x11.64) The 3.2 Alpha version does work though
Leave far away ones blocky you mean? No. The mesher is either entirely smooth or blocky. Smooth uses levels of detail for increased performance for distant landscape, which is the right way to do it.
I haven't used it in a while, so I don't know if Zylann has added that feature. I'm not aware of it. Review the current docs in his repo or ask there to see.
VoxelStreamImage is not an available stream option in either vanilla or LoD; what's the workaround? I really want to slap a heightmap onto this. Edit: Smooth mesh also seems to be missing. I initially suspected I'd kicked the wrong binary, but, that's not the case. Running the March 2020 x64 binary for Windows - 3.2.2rc+cd8d43 Edit: Temporary fix = revert to binary from November 2019 Edit: Using the old binary, how would I restrict/scale the generation according to the finite HM image I've imported? It's relatively large, so it seems like Godot's voxel generation is compressing it into really steep heights. The newer binary includes an ISO option, as well as the option of setting the height range; I'd like to set similar parameters using the old (working) binary.
In the newer binaries the name of the class is now VoxelGeneratorHeightmap. All of my demos from my github repository work with the new binaries, so use and learn from them. See my website for which git revision works with which binary version. For detailed questions about the module, read the docs and open an issue on unanswered questions in Zylann's Godot voxel github repository.
@@TokisanGames I think I've tried VoxelGeneratorHeightmap and VoxelGeneratorImage, with no voxel output. I vaguely remember trying out the project examples (for the new binary, not old), which DID generate the map as shown in your video. I'll give it a go later tonight when everything's out of the way. Thanks for the feedback!
For the Blocky mesh, is there any way to add custom mesh voxels like for example an fence, or tree trunk. I would like to be able to make trees like RLMinecraft or just basic grass. How would I do so if possible?
The voxel terrain is a static body. The nodes only support infinite, paged, terrain generation. On the wishlist is a node that can create an independent, movable, non-terrain voxel object. But that hasn't been implemented yet.
The voxel meshing classes are available to the scripting API so in theory, with a bit of scripting, you can voxelize an arbitrary chunk as a mesh if you like, and turn that into a regular RigidBody with a MeshInstance.
Alright, kinda tried to use your demo but it's missing something.. Also How would you go about generating different types of voxel depending on the height or randomly chose those?
Missing what? Did you use my binaries or build the engine yourself. If the latter the engine is going through major changes right now and not stable. As for different types of voxels peruse the Github Issues on Zylann's repo for discussions on that topic.
@@TokisanGames I've downloaded your demo and it somehow doest let me open your scenes, it spit out a error about it being the wrong data-ending :confused: anyways i saw you're going to make new prebuilt binaries any info on that?
@@officialfoxelgames DM me on twitter or file an issue on my github repository so we can work through it. Also see my notes here: tokisan.com/godot-binaries
Quick question. New to coding but would I be able to change the texture of the voxels and assign different properties to voxel blocks? (For example, for making biomes or different types of stone and grass, lava voxels and have different properties (lava burns you)
You can add different materials for different blocky voxels. For smooth voxels, you only get one material at the moment. However with shaders you can create multiple materials based on factors like angle or height.
@@TokisanGames Thank you. I am like the smooth voxels but not being able to make different materials. I know it's possible as Deep Rock Galactic had something like that despite it being a different engine. Thank you so much again for developing this.
@@funnytimeoofman8855 Blocky voxels are used in the VoxelTerrain node. It looks different, provides multiple materials, has a few other technical differences. VoxelLodTerrain is much faster and provides a far greater view distance, but is smooth only.
@@funnytimeoofman8855 Deep Rock Galactic probably used shaders, which you can do here. In the first few seconds, and in my other videos you can see footage of a landscape with grass on top and rock on the sides.
The discussion has been around moving VT to block type exclusively, VLT smooth exclusively and each doing their own thing well. No discussion about LOD for blocky as of yet.
@@TokisanGames pardon me for asking another question, but in the features not supported list it said importing voxel data is not supported, will this eventually be added? Or is there some way to import a .vox file? A file type that could be parsed and imported to retain an objects voxel data? This would be exclusive to blocky of course.
Although that's not nearly enough information to help you with, make sure you're using the commit version of my demo that matches the binaries on my site.
@@TokisanGames actually i think i figured it out. It didn't accure to me i had to download a modified goddot. So i download the 2020 3.2.2 then the 64 version. afterwards i imported the comit on the modified godot. Thanks for your help
Using blender to create terrains gives you a mesh. You can't modify it in a a game engine without a lot of programming. A voxel system allows the user to modify the mesh in game.
well this just sucks. I am using Godot Engine v3.2.2.rc.custom_build.cd8d43714 and apparently there has been some rather dynamic changes since this video was created as I do not have a "voxelstreamimage" but I do have a "voxelstreamfile" and a "voxelgeneratorheightmap" so my project is dead in the water befor I can even get it started
You can build your own binaries. The process is not complicated and well documented. Hardly enough to kill your project. There are far greater challenges coming in your journey than building the engine. My binaries and demo are there to get one started trying it out, not necessarily for production ready games.
I'm not sure I understand what you mean. You don't like that people make free addons for you to use? Instead, you'd rather we spend our time teaching you how to make your own addons or change them? The Godot docs already show how to make addons. Search "making plugins" in the documentation. As for modifying any existing open source plugin (like our newest Terrain3D), any developer can do that. You need to know how to program, which is out of scope for my tutorials. There are plenty of classes and videos online that can teach you how to program.
