The PokéCommunity Forums

The PokéCommunity Forums (https://www.pokecommunity.com/index.php)
-   Binary ROM Hacking (https://www.pokecommunity.com/forumdisplay.php?f=284)
-   -   Other ERRORS !!! (https://www.pokecommunity.com/showthread.php?t=436916)

FireFig June 27th, 2020 11:47 PM

ERRORS !!!
 
I wanted to replace professor oak with a xerneas ;) and I used infranview to rearrange the pallets in the 7th row so I was trying to insert it and this showed u .https://ibb.co/Zxh9p5D Can anyone help me with it plz :(

Pyxal June 28th, 2020 12:07 AM

Quote:

Originally Posted by Azz~kun (Post 10175794)
I wanted to replace professor oak with a xerneas ;) and I used infranview to rearrange the pallets in the 7th row so I was trying to insert it and this showed u .https://ibb.co/Zxh9p5D Can anyone help me with it plz :(

Copied answer from somewhere:
If you get an error when writing to ROM which says that it's too big, you will need to find space for it. For this use Free Space Finder. When you get an error in unLZ-GBA, copy down the hex number displayed in the error box, which in your case is 7F4. Open up Free Space Finder, and load your ROM from the "File" tab. Now, in the bottom right corner in the hex box, write in the number the error box displayed. In the box above it, it will show the number in decimal. Copy the decimal number and paste it in the box next to "Needed Bytes". Under that, make sure "Search from the beginning of the ROM" is selected, then click "Search". After that click "Copy". In unLZ-GBA, click "Write to ROM" again. Tick the "Automatically fix pointers" option, and in the first text box, delete everything, then type in two 0 and press Ctrl+V. Once that's done you can click OK.

Please search for an answer before asking.

FireFig June 28th, 2020 3:23 AM

I am sorry to ask but can u tell me where exactly is the box next to "Needed bytes" . There is a box below it called byte skipping (i don't remember clearly) and a box above it and then there is a huge box where free space offsets appear after a search

Tacobell24 June 28th, 2020 5:22 AM

Ulgh, this error really bugs me... it should say "which is too big".

But to answer your question - When you click "Write to ROM", you can uncheck the box
Auto abort if new data is bigger

Just make sure you do like what PokeChu said first and find a new offset to put the image and type it in the Image Offset box first.

Entaro Ceraphenine June 28th, 2020 6:30 AM

Quote:

Originally Posted by Azz~kun (Post 10175860)
I am sorry to ask but can u tell me where exactly is the box next to "Needed bytes" . There is a box below it called byte skipping (i don't remember clearly) and a box above it and then there is a huge box where free space offsets appear after a search

If you dont see a hexadecimal to decimal converting box in your Free Space Finder, then you are probably using the version which I use, which is also different from what a lot of people use.

You can download the other free space finder and then in that case, you can follow PokeChu's steps.

I just never bothered to find and download a different free space finder because I use a physical calculator to do the hexadecimal <---> decimal conversions and all. You can also use online converters. Just google a "hex to dec converter" or something like that.

Basically, once you convert the hex number in unlz error box to decimal, put the decimal number in free space finder's Needed Bytes box and follow PokeChu's steps from the "Under that, make sure 'Search from the beginning of the ROM' is selected" portion and afterwards.

Sorry for poor English.

Pyxal June 28th, 2020 6:41 AM

Quote:

Originally Posted by Azz~kun (Post 10175860)
I am sorry to ask but can u tell me where exactly is the box next to "Needed bytes" . There is a box below it called byte skipping (i don't remember clearly) and a box above it and then there is a huge box where free space offsets appear after a search

Download the latest version of FSF from here to understand what I am talking about.

Quote:

Originally Posted by Tacobell24 (Post 10175894)
Ulgh, this error really bugs me... it should say "which is too big".

But to answer your question - When you click "Write to ROM", you can uncheck the box
Auto abort if new data is bigger

Just make sure you do like what PokeChu said first and find a new offset to put the image and type it in the Image Offset box first.

By thunder, are you out of your mind? Unchecking this box literally means that you are telling unLZ.gba to delete anything that is in it's way. But I suppose that if you specify new offsets, then maybe it is safe...

FireFig June 28th, 2020 8:49 AM

Thank u so much mate, But thinking bout it I was using the latest version of fsf , and I also had the hexadecimal conversation at the bottom right corner the problem was pokechu telling me "to paste the decimal number in the box 'NEXT' to the needed bytes.

So I was confused coz I was not able to find the box pokechu mentioned. It was jus misunderstood. Sorry.

And BTW I used HxD to find free space it was quite easy :)

Pyxal June 28th, 2020 9:53 AM

Quote:

Originally Posted by Azz~kun (Post 10175953)
Thank u so much mate, But thinking bout it I was using the latest version of fsf , and I also had the hexadecimal conversation at the bottom right corner the problem was pokechu telling me "to paste the decimal number in the box 'NEXT' to the needed bytes.

So I was confused coz I was not able to find the box pokechu mentioned. It was jus misunderstood. Sorry.

And BTW I used HxD to find free space it was quite easy :)

Yes, that is another way, but opening it again and again... FSF is better in my opinion.

Tacobell24 June 28th, 2020 2:18 PM

Ah yes. Sorry it was late when I posted this. I was actually thinking of the other one about checking the auto repointing box.

Basically, don't uncheck the Auto abort one, unless you can no longer suffer the indignation of a typo in a completed program :P

FireFig June 29th, 2020 1:39 AM

I got another error :( after importing the picture I replaced oak's palette with xerneas palette using adv palette editor. (I used a 16 color pal). The problem was when I tested it out and to my surprise the palette suited perfectly....................



BUUUUUUUUUUUUUUUUUUUTTTTTTTTTTTTT The borders were replaced with a color that wasn't even there in my palette, some kind of green, not my neon green (I will attach the pic later) replaced my black border.

Can anyone suggest the problem plz

Tacobell24 June 29th, 2020 3:28 AM

Did you make sure you changed the original background colour of your Xerneas to the top leftmost colour of the palette?

I.e. like with all sprites (even ones with 256 colours in their palette), the top left/first one is still the background one.

FireFig June 29th, 2020 3:31 AM

Quote:

Originally Posted by Tacobell24 (Post 10176189)
Did you make sure you changed the original background colour of your Xerneas to the top leftmost colour of the palette?

Top left most of the 256 color pal or the top left most replaced 16 color pal ??? (I replaced both with the neon green BG color :)

Tacobell24 June 29th, 2020 3:37 AM

Top left of 256. The other colours are still part of the palette despite only using the 7th row etc

FireFig June 29th, 2020 3:55 AM

Quote:

Originally Posted by Tacobell24 (Post 10176193)
Top left of 256. The other colours are still part of the palette despite only using the 7th row etc

So the bg color should only be filled in the top left of 256 color pal and not the 7th row upper leftmost 16 color palette ?!?!

Tacobell24 June 29th, 2020 4:30 AM

Yep. Colour #1 of the 256 is still the background colour.

PS, you can use two rows of colours for the intro sequence sprites, so 32 + the background one

FireFig June 29th, 2020 4:47 AM

Quote:

Originally Posted by Tacobell24 (Post 10176199)
Yep. Colour #1 of the 256 is still the background colour.

PS, you can use two rows of colours for the intro sequence sprites, so 32 + the background one

Thanks but I have one last question, should I fill the background color in first column of the 7th row 16 col palette?

Tacobell24 June 29th, 2020 4:51 PM

Like I explained, the background colour is still the first slot of the 256 palette, regardless of which rows the sprite accesses. So the first colour of your 7th row can be whatever.

FireFig June 29th, 2020 6:35 PM

Thanks

FireFig July 4th, 2020 3:25 AM

Palette error :( I have first inserted back sprites to my ROM, then I thought of changing it and replacing it another set of back sprites, I inserted the back sprite and the pal using NSE 2.0, it looked okay in NSE but when I tested out the ROM, the image was inserted but not the pal, (BTW it used the first inserted sprite pal) , I tried repointing it and reinserting, and yet it didnt work (╥_╥) can somebody point out my issue (mostly poke chu or taco bell24 :)



P.S : I WILL USE THESE (个_个) , POKECHU

Tacobell24 July 4th, 2020 5:48 AM

Did you click the Save Palette to ROM button in NSE?

FireFig July 4th, 2020 9:19 AM

Quote:

Originally Posted by Tacobell24 (Post 10178338)
Did you click the Save Palette to ROM button in NSE?

Yes, (its the button that appears while u click the palette icon right)

Tacobell24 July 4th, 2020 3:06 PM

Ok, i think what the issue is... Maybe.

The way Pokémon battle sprites work ia they use the same palette for both front and back sprites.

So if I understand what you've tried to dk correctly, you've tried to repoint the palette for the new back sprite only? Which in turn is not the exact same as the one for the front sprite. Which is what ks messing it up.

Does that sounds about right?

FireFig July 4th, 2020 6:32 PM

Quote:

Originally Posted by Tacobell24 (Post 10178508)
Ok, i think what the issue is... Maybe.

The way Pokémon battle sprites work ia they use the same palette for both front and back sprites.

So if I understand what you've tried to dk correctly, you've tried to repoint the palette for the new back sprite only? Which in turn is not the exact same as the one for the front sprite. Which is what ks messing it up.

Does that sounds about right?

I am not talking bout Pokemon's I am talking bout the protagonist back sprites :(









P.S : U CURRENTLY HAVE 69 POSTS :) NOICE !!!

Tacobell24 July 4th, 2020 8:35 PM

Righto. Not sure what the go is.

You can always just change the palette colours manually in NSE by copy and pasting the 4 digit code for each.

See if that works instead of repointing the palette

FireFig July 4th, 2020 9:59 PM

Quote:

Originally Posted by Tacobell24 (Post 10178582)
Righto. Not sure what the go is.

You can always just change the palette colours manually in NSE by copy and pasting the 4 digit code for each.

See if that works instead of repointing the palette

Thanks I ll try :)


All times are GMT -8. The time now is 2:29 AM.


Like our Facebook Page Follow us on Twitter © 2002 - 2018 The PokéCommunity™, pokecommunity.com.
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, The Pokémon Company or The Pokémon Company International. We just love Pokémon.
All forum styles, their images (unless noted otherwise) and site designs are © 2002 - 2016 The PokéCommunity / PokéCommunity.com.
PokéCommunity™ is a trademark of The PokéCommunity. All rights reserved. Sponsor advertisements do not imply our endorsement of that product or service. User generated content remains the property of its creator.

Acknowledgements
Use of PokéCommunity Assets
vB Optimise by DragonByte Technologies Ltd © 2023.