logoalt Hacker News

vunderba • today at 6:14 PM • 1 reply • view on HN

Nice job~~

So I've done a little bit of testing. When I loaded up the editor, I expected it to communicate with the installed binaries for my large language models, or possibly use a BYOK (bring your own key) approach. But once I understood that it's driven from the command line and you see the changes happen in the editor that gets spun up, I had no problems.

I've been experimenting a fair amount with LLMs driving procedural graphics myself, although my experiments have been mostly limited to relatively low-resolution stuff, such as EGA adventure game graphics.

So I decided to put Klad through a relatively hard test: I took a reference picture of an illustrated squirrel and asked it to recreate it, then set up the rigging for a basic walk cycle. This was using Fable 5.2 high.

Then I did the same thing, but with a more traditional approach, using standard generative models to manually create a walk cycle. This was all done relatively quickly, so bear that in mind.

Here are the results. I still think these are early days, and LLM-driven graphics are only going to improve.

And there are obvious advantages to a procedural system with rigging: Much easier to maintain consistency, palette control, and the ability to make precise alterations without having to deal with any kind of conventional in-painting nonsense.

https://imgpb.com/vJFpP


Replies

ambewas • today at 6:22 PM

Hey thanks so much for putting Klad and Fable through this test!

I think the results are really interesting. I think it's very obvious the classic image-to-video approach yields much more natural results at this time and with the current models.

I think I'm going to do some testing of my own, and see where things can be improved. I do think that the bottleneck at this time, is the model you use itself.

But it's like you say, it's very early days with an LLM expressing its ability to draw/paint. In my own testing, it kind of feels like it did with coding 2 years ago: yeah sure the model is pretty Okay at building a function, but I wouldn't have let it build a whole feature back then.

Nowadays, I'm practically only reading code and thinking about how to refine my instructions for the next build.

I'm sort of betting that this evolution could go the same way for graphics (and possibly audio/midi as well). And I wanted to have a tool ready, to see how it evolves.