Star Fox 2 Bug in ZSNES V1.42
Moderator: ZSNES Mods
Star Fox 2 Bug in ZSNES V1.42
This from Cyber Louis's, of Aeon Rom Translation Fandom, own page on the topic of which rom is the proper dump in reference to his Star Fox 2 patch:
"It ought to work on the roms that goodsnes has labelled "Beta TD" and "J o1" (which is funny, 'cuz the so-called overdump is actually the right size :p)"
"
I am using this exact particular dump (the BETA TD" to be specific). I have reproduced this both with auto patching on and off and my rom is not hard patched. I fear I may be the only one with courage to report the bug I'm sure every else saw, but was afraid to report due to a bad check sum (in situation where there is no good checksum on the proper rom, and so I must report this anyways). Thus I claim that rule 3 of the bug report submissions is not applicable in this case (if this is not so, then there is no reason to ever again try to make this game work as the perfect rom is verboten to all bug reports).
This is the info for the last game you ran.
File: Star Fox 2.smc Header: No
STAR FOX TYPE:SUPER FX
INTERLEAVED:No BANK:Lo CHKSUM:FAIL (irrelevant)
VIDEO:NTSC CRC32:1B3BC708
(The above was with the patch NOT being applied by ZSNES)
The error I am about to describe DID NOT show up in version 1.40 of ZSNES. I am currently using the WIN32 build of ZSNES v1.42 to produce this error, and I have done so every time I have ran the game. When you first start a new game, immediately after selecting your difficulty, there is a cut scene where in warships blast off towards Corneria while Andross is Gloating and the Camera moves to follow them as they blast off. This was the way is used to be, the way it was suposed to be. Now the camera gets stucked focused on the rotating space station the warships are leaving and will watch it indefinitely until you hit a button that can be used to escape a cutscene. The game will then play normally after that, at least as far as I looked.
I just know someone is going to scream at this post over Rule-3 despite all I've pointed out.
"It ought to work on the roms that goodsnes has labelled "Beta TD" and "J o1" (which is funny, 'cuz the so-called overdump is actually the right size :p)"
"
I am using this exact particular dump (the BETA TD" to be specific). I have reproduced this both with auto patching on and off and my rom is not hard patched. I fear I may be the only one with courage to report the bug I'm sure every else saw, but was afraid to report due to a bad check sum (in situation where there is no good checksum on the proper rom, and so I must report this anyways). Thus I claim that rule 3 of the bug report submissions is not applicable in this case (if this is not so, then there is no reason to ever again try to make this game work as the perfect rom is verboten to all bug reports).
This is the info for the last game you ran.
File: Star Fox 2.smc Header: No
STAR FOX TYPE:SUPER FX
INTERLEAVED:No BANK:Lo CHKSUM:FAIL (irrelevant)
VIDEO:NTSC CRC32:1B3BC708
(The above was with the patch NOT being applied by ZSNES)
The error I am about to describe DID NOT show up in version 1.40 of ZSNES. I am currently using the WIN32 build of ZSNES v1.42 to produce this error, and I have done so every time I have ran the game. When you first start a new game, immediately after selecting your difficulty, there is a cut scene where in warships blast off towards Corneria while Andross is Gloating and the Camera moves to follow them as they blast off. This was the way is used to be, the way it was suposed to be. Now the camera gets stucked focused on the rotating space station the warships are leaving and will watch it indefinitely until you hit a button that can be used to escape a cutscene. The game will then play normally after that, at least as far as I looked.
I just know someone is going to scream at this post over Rule-3 despite all I've pointed out.
-
- ZSNES Developer
- Posts: 3904
- Joined: Tue Jul 27, 2004 10:54 pm
- Location: Solar powered park bench
- Contact:
First of all, when you use the AGTP patch, it also fixes bugs in the ROM.
If you're not using a patch, make sure you fix your ROM with NSRT.
About bugs in Star Fox 2, we know, we're working on it.
If you're not using a patch, make sure you fix your ROM with NSRT.
About bugs in Star Fox 2, we know, we're working on it.
May 9 2007 - NSRT 3.4, now with lots of hashing and even more accurate information! Go download it.
_____________
Insane Coding
_____________
Insane Coding
Actually, the only reason I turned off the AGTP patch (through the menu's auto-patching option) was to be sure it wasn't the patch doing it. It happened to me first under the AGTP patch. I know how people can be around here to members who don't thuroughly investigate EVERYTHING before making a bug report (despite the number of posts in my account, I've been watching this place for ages). I understand the importance of clarity in a bug report, and not making a stupid report (but I still think some people here are a little trigger happy).
Still, thanks for the advice.
Still, thanks for the advice.
-
- ZSNES Developer
- Posts: 3904
- Joined: Tue Jul 27, 2004 10:54 pm
- Location: Solar powered park bench
- Contact:
Yes, but you have to make sure you have a good ROM too.clovis15 wrote:Actually, the only reason I turned off the AGTP patch (through the menu's auto-patching option) was to be sure it wasn't the patch doing it.
Yes. I was flamed to kingdom come after my second post here. By one major ZSNES contributor no less.clovis15 wrote: It happened to me first under the AGTP patch. I know how people can be around here to members who don't thuroughly investigate EVERYTHING before making a bug report (despite the number of posts in my account, I've been watching this place for ages). I understand the importance of clarity in a bug report, and not making a stupid report (but I still think some people here are a little trigger happy).
May 9 2007 - NSRT 3.4, now with lots of hashing and even more accurate information! Go download it.
_____________
Insane Coding
_____________
Insane Coding
-
- Dark Wind
- Posts: 1271
- Joined: Thu Jul 29, 2004 8:58 pm
- Location: Texas
- Contact:
-
- "Your thread will be crushed."
- Posts: 1236
- Joined: Wed Jul 28, 2004 1:49 am
- Location: Not in Winnipeg
- Contact:
Hey, I was flamed on my first post as well. I learned very quickly to read all the threads in the forum before posting. :pNoxious Ninja wrote:Wow.Nach wrote:Yes. I was flamed to kingdom come after my second post here. By one major ZSNES contributor no less.
Makes me look at myself and realize that even I have started becoming an asshole as of late.
<pagefault> i'd break up with my wife if she said FF8 was awesome
-
- ZSNES Developer
- Posts: 3904
- Joined: Tue Jul 27, 2004 10:54 pm
- Location: Solar powered park bench
- Contact:
I wasn't flamed for not reading threads, I was flamed for suggesting certain more out there things to do.Evan wrote:Hey, I was flamed on my first post as well. I learned very quickly to read all the threads in the forum before posting. :pNoxious Ninja wrote:Wow.Nach wrote:Yes. I was flamed to kingdom come after my second post here. By one major ZSNES contributor no less.
Makes me look at myself and realize that even I have started becoming an asshole as of late.
Regardless of how I was told it was impossible, nearly impossible, too insane etc..., I implemented all that stuff already.
May 9 2007 - NSRT 3.4, now with lots of hashing and even more accurate information! Go download it.
_____________
Insane Coding
_____________
Insane Coding
Which is evidence here some people are flame happy. But sure, if it's about porting ZSNES to a MAC then just flame away. However these people are jumping far more than just the justifiable stuff. In fact, there's a Chrono Trigger bug I once reported years upon years ago, that I will refrain from mentioning right now, that got me flamed to high hell for reporting. The bug still exists (in fact, the first thing I do when I run a new version is to see if it's finally fixed), but I'm not brave enough to point it out. Those of you who know what I'm talking about, please don't kill me (and no, it's NOT sound).Nach wrote:I wasn't flamed for not reading threads, I was flamed for suggesting certain more out there things to do.Evan wrote:Hey, I was flamed on my first post as well. I learned very quickly to read all the threads in the forum before posting. :pNoxious Ninja wrote:Wow.Nach wrote:Yes. I was flamed to kingdom come after my second post here. By one major ZSNES contributor no less.
Makes me look at myself and realize that even I have started becoming an asshole as of late.
Regardless of how I was told it was impossible, nearly impossible, too insane etc..., I implemented all that stuff already.
-
- Dark Wind
- Posts: 1271
- Joined: Thu Jul 29, 2004 8:58 pm
- Location: Texas
- Contact:
Which one? The Black Omen bug?clovis15 wrote:In fact, there's a Chrono Trigger bug I once reported years upon years ago, that I will refrain from mentioning right now, that got me flamed to high hell for reporting. The bug still exists (in fact, the first thing I do when I run a new version is to see if it's finally fixed), but I'm not brave enough to point it out. Those of you who know what I'm talking about, please don't kill me (and no, it's NOT sound).
[u][url=http://bash.org/?577451]#577451[/url][/u]
-
- Seen it all
- Posts: 2302
- Joined: Mon Jan 03, 2005 5:04 pm
- Location: Germany
- Contact:
-
- ZSNES Shake Shake Prinny
- Posts: 5632
- Joined: Wed Jul 28, 2004 4:15 pm
- Location: PAL50, dood !
The black omen bug is a compile-time bug in the offset-per-tile code.
皆黙って俺について来い!!
Pantheon: Gideon Zhi | CaitSith2 | Nach | kode54
Code: Select all
<jmr> bsnes has the most accurate wiki page but it takes forever to load (or something)
No, actually it's the fact that the white bar at the middle of the screen, the light at the end of the tunnel if you will, doesn't appear on the New GFX engine and only the old one during the Crash the Epoch into Lavos sequence. Also, the 2-D graphic representing the control panel of the epoch doesn't quite display properly in the new GFX engine either, but it does in the old GFX engine. Pointing this out was a good way to get raped in the past, but it seems everyone has forgotten about it (which may mean it needs to be pointed out again).Noxious Ninja wrote:Which one? The Black Omen bug?clovis15 wrote:In fact, there's a Chrono Trigger bug I once reported years upon years ago, that I will refrain from mentioning right now, that got me flamed to high hell for reporting. The bug still exists (in fact, the first thing I do when I run a new version is to see if it's finally fixed), but I'm not brave enough to point it out. Those of you who know what I'm talking about, please don't kill me (and no, it's NOT sound).
-
- Seen it all
- Posts: 2302
- Joined: Mon Jan 03, 2005 5:04 pm
- Location: Germany
- Contact:
Didn't Matt Kendora flame you for suggesting the SETA 10 difficulty setting?Nach wrote:Yes, but you have to make sure you have a good ROM too.clovis15 wrote:Actually, the only reason I turned off the AGTP patch (through the menu's auto-patching option) was to be sure it wasn't the patch doing it.
Yes. I was flamed to kingdom come after my second post here. By one major ZSNES contributor no less.clovis15 wrote: It happened to me first under the AGTP patch. I know how people can be around here to members who don't thuroughly investigate EVERYTHING before making a bug report (despite the number of posts in my account, I've been watching this place for ages). I understand the importance of clarity in a bug report, and not making a stupid report (but I still think some people here are a little trigger happy).
I think I remember that.Metatron wrote:Didn't Matt Kendora flame you for suggesting the SETA 10 difficulty setting?Nach wrote:Yes, but you have to make sure you have a good ROM too.clovis15 wrote:Actually, the only reason I turned off the AGTP patch (through the menu's auto-patching option) was to be sure it wasn't the patch doing it.
Yes. I was flamed to kingdom come after my second post here. By one major ZSNES contributor no less.clovis15 wrote: It happened to me first under the AGTP patch. I know how people can be around here to members who don't thuroughly investigate EVERYTHING before making a bug report (despite the number of posts in my account, I've been watching this place for ages). I understand the importance of clarity in a bug report, and not making a stupid report (but I still think some people here are a little trigger happy).

-
- ZSNES Developer
- Posts: 3904
- Joined: Tue Jul 27, 2004 10:54 pm
- Location: Solar powered park bench
- Contact:
Yes, but that wasn't my first set of posts on this board.Metatron wrote:Didn't Matt Kendora flame you for suggesting the SETA 10 difficulty setting?Nach wrote:Yes, but you have to make sure you have a good ROM too.clovis15 wrote:Actually, the only reason I turned off the AGTP patch (through the menu's auto-patching option) was to be sure it wasn't the patch doing it.
Yes. I was flamed to kingdom come after my second post here. By one major ZSNES contributor no less.clovis15 wrote: It happened to me first under the AGTP patch. I know how people can be around here to members who don't thuroughly investigate EVERYTHING before making a bug report (despite the number of posts in my account, I've been watching this place for ages). I understand the importance of clarity in a bug report, and not making a stupid report (but I still think some people here are a little trigger happy).
I was originally flamed for suggesting to make a program that currently does what NSRT's -modint feature does and my idea for ZSNES to automatically enable the Super Scope on Super Scope games like Battle Clash which ZSNES currently does if you add an NSRT header to Battle Clash.
May 9 2007 - NSRT 3.4, now with lots of hashing and even more accurate information! Go download it.
_____________
Insane Coding
_____________
Insane Coding
-
- Born to Rule... Impatiently
- Posts: 265
- Joined: Wed Nov 17, 2004 8:21 pm
- Location: Everywhere I want to be.
- Contact:
You should actually post in the Official Bug Topic instead, so the necessary information about the bug can be gathered correctly for ipher to add to the Bug Tracker. Otherwise, the bug report might have to be modified somewhat after it's posted, and that's just unnecessary extra hassle.clovis15 wrote:Looks like I will be making a report soon on it, then. Once I get back from a class, that is.
[url=http://board.zsnes.com/phpBB2/viewtopic.php?t=3298][color=brown]My [u]NES palette[/u][/color][/url] - better colors with any emulator.
"the more you know, and the more you can do... the more you are."
- [url=http://www.danielbohman.com][color=brown][u]daniel bohman[/u][/color][/url]
"the more you know, and the more you can do... the more you are."
- [url=http://www.danielbohman.com][color=brown][u]daniel bohman[/u][/color][/url]