Anyone needs a fix?
Added 2025-07-20 14:45:06 +0000 UTCHey folks!
Release 21.5.0 of the R.E.A.L. VR mod, attached below, restores VR functionality to CP2077 which was broken by the recent official 2.3 patch.
We tested everything we could, but Cyberpunk 2077 is a very complex game, so if you find something that still looks wrong please report it in the comments, preferably with a Pastebin link to your RealVR64.log file, and we'll take a look.
During testing some crashes were reported when toggling Ray Reconstruction on and off, or when starting the game with RR on. I cannot reproduce any of those crashes, but I do see a weird behavior where the left eye will be all black (with only the HUD visible) when I switch RR on for the first time after a system reboot. The problem goes away for me as soon as I bump the resolution up or down a little, and it won't happen again until the next system shutdown. That makes me think that NVIDIA still has a few kinks to iron out in their drivers, but unfortunately there is nothing I can do on my side about that.
Ray tracing (or path tracing) are just too expensive anyway for the time being, even on an RTX 5090. They basically cut frame rate in half, and to compensate you have to lower the DLSS quality so much that in my opinion the result ends up looking poorer. You're free to experiment though.
This release also adds an experimental tweak for which I got many requests. Disclaimer: it's NOT intended for general usage. If you add the line "ExpertMode=1" (without the quotes) to the [RVR] section of your RealVR.ini file in a game folder, the next time you launch that specific title you will have all Render modes unlocked in the mod: AER v2 (the complete range from full frame rate to 1/6 rate), Legacy AER and Mono.
Beware though: forcing them will not make your game magically play better in the general case. The reason why I disable some modes for certain titles is simply because they don't look good, for instance because the engine is not performant enough to render at full frame rate.
However, I understand there are special cases (like people playing on 3D displays that need much lower resolutions and frame rates compared to VR headsets) where having access to full-rate AER v2 would be beneficial. I also know that some other users have long been asking for a way to try out higher interpolation rates. Personally, on a VR headset, I think that the sweet spot tends to be around 1/2 or 1/3 rate for most games, but again you're welcome to experiment!
The Last of Us Part II Remastered is coming, but since these days I've been working almost exclusively on fixing CP2077, I'm gonna need some more time to finish it. Should be ready in a week or so!
Comments
Try using OpenXR from the runtime dropdown at the top of the main tab of the REAL overlay. Make sure SteamVR is set as your OpenXR runtime in the SteamVR settings as well. flickering could be from low performance or really high latency. What kind of fps are you getting if you enable the fps tracker in the overlay tab of the REAL overlay? While the game is active, not paused or in menus. There is also a check box there for latency as well.
Brandon(Post Maester)
2025-11-05 19:08:34 +0000 UTCI also havea small problem soo i see that people shouldnt use steam vr tho my heaset is a pico neo 3 link, using it with wifi is the worst possible option (didnt try yet) im using through DP tho the app makes me open steam vr when its on i see that in the game is flickering a lot even after tweaking some settings is there any video showing extra steps like resolutions and flickering problems? Sry to bother with this...
DVgamer 1
2025-11-05 15:38:07 +0000 UTCSorry for missing this! You don't need SteamVR and it is most likely going to cost you performance or cause issues. How are you connecting your headset? You want to end up using oculus runtime. If you are using Link cable or Air Link, just connect your headset to your system through the Meta Link app and then run the game from your library and it should default to using Oculus runtime. Don't launch SteamVR at all. If you are using VD, use VDXR in the streamer app and then it should also default to using Oculus runtime in the REAL overlay, if not, then switch to Oculus runtime from the runtime dropdown in the REAL overlay. I see that you also have mods installed, but you said you did a fresh install. For a completely fresh install, you would need to delete the main game folder manually and then reinstall. If you uninstall through Steam for example, it will only remove things it installed, so not mods :)
Brandon(Post Maester)
2025-11-01 03:44:49 +0000 UTCHeya! Bit new to VR in general here, just did a fresh Cyberpunk 2077 install and from what I can tell I downloaded the mod correctly (downloaded, extracted, put into Cyberpunk 2077 bin folder, ran batch file) though its crashing on startup. I have a Quest 3S with an RTX 3090Ti, i9-12900KS, and 32GB of DDR5 memory. I run version Nvidia 581.57 drivers for my card. Any assistance would be nice, thanks! REALVR64.log (crashlog) Pastebin: https://pastebin.com/9LD5MNNK REALVR.ini settings pastebin: https://pastebin.com/CgBC3rg2
Aurora
2025-10-29 14:28:42 +0000 UTCIf you are using 1/3 rendering mode, the latency is pretty high, which makes this worse. You can lower the "reduce shaking" slider first to see how much that helps. Basically, it is either poor performance like not enough fps or a combo of latency and the fov optimizations that keep the game from rendering beyond your headsets fov. You can disable the fov optimizations but then you will lose a big chunk of performance. You can switch to using 1/2 or Legacy to lower latency, even using 1/2 rendering mode with your headset set to 72hz will have less latency. You also have the option of using the Oculus debug tool and adjusting the fov tangent multiplier a bit, something like 1.1:1 to extend the horizontal part. VD also has a built-in option for this now. So, you could disable the fov optimizations in the REAL overlay and use those other options to accomplish the same thing less aggressively. Hope all that makes some sense and helps :)
Brandon(Post Maester)
2025-10-22 23:13:04 +0000 UTCUsing a 4090 and Quest 3 and when I turn my head horizontally, I get black vertical bars at the edge of my headset like the rendering can't keep up with my headset. Is there anything I can do about this or any settings to change? I dont want to give up on cyberpunk in VR and seems like a 4090 should be capable of not doing this
David Dunn
2025-10-22 07:15:23 +0000 UTCDon't use SteamVR at all with Meta headsets. If you are using Virtual Desktop, use VD in the streamer app and Oculus runtime in the REAL overlay. You will need to use Oculus runtime no matter which way you go with the Quest 3 for best compatibility. I have not checked out the new version of Steam Link to see if you can use OpenXR runtime with it successfully on Quest 3 but even then, you are just adding another layer on top of Oculus runtime, which may cause issues. AER v2 is not going to work well for you unless you mean the 1/2 or 1/3 options. With a 3070ti, using 1/3 at 72hz may be a good option to try as it will lower the fps requirement down to 48fps but latency will be pretty high. 1/2 and 1/3 are available in the rendering mode dropdown in the main tab of the REAL overlay. Pretty easy to find. Litteral AER V2 in the rendering modes caps at 2x your headset refresh rate, which you will not reach on a 3070ti without things looking quite terrible, if at all. First step is to get rid of SteamVR and use Oculus runtime though, that should improve things quite a bit.
Brandon(Post Maester)
2025-10-06 19:25:56 +0000 UTCI just installed Cyperpunk Vr for the first time and I'm using SteamVR with the Quest 3 and a 3070 TI. The first time I launched before changing any settings I could see the menu fine, I just couldn't use my mouse properly because it was locked to the left upper part of the screen. After the tooltip I changed my renderer in your VR overlay menu to OpenVR. This caused my two screens to became unnaligned and cross-eyed making me have to close one eye to focus propperly. This hasn't gone away even after changing OpenVR to auto. The tooltip also said I should change the runtime to OpenVR in SteamVr settings but I can't find that setting anywhere even with advanced settings enabled at the developer section. And how do I get AER v2 to run is that just a setting in the game or VR overlay? Could you help me please?
Rutger
2025-10-06 10:57:13 +0000 UTCDownload the Meta Link app for PC and install it. You don't need to run it when playing but you do need to make sure it updates so run it now and then just to see if there are updates. Pimax needs to use Oculus compatibility mode for REAL. Your system will need the dll files or it, so you will need to Meta app installed :) It should then default to using Oculus runtime for REAL, but you can always double check in the main tab of the REAL overlay.
Brandon(Post Maester)
2025-09-28 04:55:20 +0000 UTCHi Brandon, after quite some time I am back with my new Pimax super and 5090 combo but have issues to bring cp2077/GOG up and running in VR. renderer is set to auto but status is "not rendering". Log says something about oculus runtime missing or similar. But I have super only and never had a oculus/meta on this pc. Back in times I got it working fine but now I am lost. OpenXR, quadview or similar is switched off. Guess you need the log, right?
Chris
2025-09-27 19:43:34 +0000 UTCHave you made any other changes recently? Pico software, DLSS dll or other dll file changes like that? Nvidia app changes (make sure motion smoothing is not on)? If you have Ray or Path tracing on, try turning them off along with DLSS and see if the same things still happens. Also make sure you don't have frame gen on :)
Brandon(Post Maester)
2025-09-23 17:49:56 +0000 UTCHey. there! Been enjoying playing the mod for two weeks already, today all of a sudden the game launched in a square window (within VR). I can still look around but everything is in 2D within a smallish square. I've tried to reinstall the mod and it didn't help. https://pastebin.com/P7WQqrWW
Denis Aganin
2025-09-23 17:15:19 +0000 UTCYou are going to be limited by your GPU of course but definitely look into using Optiscaler so you can use the DLSS fix that Luke added to the framework. It will get rid of most all the shimmering around objects and image quality is way better than fsr 2! https://www.patreon.com/posts/score-one-for-129841705 54fps is not a good place to be. What rendering mode are you using? If you are using 1/2 or 1/3 you really need to hit the fps cap reliably or they won't perform well. Legacy is more forgiving but 54fps with Legacy will have terrible motion jitter/reprojection.
Brandon(Post Maester)
2025-09-20 19:24:33 +0000 UTCim using an amd gpu, rx 7600 OC. I get this crazy graininess and this sort of ghosting around singular small objects. im running the game at minimum settings 16 pixels per degree with fsr 2.1 quality. can anyone offer some help? im also pretty new to this (also running the game at 54 fps). Also, im using a quest 3s using a cable link
kacolek rad
2025-09-20 13:26:45 +0000 UTCReplacing an older version with the newer version should be fine. The latest version of REAL works fine with Cyberpunk for me and some other people. As far as the game freezing, make sure you choose to reset settings after running the config.bat file and then adjust the important REAL settings like rendering mode and runtime if necessary. Also make sure you don't have frame gen on or motion smoothing in Nvidia app. What headset are you using and how is it connected? If you want to put a copy of your RealVR64.log file on pastebin.com and post a link here, I'll take a look at it :)
Brandon(Post Maester)
2025-09-17 07:39:08 +0000 UTCi have cyberpunk 2077 2.3 version and i downloaded yoour latest real vcr mod and replaced it with the older version should i have done that bewcause its still freezing and wont plaY CORRECTLY IS THERE A SETTING I SHOULD PUT IN MY GRAPHICS IM USING A 4060 GRAPHIC CARD
Reginald Telcy
2025-09-16 21:00:38 +0000 UTCI don't think air link was ever the best :) Cable or VD are both better options I think. VD has built in fov adjustments now. So, if you have issues with the REAL fov ones, you can disable them and use VD instead to your liking. You can also use Oculus Debug tool and adjust the "fov tangent multiplier" to do the same thing. For cable or Air Link.
Brandon(Post Maester)
2025-09-07 20:13:55 +0000 UTCIs Air link still the best way to run this or can I get fov cropping on VD now? I’m getting solid frames with rtx reconstruction on all medium settings with 5090 at 30 target pixels using air link.
Virtual Samurai
2025-09-07 14:29:11 +0000 UTCFirst install. Ran Config.bat. Launched the game and got cross eyed instantly. UI renders as if my eyes are 1m apart. Turend off HFOV VFOV and it normalized, but resolution dropped so that I couldn't read anything. There was a button with resolution, but after clicking it things changed, and I barely could see anything. Experience is horrific, its painful.
zORg_alex
2025-08-28 22:14:25 +0000 UTCCan you try turning off DLSS to see if that helps?
Brandon(Post Maester)
2025-08-28 17:28:03 +0000 UTCHere's the copy on pastebin - https://pastebin.com/bWp89aTy I had to crop it because the logfile was 1198kb and only half is alloud. After installation of the RealConfig.bat i closed it by pressing a key. Then opened meta quest link and tried to open cyberpunk. The game then runs but without the mod. Gameversion is 2.3
Simmie
2025-08-28 06:38:22 +0000 UTCGamepad is the way to go! It is considered the most compatible because of issues like clicking out of the window in some games or reaching things on screen if the window exceeds your monitor size. A 2080 super is not going to be a great experience probably but with proper expectations and tinkering, I have seen people still able to enjoy it on older hardware. Just realize you are asking a lot of your 2080 if you are playing something like Cyberpunk or Horizon Forbidden West etc in VR, which is definitely harder on your system than flat. Lower all the settings you can and focus on resolution above all else. Try different rendering modes in the REAL overlay to see what works best for you. 1/2 is probably out of the question with Legacy being the easiest Stereo 3d option on performance. If your headset can do 60 or 72-5 hz, that would make it easier to use 1/2 or 1/3 if you find that you prefer them. Going lower than 90hz with Legacy will make motion jitter worse but it is an option as well. Mono can be a really good experience for older hardware but it is just the render from one eye, so no Stereo 3d. It is still much more immersive than playing on a monitor though :)
Brandon(Post Maester)
2025-08-25 18:30:44 +0000 UTCHi. First patreon user here. I have just tried to install the mod on my pc, but I am having some issues and I am not sure i understand how it's supposed to work and whether my pc can run it. My pc specs: 7800x3d 2080 super 32gb 6000mhz ram. Is the game supposed to be played with keyboard and mouse? I really struggle to bring up the mod menu and actual controls. Seems really choppy and the controls dont work properly either. It seems like the mouse runs of the window that the game is playing in and i end up clicking on my taskbar etc.
Kamil Gorniak
2025-08-25 14:57:47 +0000 UTCYou could try adjusting the zoom levels for them using the sliders in the Cyberpunk tab of the REAL overlay. There are a bunch of slider options for different weapon types towards the bottom, you just have to click to make them visible. There is also a 2d screen option in that tab, I don't think this one has a gamepad shortcut for it though. Experiences like this where you lose control of the camera and things get wild sometimes, will require some decent VR legs :) You can get there, just take your time. I started to get motion sickness fairly easy as I got older but after playing a lot of early VR games, and these mods, I have an iron stomach again 🤪 I remember one year not being able to do more than one fair ride at a time with my wife on her birthday, I would have to take a break for a while. Now, I can do them all in a row no problem.
Brandon(Post Maester)
2025-08-23 05:30:35 +0000 UTCHello there, I've been trying to look through the conversations to find an answer but having no luck. First off thanks so much for creating the Cyberpunk VR mod, a million times easier than Vorpx, and you are my first Patreon member I've ever subscribed to as a result of your hard work. My problem is in Cyberpunk the recoil from shotguns or assault rifles. The recoil is making me dizzy as the camera follows the recoil. I looked for ways to turn this off in the R.E.A.L VR menu but I am having no luck. Looked in the Cyberpunk menu as well but haven't found an option that works. I could have missed it but wanted to reach out as I don't know what I'm doing. Also wanted to know if a toggle exists for action scenes where I don't have control and to turn them 2D. I almost threw up the first night V laid on his bed. Thanks so much!
Whosile
2025-08-22 19:44:47 +0000 UTCWhat headset? How is it connected if not DisplayPort? Did you change any display settings after running the config file?
Brandon(Post Maester)
2025-08-20 23:16:58 +0000 UTCHi Brandon i have an issue with starting cp in vr because instead of booting it in vr it starts flat with really wide resolution and i dont really know what to do with it
kolodziej82
2025-08-20 22:31:50 +0000 UTCIf you have black borders when turning your head, it is likely either low performance/high latency, the Hfov optimization or some combo of those three. You can try bringing down the "reduce shaking" slider in the main tab of the REAL overlay first. If you are using the default rendering mode of 1/3 that will have the highest latency. You can disable the Hfov optimization in the main tab of the overlay too but that will cost you a chunk of performance. It keeps the game from rendering beyond your headsets fov. VD recently included the ability to adjust this too, but I haven't tried it yet. So you could disable Hfov Opti and try VDs method. Lowering latency will also help the game view to keep up with your head movements. Using 1/2 or Legacy or running at a higher fps, if able. If you are using a Meta headset with cable, you can also use the Oculus debug tool to adjust the fov tangent multiplier to something like 1.1:1 to increase the horizontal fov a bit.
Brandon(Post Maester)
2025-08-18 16:14:15 +0000 UTCSee response to other post :)
Brandon(Post Maester)
2025-08-18 16:09:56 +0000 UTCAny help with the black to my left or right as I move my head I see black borders on both sides. Game seems to be running fine so unsure what could be causing it.
209Race_ Wars
2025-08-18 12:52:24 +0000 UTCSubject: Crash Issue - Phantom Liberty Chimera Boss Fight Hello, I hope you're doing well. I'm writing to report a crash issue I'm experiencing with your mod. The game consistently crashes during the "Phantom Liberty" expansion, specifically during the boss fight against the Chimera. I'm running the game on a powerful rig with an RTX 5080, so I don't believe hardware is the issue. It seems to be a conflict or bug related to the mod itself. Have you heard of this problem from other users? Do you have any suggestions on how I might fix this? Any help would be greatly appreciated. Thank you for your time and for all your hard work on the mod! Best regards,
Simone Frangini
2025-08-18 09:56:47 +0000 UTC1/2 and 1/3 will have motion artifacts, try switching to Legacy rendering mode and if the issue you are talking about goes away, then that is probably it. 1/2 will have less of this issue than 1/3 and you can also tick the "higher quality" AER box in the main tab of the REAL overlay to help with this. It will reduce it some but cost a bit more performance.
Brandon(Post Maester)
2025-08-16 17:44:32 +0000 UTCLuke's mods don't support motion controllers, gamepad is the best way to play overall for compatibility, but mouse and keyboard can work too. How is your Quest 2 connected? You are not running SteamVR correct? Game version is up to date? You are using a recent version of REAL?
Brandon(Post Maester)
2025-08-16 17:42:11 +0000 UTCHey all, I can't seem to get it working at all. Installed CP and launched. Files moved over to 64x and ran bat file. Connected up my meta q2 and the launched the game. However the game just loads in 2d flat and doesnt recognise my vr joycon controllers? Any advice?
AAH!!
2025-08-16 10:22:39 +0000 UTCHey quick question, i just tested out the mod for CP and no matter what im doing i seem to always have some sort of ghosting effect. Be it with 1/2 or 1/3 or legacy to a degree. Im running a 4070ti and can hit 90fps+ consistently but idk the ghosting is still there especially when i myself move. I came to ask if there are any commonly known troubleshoots or known settings to eleviate this ? Do i need more frames aka turn down the resolution ? Cause i thought as long as i can hit 90 fps all is fine
Alexander Braun
2025-08-16 09:19:12 +0000 UTCYou should be able to get it working pretty well on a 5080, you just need to do some learning and tweaking probably. If you aren't interested, I can pass on your refund request though.
Brandon(Post Maester)
2025-08-15 03:40:13 +0000 UTCNo me funciona correctamente… tengo una 5080 de tarjeta gráfica Va fatal el mod , quiero cancelar la suscripción y que me devuelvan el dinero
David Guerrero Mallen
2025-08-15 02:50:16 +0000 UTCIt's copy paste time again :) If you have black borders when turning your head, it is likely either low performance/high latency, the Hfov optimization or some combo of those three. You can try bringing down the "reduce shaking" slider in the main tab of the REAL overlay first. If you are using the default rendering mode of 1/3 that will have the highest latency. You can disable the Hfov optimization in the main tab of the overlay too but that will cost you a chunk of performance. It keeps the game from rendering beyond your headsets fov. VD recently included the ability to adjust this too, but I haven't tried it yet. So you could disable Hfov Opti and try VDs method. Also going to paste this just in case you don't know much about the different rendering modes and would to ask about that next :) Rendering mode is really dependent on your system and what you value. 1/2 will cap at your headset refresh but it interpolates extra frames between, like a built-in motion smoothing, so it has the fluidity of twice the fps but it will cost performance to do that. 1/3 will do the same thing but with more frames in between so it caps at 1/3 of 2x your refresh rate but should feel like 3x the fps or the same fluidity as 1/2 but with a lower fps target you have to hit. 1/3 will have much higher latency, 1/2 will have a bit more, Legacy less and AER V2 will have the least. Legacy is basic Alternate Eye rendering that just caps at your headset refresh rate. So having your headset set to 90hz will have a 90fps cap. Since it is alternating eyes, it is 45fps per eye. AER V2, which is only available in some games where performance is really good, will cap at 2x your refresh rate. So, if you can hit 180fps with AER V2, you are actually getting 90fps per eye which is an Ideal situation and plays like Native VR pretty much. That is really hard to hit with a lot of these AAA games, so that is why you won't find it in most of them. Luke usually just puts it in older titles like the Dark Souls series or Doom Eternal, because performance is great in those games. You can lower your refresh rate to lower the fps cap for all of these, and 144hz with AER V2 is still really solid. 72hz using 1/2 is also really good. You will just have to experiment and see what you like or what works well with your system and a given game." There is also Mono rendering mode which is just the render from one eye, so doesn't have Stereo 3d, but I used to use it when I was on a 3070 years ago. Obviously not the best choice for VR, but still much more immersive than playing the game flat. I would start with settings at low and focus on figuring out what rendering mode you want to use and then see how high you can push resolution with that mode. Resolution will have the greatest visual impact over other settings. I'd also recommend using a LUT mod off Nexus to help with the game contrast in VR as well as the horrible lighting exposure at times in this game. I like Real Colorr 3 myself. There are a number of them though. Supernova is another popular one with lots of options. Don't get sucked in the "real life" ones, as they only look good in certain conditions usually. There is also the deblur slider in the main tab of the REAL overlay that is built in sharpening. It defaults to all the way up and can make the game look really grainy (over sharpened) if you are using DLSS sharpening or other sharpening on top of that.
Brandon(Post Maester)
2025-08-14 20:46:49 +0000 UTCHello Brandon, downloaded and got the mod to run for my Quest 3 last night but game looks pretty rough. I'm running Ryzen 9 7900X, RTX 3070 Ti. I'm new to pc gaming and I know my GPU isn't the best but I'm a bit lost, what should my in game resolution be set at? I moved it around a little last night but didn't notice much difference. In game graphics settings are set to med/low with DLSS set to balanced, no RT. Also I don't understand what 1/2, 1/3, or legacy settings mean or what it should be set at in my case. Game is really cool to look and play in on VR but just looks bad/grainy. TY for your help! *Forgot to mention im running the game wirelessly through VD, pc is wired in and have really good/fast internet. If there are certain settings I should be using in VD please let me know. TY!
KeEpHy
2025-08-14 18:08:35 +0000 UTCWhat rendering mode are you using? If you are using the default 1/3, it will have motion artifacts from interpolating extra frames for added smoothness. You can find the rendering mode dropdown in the main tab of the REAL overlay. 1/2 will have less motion artifacts but caps at your headsets refresh rate, so harder on performance vs 1/3, which caps at 1/3 or 2x your headset refresh. You can drop down to 72hz on your Quest3 and use 1/2 though which is pretty solid but will still have some motion artifacts. Legacy will get rid of that entirely but will have motion jitter that gets worse the lower your fps. 90fps recommended for Legacy. 120 would be better, but that will be hard to hit on a 5070ti. Anyways, see if switching to Legacy gets rid of the artifacts you are talking about, if so, then it is the motion artifacts from interpolation. Do you have anything changed from default settings in the Nvidia app? For the PS5 controller, do you have Steam Input enabled in the Steam controller settings for the game? Do you have any controller software running? Any other control devices plugged in besides your controller and mouse/keyboard? Thank you for all the detailed info!
Brandon(Post Maester)
2025-08-10 18:38:14 +0000 UTCWhat headset and how is it connected if not DisplayPort? Always a good idea to look over the game's release post to double check display settings are correct.
Brandon(Post Maester)
2025-08-10 18:32:45 +0000 UTCHello Luke, I downloaded your mod to play The Last of us Part II". But after starting the game in VR everything is not configured correctly. I can play in VR but everything is shaking terrible. Can I play "sons of the forest" also in VR? Thanks.
Willy Free
2025-08-10 09:38:31 +0000 UTCI've put my RealVR64.log in pastebin (hope that worked, never used before) Link here: https://pastebin.com/yNyEG24J Main issue: I'm having severe rendering glitches and visual artifacts in VR mode making the game nearly unplayable. Graphics appear broken, distorted, or corrupted when using Luke Ross VR mod. Secondary issue: PS4 controller fails to be recognized in VR mode. Controller works perfectly in regular Cyberpunk 2077 gameplay but becomes unresponsive when VR mode is active. Only keyboard/mouse input is recognized in VR. ## System Specifications - **CPU:** AMD Ryzen 9 7900X (12-core) - **GPU:** NVIDIA GeForce RTX 5070 Ti 16GB - **RAM:** 128GB DDR5-5200 (Kingston FURY Beast) - **Motherboard:** ASUS ROG STRIX B650-A Gaming WiFi - **OS:** Windows 11 Pro (Clean install, local account) - **VR Headset:** Meta Quest 3 - **Controller:** PlayStation 4 DualShock controller ## Software Versions - **Steam:** Latest version - **SteamVR:** Latest version (12.9) - **Cyberpunk 2077:** Latest version via Steam - **Meta Quest Link:** Latest version - **Luke Ross VR Mod:** [Version from downloaded ZIP] ## Technical Analysis from RealVR64.log **VR Initialization (Working):** - ✅ Luke Ross VR mod v21.5.0 loads successfully - ✅ Meta Quest 3 detected and initialized ("Rendering to Meta Quest 3") - ✅ OpenXR runtime (Oculus) active and functioning - ✅ RTX 5070 Ti properly detected - ✅ NVIDIA driver 580.88 detected - ✅ VR textures initialized successfully **Critical Issues Identified:** - ❌ **Frame parity mismatches:** "3 frame parity mismatches in the last 205 seconds" - ❌ **DLSS synchronization errors:** "DLSS eval/exec mismatched frame # (eyes swapped)" - ❌ **Pose tracking failures:** "Poses not available: skipping submit" (multiple occurrences) - ❌ **Frame index mismatches:** Expected vs actual frame indices consistently off-sync **Performance Metrics:** - **Initial PPD:** 23.2676 (Pixels Per Degree) - **Rendering Resolution:** 2864x3120 → 3088x3088 (dynamic changes detected) - **FOV Settings:** 49.5° vertical, 47° horizontal per eye - **Performance Index:** 1/1.44815 Thank you for your time and assistance with these technical issues.
Nik Ranger
2025-08-10 09:23:58 +0000 UTC
