Comment by OtherShrezzing

1 day ago

If you're working on a small game project without an existing framework/platform, you usually build a really bargain-basement game editor alongside it. That editor takes a long time, and it's often spent in arranging UI stuff.

If you're already using Blender to make assets, there's some benefit to stuffing Blender's UI into your game editor too.

In that case it would be competing with imgui, egui and similar libraries, but the submission is comparing it to GPUI.

  • Do imgui/egui have comparable numbers of interface objects and parameters to adjust their look and behavior? I certainly wouldn't suggest either as an alternative to QT-level interfaces—which seems to be what's offered here.

>If you're working on a small game project without an existing framework/platform, you usually build a really bargain-basement game editor alongside it. That editor takes a long time, and it's often spent in arranging UI stuff.

Not in an age of AI.

I mean if you want to code all this stuff by hand, I get it. But that's a choice. And since it's a choice that means shoehorning a Blender UI into a "bargain-basement game editor" (and having a "bargain basement game editor) isnt really needed. You absolutely don't need to spend a lot of time arranging UI stuff.

Game tooling is pretty trivial now and it's not user-facing. Again, I fully understand why someone would want to do this themselves still but let's not pretend thats not a choice at this point.

  • Depending on what you and the other poster mean by "arranging UI stuff", AI could either solve the problem for you or create larger problems, especially if you're not opinionated on either technical or UI matters.

  • Just curious: if this is really the case, why are you even spending time commenting on and thinking about one particular UI framework or not? As a dummy still writing code and making games by hand, I know why it interests me, but isn't this like an archaic topic for you? What is there to actually gain or learn from one library or another? Can't you just think about high level concepts and pure ideas now? Spend money to do the rest?

    • I think it’s just about as weird as questioning somebody’s motives on an Internet comment thread. I certainly share GP’s opinion about game tooling, but i’m here because i still care about making good software and that involves learning about and navigating technological developments as they happen. Is that sufficient reason for you?

      Edit: the snark I’m responding to has been edited out

      2 replies →

After trying blender for about 20 years I still find the UI/UX awful. I think a lot of the new blender generation has baby duck syndrome.

  • Blender had a very different ui before and a big redesign, so most people have different opinions between the old and the new design. It sounds like you find all of them awful. I find that surprising and wonder what 3d program you find have good ui.

    • I have used every version of blender and it has always felt harder than it should.

      I have used 3Ds max, maya, lightwave, cinema4D, milkshape, wings, Houdini, unreal engine 1 - 5, Hammer, Threejs editor and probably more. The Blender UI is worse than all of the above.

      5 replies →

  • > I think a lot of the new blender generation has baby duck syndrome.

    Maybe some of them do, but even though I disliked the UI at first, I've come to appreciate it as I've learned it. It's simply different from most other software, so that obviously causes friction. However, I think once you learn it, it's quite a good system. There's a tradeoff between optimizing for familiarity/new users, and providing an optimized experience for advanced users.

  • I'm not a professional designer or 3D modeler but I've used Blender quite a bit. I know what you mean but the latest UI post redesign isn't bad.

    Blender does a LOT of stuff. Its not an easy product to create an UI for. But I think the problem is much bigger when coming from a different 3D package than when learning from scratch.

    My teenage kids use Blender as the first 3D package they've ever learned. I was impressed with how quickly they ramped up through videos and learning from each other.

  • Apparently there is a crowd still using 2.79b, the last version with the old UI (current LTS is 5.2)

    My baby duck fingers could probably pick up LightWave 3D again in an hour or two. I could never gel with Blender.

  • I agree, I don't think blender has changed as much as people say. But I don't think it is baby duck, I think blender always had a good UI, it has just taken the rest of the world 20 years to catch up.

    A lot of people go "Blender UI was horrible, but they redesigned the whole thing and now it is good" Having used blender in a minor role for 20 years(i think I started on 1.7), I think this was just a big psyop by the blender team. Sort of how the client goes "Change things" and you change nothing, wait a day, and tell the client "I made the changes you requested" client: "I love it"

    I am not saying the blender team has not made substantial improvements to the UI over the years, but the core is still that same quick blender workflow, This is very different from the normal clunky GUI design of 3d modelers of the era and as such blender got a reputation for having a weird UI which was easily translated to blender having a bad UI. So what do you do when you have an unwarranted bad reputation? Especially now that the rest of the world has caught up and is using your flows and they are not so weird anymore. Make a dark mode and put out a big press release "we redesigned everything, it's good now" so people will try it.

    • I feel like the 2.49 to 2.6 update was a bit overblown, but the 2.8 update was pretty damn massive to me eyes

  • First time I hear "baby duck syndrome".

    > Baby duck syndrome is a cognitive bias where people automatically prefer the first system, interface, or product they learn to use, judging all later versions or alternatives by how well they match that initial experience.

    That's actually extremely common in scientific (GUI) software. And in any professional setting I guess.

    • > That's actually extremely common in scientific (GUI) software. And in any professional setting I guess.

      I don't think that qualifies. There's an important distinction to be made between an aesthetic preference versus a professional not appreciating a tool being mucked with. Anything that interferes with my workflow without immediately providing substantial benefit is something that's actively harmful. In fact even if it does hypothetically provide huge benefits I still might not want to deal with it right this second.

      5 replies →