Rooba
/
ReC98
mirror of https://github.com/nmlgc/ReC98.git
1
1
Fork 0
Code Issues Packages Projects Releases Wiki Activity
ReC98/th04/hardware/fillm64-56_256-256.asm

42 lines
1008 B
NASM
Raw Normal View History

[Reverse-engineering] [th04/th05] Playfield fill-around function names These are used from quite a few places, so it seems best to just name them after the rect on the playfield they leave out, which is then typically where the background picture goes. …*except* that in doing this, we quickly run up against the symbol length limit of 32 characters. TASM can expand it via the /mv option, but TCC only lets you *reduce* it to even less. (Why?) So, my initial idea of `playfield_fill_around_(x)_(y)_(w)_(h)` wouldn't have worked. But those coordinates are kinda important, I'd say… Well then, let's just go with `fillm` instead of `fill_around` then. "Fill with mask at the given coordinates"… yeah, that would work. Part of P0029, funded by zorg.
2019-09-13 09:44:21 +00:00
; Fills the playfield around the 256×256 pixels starting at (64, 56) with the
; current GRCG tile.
; Assumes that the GRCG is set to TDW mode.
[Naming] [th04/th05] Boss-specific names for backdrop colorfill functions Once we decompile whatever can be decompiled of those, we're going to use the same coordinate constants for both these and the backdrop image. Ideally, we can even macro (or inline-function) away the entire implementation, so that the redundancy between TH04's and TH05's Stage 4 bosses won't matter as much. Part of P0189, funded by Arandui and Lmocinemod.
2022-04-02 23:03:58 +00:00
public @REIMU_MARISA_BACKDROP_COLORFILL$QV
public @MAI_YUKI_BACKDROP_COLORFILL$QV
label @mai_yuki_backdrop_colorfill$qv near
@reimu_marisa_backdrop_colorfill$qv proc near
[Reverse-engineering] [th04/th05] Playfield fill-around function names These are used from quite a few places, so it seems best to just name them after the rect on the playfield they leave out, which is then typically where the background picture goes. …*except* that in doing this, we quickly run up against the symbol length limit of 32 characters. TASM can expand it via the /mv option, but TCC only lets you *reduce* it to even less. (Why?) So, my initial idea of `playfield_fill_around_(x)_(y)_(w)_(h)` wouldn't have worked. But those coordinates are kinda important, I'd say… Well then, let's just go with `fillm` instead of `fill_around` then. "Fill with mask at the given coordinates"… yeah, that would work. Part of P0029, funded by zorg.
2019-09-13 09:44:21 +00:00
push di
[Maintenance] Rename all old *_X and *_Y constants to *_LEFT and *_TOP Part of P0112, funded by [Anonymous] and Blue Bolt.
2020-08-25 18:29:24 +00:00
mov ax, GRAM_400 + (PLAYFIELD_TOP * ROW_SIZE) shr 4
[Reverse-engineering] [th04/th05] Playfield fill-around function names These are used from quite a few places, so it seems best to just name them after the rect on the playfield they leave out, which is then typically where the background picture goes. …*except* that in doing this, we quickly run up against the symbol length limit of 32 characters. TASM can expand it via the /mv option, but TCC only lets you *reduce* it to even less. (Why?) So, my initial idea of `playfield_fill_around_(x)_(y)_(w)_(h)` wouldn't have worked. But those coordinates are kinda important, I'd say… Well then, let's just go with `fillm` instead of `fill_around` then. "Fill with mask at the given coordinates"… yeah, that would work. Part of P0029, funded by zorg.
2019-09-13 09:44:21 +00:00
mov es, ax
assume es:nothing
[Maintenance] Rename all old *_X and *_Y constants to *_LEFT and *_TOP Part of P0112, funded by [Anonymous] and Blue Bolt.
2020-08-25 18:29:24 +00:00
mov di, (55 * ROW_SIZE) + PLAYFIELD_VRAM_LEFT
[Reverse-engineering] [th04/th05] Playfield fill-around function names These are used from quite a few places, so it seems best to just name them after the rect on the playfield they leave out, which is then typically where the background picture goes. …*except* that in doing this, we quickly run up against the symbol length limit of 32 characters. TASM can expand it via the /mv option, but TCC only lets you *reduce* it to even less. (Why?) So, my initial idea of `playfield_fill_around_(x)_(y)_(w)_(h)` wouldn't have worked. But those coordinates are kinda important, I'd say… Well then, let's just go with `fillm` instead of `fill_around` then. "Fill with mask at the given coordinates"… yeah, that would work. Part of P0029, funded by zorg.
2019-09-13 09:44:21 +00:00
nop
@@rows_next:
mov cx, PLAYFIELD_VRAM_W / 4
@@rows_top_and_bottom:
mov es:[di+(312 * ROW_SIZE)], eax
stosd
loop @@rows_top_and_bottom
sub di, ROW_SIZE + PLAYFIELD_VRAM_W
jge short @@rows_next
[Maintenance] Rename all old *_X and *_Y constants to *_LEFT and *_TOP Part of P0112, funded by [Anonymous] and Blue Bolt.
2020-08-25 18:29:24 +00:00
mov ax, GRAM_400 + ((56 + PLAYFIELD_TOP) * ROW_SIZE) shr 4
[Reverse-engineering] [th04/th05] Playfield fill-around function names These are used from quite a few places, so it seems best to just name them after the rect on the playfield they leave out, which is then typically where the background picture goes. …*except* that in doing this, we quickly run up against the symbol length limit of 32 characters. TASM can expand it via the /mv option, but TCC only lets you *reduce* it to even less. (Why?) So, my initial idea of `playfield_fill_around_(x)_(y)_(w)_(h)` wouldn't have worked. But those coordinates are kinda important, I'd say… Well then, let's just go with `fillm` instead of `fill_around` then. "Fill with mask at the given coordinates"… yeah, that would work. Part of P0029, funded by zorg.
2019-09-13 09:44:21 +00:00
mov es, ax
assume es:nothing
[Maintenance] Rename all old *_X and *_Y constants to *_LEFT and *_TOP Part of P0112, funded by [Anonymous] and Blue Bolt.
2020-08-25 18:29:24 +00:00
mov di, (255 * ROW_SIZE) + PLAYFIELD_VRAM_LEFT
[Reverse-engineering] [th04/th05] Playfield fill-around function names These are used from quite a few places, so it seems best to just name them after the rect on the playfield they leave out, which is then typically where the background picture goes. …*except* that in doing this, we quickly run up against the symbol length limit of 32 characters. TASM can expand it via the /mv option, but TCC only lets you *reduce* it to even less. (Why?) So, my initial idea of `playfield_fill_around_(x)_(y)_(w)_(h)` wouldn't have worked. But those coordinates are kinda important, I'd say… Well then, let's just go with `fillm` instead of `fill_around` then. "Fill with mask at the given coordinates"… yeah, that would work. Part of P0029, funded by zorg.
2019-09-13 09:44:21 +00:00
nop
@@cols:
mov es:[di+(320 / 8)], eax
stosd
mov es:[di+(320 / 8)], eax
stosd
sub di, ROW_SIZE + 8
jge short @@cols
pop di
retn
[Naming] [th04/th05] Boss-specific names for backdrop colorfill functions Once we decompile whatever can be decompiled of those, we're going to use the same coordinate constants for both these and the backdrop image. Ideally, we can even macro (or inline-function) away the entire implementation, so that the redundancy between TH04's and TH05's Stage 4 bosses won't matter as much. Part of P0189, funded by Arandui and Lmocinemod.
2022-04-02 23:03:58 +00:00
@reimu_marisa_backdrop_colorfill$qv endp
[Reverse-engineering] [th04/th05] Playfield fill-around function names These are used from quite a few places, so it seems best to just name them after the rect on the playfield they leave out, which is then typically where the background picture goes. …*except* that in doing this, we quickly run up against the symbol length limit of 32 characters. TASM can expand it via the /mv option, but TCC only lets you *reduce* it to even less. (Why?) So, my initial idea of `playfield_fill_around_(x)_(y)_(w)_(h)` wouldn't have worked. But those coordinates are kinda important, I'd say… Well then, let's just go with `fillm` instead of `fill_around` then. "Fill with mask at the given coordinates"… yeah, that would work. Part of P0029, funded by zorg.
2019-09-13 09:44:21 +00:00
even