I was trying to play a game which I downloaded from Romnation on the NES using my Devcart. The game played perfectly on FCEUD but on the NES the graphics were completely off as if the mapper was accessing the wrong bank of CHR ROM. I know the particular ROM was from a battery back up MMC3 cart which I used-TKROM. Any ideas why the game would play perfectly on FCEUD but with the wrong graphics on the NES?
It would help to know what game you were trying to run...
Specifically, what does GoodNES call it?
I wrote the post and then couldn't remember the name. It is:
Radia Senki - Reimei Hen (J) [T-Eng1.0] on Romnation. When you play it is called Chronicles of the Radia War in the translation. In the header it is listed as having battery back-up WRAM so I tried it on a TKROM but the graphics were almost invisible as they were on a TSROM. Strangely on a TLROM with no extra RAM the graphics were more or less visible but too scrambled to play the game. I don't know how to use Goodnes although I tried it. Any instructions? Any ideas?
Are you certain that there is no physical problem with your devcart?
That is, does it play other games properly?
I found a simmalar problem playing real NES games, my NES was REALY beat up though so the problem was where the cart meets the console. Bad contacts, NES, he only console that will run with only most of the pins makeing contact with the cart hmmm...
why not try cleaning the contatcs wih metal cleaner?
I've played dozens of Rom's on each of my devcarts and they each have worked perfectly with compatible games. I have had problems with mainly translations of Japanese games. It seems that the code can work on FCEUD and Nintendulator but not on the NES. The orginal Japanese ROM's work fine but we can;t play them. As far as I know the various flavours of MMC3 carts are fairly compatible with the exception of CHR-RAM or WRAM. There is no problem with dirty contacts as I installed a new gold connector and have an official NES cleaning gadget.
Excuse me for duh-ing, but isn't it obvious then that the translation patch is broken? Don't trust emulators, even the very accurate ones; they're not 100% accurate.
Are there known bugs in
Nintendulator version 0.960? How about pre-0.965?
tepples wrote:
Are there known bugs in
Nintendulator version 0.960? How about pre-0.965?
I know for a fact that there are plenty of bugs in it, particularly in its PPU and APU emulation (evident by the fact that most of blargg's advanced tests fail in it), but some of those are exceedingly difficult to fix properly. I don't know of any bugs that would cause this particular game to fail, though.
I couldn't see why transltator would change the code of the game to use tricky frame IRQ timing issues or mid-scanline PPU writes or anything that still cause problems under Nintendulator.
Translations normally does just change the game script and tile graphics. Sometimes they change code too, but that's pretty rare. In most case it will just change the width of windows, or some interface stuff. If they happen to programm something wrong here, it will normally not work under nintendulator, unless they try something really tricky, but I really couldn't see why changing some small piece of sript could crash the game, if it works under nintendulator.
Are you sure you didn't try a NTSC game on your PAL NES or something ?
Bregalad wrote:
I really couldn't see why changing some small piece of sript could crash the game
Unless it runs into an edge case where the timing is related to the length of a line of script, unwittingly exceeding the limitation of the text engine.
Quietust: Could you document some of the more major bugs on the wiki?
Quietust wrote:
tepples wrote:
Are there known bugs in
Nintendulator version 0.960? How about pre-0.965?
I know for a fact that there are plenty of bugs in it, particularly in its PPU and APU emulation (evident by the fact that most of blargg's advanced tests fail in it), but some of those are exceedingly difficult to fix properly. I don't know of any bugs that would cause this particular game to fail, though.
What zip files should I download from blargg's site to see the tests that fail? What zip files should I download to get the most complete and up_to_date version of the APU tests? (Specifically, I'm confused as to whether "validated_apu" is up to date or out of date.)
As of version 1.29, Nestopia seems to pass all of the blargg_ppu_tests (unless my blargg_ppu_tests is out of date), branch_timing_tests, mmc3_irq_tests, sprite_hit_tests, and sprite_overflow_tests. That leaves sprite_hit_timing to be tested. Assuming that Nintendulator is comparable to or better than Nestopia in most of these areas, I'm guessing that most of the problems are in sprite_hit_timing...?
The problems are mainly in the APU tests and in some of the strict PPU timing, mainly due to the way I'm handling CPU/PPU/APU synchronization and also due to the fact that I haven't gotten around to fixing them to behave correctly.
Let me clarify my questions:
What's the proper set of APU tests I should download from blargg's page?
How does Nintendulator compare to Nestopia in these problem areas?
Quote:
What's the proper set of APU tests I should download from blargg's page?
the 11 tests from late july 2005.
Quote:
How does Nintendulator compare to Nestopia in these problem areas?
I don't think Quietust (or anyone else than the Nestopia author himself) knows the inner workings of that emulator to be able to clarify the answer more.
I know that it's the translation that is faulty. I'm just curious about why. I was thinking of trying to get it to work, although it's probably not worth the trouble.
Lloyd Gordon wrote:
I know that it's the translation that is faulty. I'm just curious about why. I was thinking of trying to get it to work, although it's probably not worth the trouble.
Um... maybe use Nintendulator's debugging features to find the code that needs to be modified?
I should have clarified my second question more: If Nestopia is passing some tests that Nintendulator is failing (and vice versa?), then where is Nintendulator more accurate than Nestopia and vice versa? Oops, don't answer that - it's just a rhetorical question...which
should be directed at all the Nestopia contributors...