Видео

I think the three little dots in the 3D viewport and then near the bottom there's a Stats button

thankyou, thats gonna be a really useful tool to have on screen

AnimatableBody technically is a StaticBody, just has that field which allows synchronizing to a physics frame (which I'm not sure what that does precisely. Maybe animation frame times have no coupling to the physics frame by default). I need to add AnimatableBody to the pipeline. It wouldn't break anything else at this point, just another body type

Hi there! So there's two main usecases for this add-on. 1) is level design in Blender. 2) is designing entities (like props) in Blender. In both cases you can author collisions, assign scripts, and do lots of other things. Really I would only say people should use it if they are interested in designing in Blender rather than composing things in Godot. I could give a much longer answer but that's the short version :)

And just to add one more though. I absolutely encourage people to play around with import scripts. Of course, that's what this add-on does, but the import script has a few stages and does lots of different things. It might be overkill for some folks if they just need some very minimal import tooling.

@@michaeljburt Hey thanks for the reply! Yeah I find Blender to be clunky for more than just editing some assets I already have because I'm a complete beginner to Blender. I have a couple of import scripts that do different things for me in Godot. The main one I have is to remove the textures on import and assign a texture resource that I have to all my assets which use that particular texture. Then I can edit the texture resource in Godot and it updates all the assets using it. And if I ever wanted to adjust one or two assets differently I just make them unique. Probably my biggest gripe about 3D workflow inside of Godot is not being able to just apply different textures to assets because they are Node3D when you drag them into the scene. I do something similar with collisions. Your tool looks very helpful for the more Blender savvy users though!

I think I fixed it by using the "value" modifier in shading instead of scaling the UV in the UV Editing tab. Guess this should be the norm instead of my ghetto solution?

Sounds like a UV mapping issue

Ahhh that's a blunder on my part now... link in the comment should be fixed now, and I will begin fixing the others Thanks for the heads up!

Yeah that totally works. I just like doing the complete gltf export from blender that has the mesh, material and textures all together.

@@michaeljburt okay! thank you that's helpful. and i do get it, no giant mess of extra material files

Just commenting here for posterity - it seems the issue was using the mono version of the engine. You can still build and run, but no breakpoints.

Good idea. I will try to get that into the final release!

Depends on UV mapping and how normals are split. In the simplest case, with smooth normals and no UV mapping, there's 8 vertices in the GPU. Depending on how you break up your UVs, some verts will share UV coords and some won't.

If I ever get time then an update will be coming! A few things have changed, so I really need to test it well.

@@michaeljburt is there a way to setup on blender what meshs should be unwraped for lightmaps on import?

@@dani3d_b it's definitely an idea to consider. I will try tinkering with it

If you're using the old test repo, that's way out of date. The way to get it now is from blendermarket

I think I might be doing a bad job of marketing 😢 but it is in my backlog of things to do! Hopefully will be up soon.

@@michaeljburt Haha, it's all good. Marketing rarely works anyway, even when it's done perfectly it usually just feels like screaming into the void. I saw the game in "recent games" in the Steam store, and thought "my friend will love this, I gotta send her the trailer." I joined your discord btw. 👹

I would look up "association" vs "inheritance" if I were you. The scene tree is technically composed (via association of children to parents) and classes are inherented, e.g a MeshInstance3D inherits a GeometryInstance3D so it gets all the stuff that GeometryInstance3D has. You can build your own classes using the "extends" keyword and giving it a "class_name" at the top of your gdscript file.

@@michaeljburt ok thank you

Hitting "use this template" is effectively the same as a fork, except it cleans the git history so it doesn't take as much space (you typically don't care about the repos history for template-like repos)

I ditched it recently. Adobe was just too aggressive. I'm trying out other texturing workflows. We'll see how that goes.

Hey there. I can get you the update, you just have to DM me on Twitter @_michaeljared

In my experience procedural gen will always be a mix of batching draw calls and messing with shaders that effectively get instanced somehow. But as long as you stick to those two constraints the sky is the limit! It's something I 100% want to investigate more.

@@michaeljburt I’ve got the city kit from Synty, would be handy for placeholder models

Yeah that would be a really nice optimization... The bool/setter hacks is perfectly fine, but just not as pretty as it could be

Thanks! And that's correct, we shouldn't scale collision bodies (or shapes) in Godot. My more recent videos take a closer at this in terms of proper workflow

You know, importing every object at 0,0,0 is an interesting idea. I'm wondering if I should include that as a checkbox in the add-on that you can apply to a whole bunch of meshes if you want. Otherwise, I have no idea how to get that done

@@michaeljburtYeah, the whole "export individually" really gets on my nerves ! I mean, you can bring them in, localise them and reset their position. But that's still a pain in the arse if you have dozens of assets. Anyway. Keep up the good work. There's people that appreciate you around here 😊

It's on GitHub

It's on GitHub, I tell you in the video. You just gotta watch it

Gltf natively supports armatures, weight paints, animations , etc. so I see no reason why exporting the armature in isolation wouldn't work. I haven't personally tried it though.

These are good ideas. Another thing I've been thinking about leveraging Blender's asset drawer, and having fully kitted "game entities" that can just be dropped into a scene for composition. Then your proposal of having an object just come in (when importing into Godot) as a packed scene instantiation, the path having been already tagged in blender with that kit, makes a heck of a lot of sense.

For my use case, just having 1. replacing with an existing scene would be perfect.

So I don't think we should push it to an "auto update" feature(I'm also not sure if it's possible). Exporting a GLTF or saving a .blend file can be a resource intensive process. And trying to do that every time we tab might slow down the system a lot. So basically your options are to set up a one click export (using the add-on Export button) or hit Ctrl+S to save the .blend and import that way.

Merge by distance doesn't always fix it. A hair mesh will often mess it is up, that's why I recommend separating it, and then weight painting it separately

I've actually never tried parenting animations to an empty- so I'm not sure! But it's on my backburner of things to try