I made a simple ROM that just displays a .nam file on screen. I tested it out on a few emulators, and it looked just like I wanted it to. However, I tested it out in NESticle just for kicks, and I noticed that the colors were horrible. I thought that when I display that image in a real game, I really don't want it to look like that. So I just need to make sure of something. Since Nintendulator is a really really accurate emulator, is it also accurate in terms of color? I don't have the proper things to test it on the real system. If it is, then I'm safe. If they look like NESticle's, then I'm screwed.
with the NTSC emulator rendering it should be pretty accurate I guess 
Nesticle was good for its time but sucks now.
I second dXtr's motion to try your screen mock-ups on an emulator that performs NTSC simulation, such as Nestopia. Also remember that pixels on an NES connected to a TV are not square; instead, NTSC NES images are stretched horizontally by a factor very close to 8/7, which Nintendulator did not emulate last time I checked.
I second dXtr's motion to try your screen mock-ups on an emulator that performs NTSC simulation, such as Nestopia. Also remember that pixels on an NES connected to a TV are not square; instead, NTSC NES images are stretched horizontally by a factor very close to 8/7, which Nintendulator did not emulate last time I checked.
Yeah, Nesticle's colors are not very good. The Color $11 appears too bright, and it just is too much of a step up from $01.
I noticed that 2x2 metatiles are not square on a television. Nintendulator does not emulate this. That's just because the TV's pixel ratio is 3:4 when what's being displayed on screen is supposed to be 7:8(224:256), right?
I noticed that 2x2 metatiles are not square on a television. Nintendulator does not emulate this. That's just because the TV's pixel ratio is 3:4 when what's being displayed on screen is supposed to be 7:8(224:256), right?
You can load this into Nintendulator for a pretty good representation of the NTSC palette (ripped from one of blargg's old topics).
I wouldn't recommend using just a palette to see how it would look, since there are lots of color mixing effects you get with NTSC composite video, some making things look awful. Some emulator authors aren't interested in what happens to the pixels once they get converted into composite video, so you have to use a different emulator like Nestopia.
No, the TV screen is 4:3, but the pixels on it depend on the system generating them. To summarize, an NTSC NES pixel is about 15% wider than it is tall, and a PAL NES pixel is about 39% wider than it is tall (full details).
Quote:
That's just because the TV's pixel ratio is 3:4 when what's being displayed on screen is supposed to be 7:8(224:256), right?
No, the TV screen is 4:3, but the pixels on it depend on the system generating them. To summarize, an NTSC NES pixel is about 15% wider than it is tall, and a PAL NES pixel is about 39% wider than it is tall (full details).
I had the ratios backwards, sorry. And even that isn't correct. Oh well.
So let me ask this, even though it's slightly unrelated. It says that there are 282 pixels horizontally per scanline, 256 are on screen. Would that be the reason for no sprite wrap around?
So let me ask this, even though it's slightly unrelated. It says that there are 282 pixels horizontally per scanline, 256 are on screen. Would that be the reason for no sprite wrap around?
Quote:
It says that there are 282 pixels horizontally per scanline, 256 are on screen. Would that be the reason for no sprite wrap around?
No. The way you described it a few messages ago for lack of vertical wrapping sounded spot-on, and would be the same reason for lack of horizontal wrapping I'd think.