Dodge

I think they are looking at a June(ish) release

Thank you very much @Underscore for the fantastic offer I can confirm that the item has now arrived with the user. The user will be setting this up shortly (once he receives my throttle), and we'll ensure his 'older' setup (X56) is sent to another user (either with our group of friend who needs an upgrade. Otherwise if its not needed within our group of friend we'll post a separate post on here) This post can be completed

Thank you @Underscore

Fabulous. I have actually messaged you @Underscore - With your TM Warthog Throttle, and my TM Warthog Stick, I'd like to combine these to pass onto a friend (who has a X52 Pro) that I wanted to replace his with. He can then pass onto X52 Pro to someone else (family, friends, or on here). If possible, please reply to my PM to you We are UK based

546.33 looks like it's been released today https://us.download.nvidia.com/Windows/546.33/546.33-win11-win10-release-notes.pdf

As with @Zebra1-1 I'm pretty much doing the same thing, without issue Install OpenXR Tools for WMR (via the Microsoft Store). My settings are the following options (yours may vary) Use latest preview OpenXR runtime Customised render scale (mine is set to 115%) Motion Reprojection disabled Prefer frame rate over latency I also have a shortcut of my DCS MT exe on the desktop with the following in the "target" field within the properties [YOUR DRIVE LETTER]:\Steam\steamapps\common\DCSWorld\bin-mt\DCS.exe --force_OpenXR As my DCS is purchased and used within Steam, I just need to ensure that i have start the Steam client (not SteamVR) before starting the DCS shortcut Hope that helps.

I've noticed this to, when attempting to connect one the TDCS Community Training Server

Appreciate the overview and insight. And, whilst I've read elsewhere that there are overall improvements to plane spotting (testing phase), I look forward to seeing these 'issues/oddities' being resolved and released in a future update, soon.

The rendering and weird LOD/disappearing contacts is also something I feel has deteriorated (especially recently; after the last patch). To add to your smoke/tracers only partially rendering in one eye, I can add plane contrails to that (from a distance).

I've noticed this for some time (and definitely since using the MT exe). IIRC, other 'things' do it (or of a similar nature) as well (like the aircraft 'vapour trails')

I have both the Quest 2 and Reverb G2 and use the G2 100% of the time for DCS. I just became extremely frustrated with the constant tinkering of settings to try and get a stable experience. One session/day it may work fine, and another it wouldn't. Especially after Q2 software updates. The image quality isn't as good as the G2 either (although for the price point it's good). With the G2, once the settings were configured to my liking I've never had to change a setting since. As other's have indicated, if you are set on the Q2 it might be prudent to wait for the Q3 (if anything, it should lower the cost of the Q2).

dcs-wii-chat channel in the ED discord (from yesterday) null

There was a message on the DCS Discord server (dcs-wwii-chat channel) with some reference this being worked on, as well as LOD... null

Thank you you for the additional information In my particular instance, I'm using 2xMSAA

Thank you for the tip. I've edited the dots.fx file as indicated and the 'spotting' doesn't look like 'brick/blocks' (large) and feels much better in my instance (also a G2 user with a monitor resolution of 3440x1440). For others who are interested.... It's line 84 in the dots.fx file (here's a snippet of what I've edited) ===Snippet=== // The entire screen in clip space actually goes from -1 to 1, a distance of 2. //float2 scaledDotSize = onePixelSize * sizeMultiplier * controlPixel * 2; float2 scaledDotSize = onePixelSize * sizeMultiplier * controlPixel; ===========

Images are the wrong way around (can't seem to swap them)

https://forums.flightsimulator.com/t/openxr-tools-for-windows-mixed-reality-update-in-the-store-4-14/586988 I didn't notice the other thread containing this update news from the author himself

OpenXR Tools for Windows Mixed Reality Updated - 113.2304.14003 https://github.com/microsoft/OpenXR-MixedReality/releases/tag/113.2304.14003 OpenXR Tools for Windows Mixed Reality - 113.2304.14003 Latest Compare mbucchia-msft released this 8 hours ago 113.2304.14003 a46ea22 Note: This runtime must be enabled from the OpenXR Tools for Windows Mixed Reality, under the Settings tab, by toggling Use latest preview OpenXR runtime on. Changes for Hololens 2: Added support for XR_EXT_hand_interaction (cross-vendor implementation of the hand interaction action profile). Added support for XR_MSFTX_scene_marker (HoloLens 2 QR code location and recognition). Changes for Windows Mixed Reality VR: Added support for temporal post-processing of motion vectors (same algorithm as Windows Mixed Reality for SteamVR). Improves the quality of motion reprojection. Added support for Nvidia Optical Flow as a source of motion vectors. Improves the quality of motion reprojection on Nvidia RTX cards only. Added option "Prefer frame rate over latency". This option allows an application to render frames faster at the cost of additional latency. It can be used in conjunction with motion reprojection. This is similar to the so-called "Turbo Mode" in the 3rd party application "OpenXR Toolkit". Moved motion reprojection rendering to a high-priority command queue to prevent interference from the application. Fixed a hang in Digital Combat Simulator when motion reprojection is enabled. Fixed a bug with transparency when using motion reprojection. Removed "Automatic" motion reprojection mode (which only meant "Enabled only in Flight Simulator 2020"). Added options to limit the motion reprojection rate to a specific fractional rate. General changes: Fixed miscellaneous issues and OpenXR conformance issues. === Noticed this has a mention about a Motion Reproduction fix for DCS (hanging) Access this update via the 'Microsoft Store' app on your WIndows operating system [Added after initial posting] Some detailed explanation of some of the options available: https://forums.flightsimulator.com/t/openxr-tools-for-windows-mixed-reality-update-in-the-store-4-14/586988 Another post discussion this particular version (from Page 3)

I've noticed this while in MP session (example 4YA - WWII servers) *HP Reverb G2 (VR)

It's reproduceable for me in that if I do the following then I have to re-validate my files 0) Start my HP Reverb G2 headset and any associated software that I plan on using (G2 headset and then VoiceAttack) 1) (Forget to start Steam (stable)) 2) Start my 'shortcut' of DCS (MT) 3) Error appears that files are corrupted. (Image of the message is included below) ==Log== === Log opened UTC 2023-04-10 17:04:57 2023-04-10 17:04:57.137 ALERT SECURITYCONTROL (Main): Can't run Steam! 2023-04-10 17:04:57.143 INFO EDCORE (Main): system affinity mask: 1111111111111111 2023-04-10 17:04:57.143 INFO EDCORE (Main): process affinity mask: 1111111111111111 2023-04-10 17:04:57.152 INFO EDCORE (Main): all CPU cores have the same efficiency class 0 2023-04-10 17:04:57.152 INFO EDCORE (Main): common cores: {8, 9, 10, 11, 12, 13, 14, 15} 2023-04-10 17:04:57.152 INFO EDCORE (Main): render cores: {0, 1, 2, 3, 4, 5, 6, 7} 2023-04-10 17:04:57.152 INFO EDCORE (Main): IO cores: {} 2023-04-10 17:04:58.603 INFO EDCORE (Main): Create boot pool. 2023-04-10 17:04:58.603 INFO EDCORE (Main): Created boot pool: n:16 2023-04-10 17:04:58.604 INFO APP (Main): Command line: "D:\Steam\steamapps\common\DCSWorld\bin-mt\DCS.exe" --force_OpenXR 2023-04-10 17:04:58.604 INFO APP (Main): DCS/2.8.3.38090 (x86_64; MT; Windows NT 10.0.22621) 2023-04-10 17:04:58.604 INFO APP (Main): Application revision: 218090 2023-04-10 17:04:58.604 INFO APP (Main): Renderer revision: 23977 2023-04-10 17:04:58.604 INFO APP (Main): Terrain revision: 23938 2023-04-10 17:04:58.604 INFO APP (Main): Build number: 329 2023-04-10 17:04:58.604 INFO APP (Main): CPU cores: 8, threads: 16, System RAM: 65450 MB, Pagefile: 4096 MB === Log closed. Workaround/Or perhaps the way it should be done 0) Start my HP Reverb G2 headset and any associated software that I plan on using (G2 headset and then VoiceAttack) 1) Start the steam client (stable) 2) Start my 'shortcut' of DCS (MT) 3) DCS loads correctly For me, its frustration; As I become older my memory doesn't always remind me to start the 'Steam' client before I run the 'DCS (MT)' shortcut, thus I run into the 'important files are damaged' message - I then have to wait approximately 15mintes each time for the re-validation to complete. @BIGNEWY - If there's anything else needed to have the team take a look at this (again) then let me know and I'll see if I can assist

Yesterday I noticed (on an MP Server TDCS Community Training Server) that one of 3 Spitfires (3 players), one of the spitfires was 'invisible' except for the propellor that was visible (ground and in the air). (Latest DCS Open Beta)