Superskuj: Superskuj moved page Rom/Pages 0x10 to 0x17 to RAM: Bank 0x7E: Pages 0x10 to 0x1F

2016-12-20T22:32:27Z

Superskuj moved page Rom/Pages 0x10 to 0x17 to RAM: Bank 0x7E: Pages 0x10 to 0x1F

Tatters: Created page with "* {{$|1000}}[{{0x|02}}] = For transfers that use variable $14, this indicates the current length written into the buffer starting at * {{$|1002 Seems to be addresses used for..."

2016-12-20T07:18:39Z

Created page with "* {{$|1000}}[{{0x|02}}] = For transfers that use variable $14, this indicates the current length written into the buffer starting at * {{$|1002 Seems to be addresses used for..."

New page

* {{$|1000}}[{{0x|02}}] = For transfers that use variable $14, this indicates the current length written into the buffer starting at
* {{$|1002
Seems to be addresses used for blitting graphics onto the screen after a room or area has already loaded.
* {{$|1002}}[{{0x|02}}] = Big endian representation of the VRAM target address (word address)
* {{$|1004}}[{{0x|02}}] = dma configuration
ssssssss wftttttt
f - If set, DMA source address is fixed. Otherwise it auto increments.
s, t - One less(!) the 14-bit size of the DMA transfer, as expressed in bytes.
This value is composed of the 's' and 't' bits thusly:
00ttttttssssssss
w - If not set, vram target address increments on writes to $2118.
Otherwise, it increments on writes to $2119.
^ This documention is not 100% correct. I'll fix it when I have time.
Basically it determines whether or not to increment vram address by 1 or 32 words
after each adjustment (write to $2118 or $2119)
* {{$|1006}}[{{0x|??}}] = First word of data for the transfer. Many more may follow.
Setup for making overlaid tiles appear (word addresses):
Notes on converting in game tile positions into VRAM positions:
In game layout: (u = unused?) uuddaaaa abcccccc
Translated into VRAM base address: uuuddbaa aaaccccc
* {{$|1100}}[{{0x|02}}] = Target VRAM address for the transfer
* {{$|1102}}[{{0x|01}}] = The value that will be written to VMAIN ($2115) before the transfer.
Typically this controls whether the DMA transfer is intended to write words
or alternating bytes to VRAM.
* {{$|1103}}[{{0x|01}}] = Number of bytes to transfer to VRAM.
Note: Putting 0 here would transfer 0x10000 bytes, which could be really crazy.
* {{$|1104}}[{{0x|??}}] = Local portion of the source address for the DMA transfer. The source bank is forced to zero by the code.
584$1100 - Contains two chunks of data for blitting an extra tile to the screen. The hex values indicate where each portion
lies in the memory address.
0x8000 - indicates whether to use 2 byte or 64 byte increment when doing the DMA
0x4000 - ? not used?
0x3FFF - Contains the number of bytes to transfer
* {{$|1102}}[{{0x|02}}] = VRAM target address for the tile setup.
* {{$|1104}}[{{0x|02}}] = $1183 - The bytes that get blitted to VRAM
* {{$|1980}}[{{0x|20}}] = Low Byte: Door type (Take HM door type number, convert to hex, and multiply by 2)
High Byte: Door direction (0 = up, 2 = down, 4 = right, 6 = left)
* {{$|19A0}}[{{0x|10}}] = Door tilemap address
* {{$|19B0}}[{{0x|10}}] = For doors that have two halves, this is the tilemap address for the other half
* {{$|19C0}}[{{0x|20}}] = Door direction. 0 - up, 1 - down, 2 - left, 3 - right
* {{$|19E0}}[{{0x|02}}] = current door index when loading doors
* {{$|19E2}}[{{0x|08}}] = Seems to store the addresses of up to 4 different exit doors.
* {{$|19EA}}[{{0x|16}}] = free ram
* {{$|1A00}}[{{0x|14}}] = These $1AXX addresses seem to be related to tagalongs, that's the best I can tell so far
* {{$|1A14}}[{{0x|14] -
* {{$|1A28}}[{{0x|14] -
* {{$|1A3C}}[{{0x|14] -
* {{$|1A50}}[{{0x|14}}] = see Bank 09
* {{$|1A64}}[{{0x|14}}] = Tagalong priority bits
* {{$|1A78}}[{{0x|??}}] = ????
* {{$|1B00}}[{{0x|1C0}}] = indirect HDMA pointers for the spotlights that open and close when leaving/entering doors
* {{$|1CC0}}[{{0x|10}}] = free ram?
Text related variables ($1CD0}}[{{0x|20])
}}[{{0x|02}}] = When drawing the message box border, the value of $1CD2 gets stored here during initialization.
It is subsequently used as an index for forming DMA transfers that will copy the tilemap entries of the
message box border during the NMI interrupt.;
* {{$|1CD2}}[{{0x|02}}] = The VRAM position of upper left corner of the message box. This only has one of two values, and they
are
designed to not obscure Link's sprite.
* {{$|1CD4}}[{{0x|01}}] = Second Level controller for Module 0x0E.0x02
* {{$|1CD5}}[{{0x|01}}] = Maybe the current position the message is outputting to?
* {{$|1CD5}}[{{0x|01}}] = Mirror of speed below... but... not sure why this is different
$1CD6}}[{{0x|01}}] = Speed XX
* {{$|1CD7}}[{{0x|01}}] = ???? related to [window 01] (not used in game)
* {{$|1CD8}}[{{0x|01}}] = First Level controller for Module 0x0E.0x02 (i.e. it controls the sub-submodule)
* {{$|1CD9}}[{{0x|02}}] = Number of bytes into the $7F1200 buffer for the processed characters of the dialogue.
* {{$|1CDB}}[{{0x|01}}] = free ram
* {{$|1CDC}}[{{0x|01}}] = This is supposedly some kind of color variable according to Hyrule Magic but I can't find any affect to
using it. It's modified by the [Color XX] command in the monologue editor. This was included
presumably before they implemented a VWF, and used single or double spaced characters? The
reasoning being, with such a font you can set the colors for individual characters much more easily.
With 2bpp font characters you don't have a lot of available variety for colors in a single tile anyways.
* {{$|1CDD}}[{{0x|02}}] = Number of bytes into the source buffer for the dialogue message.
* {{$|1CDD}}[{{0x|02}}] = (alternate) - once the text begins being processed, this is instead the tile position for the output
0x00 is the first line, 0x28 is the second line, 0x50 is the third line
* {{$|1CDF}}[{{0x|01}}] = Used in [Scroll] command, not sure what else
* {{$|1CE0}}[{{0x|02}}] = ???? referenced in [Wait XX]
* {{$|1CE2}}[{{0x|02}}] = Is the template for the text message's tilemap. Each character has a tilemap value that differs
only in CHR
[Color XX] can change the palette (out of 8) obviously.
Changing this value can also alter the h-flip and v-flip, as
well as priority settings. Generally speaking you wouldn't want to do that unless you had a good reason.
* {{$|1CE4}}[{{0x|02}}] = free ram
* {{$|1CE6}}[{{0x|02}}] = Perhaps this is the graphical position of where the next character goes?
* {{$|1CE8}}[{{0x|01}}] = For a multi selection box with two choices, this is either 0 (the top choice) or 1 (the bottom choice)
* {{$|1CE9}}[{{0x|01}}] = This is a delay timer for the [WaitKey] command. Starts at 0x1C, when it counts down to zero
it starts looking for player input. (basically this is 1/3 of a second and is probably there to
give the game more time to draw its text
* {{$|1CEA}}[{{0x|01}}] = Determines how many times to scroll the text up by one pixel per frame
Only applies during the [Scroll] command and is set by the [ScrollSpd XX]
command. However, some other commands may inadvertently affect this address.
E.g. [Name], [Position XX]. As there is no logical connection I can only guess
that this was a coding oversight.
* {{$|1CF0}}[{{0x|02}}] = Dialogue Message Index. e.g. 0005 = "you can't enter with something following you"
This is the same numerical value that can be viewed in Hyrule Magic
(except there they're in decimal.)
* {{$|1CF2}}[{{0x|02}}] = Numeric parameter that can be passed to text messages. It goes as follows.
first byte: low nybble corresponds to [Number 00], high nybble to [Number 01]
second byte: low nybble is [Number 02], high nybble is [Number 03]
If you're confused see message number 004 in Hyrule Magic's dialogue editor.
586$1CF4}}[{{0x|01}}] = Used to save the value of $1CE8 when the save and continue box comes up
* {{$|1CF5}}[{{0x|0B}}] = free ram
* {{$|1D00}}[{{0x|10}}] = Cache for $0DD0
* {{$|1D10}}[{{0x|10}}] = Cache for $0E20
* {{$|1D20}}[{{0x|10]
* {{$|1D30}}[{{0x|10]
* {{$|1D40}}[{{0x|10]
* {{$|1D50}}[{{0x|10]
-
-
-
-
Cache for $0D10
Cache for $0D30
Cache for $0D00
Cache for $0D20
* {{$|1D60}}[{{0x|10}}] = Cache for $0DC0
* {{$|1D70}}[{{0x|10] -
* {{$|1D80}}[{{0x|10] -
* {{$|1D90}}[{{0x|10] -
* {{$|1DA0}}[{{0x|10] -
* {{$|1DB0}}[{{0x|10] -
* {{$|1DC0}}[{{0x|10] -
* {{$|1DD0}}[{{0x|10] -
* {{$|1DE0}}[{{0x|10] -
* {{$|1DF0}}[{{0x|10] -
Cache for $0D90
Cache for $0EB0
Cache for $0F50
Cache for $0B89
Cache for $0DE0
Cache for $0E40
Cache for $0F20
Cache for $0D80
Cache for $0E60
* {{$|1E00}}[{{0x|01}}] = Step counter during the Triforce sequence at the beginning.
* {{$|1E08}}[{{0x|01}}] = see module 0x14
* {{$|1E09}}[{{0x|01}}] = see module 0x14
* {{$|1E0A}}[{{0x|01}}] = Seems to be a frame counter (loops at 0xFF) used for various delays and timing
of events during the Triforce or Crystal sequences
* {{$|1E10}}[{{0x|01] -
* {{$|1E68}}[{{0x|98}}] = free ram???
* {{$|1F00}}[{{0x|01}}] = Flag that when set, tells IRQ to activate
* {{$|1F0A - Use to swap out the two different stacks. (the $1F00 region and the $1FF region)
* {{$|1F0C - Related to IRQs?
* {{$|1F32-$1F3F - Contains data to use when coming out of the IRQ. Including a return address, the Data Bank Register, the
Direct Page register (gets set to $1F00), and various other data. It took a while to figure this out, believe me.

← Older revision	Revision as of 22:32, 20 December 2016
(No difference)

RAM: Bank 0x7E: Pages 0x10 to 0x1F - Revision history

Superskuj: Superskuj moved page Rom/Pages 0x10 to 0x17 to RAM: Bank 0x7E: Pages 0x10 to 0x1F

Tatters: Created page with "* {{$|1000}}[{{0x|02}}] = For transfers that use variable $14, this indicates the current length written into the buffer starting at * {{$|1002 Seems to be addresses used for..."