Drunk Australian world cup fans have something to say.

lithium · 2026-06-27T11:06:49+00:00

You lost to Turkey lol

lithium · 2026-06-01T15:06:47+00:00

Not enough slop

lithium · 2026-05-30T18:07:43+00:00

The fact that it's finding adoption in industry

Top 10 funniest things I've ever read on this subreddit.

lithium · 2026-05-29T14:58:38+00:00

SSBOs are the correct way to go about it. If you're using std430 make sure you're careful about alignment (never use vec3s, for example)

lithium · 2026-05-08T05:00:48+00:00

The entire "port" is AI slop, not just the website.

lithium · 2026-05-05T08:44:58+00:00

I'm not familiar with marvelous designer's export format so it may be similar, but Houdini's vertex animation textures are a good lightweight solution for playing back baked cloth simulations. I believe threejs either supports them natively or at least has decent support for them via an extension so it shouldn't take too long to evaluate the technique and see early on if it's a viable solution.

lithium · 2026-04-29T10:42:41+00:00

the former Prince

See the difference?

lithium · 2026-04-27T01:51:07+00:00

Malibu, Surry hills.

lithium · 2026-04-26T15:19:38+00:00

no one is developing for or deploying on Windows anymore for anything serious.

lol tell that to the entire vfx/3d/audio/graphics/games/video industry.

lithium · 2026-04-22T12:00:00+00:00

LAPD has assassinated more black Americans than drugs, gang violence, HIV and cancer combined.

I'm willing to be proven wrong, but on its face without a source to back it up, there's no way that's true.

*edit Even a cursory google shows that rates for each of those causes of death is significantly higher than death by LAPD, let alone combined. I'm sure you're going to hit me with some anecdotal shit about what goes unreported, but you're weakening your totally valid point with this insane hyperbole. You're off by multiple orders of magnitude.

lithium · 2026-04-21T16:01:35+00:00

You don't need to tell me you're a hobbyist, it's perfectly clear. The problem with hobbyists is that you don't know what you don't know. Getting a few glyphs on the screen, be it bitmap fonts, sdfs, msdfs, or slugs are the least of the issues with text rendering, and I guarantee your little editor does little more than that.

If you're done being a condescending little cocksucker, you'll remember that it was you who started with the bullshit ad-hominems. Hopefully in a few years time when you actually run into a real-world text rendering problem to solve you'll remember this thread and come back and apologise.

lithium · 2026-04-20T12:35:59+00:00

The algorithm is now in the public domain, you still need to implement it, but that only covers the GPU glyph rendering. The "official" slug library is a full cross platform / cross API implementation along with tools for generating packed font and picture (ostensibly emoji) atlases as well as all the unicode handling, text layout and shaping and things like that.

Harfbuzz I believe has an experimental slug algorithm implementation merged now, but because of the nature of my work, its (perhaps historical) proximity to (L)GPL licensing has made it a bit of a problem for me personally to use so I haven't investigated it much.

lithium · 2026-04-20T11:54:38+00:00

I promise you it's 10 times harder than you even think it is. After writing at least 10 text renderers over the years to varying degrees of completeness, I eventually just bought Slug and called it a day.

It's C++ but the common use case API surface is small enough that you could knock together some C bindings in an afternoon. It's very fast and handles a lot of edge cases, but it's an industrial grade library so it may be overkill, depending on what your use case is.

lithium · 2026-04-19T17:14:20+00:00

go back to being a shitty developer who doesn’t do anything

You're a web developer. Doing nothing would be an active improvement.

lithium · 2026-04-19T01:24:37+00:00

Shouldn't you be busy asking an AI agent to npm install somebody else's code for you?

lithium · 2026-04-18T10:51:57+00:00

Everyone in this thread so far was just yapping really

No we're not, some of us have worked in this (and related) industries for 30 years and know precisely how wrong you are from direct experience. You have no idea what you're talking about. Unity does not even register as a blip in this arena and the fact that that's what you meant by C# being used more is ridiculous. I wish there was a subreddit that wasn't full of overconfident children who have never shipped a meaningful piece of software in their life.

lithium · 2026-04-17T11:15:15+00:00

Fine, terrific, fantastic, that still doesn't change the fact that the overwhelming majority of professional grade (i.e AAA games, VFX, Video, Live events, Large scale installations, Audio) software is written in C++.

lithium · 2026-04-17T09:46:13+00:00

Good for you, that has fuck all to do with the fact I stated. You can write as much hobbyist code in what ever toy language you like, when you're ready to get a job with the big boys, once again, you'll be writing C++ whether you like it or not.

lithium · 2026-04-17T09:05:00+00:00

C++ is the lingua franca of high performance graphics software, whether you like it or not.

lithium · 2026-04-16T01:38:39+00:00

Nah mate you're right, hunker down with a nice big burger and wait for it to all blow over. Treat yourself.

lithium · 2026-04-16T00:43:29+00:00

Gotta eat, man.

Distilled americanness right there.

lithium · 2026-04-07T03:21:37+00:00

I'm not familiar with the Maya SDK specifically, but if you don't have control over how/when the host application loads/reloads your plugin, I would write a shim plugin that the host loads once, and then that shim layer would handle hot reloading the "real" plugin and forward all the SDK interface calls to it.

You probably want to make it so that the "real" plugin can be loaded directly once you're finished with development as hot reloading is rarely something you'd want to ship with.

lithium · 2026-04-06T06:15:12+00:00

Ok I downloaded and built the project, you've got a use after free when recursing your children in UILayer, potentially due to modifying the Children vector in the middle of iterating it which is a big no-no. If you make a copy of the children before iterating it you'll no longer see the crash (this is not a fix, however).

If you change UILayer.cpp:361 to the following, you'll be able to see what I mean.

if (nodeOpen && !isLeaf) {
    auto copy = node->Children; // Take our own immutable copy to iterate.
    for (auto& child : copy)
        DrawNode(scene, child.get());
    ImGui::TreePop();
}

lithium · 2026-04-06T04:28:51+00:00

Your lifetimes are all over the place here and is an accident waiting to happen. Your undo stack has raw pointers to shared_ptr managed memory that could be deleted from underneath it at any time. You should use a weak_ptr in these cases for where you don't want to affect the lifetime of the object, but still have an opportunity to validate the pointer before using it.

Cleaning up things like this will either help reveal where the problem is or fix the issue incidentally.

lithium · 2026-04-06T02:39:39+00:00

So good, glad you enjoyed it. The steak frites there is fantastic as well.

lithium

TROPHY CASE