Dog 1-1

I haven't been able to get SSA to work since I started using MT standalone. I can get the seat shakers to activate using the test button however I get no sound output from the game itself.

Ever since the new update I cannot get my game to launch in VR mode. It always opens in pancake. I have enabled use virtual reality headset check in options. This occurs in multi thread version and regular. HP reverb G2. I used to set launch options to force OpenXr so I could continue to use neck saver but those launch options are no longer working it seems.

Hello all, I'm having an issue with XR neck safer not working in the new MT build. I forced Open XR runtime just as I had to in the previous OB to get the app to continue to work. However it is producing some strange behavior. I get into dcs and XR neck safer registers movement, it even registers that it is doing the accelerated movement of looking behind me. However my view remains the same. MY JHMCS however shoots out of my view as if it is still being controlled by the app. Also if I look to the side and them zoom in, my view zooms in towards the rear of the plane because thats where XR neck safer is accelerating my view to. However my default zoom level view remains at the point my head is facing. Anybody experiencing something similar? HP reverb G2, standalone version.

This one specifically but I’m sure any one would work. It is not externally powered. PCI-E to USB 3.0 7-Port(2X USB-C - 5X USB-A ) Expansion Card ,PCI Express USB Add in Card , Internal USB3 Hub Converter for Desktop PC Host Card Support Windows 10/8/7/XP and MAC OS 10.8.2 Above https://a.co/d/4OrhudF

I was able to finally solve this issue by getting a USB 3.0 PCI extension card for my PC. To anyone that finds this thread the powered external USB hub that HP recommends did NOT solve my problem. You need to buy a separate PCI usb expansion card to put into your machine. Since I added the expansion card I haven’t had any crashes, and as a bonus the tracking of the headset has improved greatly. Whenever I would look down at the panels in the cockpit the headset would drift causing me to be too low in my seat when I looked back up. Now it tracks very good and there is no drift. I figured that was just the way the headset performs but I can see it’s been broken for a while and now it’s fixed.

So I just removed the page file that I had set and it removed the memory leak. Now no matter how much I F2 around the map the RAM usage tops at 21Gb and the source of that crash is solved. However I just got the blue screen error again and the headset failed. It listed an audio problem right before the device failure again. I'll contact HP about getting the headset repaired but I'm not sure either way. dcs.log

C:\Users\>wmic pagefile list /format:list AllocatedBaseSize=16384 CurrentUsage=414 Description=C:\pagefile.sys InstallDate=20220828211649.117791-300 Name=C:\pagefile.sys PeakUsage=879 Status= TempPageFile=FALSE So I set a pagefile according to the forums when this problem began. I've tried a few more times inside the game and it would appear that there is a massive memory leak taking place. When I join a server I can see my Ram steadily being used and as soon as I hit 34 GB of usage the game crashes.

Further testing in the task manager and resource monitor shows that as I view different units on the map RAM is committed and not released. I started out on the deck of the carrier using 20 GB of my ram and it goes up rapidly if you F2 different units around the map. When my ram hits 34GB of usage, which is insane by the way, my game crashes. This crash is repeatable. Also since I've been doing this test with my headset on the desk I can see a new error message that has been appearing on the screen Opencomposite Error xrWaitSwapchainimage timeout dcs.20221029-150601.dmp dcs.20221029-150601.crash dcs.20221029-150601.log dxdiag.txt hash

Georgia at war, load onto carrier, F2 view on different jets in the server, get to hornet supercruising, instant crash. I had the headset sitting on the desk so no movement through the cable or connector. dcs.20221029-145421.dmp dcs.20221029-145421.log dcs.20221029-145421.crash dxdiag.txt hash

I haven't heard of that being an issue with this headset. I've seen the cable being an issue. I just flew for a little bit on tempest and respawned into a M2000C and it crashed on me again. Before the device unplugged warnings I see that there is always an audio warning. And this seems to coincide with the headset crashing. I always get a loss of sound to my seat shakers, then the screen goes blue, then WMR crashes. I can have the headset sent back to HP for repair but its just strange that DCS is the only game this happens with. dcs.log-20221029-031824.zip

It happened on a factory new cable that I received earlier.

BUMP. Received the replacement cable from HP earlier. I've been playing most of the day without incident. However on Blue Tempest server the issue continued to happen. It really seems to be audio related. dcs.log

I have a replacement cable on the way from HP. However I kept trouble shooting and I was able to reproduce the bug and push it all the way to a crash. When the audio file of a jet in afterburner is played it triggers the blue screen and eventual crash if the sound file is played long enough. I was able to reproduce the bug on the blue flag server sitting on the taxi way while jets did low passes and took off overhead. Log attached. dcs.20221026-184320.crash dcs.log

I'll start looking at HP for cable replacement options. In any case, There is a windows event log error at the time of the blue screen: Faulting application name: DCS.exe, version: 2.7.18.30765, time stamp: 0x63359821 Faulting module name: DCS.exe, version: 2.7.18.30765, time stamp: 0x63359821 Exception code: 0xc0000005 Fault offset: 0x00000000008fb939 Faulting process id: 0x4308 Faulting application start time: 0x01d8e816ec3e6cda Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\bin\DCS.exe Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\bin\DCS.exe Report Id: 4f433690-ea99-4fa0-8117-f7197f9aa12c Faulting package full name: Faulting package-relative application ID: And the event details are: - Provider [ Name] Application Error - EventID 1000 [ Qualifiers] 0 Version 0 Level 2 Task 100 Opcode 0 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2022-10-25T02:26:47.4740634Z EventRecordID 4366 Correlation - Execution [ ProcessID] 0 [ ThreadID] 0 Channel Application Computer DESKTOP-FPSIKMS Security - EventData DCS.exe 2.7.18.30765 63359821 DCS.exe 2.7.18.30765 63359821 c0000005 00000000008fb939 4308 01d8e816ec3e6cda C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\bin\DCS.exe C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\bin\DCS.exe 4f433690-ea99-4fa0-8117-f7197f9aa12c

I saw that that was an issue in the past but my reverb came with the revision 2 cable out of the box. I’ll look at windows event viewer tomorrow and see if there are any errors.