Talk:Mapper

Allocations

By FCEUX 2.2.1, they allocated mapper 160 to describe an undersize NINA-003-006 board (32k PRG, 16k CHR). This seems superfluous. They also allocated mapper 181 to describe another board like iNES Mapper 185 that didn't fit with the existing heuristic. It would be nice to take the opportunity to promote NES 2.0 submappers#iNES Mapper 185. —Lidnariq (talk) 21:41, 23 June 2013 (MDT)

Also, wasn't 256-511 supposed to be for developers or debugging use? I need to request a reserved number for future hardware designs. I'll probably go find the IRC channel for that.  ;) BTW: The documentation for NES 2.0 header format has different allocation planes. It's best to fix this BEFORE someone goes and tries to update/make any mapper code libraries. Again, going to bring this to attention of mods in chat. alphamule (talk) 13:51, 29 August 2014 (MDT)

Rule of thumb: once you have final hardware, then you can get a mapper #. Before then, pick something arbitrary and otherwise unusable such as m100, or use UNIF. There's more theoretical possible mappers than there will ever be space for. —Lidnariq (talk) 14:40, 29 August 2014 (MDT)

In the plan as described by KH in the original NES 2.0 doc, 256-511 were to be filled after 0-255 had been filled. Because of the continuing pace of new Chinese discoveries since then, a revised, Unicode-inspired plan splits this into 256-511 for western games and 512-767 for eastern games. Presently, 3840-4095 are reserved for private use, as well as 100 and 248. --Tepples (talk) 15:34, 29 August 2014 (MDT)

Cool, thanks for the info! This should be helpful to future readers, as well. I found out that blargg is working on a similar project so I'm waiting for a PM response. I also need to get a working NES to test the hardware out on. alphamule (talk) 07:42, 30 August 2014 (MDT)

unicode joke terms

Might we rename "Supplementary Multilingual Plane" and "Supplementary Ideographic Plane"? Jokes about the unicode standard are rather obscure, and don't help anyone understand what these categories are for. - Rainwarrior (talk) 16:33, 16 April 2015 (MDT)

Jokes about unicode ?! I would never have guessed that was some. Anyways, jokes do not belong to here.Bregalad (talk) 04:12, 17 April 2015 (MDT)

I found them funny, but it was a laugh and an eye-roll. Myask (talk) 23:55, 20 April 2015 (MDT)

So, the second question to ask is what to name them. From what I can tell, the two planes are meant to distinguish mappers for new games (plane 1) from mappers that are used for illegal compilations/reproductions/modifications (plane 2). Presumably the idea is that emulator authors may wish to de-prioritize pirate mappers that don't contribute new games to the library. There's a bit about "east asia" in the current description which seems unnecessary to me; shouldn't pirate carts from any region be included here? (Russian? Brazilian?) China probably has the most prolific market for it, sure, but I don't think that needs to be part of the plane's definition. My suggestion:

Plane 0: iNES 1

• Still has a few slots open for new homebrew?
• Put new pirate mappers in plane 2, not here.

Plane 1: Homebrew

• New games developed for newly created mappers
• Undiscovered commercial-era mappers (if any exist)

Plane 2: Pirate

• Multicarts used to illegally compile existing games
• Modifications and hacks of existing games

- Rainwarrior (talk) 10:06, 17 April 2015 (MDT)

True, title hacks, graphics hacks, pure mapper hacks, and multicarts "that don't contribute new games to the library." But not all games made for the East Asian market fall into these categories. Some are ports from a more powerful system, such as Final Fantasy VII, Pokemon, and Somari. Some are original games (ab)using others' characters, such as Kart Fighter and various Pokemon and Harry Potter-themed games. But what makes East Asian games stand out from games for other markets is provision in the mapper for writing systems with more than a hundred characters, which needs either CHR RAM, ExGrafix, or precomposed phrases. (See CHR ROM vs. CHR RAM.) Games for Russian and Brazilian markets can get away with assuming a 1:1 relationship among tiles, glyphs, and characters. Besides, with the deprecation of UNIF, we need to allocate mappers for a bunch of CaH4e3 dumps, and separating out the Chinese stuff will help keep that effort from colliding with homebrew too much. So I've renamed the planes to "Plane 1" and "Plane 2" but left the East Asian wording. --Tepples (talk) 17:45, 19 April 2015 (MDT)

Okay, so you're not trying to separate pirate/multicart from homebrew/legitimate? Your goal is just to separate them by language/region? The language in place right now doesn't seem to mention an appropriate place for new pirate stuff, unless it already falls in the East-Asian category. You should probably write a description that designates that material to one plane or another, so that it's clear where to allocate. Of course, nobody has wanted to allocate anything yet, except zzo38 who appears to have pre-allocated 380, despite not having released any ROMs for it? I'm never going to be the maintainer of pirate mapper allocation, so I don't feel very strongly about how they are specifically organized. I just found the names borrowed from unicode the opposite of helpful when trying to figure out what the planes were being designated for. - Rainwarrior (talk) 21:09, 20 April 2015 (MDT)

n\T icon

The n\T icon (File:Mfr icon Namco Tengen.png) is a bit harder to read than the ir\AVE icon because both have the same (transparent) background and similar (reddish) colors, so the strokes of the twosort of blend into each other. NesCartDB lists 20 games developed or published by Namco and only three (Fantasy Zone, Gauntlet, and Indy 2) that Namco did not develop or publish. --Tepples (talk) 08:00, 11 June 2015 (MDT)

Not sure how you're getting only three non-Namco for mapper 206; plus Tengen Gauntlet is a pretty high-profile game. I see some Data East games in there, too! (Perhaps you missed the pagination?) Myask (talk) 19:32, 11 June 2015 (MDT)

Most of the rest were renamed and/or ported by Tengen for the US Market, but are originally made by Namco. (AFAICT, the entire reason that Tengen used the MIMIC-1 is because they were importing Namco games to the US market to get around Nintendo's limitation on a maximum of 6 (or was it lower?) games per publisher per year. —Lidnariq (talk) 19:57, 11 June 2015 (MDT)

Okay, that knocks out RBI and Ring King. And Pac-Mania is so obviously a Namco-developed game it hurts, but doesn't seem to have had a Famicom release? Super Sprint and Toobin', though... Still, the icons are for manufacturers (that is, publishers), and the Tengen boards are different, so does it really matter for our "whose-mapper-is-this" if someone was pulling an ljn trick? Myask (talk) 21:14, 11 June 2015 (MDT)

Why some mappers are assigned to "Rare, Ltd."'s logo

TQROM board's mapper was only used by Rare, Ltd. but uses a chip from Nintendo, the MMC3. It could be labelled Nintendo.

Mapper #7 was used most often by Rare, Ltd., but not exclusively. Solstice was not developed by Rare, Ltd. but uses mapper #7. Also, the PCB and carts were made by Nintendo, and contains no chip developed by Rare, Ltd, not even the PCB. Other discrete logic mappers which were used by various 3rd party developers but licenced by Nintendo are tagged Nintendo, there is no real reason mapper #7 would escape that rule.

It's true there is no mapper #7 games that was developed by Nintendo, however, this is true for many other mappers as well, such as the MMC5.Bregalad (talk) 03:38, 12 June 2015 (MDT)

I don't think it's reasonable to expect perfect accuracy when you reduce a mapper to a single 16x16 image. There's no good scheme for choosing that will be entirely consistent. It's always going to be subjective. The point of the images is just to make it easy to spot which mapper is which, so we're not just looking at some monolithic block of buttons. For that reason, I'd rather see a "mostly Rare" mapper with a Rare icon than have yet another Nintendo icon in there, but that's just my subjective opinion. - Rainwarrior (talk) 14:08, 12 June 2015 (MDT)

For the same reasons, I think Image:Mfr icon Namco Tengen.png is pushing the limits of utility for these icons, and I'd really hate to see someone try to stuff 3 companies into an icon. Don't try to cram too much information into these things. It's supposed to be easy to read at a glance, not tell you 20 years of game development history. - Rainwarrior (talk) 14:15, 12 June 2015 (MDT)

Also, the saturated green of the current icon really stands out from the others in an ugly way (it's very harsh against the white background). Personally I'd go with the 16/32-bit era logo with the gold rimmed blue badge, but again this is a rather subjective suggestion. (I don't think they had a consistent logo before then?) - Rainwarrior (talk) 15:30, 12 June 2015 (MDT)

Agreed. I intended the Nintendo icon to be used where no third party developer or publisher has a majority. Of the 34 unique games on mapper 7, 26 were either developed or ported by Rare, and an additional four were developed or ported by Zippo Games, which appears to also be Rare in the sense that Ultra is Konami. Hence Ꝛ on 7. Namco likewise has a stake in a supermajority of 206, which is why I think 206 deserves the Namco n. --Tepples (talk) 19:04, 12 June 2015 (MDT)

It's no problem as long as the way icons are chooses was never meant to be consistent. I was just pointing to an inconsistency.Bregalad (talk) 12:51, 14 June 2015 (MDT)

32x32 upscaling

I'd like to offer a guideline for upscaling mapper images 32x32. The vast majority display resolution is 16x16, and for that reason all of these images should be optimized for 16x16 first. What this means is that pixel art should be 16x16 and nearest-neighbour rescaled, creating the optimal image at 16x16 and defeating unpleasant linear resampling at 32x32. Do not upscale pixel art by adding smoother edges, etc, as this reduces legibility when downscaled to 16x16. For things that are vector art, text that is already anti-aliased, etc. feel free to take advantage of the full detail level at 32x32. Just remember the most important thing is legibility at 16x16. After doing a quick pass over it, I think everything we've got now is OK. - Rainwarrior (talk) 22:17, 12 June 2015 (MDT)

A newbie-friendly page introduction

As a beginner I found this page to be confusing and unhelpful. The opening paragraphs are overly technical and contain too many details and acronyms for a beginner to grok. The information contained may be factually true and helpful to some, but I'd really like to see a plain-English introduction added in addition to what's already on the page. Something like:

Mapper

NES games come in cartridges, and inside of those cartridges are various circuits and hardware. Different games use different circuits and hardware, and the configuration and capabilities of such cartridges is called their mapper. Mappers were used to extend the system and bypass its limitations, such as by adding RAM to the cartridge or even extra sound channels. More commonly though, mappers were used to allow games larger than 32K to be made.

Example games and their mappers:

• Contra uses a mapper called UNROM, providing it with 128K of PRG ROM space.
• Castlevania 3 uses a mapper called MMC5 offering additional sound channels (on Famicom systems only).
• Bible Adventures uses the "Color Dreams" mapper which contains CIC-defeating circuitry.
• Super Mario Bros. uses the simplest mapper: NROM, which contains 32K of PRG ROM and 8K of CHR ROM. Many early NES games and modern homebrew games use the NROM mapper.

Pubby (talk) 11:21, 11 May 2016 (MDT)

I wanted it to provide true and complete information. I may be in the habit of using technical vocabulary. Which acronyms are newbie-unfriendly besides PRG and CHR? CIRAM? (also, Famicom version of Castlevania 3, 悪魔城伝説, is on VRC6, not MMC5. Also, on some metrics, onechip mapper is simpler than NROM.) Myask (talk) 11:17, 10 July 2017 (MDT)

Mapper Grid

This causes this page to choke when you load it. Should it really be on the "explaining mapper" page?Myask (talk) 11:28, 10 July 2017 (MDT)

Would it help if the images were 1/4 the size, at the original 16x16 instead of the 32x32 they were "upgraded" to? I never liked the upscale effort, since all of them are meant to be displayed at 16x16 on a normal screen anyway. - Rainwarrior (talk) 15:58, 10 July 2017 (MDT)

Then again, after PNG compression they seem to be mostly he same size anyway. I don't know what exactly is "choking" in this case; bandwidth? Number of image fetch requests? Would ditching the company specific icons help, alternatively? - Rainwarrior (talk) 16:03, 10 July 2017 (MDT)

The page serves the 16x16 downsampled version in the first place, and uses javascript to replace them with the high-resolution version if appropriate. That said ... I really just kicked off the upsampling project to get rid of the of the things with baked-in chroma error ("subpixel AA"). —Lidnariq (talk) 16:48, 10 July 2017 (MDT)

It's the table, I expect. I'm not sure what precisely makes it that a preview of that is taking "Parser profiling data: CPU time usage 1.033 seconds Real time usage 1.081 seconds" whereas this is only 0.003s. (Server-side, not client-side.) Myask (talk) 16:39, 10 July 2017 (MDT)

That's pretty clearly caching the resultant HTML for subsequent servings. Quickly experimenting: neither changing the specified rescale size (|16px) nor changing the specific image served (changing them all to "Generic") sped things up at all. Only removing the ≈1000-images-are-equivalent-to-transclusions sped up preview. Regardless, due to caching, is this even worth caring about? —Lidnariq (talk) 16:48, 10 July 2017 (MDT)

pirate/pirate MMC3

The specific bootleg company logos have replaced this information. I'm uncertain if this is a good thing. Myask (talk) 11:28, 10 July 2017 (MDT)

I'm really not clear how the "pirate/pirate MMC3" grouping was ever useful. —Lidnariq (talk) 16:48, 10 July 2017 (MDT)

mappers 256-9

"have been tentatively allocated" per rainwarrior's edit…citation? I looked at FCEUX's source and couldn't find it. https://sourceforge.net/p/fceultra/code/3372/tree/fceu/trunk/src/ines.cpp#l715 Nvm, found it. Annoyingly, incorrectly, their source code calls NES 2.0 "ines 2.0"… Myask (talk) 11:28, 10 July 2017 (MDT)

I did not make that edit, lidnariq was responsible: http://wiki.nesdev.org/w/index.php?title=Mapper&diff=11931&oldid=11727 - Rainwarrior (talk) 15:54, 10 July 2017 (MDT)

Whoops. You're right, of course. Myask (talk) 16:39, 10 July 2017 (MDT)