I just saw this video about how a team of coders used some special techniques and make a really nice looking game fit within a very small space 96 kilobytes. I was wondering, could similar methods also be used for making NES games.
https://www.youtube.com/watch?v=bD1wWY1YD-M
Like for instance, they used algorithms to draw the graphics so that they didn't have to store textures. It's a pretty interesting video.
96kb FPS
Moderator: Moderators
Re: 96kb FPS
I remember trying this game and was amazed by it. Never dug into how it's done (so thanks for the video!) but I figured that (nearly) everything was procedurally generated.
My virus scanner later treated the executable as a threat (possibly because it did a lot of hacky stuff at low level) and deleted it automatically. I just didn't care as I was disgusted by FPS and quit playing them since around the turn of the millenium.
My virus scanner later treated the executable as a threat (possibly because it did a lot of hacky stuff at low level) and deleted it automatically. I just didn't care as I was disgusted by FPS and quit playing them since around the turn of the millenium.
Re: 96kb FPS
Not really. These very tiny demoscene products are relying on the other side of space-vs-time tradeoffs: a fast CPU, and lots of space to store the results of dynamic generation.. The NES is both slow and has a paucity of RAM, so dynamic generation of anything noticeably more complex than, say, 2600 Pitfall's LFSR-based level design is going to be difficult.
You might look at the small demos for all legacy machines to see what's reasonably in scope. The favorites on Pouet (in terms of "most thumbs up" which is roughly equal parts "popularity" and "interesting"), filtered for older devices and demos that are 32KB or smaller, comes up with a bunch for the comparatively beefy Amiga AGA, and ... a bunch of others that are probably actually a reasonably proxy for what's doable on the NES.
More reading: search for "bytebeat"
You might look at the small demos for all legacy machines to see what's reasonably in scope. The favorites on Pouet (in terms of "most thumbs up" which is roughly equal parts "popularity" and "interesting"), filtered for older devices and demos that are 32KB or smaller, comes up with a bunch for the comparatively beefy Amiga AGA, and ... a bunch of others that are probably actually a reasonably proxy for what's doable on the NES.
More reading: search for "bytebeat"
Re: 96kb FPS
Sure, but it would take an eternity in loading times. Even that had long loading times on a PC.
It would also require a board with tons of banked CHR RAM and RAM, otherwise you'd get those loading times every level/whatever.
A roughly comparable scenario is very advanced compression. Someone used rABS (1-bit asymmetric numerical coding) to get very high compression for some 4kb demo on a 6502 IIRC, but it had a loading time like a minute.
It would also require a board with tons of banked CHR RAM and RAM, otherwise you'd get those loading times every level/whatever.
A roughly comparable scenario is very advanced compression. Someone used rABS (1-bit asymmetric numerical coding) to get very high compression for some 4kb demo on a 6502 IIRC, but it had a loading time like a minute.
Re: 96kb FPS
But what about trying to do something like this with the N8 everdrive pro with its cyclone 4 FPGA and extra RAM.
Re: 96kb FPS
... You already asked that question. viewtopic.php?t=21800
Re: 96kb FPS
Plus that doesn't make any sense: if you're targeting the Everdrive, you can already access gigabytes.
Re: 96kb FPS
How convenient is it for a program running on the EverDrive N8 or EverDrive N8 Pro to access data outside the ROM and save game, even if restricted to the same directory? I ask because for comparison, on the Game Boy, a means hasn't been found for a ROM running on an EverDrive GB X3/X5 to read and write other files, and this has caused inconvenience for a particular Super Game Boy-related project.
Re: 96kb FPS
I haven't looked. Ed64 has a SD card API, N8 (/pro) likely has something similar. Dig around in krikzz.com/pub.
edit: Remembered the Mega Everdrive Pro's video player also uses a similar API to access huge files.
edit: Remembered the Mega Everdrive Pro's video player also uses a similar API to access huge files.