The community installer that puts the Titanfall 2 VR conversion onto a PC has gone through EIGHT PUBLIC builds in roughly a WEEK, and the NUMBERS on its own GitHub release page now tell a MESSIER story than the “press play and go” reputation it earned in early reviews. The CircuitLord VR Mod Installer releases page, read at about 20:45 UTC on October 7, shows the most-downloaded Titanfall 2 VR mod file is a BETA package that, by the project’s own README RULE, should no longer appear as an OPTION.
Eight builds, one week
GitHub’s release feed timestamps v1.2.0, whose entire note reads “release multi-game support starting with Titanfall 2 VR,” at 22:43 UTC on September 29. The NEWEST build, v1.2.9, landed at 07:08 UTC on October 6. In between came v1.2.3, v1.2.4, v1.2.5, v1.2.6, v1.2.7 and v1.2.8. Three of those builds (v1.2.3, v1.2.4 and v1.2.5) shipped on September 30 ALONE, and v1.2.4 was REPLACED by v1.2.5 in LESS than two hours. No v1.2.1 or v1.2.2 appears on the release list.
MIXED counted six builds (v1.2.4 through v1.2.9) between September 30 and October 6, which is accurate for that WINDOW. Widening the window by a few hours to include the first Titanfall-capable release and its first fix makes it EIGHT.
The download COUNTERS attached to each build’s single installer file, read on October 7, are:
- v1.2.8 (October 3): 17,208
- v1.2.7 (October 2): 14,026
- v1.2.6 (October 1): 10,596
- v1.2.9 (October 6): 10,178
- v1.2.5 (September 30): 6,763
- v1.2.3 (September 30): 1,385
- v1.2.4 (September 30): 478
- v1.2.0 (September 29): 106
That is 60,740 installer downloads across the EIGHT builds, and 59,249 for the six MIXED tracked, UP from the 54,100 MIXED recorded at 23:21 UTC on October 6. These are RAW fetch counts. They do not measure UNIQUE PLAYERS, and they say NOTHING about how many people actually reached the campaign in a HEADSET.
The most-downloaded mod file is a beta
The installer is a DOWNLOADER as much as a setup tool. Per its README, a file called manifest-v3.json lists each mod release with its download URL and hash, and the app compares it against what is installed. Mod entries can carry optional “channels,” such as a beta, that users pick from a version dropdown.
The Titanfall 2 VR packages hosted on the same release page show this SPLIT:
Titanfall2VR-beta-1.0.12.zip: 14,482 downloadsTitanfall2VR-1.0.13.zip: 9,445 downloadsTitanfall2VR-1.0.14.zip: 5,164 downloads
The CURRENT manifest names 1.0.14 as the STABLE Titanfall 2 VR release and still lists a beta channel, described as “New features, may be unstable,” pointing at version 1.0.12. The README states that “a channel shows only while its version is newer than stable.” Since 1.0.12 is OLDER than 1.0.14, that rule means the beta should now be HIDDEN from the dropdown. The project has not EXPLAINED why the beta file LEADS the count. The plausible readings (that the beta was the main route for early players, or that clients fetched it repeatedly) are UNCONFIRMED, and the counters cannot SEPARATE them.
What the notes are actually fixing
Most of the week’s release notes read as a support queue. v1.2.3 promises to “explain openxr launch failures” and to “request admin access when game is installed in program files.” v1.2.6 says “launch stops when other mods replace dxgi.dll or d3d11.dll,” a BEHAVIOR change, not just better LOGGING, that will matter to anyone running other graphics mods in the same folder. v1.2.7 and v1.2.8 both widen CRASH reporting.
The newest build adds a WRINKLE. v1.2.9 “warns before VR launch when Steam, the EA app, or the installer run as admin,” and makes mod updates OPTIONAL at launch. Four builds earlier, v1.2.3 began requesting admin access for Program Files installs. The notes do not say how the two INTERACT, and a search of the repository’s issues and pull requests for “dxgi” returned ZERO results on October 7, so there is no public list of which mods trigger the v1.2.6 block. GitHub’s repository counter showed 69 open issues and pull requests combined, 20 forks and 1,124 stars.
Why the installer is the story
UploadVR’s October 6 hands-on argued the installer is the best thing about the mod, writing that “installers for mods are nothing new, but rarely are they this painless.” The README backs the design: it locates Titanfall 2 through a Steam, EA or Xbox install, checks for the EA app, and installs Northstar plus the mod into a separate TF2VR profile, so a normal launch STAYS UNMODDED and VR saves live in their own LocalAppData folder.
Both things can be true. A one-click tool REMOVES the FRICTION that has kept many headset owners away from PC VR mods, and it also CONCENTRATES every update, bug fix and rollback through one developer’s manifest at a pace of more than a build a day. The README is explicit that this is UNSANCTIONED: “These mods and this installer are community projects, not affiliated with or endorsed by the game developers or publishers. Use at your own risk.” The installer code is MIT-licensed; the mods themselves are CLOSED source. Respawn and EA have not COMMENTED.
Metaverse Watcher first covered the mod’s arrival on October 2, when CircuitLord’s Titanfall 2 VR conversion landed with manual reloads and Titan controls. For players, the PRACTICAL guidance from the notes is NARROW: run the LATEST build, avoid launching Steam, the EA app or the installer as ADMINISTRATOR, and expect the VR launch to REFUSE to start if another mod has replaced dxgi.dll or d3d11.dll.
Sources: CircuitLord VR Mod Installer releases, README and manifest (read October 7, 2026); MIXED, October 7; UploadVR, October 6.