Thanks a lot for the comment ! I'm glad you enjoyed :) Yea it was hard but I did it as a side project over a month or so. That gave me time to breathe. Doing it all in one go would have made me go crazy I think haha I worked a bit on procedural generation after making this vid and it was ( and still is ) making me go crazy... Loading and unloading all that stuff without lagging or having any memory leak... oof Give it a shot again one day if you feel like it, it's a very nice project imo :)

Thanks a lot

Bro this game is awesome keep working on It i love it@@MaxMakesGames

No it does not, BUT it could... 😏

Yes you're right I actually did this recently. Checkout my lastest videos I have 2 about raytracing ;)

lmaooo yes that's exactly what I did and you will see in the next part that it DID end up screwing me over and I struggled to fix it... You predicted it haha

@@MaxMakesGames Haha, totally not relatable...

Not yet, but that's definitely the first thing I'm adding once the engine base is done haha

Yeah there's back face culling which makes it so back faces are not rendered and also frustum culling which makes objects ( or in this case chunks ) that are outside of the camera's view not be rendered. Culling improves performance a lot :)

@@MaxMakesGames well, I am glad this tactic exists at least, I had a feeling something like this did lol

Hey I do not understand how some faces of your cube are not rendered with only glCullFace(GL_BACK); in order to not render some faces that are hide you have to re construct the mesh and disable some faces no ? @@MaxMakesGames

@@maxbrundev Yes you have to construct the mesh with only the necessary faces ( squares ) but without culling those faces will be rendered on both sides so under the map too, but with culling they are only rendered on one side ( the clockwise triangles I think ) so you get 1 sided squares which is the better than 2 sided.

Ohhh you are not using cube but 6 squares and you place your squares like a cube that's right? I am currently using a cube that's why I was having trouble, I cannot use different meshes with instancing and all my face are Counter clockwise already @@MaxMakesGames

Thanks ! Yes I'm hoping to make a game once the engine is good enough. Since I'm focusing quite a bit on the world and destruction right now, I'm thinking a simple game where you move around and destroy things at first ( the ground, trees, rocks, etc ) and also maybe use different powers to do so. I also always loved monster collection games like Pokemon so I thought maybe something like that with the monsters made of voxels too but I'd need to work on it for a while for that haha. Let me know if you have ideas :)

@@MaxMakesGames If the player can make their own monsters that could be pretty unique. I guess animation might be an issue though. 🤔

@@Skeffles Maybe you could collect voxels while playing and use them to "craft" monster presets with a few customization pieces so it's custom but not fully to allow animations, spells, etc to make sense... Anyway before my engine can handle that I have a long time to think about it haha

@@MaxMakesGames fantastic idea! Best of luck making the engine.

@@MaxMakesGames bro is making minecraft 2

@@vortexstudios_echo I started using a website called learnopengl it's good ! Also I did try Vulkan in my opinion it's really good but a bit harder to learn

@@MaxMakesGames allright thanks! ive seen learnopengl i just thought it looked a bit different than learnopengl

@@vortexstudios_echo I also used chat GPT to help me understand how some things worked and fix some issues I had. I 100% recommend using it :)

Thanks for the suggestion, I actually have something like that in mind. I mean, if I make an engine with a fully destroyable world, I sure am gonna make a game where you can destroy everything haha

That looks pretty fun haha Well yes it's definitely possible to make an FPS using an engine like this, but the multiplayer would be difficult to do. There's also a lot of things I'm missing to make games like a UI system. I still have a lot of work to do before my engine is capable of doing all that... In short: it's possible, but not right now :(

Thanks ! Maybe one day but not yet because it's still very messy and bad. I would have to maintain everything clean and working and have versions and everything that's a lot of work :/

You mean culling things outside the camera ? I didn't do it at all for a while and at one point I didn't render whole chunks outside the camera view. Trying to cull too much based on the camera view often results in lag as you said so I think it might be better to avoid culling voxels. Instead, you should focus on only adding the necessary faces like I spoke about in this vid. If a voxel only has air above it, you only need to draw a square, not the whole cube. That's not dependant on the camera so it's a 1 time calculation and is much more worth it. And a square is 1/6 the amount of verts of a whole cube so huge improvement. Also like I did you should only render the surface. Voxels under the surface should not be rendered at all. You can do that in the world generation :)

@@MaxMakesGames thank you for the reply but im not sure how do i check if there's air on that side, do i make an array of air positions?

@@solid_caliber6256 I save air positions on world gen. I place air above the voxel and on the side if the terrain on the side is lower than that voxel. Then I use that air to add faces and destroy and when I destroy I update it

@@MaxMakesGames so you save some air positions when making a cube and then every frame you go through all the air positions and check if they're above,next,etc... to the block?

@@solid_caliber6256 No when I create my world, let's say I place the voxel at 50,20,50 (x,y,z). I know nothing is above it, so above is air. Then I check all 4 sides around. If the y is lower ( like 51,19,50 ) then I know that in that direction there is air. If it's equal or higher ( like 51,21,50 ), no air. At the moment of this video I didn't actually save air, I just had 6 bools for each cube that saved if each direction had air. Then when rendering I can loop all 6 bools and if they are true ( that direction has air ) I render that side. This way any side facing an other voxel or under the map will be false and not rendered and you only need to set the bools when you create it, not every frame.

I'm trying to make videos for everyone to enjoy so I don't want to get too technical but maybe one day I'll make an other video going more into details

I didn't say it wasn't lol I said my project is different

​@@MaxMakesGamesOohhhh I see, my bad then.

Easier than with Vulkan.

I think it is possible, but not optimal. Unreal engine was not made for voxel games so you would have to code all the optimizations and features yourself so it would still be as difficult and you would probably end up with a more laggy game because of the engine. There's no point taking an engine, not using its features and doing something completely different in it haha at that point just make your own engine :P

@@MaxMakesGames but bro they have nanite and stuff wont that make things quicker? (I'm not a programmer)

@@moonshot3159 Nanite is used to reduce the rendered triangle count of meshes. So it takes a mesh with millions of triangles and reduces it based on distance and stuff. But cubes only have 12 triangles. There's nothing to reduce here. The problem is the amount of them. In unreal, you'd probably have to create an "Actor" for each cube and that would create lag because unreal will do some logic for each one of them ( such as checking the distance to them, if they have tick enabled, etc ) that my engine won't do. Basically, by making my own engine I can remove all the things that UE does that I don't want & that would slow things down and since it is pretty different from normal games, that means pretty much everything.

I never said that ? I made my own for fun and for the challenge. It is also more optimized to make your own from scratch. That's what I said.

yeah the moment i saw the triangles i stopped the video and went to the comments.... now to look for another video

It is a voxel engine. It's not a raymarched voxel engine, but it is a voxel engine.

@@Erkle64 This is a polygon engine... Does not matter that you shape polygons like cubes.

So you're saying there's no such thing as a voxel engine? @@simongido565