AI Recomping Controversy, PC Games on Switch and more (ft. Scarlet) - Tempcast #99
Theme by VinsCool and AlanJohn
The podcast is also available on Spotify!

Explain this to @EriczanderGreat one this one.
But you guys are showing your stuff, I cant see your stuff. It’s a podcast not a video.

for that sort of things, I am pretty sure the AI creates deterministic tools that will not hallucinate.The problem with AI decomps is that AI will hallucinate what does what, so at the end...
for that sort of things, I am pretty sure the AI creates deterministic tools that will not hallucinate.
But I could be wrong? maybe someone who has done this before can confirm?
And I thought I was writing messy code. Jesus Christ that is awful.If your goal is just to create PC port, sure. The AI can do that. It will probably eventually create a functionally-equivalent but nonsensical codebase full of fakematches (things that compile to the same binary, but are not anywhere close to what was in the original code) and without naming stuff properly.
Said codebase is effectively useless to humans afterwards (and possibly also AI, lacking context from the previous runs), because trying to understand what it does requires you to repeat the reverse engineering effort.
I mean just look at this AI Decomp of Banjo Kazooie. Does any of this code actually tell you anything about how the game works? https://gitlab.com/banjo.decomp/banjo-kazooie/-/blob/master/src/core2/code_C4B0.c
Compare with a decomp done properly:
https://github.com/zeldaret/oot/blob/main/src/code/z_collision_check.c
https://github.com/SMGCommunity/Petari/blob/master/src/Game/AreaObj/CollisionArea.cpp
Not humanly... but I'm sure AI can "decrypt" the code.I mean just look at this AI Decomp of Banjo Kazooie. Does any of this code actually tell you anything about how the game works? https://gitlab.com/banjo.decomp/banjo-kazooie/-/blob/master/src/core2/code_C4B0.c

Jesus. I can't even call this a decompilation. Most of the work reconstructing the code was not even done. This looks like someone just threw the entire Ghidra output at Claude and said "make it perfectI mean just look at this AI Decomp of Banjo Kazooie. Does any of this code actually tell you anything about how the game works? https://gitlab.com/banjo.decomp/banjo-kazooie/-/blob/master/src/core2/code_C4B0.c
and robust
and super fast
".
It will generate whatever ”source” translates to the same machine code after compilation which may or may not (likely not) match the original source due to how compilers work (you can code something 8 different ways and once the compiler is done with it you end up with the same binary anyway, you just used a different convention or approach). This has no impact on the end result since the end result is a binary.for that sort of things, I am pretty sure the AI creates deterministic tools that will not hallucinate.
But I could be wrong? maybe someone who has done this before can confirm?
This is what I bet most people think C code actually looks like. Add some green colors, flashing, and terminal output and you've got yourself a sweet hacker setup for a movie.I mean just look at this AI Decomp of Banjo Kazooie. Does any of this code actually tell you anything about how the game works? https://gitlab.com/banjo.decomp/banjo-kazooie/-/blob/master/src/core2/code_C4B0.c
I don't think there should be any controversy, AI has accelerated recomps and porting games to the MiSTer FPGA at an alarming rate. I'm excited to see what else comes down the decomp/recomp pipeline.
Sorry buttercup, but we can't put pandora back in the box. We need ai models to shift over to HBM modules so they leave PC RAM alone, and then RAM will be cheap again.I'd rather have lower RAM and SSD prices myself.

Memory companies have all the incentive in the world to build out production capacity, the bigger problem here is that the memory market is cyclical and, up until 5 minutes ago in historical terms, sales were high whenever standards changed (in-between DDR/GDDR versions) and moderate when they stayed the same. Now all memory that’s manufactured is either already spoken for or sold instantly which is *unusual* for that market. This causes a cooling effect in regards to otherwise obvious and surefire investment as there’s no foreseeable timeline for how long the market will need to stabilise (if it will stabilise at all - this may be the new normal for all we know and the usual cyclical pattern will flatten out long-term). On one hand the more you produce the more you sell, on the other you don’t want to build new fabs that may end up being dormant in the future. They’re cautious to avoid over expansion which causes shortages. Market testing phases like this are a pain in the ass for all parties involved. I assure you, if memory companies had the capacity to make *more money* without the prospect of long term loss, they’d jump right to it.Sorry buttercup, but we can't put pandora back in the box. We need ai models to shift over to HBM modules so they leave PC RAM alone, and then RAM will be cheap again.


There’s a huge backlog you should check out!First Tempcast I tuned in to, and then I found out it is the penultimate of all?![]()