nin-kuuku wrote:The toleration of NESdev is legendary.
It's debatable as to whether it's tolerance. I see this as a humongous time sink with little to no gain. The likelihood of the OP being able to accomplish what she/she wants is extremely slim at this point. I do not consider this topic "NESemdev" subject material, but rather "emulator support" for a very specific/niche emulator. My strong opinion is that this non-stop whinging across 2 (3?) separate threads should be redirected to the maintainers of the software and not this forum. There's an amusing catch to this however, and that piece of information I think is key:
The actual port/project for Mednafen on PS3 -- based on Mednafen 0.9.16-wip -- seems to be here: https://code.google.com/archive/p/mednafen-ps3/
The last issue reported was from October 2011. So, I imagine that project is dead.
There is a GitHub fork of the project here, done sometime in 2015, where they literally imported the Google Code project into GitHub, as well as all the Issues, but it does not appear to be maintained (i.e. it's just a GitHub import/copy): https://github.com/twinaphex/mednafen-ps3
So, the emulator hasn't been updated in almost 8 years. The latest version of Mednafen (not for PS3) is 1.22.1
. There was an announcement
regarding moving from 0.9.x to 1.x.x -- the biggest change probably being SDL2. The last 0.9.x version is 0.9.48 from September 2017.
The reason I mention newer Mednafen is that the mappers the OP wants added
(see bottom of post) -- 20 mappers, but 2 are duplicates, so 18 total; I'll provide a numerically sorted list below -- might have been added to newer Mednafen already. If that's the case, they might be able to be backported to this 0.9.16-wip PS3 project, but the effort involved is unknown. Let's try to figure that out:
Sadly, for whatever reason, the Mednafen project does not use a public VCS like GitHub or BitBucket or GitLab, so you can't easily browse the source without downloading it manually. The documentation of what mappers are supported is here, but semi-implied
The mapper list the OP wants:
Code: Select all
91 -- not listed
176 -- not listed
237 -- not listed
255 -- not listed
256 -- iNES 2.0 only, not listed
274 -- iNES 2.0 only, not listed
281 -- iNES 2.0 only, not listed
282 -- iNES 2.0 only, not listed
295 -- iNES 2.0 only, not listed
296 -- iNES 2.0 only, not listed
351 -- iNES 2.0 only, not listed
353 -- iNES 2.0 only, not listed
356 -- iNES 2.0 only, not listed
358 -- iNES 2.0 only, not listed
361 -- iNES 2.0 only, not listed
362 -- iNES 2.0 only, not listed
363 -- iNES 2.0 only, not listed
364 -- iNES 2.0 only, not listed
So, no, Mednafen does not seem to support these mappers.
My advice at this point: the OP should make an account on the Mednafen forum and ask the developers to consider adding iNES 2.0 header support, followed by adding support for those mappers. If the authors/maintainers of Mednafen can do that -- people who are familiar with the code already -- then the code could be backported with less effort. I think that's a lot more feasible than trying to have someone here do it themselves. Why is there no Mednafen forum thread asking for these mappers?
I should add that asking for 18 mappers is pretty outlandish -- I would go as far as to say rude. Mature adults don't normally do this. It's not just like one mapper that's slightly different than some other mapper (though I haven't looked at all of them), it's 18 different mappers, plus adding support for a newer file format that's nuances in itself.
I really think what we have here is a case of a whinging kid with a PS3 and no programming experience that wants a slew of these really obscure/niche Chinese bootleg games running on a specific emulator. Here's what really baffles my mind: a person named "Deviljin", the -jin suffix implying Japanese, who claims to be Czech (we aren't sure), who wants 18 different mappers for obscure Chinese bootlegs added to a ported emulator that hasn't been updated in 8 years. I literally cannot wrap my brain around this. Every "bullshit" Klaxxon I have is firing on every level. I'm not the paranoid/tin-foil-hat type, but strongly suspect this might be a case of someone wanting all of these mappers added to this emulator so that the code/etc. can be taken, put into a commercial product that's being sold somewhere, and someone making money off of it. I've seen this exact thing happen in the even more niche world of embedded systems/routers, where Chinese folks have appeared on forums demanding (read: pushy, backed by terse answers, usually 1 or 2 lines at most) support/features for something only to have people write the code which they then take and use in a product that they sell. It was enough that one firmware maintainer actually began "closing off" WIP source code and only updating the public repo occasionally.
I hope that paraphrased version of the situation puts all of this into perspective. I really think all this time/effort is for little to no gain.