Post

After that, @bodybygumdrop.bsky.social is using Blender and Godot together in increasingly entwined ways: “Never Done: An Evolving Blender Workflow for Building RPGs”

David’s showing Blender as a level editor for Godot, where if you save/export in one, it reflects to the other. Thus allowing you to make edits Godot can’t do, but Blender can do.

This workflow is based on a lot of previous work that makes it possible.

The asset pipeline is quite something. There is a lot of backbone to what is, in the end, a button that makes it immediately sync within a second.

The pipeline is pretty huge on the tech side, though in use it’s simple, and it allows for all kinds of content workflows between Godot and Blender

The reason for wanting to build this pipeline, and iterate it further, is… UX friction! The regular workflow was too frustrating, so this pipeline was built to make it feel much easier. Though, there is still friction remaining.

This Godot <-> Blender pipeline will be released soon under MIT, with example CC0 assets with a demo. Along with documentation of workflows.

Next a talk by Bart Wilmink about LODs. I didn’t have the capacity to live post this one, it had so many illustrative gifs of assets changing. Catch the recording! All I can say is: Why are LOD workflows so frustrating?! Shouldn’t this be a solved problem by now?

Next up, we’re getting the premiere of Blender’s new short: Singularity. I am seeing it the way it needs to be seen: Maximum front row

I saw a demo of this many months ago, half finished. Seeing this now, fully formed, on such a huge screen with great audio is awesome.

Definitely the most comfortable conference seating I have ever sat in

Really great discussions and demos today at GodotCon. I haven’t seen a talk yet, there are so many interesting folks to meet!

Just draw an incredible PVKK demo on an absolutely enormous cinema screen.!

Next @reduz.bsky.social is talking about how to think like a Godot developer.

How is Godot developed? There is a community, and a foundation. Contributions from the community go through the foundation.

The ideal workflow is image 1. A smooth way to work on submissions. But the reality is image 2. Many things get ignored.

Why do submissions get ignored? Volume of submissions is just too high. Answering properly takes a lot of time. Some contributors can’t take a no, no matter how polite. It’s a stressful situation for everyone.

This organically leads to shiny proposals with barely any use, drama discussions, and endlessly open PRs that will never get merged no matter how much they are worked on.

How can you help? Understand this rationale. Think about whether it’s useful now, rather than in the future. Think like a Godot developer.

Introducing an idea: Feature Scoring, to rate a feature to measure if it should be merged or not. Measuring would be on a CRIS score. Complexity, Reach, Impediment, Stakeholder.

Example issue:, just for example: VIM in Godot: Complex, few need it.

Example issue: Interfaces. Important, but technically complex.

An example from a feature request by @reduz.bsky.social himself: Action Area. Not important, undemanded.