nesdev.com

nocash wrote: ↑

Mon Jan 13, 2020 8:40 pm

On the stonelands picture... I am lost... what are floors and what are walls?

These are free assets, they are whatever you make them out to be haha.

One of the things we had to do as kids was mess with the VHold knob on the back of the TV when playing games to constantly hide the distractions. That sure sounds to me like your TV was miscalibrated. Maybe someone had screwed around with the service menu at some point in the past, or if it was a T...

I mean when a new tile appears at the left or right of the screen, it just appears, giving a weird jaggedness on the edges every 8 pixels moved. This is because the 3d area only accounts for 32 tiles. By "predicting" the future, you can see passed the 32 tile screen limit, there by blocks at the edg...

How much overscan gets applied is dependent on the TV. Shipped CRT SDTVs never reduced overscan to more than 224 scanlines. However, later TVs did move which 224 scanlines were shown. Earlier TVs (70s? 60s?) displayed a good deal less than 224 scanlines. Some TVs certainly did go beyond 224 scanlin...

All I am saying, is NES renders at 256x240, not 224, to fill a US 60hz screen. How much overscan gets applied is dependent on the TV. Some CRTs had no overscan whatsoever (Which made broadcasting television very annoying because you could see the encoded information at the bottom) My point was reall...

No, concealing would depend on your TV's overscan. The hardware still renders into a 256x240 buffer, so it was up to the developer to decide whether or not to render black tiles (or even garbage tiles) to compensate for the overscan, or to just draw the entire scene at the 240 and use a safe zone to...

I have a question peeking my curiousity, have you though about trying to "predict" the future to allow for smoother scrolling?

Native SDTV resolution is 4:3. The NES and SNES (and sometimes the Genesis and TG16) draw 256x224 pixels to fill a US 60Hz screen. But 256÷224 isn't 4÷3, so every pixel is a little wide. At the NES's native pixel aspect (which is 8:7), you'd need 14:9 in source pixels, or 256x165. Or, since it's fa...

I assume the gun just has a less light tolerance filter, where the original was specifically looking for 15hz light, the Hyperkin one just looks for light (meaning lightbulb trick revival) A friend and myself played around with tweaking the original zapper to remove the filter, but we could not come...

Does your Windows/Firewall/Antivirus have a security setting blocking unknown dlls?

I agree with knight0fdragon. For changes like that, it might end up cheaper to rewrite the entire game. Compared to tracking down and fixing a bug in a rom??! I can't think of any situation where that might be true. When the bug is the game's engine itself, reverse engineering the engine from byte ...

Is your windows 7 64 bit? You are probably using the 64 bit lua dll when you need the 32 bit one for windows XP

A lot of those games have tiny fixes though. I have played the Zelda one, and it isnt as simple as "oh, they did not retain the a register here" If you know something about 6502, run it though a disassembler and just try to see if you can understand what goes on lol.

You are better off just rewriting the game from the ground up. The Chinese port is riddled with bugs and the text is in Chinese as well as not related to the story,

Saying "It takes 50 [cycles per second] to complete a second" I know what hertz means, I am not trying to say 50cycles/second = 1 second, I am saying for the code to recognize a second happened, 50 cycles per that second were counted. with less than, the system is doing less counts per second than ...