Posted: 5/6/2005 1:14 PM
Post subject: Mode 7 Yoshi island Errors at 1-6 and Sometimes Desync
Quote
yagz
Joined: 1/11/2005
Posts: 60
Help! Mode 7 Yoshi island: VBA'll Error at 1-6 and Sometimes Desync In the M7 version when entering a game there will be a screen like the picture below How to fix this
This is my Signature. = 4aa6a32c5eb83ac0ddcbc0039a26b240
Posted: 5/6/2005 1:15 PM
Quote
Bag_of_Magic_Food
He/Him
Active player (278)
Joined: 5/29/2004
Posts: 5712
BLAST YOU, MODE SEVEN! YOU'LL PAY FOR THIS!
put yourself in my rocketpack if that poochie is one outrageous dude
Posted: 5/6/2005 1:21 PM
Quote
NrgSpoon
Joined: 6/14/2004
Posts: 646
http://www.gbadat.altervista.org/gbata.htm Bickety-BAM! or something.
I like my "thank you"s in monetary form.
Posted: 5/6/2005 1:58 PM
Quote
yagz
Joined: 1/11/2005
Posts: 60
MORE MORE MORE UPDATE: Thanks for NrgSpoon for Intro Remover Without intro the movie wont desync! Thanks MORE MORE UPDATE: Both Version of Rom Error at Exacly Same Place [6-1 Underground after second shyguy on stilt] You can test the error by download this file: http://www.geocities.com/mechakoopa_v2/upfile/yi_speed.zip Rom i used: 0595 - Yossy Island - Super Mario Advance 3 (J)(Cezar) when movie finished just walk Right and the program will automatically CLOSE! MORE UPDATE: VBA will make a fatal error but still make a file so i dont lost my speedrun UPDATE: I've searched my computer and found A Japanese Version of YI and I used that rom to record but.... Oh.. I think i must stop recording YI speedruns :..(
This is my Signature. = 4aa6a32c5eb83ac0ddcbc0039a26b240
Posted: 5/7/2005 4:53 PM
Quote
nitsuja
Emulator Coder, Skilled player (1301)
Joined: 12/21/2004
Posts: 2687
Computer TASer of 2011 TAS of 2011 First edition TAS of 2011 Computer TAS of 2011 Sega TAS of 2010 Sega TAS of 2008 Sega TAS of 2007 Glitchy TAS of 2007
I think the crash is likely to be the same problem that happens with WarioWare Inc., but at least this gives another test case... EDIT: That problem was fixed, and since nobody's said anything more about this one I'll assume it's the same problem and also fixed...