Post

Making a game without an (established) engine creates a special kind of paranoia when bugs are brought to your attention. Sometimes it's an AMD input assembler bug in drivers from 2021 and prior coming back again and again. Sometimes I actually just wrote some bullshit. Today it was the former :)

14/9/26, 7:34 pm1 repost12 likes

Echolox | Play BEAT WEAVER!

@echolox.com

14 Sept

Please keep your graphics drivers reasonably updated everyone!

Taki/滝 the Malamute (EN) (They/It)

@taki-wan-en.bsky.social

14 Sept

I'm trying to get into game programming because AI is making its way into my job and I fucking hate it and losing more chances to code every day. I'm starting with Godot, but have picked up books on the basics game engines. You're to blame for that. You love this shit so much you make it look fun.

Echolox | Play BEAT WEAVER!

@echolox.com

14 Sept

I mostly just like knowing what is going on under the hood. That knowledge helps a lot with working on the higher level stuff regular engines expose to users. Suddenly certain behaviors or API choices make sense. Or you find a good reason to despise them ("what were they thinking??").

Echolox | Play BEAT WEAVER!

@echolox.com

14 Sept

But also it's a lot of work. Very double-edged sword of agony and fulfillment :D

Taki/滝 the Malamute (EN) (They/It)

@taki-wan-en.bsky.social

14 Sept

I think with my Autism, I have trouble using something fully without knowing what's going on under the hood. It amazes me how easily people can just start using a new package in coding, and a lot of times I'm over here like "Yeah, but what's happening under the hood?"