LibretroAdmin 39be4f3627 GS: auto flush always, through handlers chosen by the draw state ...

The vertex kick handlers come in two sets, plain and auto-flush, and
which one a draw kicks through is chosen when a register that decides it
is written -- TEX0 and TEX2, TEST, FRAME and ZBUF of the current context,
PRIM and PRMODE -- and changes only when the answer does: the draw state
reads what it draws. Every other draw kicks through the plain handlers,
which do not ask, where before every kick asked whenever auto flush was
on (by default in the software renderer, and in the hardware renderer
for every game the database turned it on for).

Auto flush is now always on, for every primitive, in both renderers.
The hardware level setting, the software switch, their core options and
the GameDB fix and its entries go.

tests/gsautoflush/autoflush_select pins the choice against the state
after every register write.

2026-11-04 15:15:55 +01:00

..

build.sh

Patch: the loaded patches, the pnach parser and the loaders in C

2026-11-03 22:29:43 +01:00

dbload.cpp

GS: auto flush always, through handlers chosen by the draw state

2026-11-04 15:15:55 +01:00

dbparse.cpp

Patch: the loaded patches, the pnach parser and the loaders in C

2026-11-03 22:29:43 +01:00

ingame_glue.cpp

Patch: the loaded patches, the pnach parser and the loaders in C

2026-11-03 22:29:43 +01:00

ingame.c

tests/patch: the built-in patch harness in C89

2026-10-08 20:10:32 +02:00

mkzips.py

Patch: the loaded patches, the pnach parser and the loaders in C

2026-11-03 22:29:43 +01:00

pnachload.cpp

Patch: the loaded patches, the pnach parser and the loaders in C

2026-11-03 22:29:43 +01:00