Vivecraft is a third-party VR implementation, and it has real advantages: it works within SteamVR’s hardware model, supports room-scale motion-controller play, and can also be used seated. But it also means setup is sensitive to version matching, PCVR connectivity, and performance settings. A reliable installation starts by treating those as separate layers rather than one large “Minecraft VR” problem.
Bedrock VR support ended; Java/Vivecraft is a different route
Mojang stated that Minecraft Bedrock Edition’s ability to support VR/MR devices would end in updates after March 2025. Players could continue to receive PC updates and play Minecraft without a VR/MR device, but could not use a VR/MR device with the latest updates.
That is a retirement of Bedrock’s VR/MR support, not evidence that every form of Minecraft VR stopped working. Vivecraft uses Minecraft: Java Edition and SteamVR, so it is technically and practically a separate route.
This also sets a useful expectation: an old Bedrock configuration, headset toggle, or launcher shortcut should not be treated as a supported recovery method for present-day Bedrock VR. The precise behavior of the former OpenXR launch URI is not established here—it may not behave consistently across installations—but Mojang’s support cutoff is clear enough that it should not be the foundation of a new setup.
For Windows users choosing between editions, the key requirement is straightforward: Vivecraft requires Java Edition. A working Bedrock installation alone is not the starting point for this method.
What a Windows Vivecraft PC needs
A baseline Vivecraft setup requires the following:
- Minecraft: Java Edition.
- Steam installed with SteamVR installed and configured.
- A SteamVR-compatible headset, or appropriate VR emulation.
- A PC capable of VR using a dedicated GPU.
- A Vivecraft release and mod-loader combination that match the specific Minecraft Java version being used.
The dedicated-GPU requirement is important. VR rendering has a substantially different workload from ordinary monitor play, and Vivecraft’s own guidance treats a VR-capable dedicated GPU as a prerequisite rather than an optional enhancement. The supplied documentation does not establish universal CPU, GPU, RAM, or headset-specific minimum specifications, so it is better to begin from the official baseline and test the actual SteamVR and Vivecraft experience than rely on a generic parts list.
SteamVR is the central compatibility layer. Vivecraft says that if hardware works in SteamVR Home, it should work in Vivecraft. That is a practical compatibility test, not an unconditional guarantee: test the headset, tracking, display, and controllers in SteamVR before trying to diagnose Minecraft itself.
Headset connection choices on Windows
Meta Quest: Meta Horizon Link, Air Link, and Steam Link
For Quest PCVR, Meta’s current desktop connection product is named Meta Horizon Link. Older instructions may call it the “Meta Quest Link app,” but using the current name will make it easier to find the relevant Windows setup material.
Meta documents two primary connection styles through Horizon Link:
- Link, a wired USB-C connection to the Windows PC.
- Air Link, a Wi-Fi connection from headset to PC.
For wired Link, Meta specifies a USB-C 3.2 cable capable of at least 5 GB/s. For Air Link, Meta recommends a 5 GHz Wi-Fi network. Those are useful starting conditions, but they do not remove the need to verify SteamVR operation after the PCVR session is established.
Meta lists Link compatibility for Quest 3S, Quest 3, Quest 2, and Quest Pro. Quest 3S is therefore part of the current Link-compatible discussion and should not be omitted from a complete Windows PCVR guide.
Quest users also have an official additional wireless route: Steam Link. Valve documents Steam Link for Quest 2, Quest 3, and Quest Pro, with Steam and SteamVR installed and running on the PC. Valve’s network guidance is specific: the PC should be wired to the router and the headset should use a 5 GHz Wi-Fi network. This makes Steam Link worth considering when the aim is specifically to stream SteamVR titles such as Vivecraft rather than use Meta’s Link connection path.
The records do not establish identical Steam Link support for every Quest model. In particular, do not infer Quest 3S Steam Link status solely from the fact that Quest 3S is Link-compatible.
PS VR2: a legitimate Windows PCVR path
A blanket statement that PlayStation VR is unsupported for Vivecraft on Windows is misleading. PS VR2 can be used with a Windows PC through SteamVR, and Vivecraft’s SteamVR-based hardware guidance means it should fall within the supported PCVR model once it works in SteamVR Home.
Sony’s PC setup documentation requires the PS VR2 PC adapter and a DisplayPort 1.4 cable. It also calls for SteamVR and the PlayStation VR2 App. Sony’s requirements further include compatible Bluetooth hardware and a qualifying Windows PC.
This is a PCVR route, not proof of a native PS5 Minecraft PS VR2 mode. The distinction is critical: Minecraft Java and Vivecraft run on the Windows PC, while PS VR2 is used as the PCVR headset through Sony’s adapter and SteamVR software.
Other SteamVR-compatible hardware
For other headsets, Vivecraft’s own test is the most useful one available: if the equipment functions in SteamVR Home, it should function in Vivecraft. That means a user should resolve SteamVR recognition, headset display, controller tracking, and connection issues before assuming the Minecraft mod is at fault.
Installing Vivecraft without creating version conflicts
Vivecraft is available as a Forge or Fabric mod from Minecraft 1.18 onward. This guide focuses on the Fabric-style workflow because the version-matching rules are especially clear.
The central rule is that the pieces must agree:
- Select the exact Minecraft Java Edition version you intend to run.
- Use a Fabric loader and Vivecraft files that match that Minecraft version.
- Confirm that every mod JAR is made for Fabric, not a different mod loader.
- Place the applicable JAR files in the correct Minecraft
modsfolder. - Start the matching Fabric profile in the launcher.
On Windows, Fabric documentation identifies the usual mods folder as:
%appdata%\.minecraft\mods
A failed launch is often a compatibility problem rather than a VR problem. If Minecraft closes, refuses to load, or behaves differently after a mod change, first recheck the Minecraft version, Fabric-loader version, and the release target of every JAR in the mods folder. A Fabric build for the wrong Minecraft release can prevent startup.
Do not automatically add Fabric API merely because a generic Fabric guide mentions it. Fabric’s documentation says that the majority of mods require Fabric API, not all mods. Whether a particular Vivecraft build needs a separate Fabric API JAR should be verified on the page or file information for the exact Vivecraft release selected. Adding unneeded or mismatched files creates another opportunity for version conflicts.
Once the Java, Fabric, and Vivecraft versions match, make sure SteamVR is configured and that the headset operates normally there. Then launch the corresponding Fabric profile rather than the ordinary unmodded Java profile.
Standing and seated play are not equivalent modes
Vivecraft has two major play modes, and the difference affects both comfort planning and troubleshooting.
Standing mode uses motion controllers and enables room-scale interactions. It is the appropriate choice for users who want the expected VR controller experience.
Seated mode is not standing mode with the same controllers while sitting down. Vivecraft says seated mode disables controller input and uses mouse and keyboard. That can be useful for a desk-bound or lower-motion setup, but it should not be configured with the expectation that normal motion-controller play will remain active.
Vivecraft uses snap turning by default. Its VR settings can change rotation to smooth turning. This is an individual comfort setting, so there is no evidence-based universal choice; begin with the default if unsure, then adjust after establishing a stable play session.
Performance: reduce stacked rendering demands first
A VR-capable PC can still run into poor performance if Minecraft and SteamVR are both asked to render aggressively. Vivecraft’s FAQ provides a conservative baseline that is more useful than immediately changing many unrelated settings:
- Reduce Minecraft draw distance. Vivecraft describes a value below 10 as best even on high-end systems.
- Lower Vivecraft’s render scale.
- Keep SteamVR supersampling at 1.0.
- Avoid custom shaders and texture packs while troubleshooting performance.
The SteamVR supersampling recommendation matters because resolution controls can stack. Raising SteamVR supersampling while also increasing Vivecraft render scale multiplies rendering work rather than providing two independent performance improvements. Start at SteamVR 1.0, use a modest draw distance, and reduce Vivecraft render scale before deciding whether the system has a deeper compatibility issue.
Shaders and high-resolution texture packs are another avoidable variable. They may be desirable later, but Vivecraft explicitly advises avoiding them when performance is a concern. First establish an acceptable baseline in an ordinary world, then introduce one visual change at a time if the PC has sufficient headroom.
For wireless Quest sessions, network topology belongs in the performance diagnosis. Air Link calls for preferably 5 GHz Wi-Fi; Steam Link’s documented design calls for a wired PC-to-router connection plus a 5 GHz headset network. These requirements do not prove that every stutter is a Wi-Fi issue, but they provide a concrete first check before attributing all problems to Minecraft or the headset.
A sensible fault-isolation order
When Vivecraft does not work, changing everything at once makes the cause harder to identify. Use this sequence instead:
- Confirm the edition: verify that the installation is Minecraft Java, not Bedrock.
- Confirm PCVR first: make sure the headset works in SteamVR Home.
- Confirm the connection route: for Quest, establish Horizon Link/Air Link or the documented Steam Link setup; for PS VR2, verify the PC adapter, DisplayPort connection, required apps, Bluetooth compatibility, and Windows PC requirements.
- Confirm versions: check Minecraft, Fabric, and Vivecraft release compatibility.
- Confirm file placement: ensure the applicable JARs are in
%appdata%\.minecraft\modsand launch the Fabric profile. - Reduce rendering load: use low draw distance, lower Vivecraft render scale, SteamVR supersampling at 1.0, and no shaders or texture packs.
- Choose the correct play mode: use standing mode for motion controllers; use seated mode with the expectation of mouse-and-keyboard input.
That order prevents a common mistake: treating a failed PCVR connection, a mismatched Fabric JAR, and a difficult-to-run Minecraft world as the same problem.
What this setup does—and does not—establish
The evidence supports a durable conclusion for Windows users: Minecraft Java plus Vivecraft plus SteamVR remains a defined PCVR route even though updated Bedrock Edition no longer supports VR/MR devices. Quest users have wired Link, Air Link, and a documented Steam Link alternative for supported models; PS VR2 users have a PC path through Sony’s adapter and SteamVR.
It does not establish that Bedrock VR can be restored on current updates, that a native Quest edition of Minecraft exists, or that Minecraft has a native PS5 PS VR2 mode. No authoritative record in the supplied material proves those negatives or alternatives, so they should not be presented as settled claims.
Finally, while Vivecraft’s FAQ mentions code and installation support for macOS and Linux, that does not confirm a current, end-to-end headset and runtime combination on those platforms. For readers who want the best-supported path described here, Windows PCVR with Java Edition, SteamVR, and carefully matched Vivecraft files is the concrete route.