| User | Post |
HyperLamer
Posts: 3107/8210 |
As I understand, it sometimes turns the screen off outside of the vblank period when you finish a level. I'm not sure exactly what harm that can do, but Nintendo will reject any game that does it and does indeed warn that it can damage the system. Apparently it was bad enough for them to release a 'fixed' version (even though the bug has no actual effect on gameplay), so there ya go.  |
d4s
Posts: 118/325 |
Originally posted by Squash Monster
You'd be suprised what damage is possible through software. For example, if you're programming on a TI-83 (a very similar peice of hardware to the GB) and you set the contrast to certain abnormal values, you can make the screen glow blue (it's normally black and white mind you) and if you do this for extended times, the screen will burn out.
sounds cool. 
i wasnt implying its impossible to damage hardware through software, i just doubted you could do it on the gameboy.
there are a number of gameboy docs out there sporting exhaustive information on both undocumented features and bugs of the hardware, i have yet to find one that covers anything close to the above-mentioned.
but feel free to prove me wrong if you can. :>
|
Squash Monster
Posts: 528/677 |
You'd be suprised what damage is possible through software. For example, if you're programming on a TI-83 (a very similar peice of hardware to the GB) and you set the contrast to certain abnormal values, you can make the screen glow blue (it's normally black and white mind you) and if you do this for extended times, the screen will burn out. |
d4s
Posts: 117/325 |
Originally posted by HyperHacker
V1.0 has a bug that can damage the GB's video system, so you probably shouldn't use that.
And if it switches into double speed mode, shouldn't the entire game be faster? 
i doubt you can physically damage the gb through software.
besides, double speed only modifies the cpu-speed.
the majority of games base their timing on the vblank interrupt, thus, the speed will remain the same and you will hardly notice any difference in these.(except for cpu slowdowns, of course)
depends on how the game was written. |
BMF98567
Posts: 625/1261 |
Originally posted by HyperHacker
V1.0 has a bug that can damage the GB's video system, so you probably shouldn't use that.
Wait, v1.0 of Super Mario Land? What kind of crazy bug is that? |
HyperLamer
Posts: 3092/8210 |
V1.0 has a bug that can damage the GB's video system, so you probably shouldn't use that.
And if it switches into double speed mode, shouldn't the entire game be faster? |
iamhiro1112
Posts: 202/487 |
Ok, I sent the link to the current version of my mario land hack to your pm box. |
Parasyte
Posts: 255/514 |
If you want to upload your ROM somewhere, yeah, sure. I'll look at it.
The reason the music is "messed up" is because GameBoy Color's CPU runs approximately twice as fast as the original GameBoy. The only way you can fix that is slowing down the music code. I suppose I could look into that, as well. |
iamhiro1112
Posts: 201/487 |
Mine is 1.72 also. I also tried using it on Visual boy advance CE. If you want I can upload my rom and you can try fixing that one. Idon't know if you noticed that gb colorizer messes up the music. Do you think that can be fixed also? If not I may have to try and disable the music or advice people to turn off the sound while playing it. Thanks. |
Parasyte
Posts: 253/514 |
I screwed up my ROM's title screen with the crappy GBColorizer program. Plus the only color change I made was for Mario, and it looks nothing like yours.
What version of VBA are you using? I'm using 1.7.2. Perhaps you should try it before asking for my ROM? |
iamhiro1112
Posts: 197/487 |
It's visual boy advance. It still dont work. How about sending me the rom instead? you can give me a link thru pm. |
Parasyte
Posts: 252/514 |
I was unaware there were additional versions of the game? It sounds like v1.0 is the right one, however.
Which emulator are you using? VBA and no$gmb will play it fine. |
iamhiro1112
Posts: 196/487 |
Ok, I tried patching it to the Mario land vs 1.0. And it said there was no jump at $10 or something and an unsupported memory mapper. I tried it on Mario vs 1.1 and it opened up the rom, but when I saved it the game would not go past the title screen when trying to play it. It got froze at the title screen.
Well, I'm using version 1.1 of Mario land so that is what I would need a patch for. If you can find a way to make the title screen not freeze I would appreciate it. Thanks.
|
Parasyte
Posts: 251/514 |
Yes, it is the right patch. You're supposed to apply it to the ROM. Not to GBColorizer. |
iamhiro1112
Posts: 195/487 |
Well, thanks for trying. I patched the thing but it still acts as before. I tried patching it to GB colorizer with ips-win, then lunar ips and it still seems the same. Are you sure you uploaded the right patch? I am planning to use this colorization for my super mario land hack that I've been working on so it will definately be put to use. If I can't get the status bar to stop scrolling then I will just release 2 versions of my hack, the black and white version. and the colorized version. with a crappy status bar.
I also tried patching this to Super Mario land, but the game was frozen at the title screen when I did that. |
HyperLamer
Posts: 3081/8210 |
I think the real issue here is expecting to be able to automate something like colourizing a ROM. This program's really a piece of crap, and it's pretty easy to understand why if you think about the complexity involved... |
Parasyte
Posts: 250/514 |
sml-fix.ips should do the trick! It's not the prettiest hack ever, but it should work no matter which "refresh rate" you choose. |
iamhiro1112
Posts: 194/487 |
Sillly me. I meant to type 2.4 GB colorizer. But anyway, I uploaded the file to my webspace. Here is the link.
http://www.geocities.com/iamstillhiro1112/GB_Colorizer_3.4.zip |
Parasyte
Posts: 248/514 |
I looked into it, but I only have GBColorizer 2.3.
The problem with it is the colorize code is WAY too slow. During VBlank (after the screen is done drawing) the game is supposed to change the screen scroll registers so the status bar stays static on screen. What's happening is VBlank occurs, the colorizer code kicks in, takes far too long to complete, THEN the scroll is reset. The effect, as you can see in your screen shot, is that the screen has already drawn a little bit before the scroll is reset.
A simple fix is moving the scroll reset code closer to the VBlank handler's entry. In that way, the colorizer code can start running AFTER the scrolls are already reset.
If you could point me to a place where I can download this newer copy of GBColorizer, I'll help with the patch to fix the problem. |
iamhiro1112
Posts: 192/487 |
Well, I started playing around with the 3.4 gameboy colorizer and tried saving it in its various background refresh rates. For some reason the scores and times in Super Mario Land would not stay in place. It works best in the lowest background refresh rate (64). But the top line still scrolls funny. Anyone know if there is any way to fix it. Say a way to save it in a smaller refresh rate? I may have to get rid of the top name thing all together if I can't fix it. Anyway, here's a pic of what the problem looks like.
 |
hukka
