RESIDENT EVIL 2 N64 ROM PC
RESIDENT EVIL 2 N64 ROM TV

For one, they tend to compress things, just as a lot of GBA games do. The rest of the CD was used for the soundtrack.ДЄ typical N64 game is different. The actual game was small enough to fit onto a single floppy disk (so around 1MB), and was entirely loaded into the PS1's memory when you started the game. Plenty of space to waste!ДЄ good example is Ridge Racer. No point using compression, no point trying to do a cutscene in-game when you could just use an FMV instead, no point trying to generate music when you can just play a recording of it. Most Playstation games used lots of video sequences (which are huge), streaming XA audio (which is also huge), some of them even used uncompressed WAV files or CD Audio (again, huge), and lots of them had sampled voices, or whatever. The largest ROM size the N64 was designed to deal with was 32MB, although larger games were made (like Resident Evil 2, which was 64MB).ДЄ lot of Playstation games were only that big because they could be, not because they needed to be. The N64 used cartridges containing ROM chips, which become exponentially more expensive as they become larger. It was kinda hackish, but it works.Because a Playstation uses CDs, which have a 700MB capacity. OpenGL could not do it, but glide wrapper authors also manged to solve that problem. I could load depth image as 16bit RGB texture, render it to a texture buffer and then use that buffer as depth buffer, exactly as N64 does. Copy values to depth buffer was relatively easy with glide3x API: glide3x depth buffer format is 16bit integer, as for N64. Glide64 was the first plugin, where the problem was solved.

RESIDENT EVIL 2 N64 ROM PC

To emulate it on PC hardware the depth buffer data must be converted into format of PC depth buffer and copied into PC card depth buffer.' That depth buffer data is copied into RDRAM and each frame it is rendered as 16bit texture into a color buffer which then is used as the depth buffer. Instead, the game ROM contains pre-rendered depth buffer data for each background. But the game does not render auxiliary 3D geometry to make depth buffer. In Resident Evil 2 all screens are 3D models over 2D backgrounds. Then the background covers this scene and 3D models rendered over the background are cut by depth buffer when the models are behind the original polygonal objects. Thus, the scene gets correct depth buffer. Zelda OOT solves that problem by rendering auxiliary 3D scene with plain shaded polygonal objects, corresponding to the objects on the background. 2D background has no depth, and depth buffer by itself can't help. For fully 3D scene problem 'object behind other object' is usually solved by depth buffer. Some of objects on the background can be visually 'closer' to user than 3D model, that is part of the 3D model is 'behind' that object and that part must not be drawn. 'Few games use scenes consisting of 3D models moving over 2D background. I already described the problem hereand here, so I cite myself: For LLE we still need somehow resize buffer texture. Unfortunately, it works only for HLE, because BgCopy is high-level command.

I used that hack in Glide64 and I still don't know better solution. It is no problem to create 512x287 texture and render it to frame buffer. Why it is a problem for hardware graphics plugin? The plugin executes BgCopy command, which loads 512x287 image. Now buffer has correct proportions, and 3D models can be rendered over. In fact BgCopy works as memcpy to copy background content from one address in RDRAM to another.В When buffer copy completed, the game allocates buffer with the same origin, but with width 448. The game allocates color buffer with width 512 and renders background with BgCopy command into it. To optimize background load and rendering on N64 hardware, background loaded as image with width 512.

The first problem, which hardware plugin faces in this game is the way how background loaded to frame buffer.

RESIDENT EVIL 2 N64 ROM TV

Video interface stretches image to TV resolution 640x480. Frame buffer size corresponds to background size. Background size may vary from place to place: someplace it isВ 436x384, someplaceВ 448x328 and so on. What makes the game hard to emulate? As you know, the game consists of static 2D backgrounds with 3D models moving over. Later necessary functionality was added to glide wrapper, so you can run the game on any modern PC card. Abilities of 3dfx graphics card allowed me to obtain pretty good result: the game was fully playable on Voodoo4/5 with some minor glitches.

I spent lots of time on this game when I worked on Glide64 plugin. While the game uses standard ucode (or slight modification of standard one), it uses few non-standard tricks, which are hard to reproduce on PC hardware. Resident Evil 2 for Nintendo 64 is hard to emulate game.

Resident evil 2 n64 rom