Видео

thank goodness someone else thinks the nla stuff in blender is stupidly complicated. Not a good system. It all feels like a hack.

the only thing that helped me was CleanUp merge by distance with a value 0.0005 instead of 0.0001 which is the default

Is there any way we can convert blenders shaders so it van be used in godot? Like some scrolling lava textures would be so nice to make in ble der u know material maker can convert it to a godot shader but idk about blender

whats that gotf ur talking about ? and whats the diffrence to multimesh? i think its impotant to know right? thx!

This! This is exactly what I needed! Thank you so much!

Are you planning an macOS release?

I don't see a demo on the steam page

Wish c++ was more supported as gdscript sometimes is really limiting

Recalculate normals. Often putting both metarig and mesh at scale 100 helps.

gdextension is a real harsh mistress though lol, two days in i'm still working out how to get around bugs needed to learn pointers and macros to save all the typing.... still have bugs now but 2 days of solid coding for my framework itself.... i had good api knowledge already if that sounds fast, if that sounds slow wow you are a hardcore coder.... for me ths is my first serious cpp, i'm trying to do some fluid simulation thanks for the video, i needed a break

crazyyy

Thanks for explaining what we were too lazy to explain in the official video. About how, in my opinion, the implementation is more like a hasty inclusion of beta functionality in the release version.

What music used in this video?

It is perfect Michael! Waited so long for that feature. I was using Vertex Groups before. God, it was a nightmare, because vertices aren't exactly edges, so I had to add some geometry to "divide" the neighbouring vertices. Thank you so much!.

It actually fixed some shading issues I had with different bevel weights on the same mesh. Thanks

thanks dude!!!

i've added the launch.vs.json to .vs but there's no debugging option

This is the most useful video series ive ever seen. Thank you so much, you saved me so much time 😭

What about making a larger map. Maybe 1000 meters. Would you recommend doing the same thing or a terrain plugin that deals with LOD? I just don’t really know how I would deal with LOD

clean up by merge doesn't work, there are no holes on my model, REMOVING THE HAIR DOESN'T WORK!!!! WHAT AM I DOING WRONG!? GIVE ME A SOLUTION TO FIX THIS STUPID ANNOYING ERROR!!!!!

If you had 50+ objects, imagine the pain staking work, to do that. I don't recall needing to push them all into NLA tracks, then renaming them, to get them to be all in 1 animation in Godot. In blender, on the gltf export settings, Animation, set the animation mode to Active actions merged. I'd have to test this since it's been a long time since I've done a cell fracture animation for Godot.

I haven’t fully grasped the entire pipeline yet, but you can turn on UV tiles in Blender's Show Overlays option in the UV Map viewport, which makes it a bit easier to understand all the indexing and flooring stuff. Also, is it possible to use your other addon with this pipeline as well? Thanks in advance, man. Your work is very impressive-it brings Godot closer to others professionals softwares

This is an excellent start to building a bridge between Blender and Godot

The problem with these sharp vertex colors is that, even though blender internally doesn't do it in its own mesh model, when exported these create duplicate vertices, and in turn very thin long triangles which are really bad for gpu performance (quad overdraw)

UPDATE: Almost immediately after posting this, someone very kindly informed me that although GLTF does not directly include UDIM data, you can still shift a UV map by a whole tile outside the 0-1 range, and then use that to map to a predefined color value: uniform sampler2D trimsheet; const vec3[] colors = { vec3(1,0,0), vec3(0,1,0) }; void fragment() { int color_index = int(floor(UV.x)); ALBEDO = colors[color_index]; NORMAL_MAP = texture(trimsheet, UV).rgb; } Textures still map properly because they repeat! I will likely be reworking this for part 2 :)

Thank you very much for the amazing tools ! i gonna check it out later

I’m working on a menu that would display the Edge groups like Vertex group does. There’s also an operator to create that group and give it a name. So far it should work with your branch.

Amazing stuff, thanks

Thank you so much for making this it's super useful for nondestructive hardsurface modeling

Hey Michael - addon looks great! I've been looking for a tight solution for Blender -> Godot and this seems really promising. I wanted to add my two cents though on the origin point functionality: the addon needing to move the origin point to the center of geometry to generate the collision shapes is less than ideal. In many cases (like with these Kenney assets shown in this video), the origin is intentionally placed such that the asset will snap to the floor, or such that assets can snap together perfectly (for example, if you're making a pack of modular building pieces). Moving the origin to the geometry's center of mass makes it much more difficult and less scalable to work with assets. Maybe there's a way to temporarily move the origin to create the collision shape and then set it back? I'd defer to you on the implementation. But wanted to voice this as it's a pretty essential part of the common workflow in the games industry.

That is awesome work! Do you plan on having it out as an addon/official release?

Could you make a video on your pipeline? These are the types of things that I look for but have a hard time finding!

From blender 4.3 onwards, possibly 4.4 the action data block in Blender will be system wide and any number of objects will be able to have tracks in the same animation making this workflow so much simpler.

Subscribed! Been trying to content like this... Specifically on procedural content generation. I'm planning on taking a stab at it myself, and I'm actually somewhat surprised that there isn't more content out there like this. I'd like to eventually create some sort of procedural object generation add-on for Godot that could achieve more complex things like generating buildings (how many floors, rooms per floor, stair cases, unique bottom and top floors, etc...).

Setting individual origins seems very useful for those of us who like to import whole asset libraries into godot and saving the meshes to their own files.

when using blender 4.2 I had a similar experience with the shaded viewport slowing down.for me at this usually happens the when i open blender and switch to shaded view for the first time.after that it kinda speeds up on its own again.IDK why its like that.But i switched back to 4.1 for these minor issues.Things you don't notice till u look for them

14:00 I had the same issues "cpp:345 - Condition !is_inside_tree() etc." get introduced to my import plugin going from 4.2 to 4.3. It was from accessing global_position of a node while it was outside of the tree. Funny enough I wasn't even using the var, just a leftover debug print causing me grief Since the scene is not in the tree when you are not currently editing it, maybe that will solve the needing scene open issue, though it's that not that big of a deal IMO

hmmm sounds so useful

Can I pain texture?

Step 1: Delete The Cube Step 2: Add A Cube

Great video, can you share the code you do use to make the bricks wall?

I enjoyed this series, thanks for uploading it. I picked up some tips about NLA that I wasn't aware of before. For a better-looking end result, I've found that lerping the movement direction as well as the rotation is better than only lerping the rotation. Since your character changes its move direction immediately, the animation still looks like it's sliding while the rotation of it is still catching up. Does that make sense? This is how I addressed that in my own project: #Player rotation smoothly interpolated between existing rot + target rot var target_rotation_y: float = atan2(-input.x, -input.y) rotation.y = lerp_angle(rotation.y, target_rotation_y, delta * angular_accel) #Movement direction smoothly interpolated between existing dir + target dir var move_direction: Vector3 = Vector3(-sin(rotation.y), 0, -cos(rotation.y)) velocity += velocity.lerp(move_direction * max_mov_speed, delta * accel) (Note: I had to flip the sign of the input and the sin and cos because my character walked backwards without it for some reason!)

I like your style. Shame these videos don't have more views. Sidenote: I've never heard someone pronounce it "ridge-ify" before. Is it not "Rig-ify", because... rigging?

why wouldn't you just use triplanar textures?

Wow ! loved watching this.

Can I export it in the form of multi mesh with the textures ?

Hi, your addon is really helpful but I can not export simple locator , Camera or Light... i export a mesh with a single Vertex instead

“Classic game” 💀 yeah THE classic game

There is something really engaging and thrilling about the bouncing ball and tracing its direction to make sure you can catch it. Then I think of most games I play and Im asleep at the wheel most of the time and there are 30 layers of unnecessary complexity.

I realized the samee thing when I made pong! It was truly a profound realization