I haven't tried it, but AFAIK there are a couple ways to connect navigation meshes, from looking i think using edge_connection_margin looks easiest, i would think you make sure that is greater than the gap between any dungeon room doors: docs.godotengine.org/en/stable/tutorials/navigation/navigation_connecting_navmesh.html

you could add another multiply in the shader like * -1.0 or * vec3(-1., -1., 1.) to multiply each the xyz components separately

awesome!! thanks so much

thanks, i used my own basic one i made, i might release it at some point, but it's very basic not many features. just made it for the video real quick.

im interested in doing a video on this but i have some other stuff planned first :)

I did a video on making a swimming mechanic for FPS controllers here: kzbin.info/www/bejne/fqu0p3xqrNylY5I However, I haven't worked with buoyancy much. I think you might be able to modify gravity for rigid bodies using an Area3D.

@@MajikayoGames I am trying to build a game based around island exploration (majority ocean biome and boat travel) but buoyancy is kicking my ...

not sure i fully understand, but it sounds like that would work. you could even pre place rooms in code, then call .generate after. that's what i did in the mansion example. there's also the custom get random rooms function which could work for this.

glad you enjoyed :) i haven't tried nav mesh generation yet. but yeah i assume you could just bake it after if you needed to. or, i think you might be able to pre bake it for each individual room and then the navigation server joins overlapping points. i haven't looked too much into it though.

@@MajikayoGames oh great yah I thought maybe it would work baking it in pieces, it works for occlusion culling at least! I wonder what you got cooking now ahah this is such an awesome unknown godot add-on! 👍👍🙏

i have seen dungeon architect, it did look pretty cool. would be neat to build this out some more, if i have time :)

Dungeon Architect was one of the inspirations for my comment. If we even got a fraction of that functionality, I think it'd go a long way for making procedural generation easier in Godot.

Currently planning some other projects so I won't have time to implement this, but you may find the source code overview portion of the tutorial I did helpful. All the code is CC0 so you are welcome to modify and do with it as you please.

@@MajikayoGames Alright I'll see if I can implement it and if I get something working I'll open a pull request with the changes from my fork.

The main difference is that dungeon kits are no longer a thing, but many improvements were made other than that. Instead of dungeon kits now, you just define individual room scenes, and add them to the DungeonGenerator3D's room_scenes property. Also, you no longer need AABBs you just set the room's size_in_voxels property for that. I added a ton of debug info so hopefully the new version is a lot easier to use.

@@MajikayoGames Oh I see so I already had this version this is the same one that you showed on your last tutorial video right? I'm guessing I still need to update for a few fixes that happened over the last two weeks? I'll make sure to send you footage when I get a playable version of my game!

@@onokoreal awesome would love to see it! yep i did a few bug fixes and minor improvements in the last couple weeks, it should be stable by now. anything else ill be adding, will probably just be bug fixes if anyone finds any glitches.

@@MajikayoGames Awesome thanks. Quick question if you don't mind I just updated my whole addon folder and everything seem to work the same so it went well. But I wanted to try some of your new prefabs to see how they work, notably the mansion. Didn't want to reuse your "debug" spawn tool again since I have my own setup for things so I setup a Dungen3D node with the mansion rooms, then added the HouseExterior prefab around and also added MansionEntranceRoom and aligned it in the editor (did manually what the script does when you choose mansion with your debug tool basically) Despite that I'm getting an issue where HouseExterior stays invisible and never make the "cut" needed for the entrace to be collision free. TLDR I setup a DungeonGenerator3D with HouseExterior scene from the mansion prefab along with the mansionrooms but the housexterior script doesn't seem to load properly outside of being loaded from the debug tool. I'll let you know if I figure out why haven't dabbled too much with your tool lately. thanks.

@@onokoreal ah yeah you might have to adapt the HouseExterior to your own scenes. that one has some setup being done from the demo scene generation script. it's just meant as an example to show what is possible, you can refer to the scripts in the DemoScene and the HouseExterior and create some similar. Also you can check the wiki for more info on how to use the addon: github.com/majikayogames/SimpleDungeons/wiki

Glad you are enjoying! All valid questions, and would be very good to add. However, this add-on was more intended as a proof of concept/starting point for anyone to create their own terrain system, modifying mine or referencing my code and this video. For the core of it, I want to keep it as simple as possible. It is locked to 4 textures currently. Shader you couldn't use as a texture. It only accepts Texture2Ds as textures, whereas a shader would be a material (BaseMaterial accepts Texture2Ds to color it). I'm sure if you modified the terrain shader, you could have some interesting setup where for certain colors of the splatmap you could use different fragment shader logic. Smooth brush is a good idea. I wonder does flatten accomplish a similar purpose? I guess not as effectively, probably for smooth you would want to maintain hills. For another pretty easy to use terrain system which has a lot more features such as more than 4 textures, I would recommend hterrain if my SimpleTerrain isn't enough for your needs. Hope this helps :)

@@MajikayoGames Thanks for the reply :) I suspect I'm trying to run before I walk here. If I stick with learning GDScript I could potentially implement these changes myself for my own projects.

currently no it just works for 3d. ive thought about adding 2d but moving on to other things than this addon after doing a bunch of work on it.

interesting i don't think i ever realized i implies 'iterations' haha. i always just used i because that's what all the examples used when i first learned loops. i, then j for nested loops, nested again i think it's usually k for the var name. but yes for i in range(0, 10): iterates our i var from 0 to 9 throughout the loop

i actually just added a heuristic_scale option to DungeonGenerator3D because of this comment. previously i thought euclidean helped with that but upon looking it up it doesn't seem to. you can try increasing heuristic scale to 3 with manhattan or euclidean modes, and also try messing with the corridor cost option, raising this (probably just to 1) can make the corridors more bulky, possibly helping with the problem of zigzagging corridors. it's hard to completely prevent this when using astar.

@@MajikayoGames You are the best, thx!

I think you should be able to put a navmesh in each room scene and as long as they get connected properly, enemies should be able to pathfind through the dungeon. docs.godotengine.org/en/stable/tutorials/navigation/navigation_connecting_navmesh.html

maybe because they are spheres, easier to push, but yes it's not a perfect method, it would be very difficult to get perfect physics interaction. this is just a simple method to apply some force when pushing against objects. as i said at the end, for more complex cases you would probably want to program it in yourself.

It's hard to say without seeing your code, those accel/decel/friction vars are pretty sensitive though. I would try with my values first, copying exactly from my code. Then adjust one by one. Yes if friction or decel is higher than accel or walk speed, probably you won't be able to move. I don't have a clear explanation for each, other than it's just the quake/source movement recipe. Not super intuitive but it gets the exact same movement style so it's important that these variables are used how they are. So I would try copying exactly from my code and changing one by one adjusted until you get your desired move speed/feel. Also check if the properties are changed in the editor inspector on your character, if you change them once, they will stay the same even if you change them in code I think. If you can't figure it out, you can pastebin your code and message it to me on twitter and I could take a look if you want.

The tutorial fps controller has no clip bound to V

@@MajikayoGames ye i found it when using your dungeon exemple, thanks !

not quite, .all returns true if ALL checks pass. so in that case you are checking if the player is overlapping all water blocks. will only work if there is 1 then. you could use .any which is a similar method to .all on arrays which will check if the player overlaps ANY water blocks.

ah yeah that would be a nice effect. last time i played lego fortnite, they had a really nice example of this effect. when you looked up at the rain, it would start accumulating droplets on your screen.

The chunking is pretty simple, you can see here: github.com/majikayogames/SimpleTerrain/blob/a074a13789bd64e9a11866fb8fb6d27666145642/addons/SimpleTerrain/SimpleTerrain.gd#L302 _create_lod_meshes and _create_chunks functions create them. It just makes the grid of plane meshes. You only need a number of plane meshes to match the number of your LODs, 5 or whatever, and then all the MeshInstance3Ds can share each mesh. Then in _update_lods each frame, I just set the mesh to use for each chunk, higher LOD the closer to the camera: github.com/majikayogames/SimpleTerrain/blob/a074a13789bd64e9a11866fb8fb6d27666145642/addons/SimpleTerrain/SimpleTerrain.gd#L437 Hope this helps. Let me know if that makes sense

It sounds like your nodes are positioned differently. What I showed here is dependent on all head/camera nodes being positioned at 0,0,0 and only the HeadOriginalPosition node being moved (to 1.79)

@@MajikayoGames Holy crap you're right. That was the only thing I forgot to change.

Not really a built in way to make this easy at the moment, it gets complex if you want to alternate 4 length paths in astar, would have to do some hacks to force the algorithm to do that. But you could try just placing some 1x4s in the normal rooms phase and it will connect them. You could for instance place them manually and always have it somehow that it will have 1x4s inbetween rooms where you want them, then it's likely that it will be connected as you want. You could also do something like, just spawn totally empty corridors with no models at all, and then do a final pass at the end where you iterate through all corridors place and replace them with some certain model if there is 4 connected in a line.

@@MajikayoGames Bummer to see a small limitation like this but understandable, worth a shot for trying it out though, thanks for the detailed reply!