Matrix9

OpenXR is more widely supported, and provides (for me) the best performance for WMR and Reverb G2.

Not with my HP Reverb G2. Setting OpenXR Tools -> Motion Reprojection = Always On results in DCS OB freezing at the DCS Hangar Screen. Motion Reprojection = Automatic or Disabled results in DCS starting properly.

My wish list: Sepecat Jaguar TSR2 V-22 Osprey CH-47 or C/MH-53 Hawker Sea Fury Spitfire Mk. XIV or later - Griffon engine.

Further feedback. I've just installed 1.0.5. I've tried to bind left and right wheelbrakes to rudder brake pedal axes, but there doesn't appear to be any braking action when I press the brake pedals, no matter how I adjust the axis curves, orientation and dead space. So far I can only brake by binding a button to "Wheel Brakes On".

Hello, I've just started using this mod and it is a lot of fun. However, one or two minor points detract: At present I seem to need to have one switch bound to "Cannon" and another to "Weapon Release", and press both to fire the gun. Is this correct? I can't seem to bind "Fire Cannon" to one switch/trigger on my controls. Gun sound is not very realistic, and I don't get many rounds either. Really tedious voice warnings for "Over G" and tones for low speed, RWR threat and others. Any means of reducing or disabling these? General reliance on SU-33 for things like HUD symbology. Any means of changing this? I'm looking forward to further updates. Keep up the good work.

I've had a frustrating number of BSOD crashes caused by GraphicsVista.dll access violations. Here's a typical crash dump: Microsoft (R) Windows Debugger Version 10.0.19041.685 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Steve_DCS\Saved Games\DCS.openbeta\Logs\dcs.20210803-202020.dmp] User Mini Dump File: Only registers, stack and portions of memory are available Symbol search path is: srv* Executable search path is: Windows 10 Version 19043 MP (16 procs) Free x64 Product: WinNt, suite: SingleUserTS 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Debug session time: Tue Aug 3 21:20:21.000 2021 (UTC + 1:00) System Uptime: not available Process Uptime: 0 days 1:03:36.000 ................... This dump file has an exception of interest stored in it. The stored exception information can be accessed via .ecxr. (2b30.4848): Access violation - code c0000005 (first/second chance not available) For analysis of this file, run !analyze -v ntdll!NtGetContextThread+0x14: 00007ffd`5e28ec54 c3 ret 0:000> !analyze -v ******************************************************************************* * * * Exception Analysis * * * ******************************************************************************* *** WARNING: Unable to verify checksum for CockpitBase.dll KEY_VALUES_STRING: 1 Key : AV.Fault Value: Write Key : Analysis.CPU.Sec Value: 0 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on TITAN Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 3 Key : Analysis.Memory.CommitPeak.Mb Value: 88 Key : Analysis.System Value: CreateObject Key : Timeline.Process.Start.DeltaSec Value: 3816 CONTEXT: (.ecxr) rax=00000000ffffffff rbx=0000000000000001 rcx=000001f6954d4f08 rdx=000001f6c84a9748 rsi=00007ffcf0b3b8a8 rdi=000001f6c84a9720 rip=00007ffd1d2e3c2b rsp=000000b071cff3e8 rbp=000001d8364ee340 r8=0000000000000000 r9=0000000000000001 r10=0000000000008000 r11=000000b071cff360 r12=00007ffcf0a1815c r13=0000000000000000 r14=000000b071cff588 r15=000001d8364ed770 iopl=0 nv up ei pl nz na pe nc cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010202 GraphicsVista!Graphics::ModelPtr::release+0x1b: 00007ffd`1d2e3c2b f00fc101 lock xadd dword ptr [rcx],eax ds:000001f6`954d4f08=???????? Resetting default scope EXCEPTION_RECORD: (.exr -1) ExceptionAddress: 00007ffd1d2e3c2b (GraphicsVista!Graphics::ModelPtr::release+0x000000000000001b) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000001 Parameter[1]: 000001f6954d4f08 Attempt to write to address 000001f6954d4f08 PROCESS_NAME: DCS.exe WRITE_ADDRESS: 000001f6954d4f08 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s. EXCEPTION_CODE_STR: c0000005 EXCEPTION_PARAMETER1: 0000000000000001 EXCEPTION_PARAMETER2: 000001f6954d4f08 STACK_TEXT: 000000b0`71cff3e8 00007ffc`f09c09c9 : 000001f6`c84a9720 00007ffc`f09c4217 000001f6`c84a9720 000001d8`00000000 : GraphicsVista!Graphics::ModelPtr::release+0x1b 000000b0`71cff3f0 00007ffc`f09c6179 : 00000000`00000001 00000000`00000000 00000000`00000000 00007ffd`5e2147b1 : CockpitBase!cockpit::ceFont::~ceFont+0x39 000000b0`71cff430 00007ffc`f0872ee2 : 000001f7`49e7a7c0 000001d8`364ed770 000001d8`364ed770 00007ffc`f0a2ba53 : CockpitBase!cockpit::ceFont::construct+0x5789 000000b0`71cff460 00007ffc`f09981ce : 000001d8`364e7270 000000b0`00000000 ffffffff`fffffffe 000001d8`364ed770 : CockpitBase!UID_base::~UID_base+0x252 000000b0`71cff490 00007ffd`5b9442d6 : 000001d8`364edea8 000001d8`364ed770 ffffffff`ffffffff 00007ffc`f0865f80 : CockpitBase!cockpit::ccDrawable::ccDrawable+0x9e 000000b0`71cff4c0 00007ffd`5b9441fb : 00000000`00000000 000000b0`71cff588 000000b0`71cff840 00007ffd`5ba20e40 : ucrtbase!<lambda_f03950bc5685219e0bcd2087efbe011e>::operator()+0xa6 000000b0`71cff510 00007ffd`5b9441b4 : 00000000`00000000 00000000`00000001 00000000`00000001 000000b0`71cff578 : ucrtbase!__crt_seh_guarded_call<int>::operator()<<lambda_7777bce6b2f8c936911f934f8298dc43>,<lambda_f03950bc5685219e0bcd2087efbe011e> &,<lambda_3883c3dff614d5e0c5f61bb1ac94921c> >+0x3b 000000b0`71cff540 00007ffc`f0a17fea : 00007ffc`f0b3e1f8 000000b0`00000002 00000000`00000002 000000b0`71cff570 : ucrtbase!execute_onexit_table+0x34 000000b0`71cff570 00007ffc`f0a18110 : 00000000`00000001 000000b0`71cff800 00000000`00000001 00000000`00000000 : CockpitBase!cockpit::VR_capture_holder::update_capture+0xe68a 000000b0`71cff5a0 00007ffd`5e209a1d : 00007ffc`f06f0000 00000000`00000000 00000000`00000001 00000000`7ffe0385 : CockpitBase!cockpit::VR_capture_holder::update_capture+0xe7b0 000000b0`71cff600 00007ffd`5e24db91 : 000001d8`24682770 00007ffc`f06f0000 00007ffc`00000000 000001d8`24682790 : ntdll!LdrpCallInitRoutine+0x61 000000b0`71cff670 00007ffd`5e24da2d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!LdrShutdownProcess+0x141 000000b0`71cff770 00007ffd`5c27e0ab : 00000000`00000000 00000000`00000000 00007ffd`5b9ed3a0 000000b0`71cff840 : ntdll!RtlExitUserProcess+0xad 000000b0`71cff7a0 00007ffd`5b9505bc : 00000000`00000000 00000000`00000000 000000b0`71cff828 00007ffd`5ba20e40 : kernel32!ExitProcessImplementation+0xb 000000b0`71cff7d0 00007ffd`5b95045f : 00000000`00000000 00000000`00000000 00000000`00000000 000000b0`71cff820 : ucrtbase!exit_or_terminate_process+0x44 000000b0`71cff800 00007ff6`be78a2b0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : ucrtbase!common_exit+0x6f 000000b0`71cff850 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : DCS!SW+0x7197b0 SYMBOL_NAME: GraphicsVista!Graphics::ModelPtr::release+1b MODULE_NAME: GraphicsVista IMAGE_NAME: GraphicsVista.dll STACK_COMMAND: ~0s ; .ecxr ; kb FAILURE_BUCKET_ID: INVALID_POINTER_WRITE_c0000005_GraphicsVista.dll!Graphics::ModelPtr::release OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {120850a8-1ccc-7b76-933e-fe2f168d2911} Followup: MachineOwner --------- 0:000> .exr -1 ExceptionAddress: 00007ffd1d2e3c2b (GraphicsVista!Graphics::ModelPtr::release+0x000000000000001b) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000001 Parameter[1]: 000001f6954d4f08 Attempt to write to address 000001f6954d4f08 dcs.20210803-202020.dmp

My Quest 2 recently updated to v 29. Subsequently I experienced constant blue screen WHEA uncorrectable errors every time I entered DCS gameplay. After many hours frustrating troubleshooting I did a factory reset of my Quest 2. It appears to have cured the problem. If I have issues with this in future, it'll be the first thing I try.

Is there an issue with the JDF servers at present? For the last week I have not been able to get on to any of the JDF servers. For the main server, after I try to connect I get a permanent splash screen with a "Please Wait...." message, and the open beta servers do not appear in multiplayer server list and report "Server Offline" if I try to connect using IP address. Does anyone have any information on this?