Nightstorm

@prccowboy Thank you for the reminder! And for the new toys Updated database for the P8 as well as the aircraft in the Special Mission Aircraft and Operator's AI Mod. RWR database: DCS RWR Symbology (digitalcombatsimulator.com) Mission Aircraft (not my mod): Special Mission Aircraft and Operator's AI Mod V1.0 (digitalcombatsimulator.com)

The OpenXR mod contains a folder with two files in it and three other files that go in the BIN folder under DCS. OBS pugin (Folder, I presume it's a misspelling of PLUGIN but that's the way it is) in that folder there are: win-ocd3d.dll win-ocd3d.pdb And then the three files are: D3DComiler_47.dll dated 6/5/21 opencomposite.ini openvr_api.dll dated 3/31/22. The two I specified the date stamp are files that replace original versions in DCS. So, if the date doesn't match, they're not the versions from OpenXR mod. And then, the 3DMigoto mod is in its own folder under BIN. It's not directly related to the OpenXR mod, but the last version includes a compatible version. It has these files: NOTE: I renamed the 3DMigoto loader.exe file to just Loader.exe. It doesn't matter what it's called. You need to run the Loader.exe before you start DCS. It'll open a window that looks like this: Then just open WMR portal and start DCS in VR mode. As soon as DCS is running that window will have a line that it found the DCS.exe process and close. Once in DCS you can confirm that 3DMigoto is running by using SHF F7 to bring up it's menu. The OpenXR version requires that it be run in a separate folder from BIN and because of that, the loader needs to be run. There was a compatibility issue with the D3DComiler_47.dll used by OpenXR and this resolved it. One extra step, but minor.

It does indeed still work fine with OB 2.7.11.22211. I always revert my install to a stock / unmodified state before an update and then clear the shaders just to be sure. In an earlier post, I mentioned I started getting random crashes on a couple of video driver related DLL's. Turns out that I had FSR turned on for the sharpening. It really doesn't seem to like having FSR turned on. So, I'm using the 3DMigoto latest version for the sharpening only and OpenXR for everything else and the performance is still just as good. Both mods work together just fine. The current release has a version specifically for OpenXR. 3Dmigoto VR enhancer (digitalcombatsimulator.com)

I've noticed with my current settings etc I'm often sitting really close to 45 FPS. I do not have motion reprojection turned on, and IF it's maintaining that 45 FPS, things seem really smooth. So, I guess that's the "soft lock". I'm using a 3090 and nothing is limiting the FPS except the eye candy. When it drops to say 40 FPS, I get stuttering. Also, related to using Process Lasso, I set up a rule to keep the Mixed Reality Portal from using the same CPU core's that I have assigned to DCS. The result was, DCS started crashing upon entering or just before entering the sim environment on either an Nvidia DLL (nvwgf2umx.dll) or dx3d11.dll. I had just made that change yesterday morning and all the sudden it was crashing like crazy. Rolled that change back by just deleting the rules applied in Process Lasso for WMR and the crashing stopped. So, be advised.

@Flappie Good morning, the filter was working prior to this release DCS 2.7.11.22041 Open Beta hot fix patch.

How To: Process Lasso – Simple DCS World Tuning Thud's VR4DCS These are the settings that I have from following the tutorial I read some time ago. You'll have to identify which cores are the performance cores for your CPU. That's accomplished in BIOS usually. The 0-1/16-17 were my performance cores that run at 4.5GHz. I added 8-9 today and verified with MSI Afterburner that it's indeed using all three of those cores and six threads. And the increase I mentioned. In effect, DCS received a 50% increase in CPU power.

My system is just over three years old, built it in 2019. It's a i9-9900x @ 4.1 on all cores and 4.5 on the "fast" cores. I'm running a 3090 that I'll be swapping for a 3090Ti soon. 3090 will go to my wife's system and replace her 2080Ti. I've been using Process Lasso for some time now, recommended at one point or another in the optimization guides. At the time it was recommended to set the CPU affinity to DCS to the threads of the two performance cores on this generation of CPU's. So, that's what I've been doing for a long time. Running DCS on four threads, that fastest four. I happened upon a comment and answer in the VR4DCS Discord where there was evidently some recent change that DCS could now use three cores / six threads. So, I set the affinity of DCS.exe for two additional threads. I went from having to run at 80% custom render scale to 100% with the same settings. I'd estimate I picked up 10 FPS or so. If any of you are doing the same thing with Process Lasso, give it a try. I'm enjoying DCS with good performance and awesome visuals and no Steam VR.

Ammo types are selected in mission editor. There is a drop down. Default is no tracers which is accurate for actual aircraft. Once it's saved in a mission, you won't have to set them again for that mission.

Everything here is based on installing "OpenXR Tools for Windows Mixed Reality". So, if your headset doesn't use Windows Mixed Reality, none of this will apply.

Personally, the 60Hz flicker on the G2 gives me an instant headache.

I've tried several different things. Making sure no other shader mods are installed, the switcharoo (four times) clearing cache etc. With MR on I get the swimming artifact when taxing, a little bit even on the menus, but most noticeably when I fly through any cloud. I'm still trying to find the right balance with MR off and it really seems to be mission dependent now. Of course, the more stuff in a mission, the bigger the hit on the CPU. Here's hoping that MR issues do get resolved soon. That would be awesome.

From what I'm seeing, I've got similar performance now with some settings a bit higher than I had in SVR. And the benefit of not have to start Steam at all. There were some cases that it took me almost half an hour to get Steam VR to cooperate and let me fly. The irony was, I was trying to fly to relax, but it would piss me off so much that by the time I got to I didn't want to. I have actually NOT flown because I didn't want to deal with Steam VR and all the hoops. "Steam VR does not support VR." That message always made me pull my hair out. I mean, it's kind of IN THE NAME. And a reboot would clear stuff up. Non sensical. So, with OpenXR, Steam VR can just eff right off. I don't miss it. I start WMR, I start DCS. I fly. Period.

I was asking about something similar. See the reason a few posts up. https://forum.dcs.world/topic/295123-update-14-v063-openxr-quickstart-guide-for-g2-g1-and-other-headsets/?do=findComment&comment=4938103 For my system I found having it set at 75% which is roughly 2700x2700 is a nice balance. Motion Reprojection off and decent FPS and some stutters but not terrible. Ironically, it appears more fluid to me at 75% then it does at 50% and the shimmering is much improved.

Thank you.

Yes, the toolkit. It doesn't export but it can show you data on screen in real time.

Question for clarification. I'm running a G2 and the default resolution is 2160x2160 per eye. In steam VR my settings were as close to native resolution as I could get. So, based on that, when the custom render scale is set at 100% are we getting 2160x2160? And is it a linear change from there? I.E. custom render scale at 60% would be 1296 x 1296 per eye? Thanks, Based on a setting of 100% I see this on the second tab: So, it is in fact upscaled to 3172x3096.

Well, it's completely safe, just a few files, so you really don't have much to lose in trying it.

@lefuneste01Thank you again for all of your work on this. I've been using the various versions of this for a long time. I'm currently using the beta version you released for OpenXR. Can I integrate the latest version with the OpenXR compatible one by replacing the files? Adding the loader section to the d3dx.ini of course. Thank you, *EDIT* Seems to work just fine. From what I could see the changes were to the D3DX.INI, which needs to have the loader section added to it, and several of the shaders were rebuilt with a 4/1/22 date. Replacing the v15.0 files with all of those and the OpenXR version still appears to do what it should.

It appears a lot of radio related issues were fixed but another might have been introduced. In the FC3 aircraft and related mods you have the command for the Radio Filter that cycles between three modes. When "Player communication" was selected previously you would only get AWACS BRA reports when requested. Now Darkstar won't stop talking. "Darkstar 1-1, Colt 1-1 JUDY JUDY!!" It'd be nice to have that command too AKA "Stop talking on the radio. I see him." I've turned off Radio Assists and Allied reports, however AWACS just won't shut it. Is this a bug? Thanks.

Thank you. That's what I thought the case was. I install the mod via OvGME and will treat it the same as all other mods when DCS is updated. That's good news. That means this will likely hold us over until the day that Vulan is implemented, whenever that will be

Thank you to everyone that's been involved in this. Over the last few days, I've read through this thread and experimented on my own. I have a reasonably high-end system but I've always struggled to reach the smoothness that others have described. In some cases I suppose, with the settings bottomed out I've had DCS running completely smooth in VR but it to me, looks like kaka. Smooth kaka, but kaka none the less. So, I have typically settled for a compromise in Steam VR/DCS settings. Reasonable looking quality but is ok performance. Playable, but I've always had stutters when looking at the ground etc. I was typically getting an average of 40FPS according to FPSVR. Always had trouble hitting 45. Motion reprojection in SteamVR picked up the slack. Now, using OpenXR, with all of the stuff installed as per instructions, I'm finding that I'm getting better performance with motion reprojection off then I do with SteamVR and MR on at the same settings. I'm typically hitting 45FPS most of the time in OpenXR. There is still some stuttering here and there but all in all, it looks smoother to me. When I turn on motion reprojection in OpenXR, it becomes completely smooth in most areas. In fact, I was elated because it's the way I always wanted it to run. However, I too have the same bubbly / swimming artifacts with MR turned on. The HUD, even parts of the cockpit edges swim and distort as I fly through clouds for example, or even when taxiing. I hope that these issues can be worked through. If so, this will be completely awesome. I've tried the runtime switch a couple of times as it was described without a change. It seemed to have no effect on my system. As it is now, for me personally, SteavVR is out of a job. At least for DCS. This is much easier to adjust, faster, and it simply works. The fact that it works better than SteamVR for me is icing on the cake. I don't play multi-player and just enjoy flying my own missions. So again, great job to everyone I'm very excited to see this continue to improve! One question for clarities sake. I haven't seen it posted anywhere that a specific version of DCS is required. I presume, that this works in a similar manner to Reshade in that, it didn't care if the DCS version changes, it's just a part of the rendering pipeline when installed. The concern being, when there is an Open Beta update, will this need to be updated as well? Or will it just continue to work as is? Barring some change to the way DCS handled rendering of course. When Vulcan comes out, it wouldn't work for example. Thank you,

I've never tried to use the CFT mod w/o having the module activated. Both the CFT and the integrated F-16I SUFA were intended to be used with the Viper module. The Viper is an awesome aircraft, and it just recently got some significant improvements in the last open beta. You may be able to use the stock Viper as an AI unit but, I doubt any mods other than liveries would work with it.

@FoxHoundELite You stated: "well i got this message when launching DCS with both mods installed, however, if i uninstalled the CFT mod, this message is no longer displayed ( i dont have Viper module btw)" The CFT mod is for the Viper module. I wouldn't expect it would work without it.

*UPDATE* I updated the specs on the 9X and the 9X2. Previously we had no access to the 9X. Now the progression in performance is a little more noticeable between the 9X, 9X2, 9X2+ and 9X3. The Viper of course can only use the 9X and the 9X2+. The others are only useable on FC3 or 3rd party mods like the F22.