rogerbennett.bsky.social

rogerbennett.bsky.social

@rogerbennett.bsky.social

Software engineer, Games programmer, Developer advocate, toy collector, drinking coffee, Technical Director Elite Dangerous at Frontier.

228 followers16 following248 posts

This week in #EliteDangerous My anaconda don't want none, does yours? There are moments of working in games that barely feel real. The panther was a long payoff, but the anaconda is just forty years iconic. I hope you have as much fun with this as I have. Fly dangerous, commanders.

This week in #EliteDangerous even I'm getting excited by ship teasers these days, it's just brilliant. I was stargazing this week, and there was that weird feeling that I can just GO THERE. Like, the stars. Any of them. I mean I've always known this but there was something magical about feeling it.

This week in #EliteDangerous has seen it all happening! An ambitious release with a lot going on and just the latest in a series of iterative and incremental improvements. Over the past few years delivering new features and revisiting existing mechanics, and a stepping stone to the future. O7

This week in #EliteDangerous Either you are an explorer, and we've got a cheeky little vessel for you, or you are kicking ass for Frontline and there more options than ever before. And yes, frontine will send a runner to pick you up from the Black too. Just park up and get into the action. O7

This week in #EliteDangerous. For those who know me, this is what it's all about. I get excited each release. A ritual of steams, twitch, and youtube with a window mosaic showing a mix of familiar partners and names that are new to me. So Yeh, we gonna. bsky.app/profile/fron...

Frontier@frontierdev.bsky.social

The surface is calling. Discover the next new Elite Dangerous vessel. Full Concept Reveal - 2 June 2026

This weekend in the code mines, slipped and wrote some GPU lodding with OpenGL 4.6 I sat down to fix a 6502 pixel error, but ended up knee deep in RTX shaders. Now I have a kinematic hierarchy with mesh shaders so I've got that going for me which is nice. I like writing code by hand.

This week in #elitedangerous ... The Lynx Liner! I joined FDev 5 or 6 years ago becoming a custodian of the massive space adventure sandbox I loved. It's been hard work, I'm proud of my team and the Lynx has become a symbol of the shared journey we have been on together as a team and community. o7

Modern GPUs are faster than you think. I've now written a tumbling cobra at every tech level from 6502 assembly to compute raytracing. Holy smokes when did hardware get so good? 200μs render is... five thousand frames per second? Yeah no. I'm thinking I need more evil plans and stuff. Any ideas?

kicking ass is back in town. This week in mad code plans... writing a barycentric approximator! You know triangles? What if you were bad at drawing them but it was faster. Sure they are a bit blobby but those blobs are a couple of pixels and the GPU isn't fill rate bound. Yes I have gone wrong.

OK I tried some code and slept on it. Drawing triangleish blobs without precise edges should be faster if you dont have a GPU but there are problems. Depth gets weird. But there is an image stability problem. One frame is faster because errors but different errors every frame is an ocular nightmare.

Well, my AI coding adventurers have been fun but are coming to a close, and I'm working on the final write-up. An 80b qwen with 256k context is woefully insufficient to help with simple tasks in code ~1% the size of a real game. I've still been unable to find anything it can help with.

If you like languages where whitespace matters please reach out. We can help you. If you design a language where whitespace matters you are going to hell. Straight to Hell. To the boiler room of Hell. All the way down. Python and yaml I'm looking at you.

My AI coding "assistant" just gave me a inappropriate singleton that I'm going to have to remove. And uses strings where it should very obviously use integers. If it makes bad decisions like this, whose code was it trained on? I can identify and reject these, but would an inexperienced developer?

This AI agent has suggested that perhaps we should try again later when I have more patience or try something else. An alternative would be that its less wrong all the time. There are only so many times I can call out a liar who responds with "You're absolutely right!" before I give up.

I'm on a train so no AI programming adventurers this week, but I am able to sit and develop some human made code. I did encounter the phrase "Slop jockey" as a pejorative for AI programmers. This week I'm trying to pull every trick to not allocate memory, and reduce, reuse, recycle my footprint.

This weeks AI coding hasn't gone as well as the previous two failures. All was going well until my quota ran out and IDK what it was in the middle of but doing half of it was bad news bears for my CMake file and who knows where its mucky paws were. Anyway I guess this is what revert all is for.

I'm pretty sure this new fangled thing has some value buried in it somewhere if I can just find it without terrible things happening. Robot uprising aside. And ignoring the environmental impact of burning sea turtles or whatever powers this abomination.

This weekend saw my second attempt at using an AI tool to help develop software and you'll be pleased to know that humanity are winning 2-0 There were a few brief moments of "oh that's neat" in a mire of "why is what" and the results I got were no better than last time.

It was also my first attempt at debugging AI generated code and that went about as expected. Parachuting into "whatever this is" and finding a problem is never easy. Smaller iterations and stricter tests would have helped keep it on the rails - and I can already do that without AI.

Tried today to write down the unwritten rules of programming so that a mindless AI assistant can follow them. These implicit rules that a human intuits from context. Seperate your design time data from local data and from live/replicated data.

This is obvious to a human but I don't need to specify which to use where... I need to be explaining the rules by which we determine which variables are compile time, cook time, need designer live-edit, are local runtime variables or are replicated live. This is a semester of lessons not a prompt.