Welcome to the PokéCommunity!

Hi there! Thanks for visiting PokéCommunity. We’re a group of Pokémon fans dedicated to providing the best place on the Internet for discussing ideas and sharing fan-made content. Welcome! We’re glad you’re here.

In order to join our community we need you to create an account with us. Doing so will allow you to make posts, submit and view fan art and fan fiction, download fan-made games, and much more. It’s quick and easy; just click here and follow the instructions.

Pokémon Sun and Moon are now available! Read our extensive Sun and Moon review at Daily!

The finale of the fourth annual Favorite Pokémon Tournament is underway in Pokémon General!View the poll and vote for as many Pokémon as you'd like. Voting is only open until the 5th of December though, so don't wait to make your picks!

Research & DevelopmentGot a well-founded knack with ROM hacking? Love reverse-engineering the Pokémon games? Or perhaps you love your assembly language. This is the spot for polling and gathering your ideas, and then implementing them! Share your hypothesis, get ideas from others, and collaborate to create!

Research & Development programs in this forum are subject to moderator approval before they are displayed.

While browsing this section I found a post by colcolstyles (see below) about the amount of frames that the titlescreen in FireRed is displayed for. I then thought to myself "That'd be a good way to add an animation to the titlescreen!" and then I posted this thread.

Quote:

Originally Posted by colcolstyles

For anyone who's interested, at '0x078c1c' there is a 32-bit number (the default value is '0x00000a8b') which dictates the number of frames for which the titlescreen is displayed before resetting. The GBA operates at roughly 60 frames per second and '0xa8b' divided by 60 is 45 so the unedited titlescreen is displayed for 45 seconds. You can change that number (remember to reverse it) to lengthen or shorten the amount of time it takes for the titlescreen to reset.

This is for Fire Red, by the way.

Anyway, my idea is to inject a routine just before that check to change the tileset/tilemap of the Charizard on the titlescreen, based on the amount of frames passed, allowing for animations to be used.

This would be a much better way of having an animated titlescreen than anything done before now(I think), since more than 2 frames will be able to be used.

...so a simple endless-loop animation (like in the video) would be possible, or you could play the first few frames once, then loop to a frame somewhere in the middle. Or you can stop the animation at the end by pointing to its own frame. The animation can be up to 255 frames.

So yeah, it just changes the tiles, not the tilemap, as that seems to suffice.

I wouldn't know, exactly, how to get the game to load a new OAM to the title screen, or how to have it animate... well, that would probably just use the frame system we've already found. But I wouldn't know how to make it, say, go across the screen. Then again, I don't know how to do that with tilemaps either...

I like this. I'd like to see this as a complete working animated title screen someday. Congrats on your effort. Do you think it'd be possible to use the animated sprites of the Pokemon in Black and White, after resized, in the title screens?

Yeah, but not with the way they are stored in the B/W ROM, since they are stored as "parts" rather than full frames. But if you make/find full frames, and give me the order, I can make a video showing it.

EDIT: I got bored an put in Zapdos' animation. Well... kind of. Just the frames. Not the FULL animation, though that is very possible.

There is a downside to this hack, though. It takes quite a bit of space. The entire Zapdos animation (frames, tilemap and routine) take up 11.55kb (11,828 bytes) in the ROM. Which only works out to about 0.0007% of the entire (un-expanded) ROM, but it's still quite a bit.

Yeah, but not with the way they are stored in the B/W ROM, since they are stored as "parts" rather than full frames. But if you make/find full frames, and give me the order, I can make a video showing it.

EDIT: I got bored an put in Zapdos' animation. Well... kind of. Just the frames. Not the FULL animation, though that is very possible.

There is a downside to this hack, though. It takes quite a bit of space. The entire Zapdos animation (frames, tilemap and routine) take up 11.55kb (11,828 bytes) in the ROM. Which only works out to about 0.0007% of the entire (un-expanded) ROM, but it's still quite a bit.

nice vid man

i'm guessing that you should probably complete the hack before you input the titlescreen...

Yeah, but not with the way they are stored in the B/W ROM, since they are stored as "parts" rather than full frames. But if you make/find full frames, and give me the order, I can make a video showing it.

EDIT: I got bored an put in Zapdos' animation. Well... kind of. Just the frames. Not the FULL animation, though that is very possible.

There is a downside to this hack, though. It takes quite a bit of space. The entire Zapdos animation (frames, tilemap and routine) take up 11.55kb (11,828 bytes) in the ROM. Which only works out to about 0.0007% of the entire (un-expanded) ROM, but it's still quite a bit.

That's pretty damn cool. Not kidding. If I was able to do this for my hack, I would do so by all means. But, the one thing that bugs me the most is the flames in the background. Is it possible to use them elsewhere on the screen. I do know they can be edited using UnLzGBA, but yeah.

^ He's not actually making a hack. He's hacking. you know, learning, experimenting in areas others haven't really abused much. It's pretty cool and fun.
ANYWAYS, what I *really* came here with.
I tried bpr 08078C1C 2
and nothing ever came up.
But it's okay, I followed that post link, and read down on that thread a bit further where Knizz ( Reference ) posted the offset of the comparison. I looked up the point where r0 is loaded with the value.

^ He's not actually making a hack. He's hacking. you know, learning, experimenting in areas others haven't really abused much. It's pretty cool and fun.
ANYWAYS, what I *really* came here with.
I tried bpr 08078C1C 2
and nothing ever came up.
But it's okay, I followed that post link, and read down on that thread a bit further where Knizz ( Reference ) posted the offset of the comparison. I looked up the point where r0 is loaded with the value.

Nice work! Now we only need to be able to 'pull' tilemaps across the screen...
And make this work in Emerald too, as it just resets on the end of the song.

In regards to this, I looked in to it, and it's a LOT easier to move the tilemap than I thought it would be. Infact, I implemented it and it seems to work fine. Except when moving it from the X-axis, from off the screen, since the GBA hardware "wraps" the tilemap, which makes it come from left if moved off the right, and visa versa. :\ I can't see an easy way around this... Y-axis has no problem at all, though.

Hey, I tried that routine.
I think I did a nice job at understanding it.
You load a pointer to an array of those structures
Then, you load a pointer to the image and copy it.
Then you wait until the frame count for that image passes
Then you load the next and continue. { you store the fc and the current frame in that RAM_ADDRESS location thing. }
But one question, how do you know when to reset back to the first image?
{ I still haven't actually gotten this thing to work btw. I probably just need to start with a fresh ROM and go from there. }
Also, some other questions.
For that routine, does it use a tilemap? What about the graphics, should they be compressed, or decompressed?
*edit*
NVM on the knowing when to restart. You just set the `next frame` value to 0.
I FEEL SILLY now. But the questions of tilemaps uncompressed/compressed still remains.
Although I have a feeling it's uncompressed with a tilemap...(GbaTek doesn't say swi 0xC uncompresses any data )

Hey, I tried that routine.
I think I did a nice job at understanding it.
You load a pointer to an array of those structures
Then, you load a pointer to the image and copy it.
Then you wait until the frame count for that image passes
Then you load the next and continue. { you store the fc and the current frame in that RAM_ADDRESS location thing. }
But one question, how do you know when to reset back to the first image?
{ I still haven't actually gotten this thing to work btw. I probably just need to start with a fresh ROM and go from there. }
Also, some other questions.
For that routine, does it use a tilemap? What about the graphics, should they be compressed, or decompressed?
*edit*
NVM on the knowing when to restart. You just set the `next frame` value to 0.
I FEEL SILLY now. But the questions of tilemaps uncompressed/compressed still remains.
Although I have a feeling it's uncompressed with a tilemap...(GbaTek doesn't say swi 0xC uncompresses any data )

The routine I gave you doesn't load any tilemap, it just uses the one in the original titlescreen, so you can replace that one. All graphics are compressed.

EDIT: Also, I don't know where you got SWI 0xC from? The only SWI used is 0x12 (LZ77UnCompVram.)

OH! I thought that was a decimal twelve, which I thought was odd. Awesome, thanks.

Okay...I must be doing something wrong.
I inserted my routine, and adjusted the original as you recommended ( I remembered to add 1 to the offset ) and I can view the titlescreen, and continue to the continue/new game screen. However...the swi function I think is causing some issues. It's copying *way* too much data, and it looks corrupt in the tile-viewer. ( I did insert two frames using unlz.GBA )

Help

The PokéCommunity

Meta

Pokémon characters and images belong to The Pokémon Company International and Nintendo. This website is in no way affiliated with or endorsed by Nintendo, Creatures, GAMEFREAK, or The Pokémon Company International. We just love Pokémon.