UEVR: a process injector with three rendering modes and a pre-injection checklist
Universal Unreal Engine VR Mod (4.8 - 5.4)
At a glance
- What is it?
- UEVR adds virtual reality to running Unreal Engine titles by injecting into the process from a Windows GUI, choosing an OpenVR or OpenXR runtime and one of three rendering strategies. The engine support stops at version 5.4, the newest release is 1.05, and the pre-injection checklist runs to six items next to the seven injection steps.
- Who is it for?
- UEVR fits a player who has a flat Unreal Engine title, a headset and an appetite for troubleshooting, and who is comfortable reading a rendering mode comparison before pressing inject. It does not fit anyone wanting a one-click conversion, because the pre-injection checklist exists precisely because the process injection is fragile, and it does not cover anything outside Unreal Engine 4.8 to 5.4.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- Yes. The repository last received commits 77 days ago.
- What is it written in?
- Mainly C++, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- praydog/UEVR4,683 ★ · +150
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| praydog/UEVR | 4.5k | 4.7k |
150 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The engine version is the hard boundary: 4.8 to 5.4
Everything else in this project is conditional on one fact, and the file states it twice. The supported engine versions are 4.8 to 5.4, and the title itself says it is a universal mod for Unreal Engine 4 and 5. So this is not a general VR injector and not a wrapper around a game engine runtime; it targets one engine family inside a version window, and a title built with a newer Unreal release is out of scope by definition rather than by bug. The runtime prerequisites are also specific: install the .NET 6.0 SDK before launching, which the injector will point you to on first open if it is missing, with a download link as the fallback and a note that most people want the x64 installer under the Windows column.
Seven injection steps, starting with running the injector
The procedure is short and manual. Download the latest release, then launch the injector executable, launch the target game, find that game in the process dropdown list, select the runtime you want between OpenVR and OpenXR, toggle VR plugin nullification if the title needs it, configure the pre-injection settings, and inject. Four names carry the whole workflow:
UEVRInjector.exe
-nohmd
Insert
L3+R3Two details in that sequence do real work. Finding the game in a process list means the injector attaches to an already-running executable rather than launching the game itself.
The checklist before injection is longer than the injection itself
Six items are listed under to-dos, and they read like a list of things that have caused someone else's crash. Disable HDR, with the honest note that it still works without it but the game will look darker than usual. Start as administrator if the game does not appear in the process list at all. Pass -nohmd to the game's command line, and or delete VR plugins from the game directory, when the game contains existing VR plugins. Disable any overlays that may conflict and cause crashes, naming Rivatuner, ASUS software, Razer software and Overwolf. Disable in-game graphics options that cause crashes or severe issues, giving DLSS Frame Generation as the example. And consider disabling Hardware Accelerated GPU Scheduling in the Windows graphics settings.
Native stereo looks best and breaks loudest
The rendering comparison is the most useful part of the documentation, and it is organised as a preference order rather than as feature flags. Native Stereo comes first and is described as looking the best and performing the best, usually, with the caveat that it can cause crashes or graphical bugs if the game does not play well with it. The mechanism is the honest one: it uses the actual stereo rendering pipeline inside Unreal Engine, with fully synchronized eye rendering, which is why it works with the majority of games. Its specific advantage is that temporal effects stay intact, with TAA fully working and DLSS or FSR 2 usually fine with no ghosting. So the mode you want is also the one that punishes a badly behaved title.
Synchronized Sequential is the fallback, and Skip Tick is the bargain
The second mode is a form of alternating frame rendering that can fix many of the bugs Native Stereo introduces, and the cost is temporal. It renders two frames sequentially in a synchronized fashion on the same engine tick, and the game world does not advance time between frames. It looks normal to the eye, but temporal effects like TAA ghost or double, and motion blur has to be turned off. Two sub-options decide how it behaves. Skip Draw skips the viewport draw on the next engine tick, which usually works best but sometimes leaves particle effects playing at the wrong speed. Skip Tick skips the next engine tick entirely, which is described as usually buggy but does fix particle effects and sometimes brings higher performance.
AFR is named as a last resort, with the symptom given
The third mode is not recommended and the file does not hedge. Alternated Frame Rendering renders each eye on separate frames in an alternating fashion with the game world advancing time in between, which means it is not synchronized. The stated consequence is eye desyncs and usually nausea along with them, and the guidance is that it should not be used unless the other two are unusable in some way. The honest reading of the whole section is that you are choosing between fidelity that breaks some games and fidelity that makes some people ill, and that the tool's own authors rank the modes in exactly that order.
The in-game menu is Insert or L3+R3, with RT held for moves
Adjustment happens without leaving the game. Press the Insert key, or L3 and R3 on an XInput controller, and the in-game menu appears, opening by default at startup. Holding RT gives the shortcuts: RT with the left stick moves the camera left, right, forward and back, RT with the right stick moves it up and down, RT with B resets the camera offset, RT with Y recenters the view, and RT with X resets the standing origin. That last distinction is the useful one for roomscale titles, since moving the origin and moving the camera are separate operations and getting them confused is what makes a seated player feel lost.
Plugins are C++ or Blueprint, and Lua has its own directory
For anyone extending it rather than just running it, the feature list points at a C++ plugin system and Blueprint support, both documented on a separate documentation site, described as the way for modders to add features like motion controls to games that lack them. The repository layout backs that up with an examples directory holding an example plugin and a render library alongside its own licence file, and separate directories for the plugin nullifier, for dependencies, for headers, for sources and for side projects. One directory is not explained anywhere in the file: lua-api, which suggests a scripting surface without documenting what it exposes. The build side is CMake, with a CMakeLists.txt, a cmkr.cmake module file, a cmake.toml, CMakeSettings.json, a batch file that writes the commit hash, a COMPILING.md and both clang-format and clang-tidy configuration.
Editorial conclusion
UEVR fits a player who has a flat Unreal Engine title, a headset and an appetite for troubleshooting, and who is comfortable reading a rendering mode comparison before pressing inject. It does not fit anyone wanting a one-click conversion, because the pre-injection checklist exists precisely because the process injection is fragile, and it does not cover anything outside Unreal Engine 4.8 to 5.4. Before you start, check four things: which runtime your headset and games use, OpenVR or OpenXR, whether the title already ships a VR plugin that has to be nullified, whether your graphics settings include frame generation or hardware accelerated GPU scheduling, and whether you are on the stable release or the separate nightly build, since they come from different repositories.
Frequently asked questions
What is the UEVr mod?
A universal VR mod for Unreal Engine 4 and 5, supporting engine versions 4.8 to 5.4. It injects into a running game through a frontend GUI, supports OpenVR and OpenXR runtimes, and offers three rendering modes, native stereo, synchronized sequential and alternating frame rendering, along with optional 3DOF motion controls and roomscale movement in many titles.
Is UEVR safe to use?
The file makes no safety claim. It does document what has to be true before injecting: HDR disabled, conflicting overlays such as Rivatuner, ASUS software, Razer software and Overwolf turned off, in-game options like DLSS Frame Generation disabled, and hardware accelerated GPU scheduling considered. It also expects the .NET 6.0 SDK installed, and it can nullify VR plugins the game already ships.
What VR headsets are compatible with UEVR?
No headset list is given. What the file states is that the mod supports the OpenVR and OpenXR runtimes, and that runtime is the choice you make in the injector before injecting. An optional depth buffer integration is described as improving latency on some headsets, without naming them.
Can I convert any game to VR?
Not any game: the stated support is for Unreal Engine versions 4.8 to 5.4. Within that, full 6DOF headset movement and stereoscopic 3D are described as working out of the box, while 3DOF motion controls and roomscale movement are said to work in many games, with a user-authored system offered for titles that support neither.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/praydog-uevr)Star history chart for your README
[](https://hysenlabs.com/projects/praydog-uevr)Was this useful?