nesdev.org

Just trying to figure out what nestopia could be doing wrong here. In the Japanese version of Burai Fighter the status bar at the bottom of the screen is as it should be. On Burai Fighter american version you get this:



Also on ninja gaiden (u) you also have a chunk of the moon missing in the first cutscene while in the japanese version you do not. Any chance these two games with issues could be related. Weird how the japanese versions work great and the us not so great. I backtracked through all the nestopia releases i could and NOT ONE has ever played burai fighter correctly with the whole status bar showing. Seems like something is clipping the edges off.

Maybe some other devs can possibly shed some light on this issue. I also wonder if this has anything to do with some of the timer being clipped on hard drivin as well.

*Spitfire_NES* wrote:Just trying to figure out what nestopia could be doing wrong here. In the Japanese version of Burai Fighter the status bar at the bottom of the screen is as it should be. On Burai Fighter american version you get this:

9a35d62c-f9ee-11e3-8c2f-025d77e34ca7.png

Also on ninja gaiden (u) you also have a chunk of the moon missing in the first cutscene while in the japanese version you do not. Any chance these two games with issues could be related. Weird how the japanese versions work great and the us not so great. I backtracked through all the nestopia releases i could and NOT ONE has ever played burai fighter correctly with the whole status bar showing. Seems like something is clipping the edges off.

Maybe some other devs can possibly shed some light on this issue. I also wonder if this has anything to do with some of the timer being clipped on hard drivin as well.

...........You are joepogo ?

Compare fceumm and fceux the ppu....

*Spitfire_NES* wrote:Just trying to figure out what nestopia could be doing wrong here. In the Japanese version of Burai Fighter the status bar at the bottom of the screen is as it should be. On Burai Fighter american version you get this:

9a35d62c-f9ee-11e3-8c2f-025d77e34ca7.png

Looks like the 2nd scanline IRQ is firing too early. Maybe the game depends on a specific MMC3 IRQ behavior? Just a random guess. puNES 0.63 has the exact same problem

Also on ninja gaiden (u) you also have a chunk of the moon missing in the first cutscene while in the japanese version you do not. Any chance these two games with issues could be related. Weird how the japanese versions work great and the us not so great. I backtracked through all the nestopia releases i could and NOT ONE has ever played burai fighter correctly with the whole status bar showing. Seems like something is clipping the edges off.

I doubt this is related to the first issue. In this case, a single byte in the attribute table gets messed up for some reason. Same bug shows up in Nintendulator, with slightly different results. The game may be doing something unorthodox, like writing to PPU with rendering on, causing each emulator to interpret the situation slightly differently.

thefox wrote:

*Spitfire_NES* wrote:Just trying to figure out what nestopia could be doing wrong here. In the Japanese version of Burai Fighter the status bar at the bottom of the screen is as it should be. On Burai Fighter american version you get this:

9a35d62c-f9ee-11e3-8c2f-025d77e34ca7.png

Looks like the 2nd scanline IRQ is firing too early. Maybe the game depends on a specific MMC3 IRQ behavior? Just a random guess. puNES 0.63 has the exact same problem

Also on ninja gaiden (u) you also have a chunk of the moon missing in the first cutscene while in the japanese version you do not. Any chance these two games with issues could be related. Weird how the japanese versions work great and the us not so great. I backtracked through all the nestopia releases i could and NOT ONE has ever played burai fighter correctly with the whole status bar showing. Seems like something is clipping the edges off.

I doubt this is related to the first issue. In this case, a single byte in the attribute table gets messed up for some reason. Same bug shows up in Nintendulator, with slightly different results. The game may be doing something unorthodox, like writing to PPU with rendering on, causing each emulator to interpret the situation slightly differently.

Thanks fox for answering. Please excuse my noobness, but does it have anything to do with this at least regarding the burai figher issue? I think this discovery will fix mickeys safari in letterland no doubt as well with the status bar being jumpy.

viewtopic.php?f=3&t=10439

*Spitfire_NES* wrote:Thanks fox for answering. Please excuse my noobness, but does it have anything to do with this at least regarding the burai figher issue? I think this discovery will fix mickeys safari in letterland no doubt as well with the status bar being jumpy.

No idea. Every emulator I have tried has the same problem with Mickey (puNES, Nintendulator, Nestopia).

sorry i did not clarify what i was asking better. I guess what i mean is regarding the link i posted, is this something that will benefit the burai fighter issue? Seems like james found undocumented behavior but maybe that is only regarding the rambo mapper. Nestopia is hard to navigate through for me, but maybe the i need to be looking at the mmc3 code, since i think burai fighter is mmc3 IIRC.

That linked behavior won't help with this game.

Mickey's Safari in Letterland works fine with nemulator. It requires really precise IRQ timing.

James wrote:That linked behavior won't help with this game.

Mickey's Safari in Letterland works fine with nemulator. It requires really precise IRQ timing.

Thank you james, thats what i was thinking. Im going to find a way to get these fixes in for those 3 above mentioned games. As far as burai fighter goes, this will prob help me:

http://sourceforge.net/p/fceultra/bugs/382/

ill start from here since these 2 issues seem to be the same, or used to be until fce fixed it. Just trying to pinpoint exactly what the issue is regarding burai fighter first, thats all.

and by the way GREAT WORK on everything you have done for the emulation scene james!

thefox wrote:No idea. Every emulator I have tried has the same problem with Mickey (puNES, Nintendulator, Nestopia).

Strange, I thought I had fixed this problem several versions ago. Thefox which version of puNES have you tried? The latest (0.89)?

FHorse wrote:

thefox wrote:No idea. Every emulator I have tried has the same problem with Mickey (puNES, Nintendulator, Nestopia).

Strange, I thought I had fixed this problem several versions ago. Thefox which version of puNES have you tried? The latest (0.89)?

Indeed, it's working fine in puNES. But Burai Fighter isn't.

FHorse wrote:

thefox wrote:No idea. Every emulator I have tried has the same problem with Mickey (puNES, Nintendulator, Nestopia).

Strange, I thought I had fixed this problem several versions ago. Thefox which version of puNES have you tried? The latest (0.89)?

Yeah sorry, I was using an old version.

*Spitfire_NES* wrote: and by the way GREAT WORK on everything you have done for the emulation scene james!

Thanks!

Burai Fighter is broken in nemulator too. I'll look into it when I have some time.

James wrote:

*Spitfire_NES* wrote: and by the way GREAT WORK on everything you have done for the emulation scene james!

Thanks!

Burai Fighter is broken in nemulator too. I'll look into it when I have some time.

sweet! in the meantime i decided to start with ninja gaiden diffing code between 1.39 and 1.40, in 1.39 and have a question for whoever can or may put some light on this.

At initial glance at the code, the mmc1 mapper was not modified going into 1.39 to 1.40, in other words the code was left unchanged, regarding the missing chunk of moon should i move efforts to diff code to the ppu instead? This does have changes going from 1.39 to 1.40, im not sure where else he could have done something to mess up the intro like that., also he did make some changes to the apu as well going from 1.39 to 1.40.

Burai Fighter has two MMC3 IRQs per frame: one at the top of the status bar and another at the bottom. In between, there are a couple of reads to PPU memory > $3000 via $2006/$2007. These reads, if not properly mirrored to $2xxx, will cause A12 to go high and clock the IRQ counter, making the second IRQ fire a couple of scanlines too early. I fixed this mirroring in my emulator and Burai Fighter looks good now:

Thank you james for sharing that. Im going to try to implement this into nestopia. Pm sent.

It sounds easy to do and id like to get this fix into nestopia as well. Thank you for sharing this info. Im working on trying to sort out these 3 games as we speak.