Replace the SSE-translated parse chain with byte-permute kernels: one vqtbl2q_u8 builds m[0] (S/T/RGBA/Q gathered from the STQ+RGBAQ qwords — the legacy RGBA pack alone was ~11 NEON ops), and for XYZF2 a shared USHR #4 plus one vqtbl2q_u8 over {r2, r2>>4} builds m[1], with out-of-range TBL indices providing the 24-bit Z and 8-bit F masks for free. XYZ2 takes a single-register TBL for the low half and inserts {UV, FOG} as one 64-bit lane. The Q==+0.0 -> FLT_MIN rewrite folds to CMEQ+AND+ORR against a lane-3-only constant. Handlers call the new _Fast dispatchers: aarch64 takes the TBL kernels (GS_VERTEX_CROSSCHECK builds run the legacy kernels alongside and pxAssertRel bit-equality per vertex); x86 keeps the legacy path unchanged. Gates: gs_vertex_tests 9/9 including 2M-case NEON-vs-scalar-model sweeps; gsrunner frame hashes bit-identical to the GV-0 baseline (15 dumps, sw + vulkan); crosscheck build replayed all 15 dumps with zero divergence assertions. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
yaps2
This is a fork of PCSX2 targeting ARM based linux handheld devices. We're aiming to be performant and compatible on lower end ARM hardware, and adopt a "by any means" philosophy.
Thanks
A massive thank you to the PCSX2 team for 20 years of dedication. yaps2 doesn't meet the rigor required of PCSX2 upstream commits, but maybe someday it will.
The following people worked on the yaps2 fork of this project:
- bmdhacks
- tokyovigilante
- pstef
FAQ
Is it good?
A: Yeah. It's pretty fast.
Where do I get builds of this software?
A: Builds are available in nightly releases of Rocknix and Batocera
Did you vibe code it? I see that claude authors your commits you cheater!
A: This fork was written by seasoned developers using LLM devleopment tools. Our philosophy is focused on results, not policing methodology, and modern LLM tools are the most effective way for us to reach our goals.
Can I contribute?
A: Sure. Send a PR. If it's vibe-coded trash we'll reject it. If it's good we'll use it.
Can I fork this project for my own purposes?
A: Sure. If you do cool stuff we'll probably use your code.
Don't you know about XYZ project that already does this
A: Yes we probably copied a lot of their techniques.
Can I make feature requests or tell you that I don't like what you're doing or how you're doing it?
A: Look, we're not trying to be a serious project here so no.
Can I make bug reports?
A: Absolutely, file a github issue and we might look at it.