shadowborn

Hey. OP here with some new findings, confirming some sort of memory leak it appears. HP shipped me the new cable. It looks JUST like the "old" cable that came with the Rev. B. headset, and also has the little "Rev. A" flag/sticker on it. But lo behold, it appears (pending further scientific testing) to resolve a lot of issues EXCEPT, sadly, for those with DCS I don't own many VR titles. But the following worked flawlessly (apart from occasional view centering issues) now, and didn't before: - IL2 Sturmovik - Titanic VR Experience - Elite: Dangerous Currently still downloading Skyrim VR, which I just bought for more testing. HOWEVER DCS still crashes, and it is, as I suspected, seemingly a memory leak. Many times there is nothing at all in the event log, but one time I got this: Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: DCS.exe (9808) consumed 20684664832 bytes, dwm.exe (10372) consumed 1494360064 bytes, and vrcompositor.exe (3436) consumed 648605696 bytes. That's 20GB of RAM for dcs.exe, 15GB for dwm (Windows Display Manager), and negligible for vrcompositor.exe. My machine has 32GB, but this confirms to me that the Out-of-Memory killer mechanism is responsible for killing the various processes I observed being killed over the last days whenever DCS VR initializes. This is with DCS Open Beta 2.8.1.34667 and AH-64D. I have at times loaded successfully into the Viggen (twice), the KA-50 V3 (once) and the F-18 (once), but with various crashes in between. I will now keep trying with other aircraft to see if the new cable helps and maybe this is an AH-64 problem now.

> Still wondering if your usb output has enough power... maybe you can try an additional usb card (see picture) make sure it has additional power. This Solved all my problems Thanks - I will consider this if the new cable doesn't work. But I have it connected to an USB 3.0 port directly on the back plate of a (rather recent) main board, I would (carefully) assume that this should provide sufficient power, if anything does?

As for graphics driver, I'm already on 527.56, which is the latest. And for event log, there's all sorts of crashes (WUDFHost.exe, vrwebhelper.exe, svchost.exe_wlidsvc, Microsoft Sign-In Assistant, dwm.exe, OpenVRSettingsUX.exe). They can't all crash due to the actual root cause, so I'm still betting on either RAM exhaustion or something central like, yes, a graphics driver crash. There's also: "A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices." and "The device HP Reverb Virtual Reality Headset G2 (location 0004.0000.0000.001.002.001.000.000.000) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem." But I'll try the new cable first before digging further into this.

> Thats a display driver crash and partial recovery and you will see it in your System Event Viewer. Thanks! I just had a call with HP, to talk about returning the headset within the EU mandated 14 days, or else. They assure me that the problems will be solved with a new cable, and that these days, many customers call in with issues and a new cable is always the solution. This is EVEN THOUGH I specifically ordered the "Revision B" of the Reverb, while reportedly only the Rev. A's cable had problems (and to my knowledge only with ATI graphics cards though). Also, I found that while the box says "Rev. B", a tiny sticker on the cable itself actually says "Rev. A". So maybe HP is shipping "Rev. B" glasses with "Rev. A" cables? Exciting. I shall receive a new cable within three working days, we'll see how what goes.

As for the question about hardware specs, here goes: ASRock Z690M Phantom Gaming RIPTIDE/D5 Intel Core i5-13600K MSI GeForce RTX 3080 VENTUS 3X PLUS 10G GIGABYTE AORUS 32GB DDR5 (2x16GB) 5200-40 Kingston SSD NV2 NVMe 2TB EVGA 750 GQ 80+ Gold

Hm. There is something iffy with this headset. I got it to load into DCS twice tonight, and once it runs, it's great. But then I select "fly again" and DCS crashes (as do other VR apps, too). For what it's worth, for one crash I got this: I also got a Blue Screen and OTHER programs crashing (e.g. Wargaming game center crashed over an attempt to start VR, which is really puzzling as the only explanation for this would be WMR or Steam gobbling up all the RAM). I have also seen browser pages and Steam pages (which are browser pages, too) fail to render after such VR crash, so I currently suspect there's an unchecked memory allocation running wild in the VR chain somewhere, somehow. Puzzled. Still trying things, will run a RAM test and (again) a video RAM test. Will report back again.

Thanks for the many helpful replies! It will take me a few days until I have time to dabble with this again, but there is already a lot of useful info here, especially with the re-centering. I will report back in time! If I don't manage before, have a great new year fellow pilots!

Hey. I bought a HP Reverb G2 Rev. B specifically for flying DCS. I can't get it to work. I have a fresh Windows 11 install with DCS beta. Here's what happens: - 70% of the time I get the DCS menu to launch in VR. About half of the time then, the menu is waaaay down in VR (like, the floor is meters below me). Half of the time, I have no mouse control in VR in the menu. - 90% of the time, the menu and the loading screens flicker like crazy - I have managed ONCE to get into a cockpit in VR. Every other time, like 30 attempts, the VR view turns black, Windows makes that "ding dong, the witch is dead ... I mean, the USB device is dead" sound. I got a DCS error reporter once, but most of the time it just crashes with no message whatsoever. I once got a "tasklist.exe has crashed" dialog. Often, it reports SteamVR has crashed also. I tried SteamVR regular and beta, Windows Mixed Reality for Steam lkr_release branch, and something called "OpenComposite", all with no luck. So ... is VR with DCS really THAT fickle at this time, or is my experience "special"? Thanks! p.s. also when VR just for once doesn't crash, when I exit and shut down the VR headset, Windows Mixed Reality takes over and makes it so my regular screen is all black, and I can not get out of that. No alt-tab, no ctrl-alt-del, nothing works short of rebooting.

Hey. I have finally ordered a new PC, and once it arrives I want to order a VR headset. I'm assuming the HP Reverb G2 Version 2 is still one of the best choices for people who mainly want to use it for simulations. Would this be a fair or correct assessment for 2022 still? Also, I'm a "VR noob". I read or saw that the switches in high fidelity cockpits can be operated by using one's fingers in the virtual space. That's what I want - I want to "naturally" or "organically" be able to press buttons and switches in the cockpit in VR, instead of mapping them all to joysticks or the keyboard. Can someone with VR experience, ideally with the HP headset, enlighten me: How, and how well, does this work? Do I need the controllers for it, or can I order the headset without controllers and still have this functionality? If one needs the controllers, does that mean one is constantly picking up the controllers and switching back to the flight stick, "blind folded", or is there a better way? Thanks!! edit: I did stumble over PointCTRL but the original thread is five years old? One can seemingly order kits, but they look like prototypes. Anyone know of any status for this, or any alternative products? edit (2): also, p.s., any truth to this reddit post claiming that "gaze control" (I'm assuming that is, have a virtual mouse pointer where you look, then use a HOTAS button to click) is broken or removed?