PCSX2 pre-release v2.7.127 adds EyeToy macOS support; Feb 12 date discrepancy
PCSX2 pre-release v2.7.127 adds EyeToy camera support on macOS (commit e5c580a), while a ReleaseAlert entry dated Feb 12 conflicts with GitHub snippets dated Feb 14–15.

PCSX2 pre-release tag v2.7.127 is listed with the one-line note "USB: Implement EyeToy camera support on macOS" and the commit e5c580a, and appears in the supplied GitHub snippets as a Pre-release entry with "Assets 7" and "2 people reacted." The v2.7.127 snippet contains the exact release text but the provided fragment does not include an explicit timestamp.
The supplied GitHub snippets show a run of pre-release tags from v2.7.119 through v2.7.126 with explicit timestamps and commit hashes. v2.7.126 is dated 15 Feb 23:37, authored by github-actions, commit 763d005, and lists "QT: Add -turbo and -unlimited commandline parameters" with "Assets 7" and "3 people reacted." v2.7.125 is dated 15 Feb 22:40, commit 23b931c, and carries "GS/HW: Optimize GPU CLUT update frequency + convert GS draw count to u64" with "Assets 7" and "2 people reacted."
Earlier entries in the same snippet set include v2.7.124 (15 Feb 22:13) in two preserved variants: a truncated listing and a fuller line tied to commit aa04e57 with the note "GS: Fix missing GSVector4i constructor in GSVector4i::hsub32" and "1 person reacted." v2.7.123 shows commit 99a8afa dated 15 Feb 20:32 with "Achievements: Fix Active Challenges bucket with subsets" and "Assets 7." v2.7.122 (commit 16fde28, 15 Feb 19:28) lists "GS: Don't try to anti-blur if both displays are alternating" while v2.7.121 (commit fa85ef3, 15 Feb 02:58) lists "GS: Remove OpenGL/CL compat check," each showing "Assets 7" and reactions where provided.
The chronology in the snippets continues back to v2.7.120 (commit 1213621, 14 Feb 21:04) with "GS/HW: Merge together adjacent tristrips in drawlist." and v2.7.119 (14 Feb 15:19) with "CMake: Remove dead link." Every GitHub snippet preserved in the supplied material displays the UI label "Pre-release" and the repeated UI artifact "Loading" followed by "### Uh oh! There was an error while loading. Please reload this page." in the truncated captures.

A separate release-tracking data point appears in the assembled materials. The original report explicitly states: "Release tracking services and the PCSX2 project metadata indicate a PCSX2 release artifact or packaging activity dated February 12, 2026 (ReleaseAlert shows a last-published entry for a PCSX2 Git release on that date)." That Feb 12 date in ReleaseAlert does not match the Feb 14–15 timestamps shown in the GitHub snippets for v2.7.119 through v2.7.126, and the provided fragment for v2.7.127 lacks a visible timestamp to reconcile with the Feb 12 entry.
The preserved materials also document duplicated and truncated UI captures: v2.7.124 appears twice in the dataset, many entries list "Assets 7," several entries show the actor string "github-actions," and reaction counts vary by tag (for example, v2.7.126 shows "3 people reacted," v2.7.127 shows "2 people reacted"). The assembled notes recommend explicit verification steps: confirm which tag or artifact maps to the ReleaseAlert Feb 12 entry, and verify whether v2.7.127 (commit e5c580a) has an associated GitHub release timestamp that resolves the mismatch.
For now, the concrete takeaway for builders and testers is that the PCSX2 pre-release series includes a direct USB/EyeToy macOS entry at v2.7.127 and a cluster of pre-release changes across v2.7.119–v2.7.126 with precise commit hashes and timestamps in the supplied snippets; the February 12 ReleaseAlert artifact remains an unresolved date discrepancy in the source materials.
Know something we missed? Have a correction or additional information?
Submit a Tip

