PSVR2Toolkit: an unofficial PlayStation VR2 driver modification for use on a PC

What the modification adds to the official driver

PSVR2Toolkit is an unofficial modification for the official PlayStation VR2 driver and app, which aims to improve your PlayStation VR2 experience on PC.

The feature list is specific. There is Linux support through a separate project called Ignition. There is eye tracking with calibration, a camera feed with Babble support, and assisted IPD adjustment. The Play Area setup is improved, as are controller prediction, controller haptics through PCM haptics, and controller tracking with custom LED sync. There is SteamVR Room View passthrough, a Night Mode, and runtime refresh rate switching which is NVIDIA-only. The list continues with adaptive features beyond that point.

The shape of this is worth reading carefully. It is not a reimplementation of the headset protocol, it is a modification of the official driver with additional capabilities layered on, and the Linux support in particular is provided by a companion project rather than by this one. That means the toolkit is a host-side wrapper for the official driver plus a set of extensions, and the driver itself remains the vendor's.

The project is written in C++, MIT licensed, and the last push was on 2026-10-17. The release history shows v1.0.0-experimental-2 in September 2026, v1.0.0-experimental-1 in July 2026 and v0.2.1 in January 2026 marked as a pre-release.

The terms the project puts on its own users

The README opens with a warning that is unusual and worth reading in full.

It says that if you have paid for PlayStation VR2 Toolkit you have been scammed and should immediately request a refund, because the toolkit is entirely free and is intended for non-commercial use only, and that the authors do not attempt to profit from it. On top of that, eye tracking data from the toolkit must not be used in commercial environments or for commercial purposes.

That is a stronger statement than a licence clause, because it is aimed at people who might assume a paid version exists, and it is plausible that such versions have been sold by third parties. The project is drawing that line explicitly and the practical effect is that anyone considering this should expect it to remain free.

The disclaimer text itself is standard: the software is provided as is, without warranty of any kind, express or implied, including the warranties of merchantability, fitness for a particular purpose and noninfringement, and the authors are not liable for any claim or damages. And there is a separate note that Bnuuy Solutions and PlayStation VR2 Toolkit is not affiliated with Sony Interactive Entertainment, and that the project is not official or endorsed by Sony in any way, with Sony, Sony Interactive Entertainment and the PlayStation VR2 names noted as trademarks of Sony Interactive Entertainment LLC.

The MIT licence sits alongside those terms, which is a slightly unusual combination but not a contradiction, since the licence governs the code and the warnings govern the use.

Why a driver modification exists at all

The reason this project exists is a hardware and software mismatch, and the reason the mismatch is interesting is that the driver is the vendor's.

The PlayStation VR2 was designed to run on the PlayStation 5. The hardware itself is capable, but the official driver is where the PlayStation assumptions live, and that is what makes the PC experience limited out of the box. Modifying the driver is therefore a way of changing what the vendor's code will accept, rather than a reimplementation of the headset.

The features that need the modification are the ones that depend on driver-level behaviour. Controller tracking with custom LED sync, PCM haptics and assisted IPD adjustment are all things the driver has to be willing to do, and a userspace application cannot achieve them on its own. The features that do not need it, such as SteamVR Room View passthrough and Night Mode, are more likely to be application or runtime level.

The Linux support is the other half of the story, and the fact that it lives in a separate project called Ignition tells you the division of labour. The toolkit is the modification, and Ignition is the host integration, which is a sensible separation for a project that has to keep working across two operating systems with different driver models.

The experimental release labels are the honest signal about maturity. A project named 1.0.0 with an experimental suffix in the tag is telling you that the version number reflects the toolkit's own scheme rather than a promise of stability.

What a driver modification means for your setup

Because the toolkit changes the vendor's driver rather than replacing it, the practical consequences are about the host system rather than about the feature list.

On Windows, the modified driver is installed in place of, or alongside, the official one, and the headset and the controllers are then driven through it. On Linux, the host integration is the separate Ignition project, so the toolkit and Ignition have to be matched to each other and to the Linux stack, which is where version mismatches show up as a headset that is detected but not tracked.

The features that depend on driver behaviour are the ones most sensitive to this. Custom LED sync for controller tracking, PCM haptics and assisted IPD adjustment all require the driver to do something the official one does not, and they are the first things to check after an update changes the driver's internals.

A related consideration is what an update does to the modification. The PlayStation VR2 driver ships with the headset's software and can be updated, and a modification built against one driver version may not survive another. The project's release naming, with an experimental suffix on the 1.0.0 tags, is a reasonable signal that it expects to be rebuilt against driver changes rather than to survive them untouched.

None of that makes the toolkit unsuitable for its stated purpose, which is a personal PlayStation VR2 setup on a PC. It does mean it is a project to follow rather than to deploy, and the non-commercial terms are consistent with that.

Editorial conclusion

PSVR2Toolkit fits a PlayStation VR2 owner who wants to use the headset on a PC, with or without Linux, and who is willing to run a modified driver. It does not fit a commercial deployment, which the project rules out in writing, and it does not carry any of the assurance an official driver carries. Before using it, read the non-commercial terms and the data conditions, confirm your headset and controller revisions are supported, and treat the eye tracking restriction as binding, because the project states that eye tracking data must not be used in commercial environments.

Frequently asked questions

Official sources

1. BnuuySolutions/PSVR2Toolkit on GitHub
2. Issues
3. License: MIT
4. README
5. Releases