I read all the documents and information I could find on how pointer tables work. I have been having trouble with the mega man X3 graphics pointer table that euclid mentioned in his document.

Here is what I understand of it. As well as some clips of the document by Euclid.

So here are the values you would find in the rom at that address
00 80 1a c0 03
0c 83 1a 00 26
3e 88 1a a0 07
f6 8d 1a e0 07
82 93 1a 00 04

So when they are rearranged to become physical snes rom addresses they should be?

1A8000 (03C0 Bytes)
1A830C (2600 Bytes)
1A883E (07A0 Bytes)
1A8DF6 (07E0 Bytes)
1A9382 (0400 Bytes)


There sure isn't any gfx data at 1A8000, it is the Tile arrangement data for Doppler stage #1.

The thing that really confused me is he points to the following location and length for his sample C decompression routine that works great.
0xE84B3
Length of data it reads is  0xA00
0
According to this data wouldn't the pointer look like
B3 84 0E 00 0A
That surely does not show up anywhere in the rom or pointer table.

What I do know is the compressed graphics are stored around 0xD0000-0x110000 since I can easily corrupt them and see them get messed up...

I did read somewhere that pointers can be tricky and do not all follow the same rules. Obviously this one being three bytes long is different than the standard documents suggest.
I am working on learning to use the debugger and tracer to maybe understand it on my own.

Anybody got any ideas?
I'd like to put out a program to uncrompress all the compressed gfx in the rom so one can edit them and reinsert them.

It being at 0xD0000 would make perfect sense since when I corrupt it certain graphics get messed up.

But how do you go from adding 0x80 to 0x1A and getting a CPU bank of either 0x1A or 0x9A. To an address of 0xD0000?

I'm sure it is something simple I can find just by understanding ROM and RAM addressing better. So I'll go check that out for now and learn some more!

EDIT: I just figured out the whole Bank things! http://www.romhacking.net/docs/anusp.htm anusp's document really helped with that!
And here's what I determined!
Hex 0E8000 = 1D8000 Low-Rom SNES

0xE84B3(0x2600 Bytes) Tile screen graphics
What it would look like in Hex as a pointer B3 84 1D 00 26
I then did a search and I found the pointer at offset 0x37791

So the next pointer in the list is  (C3 9F 1D 00 08) and must point to
0xE9FC3 with a length of 0x800 Bytes! How cool, but I sure cannot get the gfx to decompress in the program yet.. ah well at least I understand the pointers now!

LoROM banks are 32K in size (0x8000 bytes.) 1A8000 becomes D0000 by simple counting or modulo math. Banks are mirrored at 0x808000 as well.

LoROM banks are always addressed at 0x8000-0xFFFF in the direct page. If you set the pointer at anything less than 0x8000, you're pulling at memory. Thus....

... and so on and so forth.

Technical nitpicking beyond most people's concern.