byuu's message board

Given how buggy the first releases of FFVI were, I imagine there's a bunch of code that was put in that never actually gets called because some other piece of code uses an unconditional branch instead of a conditional one, or whatever.

What if it's graphics data AND code? Admittedly, not LIKELY on the Super Nintendo, but it's done in Atari VCS games.

I've done this before on SNES for placeholder graphics while working on a demonstration, so it's not unheard of on the platform

For this post we can see that Sora has no assembly experience. He still thinks he can identify code and data statically.

But I think he even knows what "statically" means in this context.



By Sora's logic, to build an atomic bomb you need to put uranium in a box, throw it out of a plane and the bomb explodes.

Just express the movement and velocity of each atom in the bomb as a mathematical equation, evaluate them all, and then you can tell which buildings need to be destroyed, so you can go and punch them down at your leisure.

Very OT, but, I suddenly want to make a game for the asspull.

Wait a few days. I'm hoping to reimplement hardware sprites and bitmap mode. Then there's massaging crt0 into allowing initialized variables, and the rest of the BIOS functions such as ReadKey and ReadLine. Also, WriteString's newline handler seems to be bugged. Then I'll look into screen mode 3, which is tiled. Note that all screen modes allow hardware sprites.

Until then, you can already check the KeyIn register by hand, poke characters onto the screen, and redefine the textmode font. Which might suffice for certain games.

Oh, and there's a bunch of Thumb instructions still unimplemented. Any takers?

Wow, Sora's topic about compression was epic too, but the topic was closed.

Sora wrote an imense amount of (incomprehensible) text.

http://forum.codecall.net/topic/77970-looking-for-c-programmer-to-assist-in-developing-a-compression-algorithm/

... How the hell did this thread go on for ~370 posts?

Because there's no way to prove to a persistent delusional idiot that they don't have some secret knowledge that would completely revolutionize the world if only they could convince the world of their correctness. It's like the free energy crowd that loads up on a ton of actual terminology so they can sound like they might know what they're talking about, but upon further inspection, are just talking out their ass and using that technical terminology incorrectly.

However, people who do know what they're talking about feel compelled to engage those people in conversation, first to give them a fair chance to explain their ideas just in case they're on to something new but don't know how to express it, and then further to attempt to show them why they're wrong.

Post an insightful, 4000-word post correctly explaining something in great detail on any major website related to said post. You'll get no responses.

Make a minor mistake, and you'll get 100+ replies correcting you.

People love to correct others.

That, and probably 20% of the 370 posts are people asking how this thread could be so long, and others explaining their theories as to how.

Also, math.

You don't say.

Mednafen needs a motherboard file. This discussion is moot.