Getting a longer pipe adds both accuracy and power, but sacrifices usability on close range. Stocks can be added for more accuracy, the TMP and Red9 had it. It is realistic to get bigger magazines (just not on revolvers lol). Weapons in the game can be tuned by adding control (maybe speed of turning can correspond to tuning the trigger point on a real gun), and both real and digital guns can be upgraded with better aiming/optics. (In particular, 120 Hz is a no-go at any setting, based on my uncomfortable tests.) I suggest using Sidequest's "90 Hz" and "1536 texture size" settings or bumping the texture size even higher to "2048" while leaving the refresh rate at the 72 Hz default to gain fidelity at the cost of frame rate.Click to expand.
Conversely, attempts to run the game at even higher texture resolutions or higher frame rates resulted in more noticeable hitches, suggesting that the Quest 2 has a performance ceiling with this game. If the game is exhibiting any animation hitches or bugs with these ADB console commands sent to my Quest 2, I certainly can't perceive them, and I'm particularly sensitive to VR queasiness-so much so, in fact, that RE4VR is an entirely different experience for me with these boosts enabled.
In RE4VR's case, jumping up from 72 Hz to 90 Hz and slightly higher texture resolutions works without a hitch. Sidequest streamlines a few "ADB" console commands that you can send to either Quest system, and the Quest 2 can be forced to render games at preferred frame rates and texture resolutions, which can sometimes result in laggy performance, bugs, or outright crashes.
#Resident evil 4 remake reddit windows#
This process also requires toggling developer mode on your Oculus account and connecting Quest hardware to a Windows PC. The same Reddit community pointed to Sidequest as a simple way to force Quest 2 to try a few more tricks. I checked RE4VR's default menus in search of toggles to frame rates, texture resolutions, or other settings, but there are mostly just control and "comfort" options. Was this a case of the more powerful Quest 2 requiring some visual downgrades to smoothly run a port of a 2005 GameCube game? Advertisement After I began testing the game's Quest 2 version, I immediately wondered: This restriction can't be technical, can it? The answer came from the game's Quest 1-level specs, particularly its 72 fps frame rate cap and lower-resolution textures. If you own only the original 2019 Oculus Quest, you won't find RE4 in any of its native store menus. Officially, Facebook limits this week's port even further, as the company only sells the game for its newer Quest 2 platform. (Seriously, Capcom? Five years later, and you still haven't ported that wonderful game to a more powerful VR system?) Capcom seems to love locking VR versions of its horror games to specific platforms, as the groundbreaking VR mode in 2017's Resident Evil 7 remains exclusive to PlayStation VR. Investigating the Quest 1 restrictionįor now, this version of Resident Evil 4 only works on Oculus Quest hardware, not on Windows PCs or PlayStation 4's VR mode. It's unfortunate that Facebook, Capcom, and porting studio Armature didn't straighten all this out for average customers in the first place.
Facebook may sell the Oculus Quest as a simple "set-and-forget" path to VR, but in the case of RE4VR, I recommend going through some complicated steps to make the game far more playable on its target platform of the Quest 2-and I'll explain the iffy method to unlock the game's compatibility with the Quest 1. New and old players should give this one a try-even if it's missing a few crucial elements.īut as of press time, our recommendation comes with some asterisks, so this is both a review and a technical guide. As the roughly 4,000th port of RE4 since the game's original 2005 launch, this new version manages to establish itself as the action-horror classic's best version. After testing Thursday's virtual reality launch of Resident Evil 4 (RE4VR), currently an Oculus Quest exclusive, I found myself equally impressed and puzzled.
0 kommentar(er)
