ChariotOfFLAME

It may be due to some sort of USB management in windows. I highly suggest going to your USB devices menu and ensuring that all of your USB devices are not set to sleep when inactive.

You also may not need to upgrade: https://forums.mudspike.com/t/new-wmr-driver-reverb-g2-saved-on-windows-11/17333/5

Pimax QA strikes again… You likely have defective/improperly installed lenses and will need to work with Pimax to get a replacement unit. Check with their support first, but I bet this is what happened.

Yeah, check every driver, as well as the MOBO bios to make sure everything is up-to-date, and murder any and all bloatware

I also recommend increasing your resolution to 1.5x in either Oculus Tray Tool or Diagnostic tool. If you want even more Rez where you look, QuadViews with an increased center resolution can help too

I think getting used to the VR quirks with the Q2 is good advice, then switch up to Q3 when you feel like you’re in the groove

Ensure in your device manager settings you have set all USB devices to never sleep or power save.

Standard disclaimer that tracks from previous DCS versions may not operate as expected, or at all

This was may be due to the recent CPU issues in the previous patch. Try the hotfix from today and see if that helps!

But any X3D will do

My brother (@Brother_Leb) and I repeatedly fly a very lite mission on a self-hosted server with no mods and only 2 jets and like 5 static objects. Recently we both are receiving the following error when trying to load Replays of our flights: Here is the Track file: server-20250520-204029.trk Here is the crash log: dcs.log Here is the miz file: Paphos_Airshow_FILMING_v5.miz Here is a related issue, but I believe they may be different: https://forum.dcs.world/topic/343255-dcs-crash-when-loading-replays/#comment-5380922 Does anyone know why this could be happening? I flew a solo flight (on a multiplayer server I hosted with the same details as the logged flight) the other day, and I can replay that flight just fine. Its only when my brother flies with me that the issue occurs.

Well, just in case, I’ve stopped all updates to Meta Desktop and the Q3 until I hear from y’all theyve got this fixed

If the OVR service is the issue, does making Oculus the default OpenXR runtime make a difference? Or does Meta Desktop run in OVR?

@Qcumber you may have already posted this, but do you have a settings table with avg % impact of each setting higher than lowest? I feel like you’ve got enough data to do that at this point? I also understand how much work creating that can be

That would be the spotting dot setting and visible range setting, I believe

As promised, here is the duplicator: https://github.com/ChariotOfFLAME/DCS-StaticTemplateDuplicator NOTE: think of this as a small-group duplicator; it is for use with things like SAM sites, static aircraft displays, beach clutter, etc. It is not for use with map-wide or airport-specific templates. e.g. use it as a way to create re-usable templates for common groups of units you use frequently across missions in all theatres. As stated above: Hope you all like it!

Static Templates treat the unedited Neutral Bullseye as coordinates [0,0]. This used to be an issue, but now with the multiselect tool, one the steps to saving template for use elsewhere will be moving the units you want to use for the template as close to the original Neutral Bullseye as possible. After converting the file to all environments, when you import the static template, the units will spawn in that relative position to that map’s original Neutral Bullseye. Due to Nevada having its NB at the very top of the visible map, I highly suggest placing the units directly BELOW NB so you can still see them when you load the template (though the multiselect tool will still work to nab those pesky units above the map)

Alright, I’ve got what I need! I’ll share the duplicator once I get back to a computer to finalize the code!

I have created a StaticTemplate propagation python script I plan on "releasing" in User Files designed to allow the use of Static Template created on one terrain to be used on all terrains (I understand this is not the intended use of Static Templates). The last piece I am missing is the full list of ["theatre"] values that can be found at the end of any stm file (and/or the name of the terrain folders in DCS World/Mods/terrains). Here is what I have so far: Caucasus Falklands Kola MarianaIslands Syria Nevada Channel PersianGulf Normandy Sinai GermanyCW (TY @Rudel_chw) Afghanistan (TY @Brother_Leb) Iraq (TY @Brother_Leb) EDIT: this community is great! Thanks everyone! Here is the post where I shared the duplicator: Thanks!

Copying this over from what @Brother_Leb sent me in Discord. This is specifically for use with a link cable: gear: https://www.amazon.com/Oculus-Cable-Charging-Charger-Headset-Accessories/dp/B0BRQMFDQ3 guide: Familiarize yourself with your headset: - a. Start just by getting the headset out of the box, attaching your new strap, firing it up - b. I recommend just following all the suggested stuff that Meta recommends for new headset users (you won't need or use it all, but it's helpful to know) NOTE: You CAN use the double tap to switch to pass-thru mode while in DCS, but unlike with the G2, it freezes the mirror and stops interacting with the sim (including recieving HOTAS inputs AFAIK). I have not experimented with pass-thru regions or handtracking in DCS yet, but I want to. Oculus Debug Tool Settings - under the "Oculus Link" section, set "Video Codec" to H.264; - set "Encode Dynamic Bitrate" to "Disabled" - set "Encode Bitrate (Mbps)" to 900 by typing 900 into Notepad and copy-pasting into the Debug Tool (it won't let you type a number higher than 500 for some reason) - I have so far not needed to change anything else NOTE: if you change anything in the section above "Oculus Link" it will not save the next time you launch your headset. This is why people use the Oculus Tray Tool. I haven't found I need any of that stuff, but if you want to change it, I would suggest using the Tray Tool. Meta Quest Link - a. Download, install, and launch - b. connect headset to PC using link cable (connect directly to headset, NOT thru battery strap) - c. IMPORTANT: Put on headset and either A) Select the "Link" tab in the "Settings" menu and toggle "Link" on and then select "Launch" or B) once you've done A at least once you can use the notification that pops up to "Enable" Oculus Link *on the headset, too,* NOTE: DO NOT launch any apps from the Link menu in your headset, launch them from your PC - On your PC Link App, in your "Devices" tab, click on your Q3 (the picture) and scroll down to "Graphics Settings" in the menu that appears on the right side of the app. Set your refresh rate to 72hz (though you may want to experiement with higher settings later, see DCS Settings below) and set your pixel density to 1.3x (or as high as it will let you). DCS Settings - Keep them the same as the G2 and adjust for performance. So far, I'm pretty close to my G2 settings with things like "Forest Details" and "Scenery Details" scaled back, but I think I'm going to bump them back up and see how it goes - IMPORTANT: set your max framerate as close to whatever hz your heaset is running at (e.g., mine's currently 72hz and FPS max is 75, since it only does increments of 5). Smoothest performance will match hz and framerate (e.g., 90hz and either 90 or 45 fps). You can also cap the framerate using ASW in the Oculus Debug or Tray Tools. Experiment and see what works. 72hz and 75 FPS has been very smooth for me in 95% of situations (and lower GPU load than with the G2!) OpenXR Toolkit Settings - a. In sim, use your shortcuts to open the OXRTK menu (mine are LCTRL + LAFT + 2) - b. Turn off anything you have on except Turbo Mode, keep that on (or turn it on) - c. You can also use the world-scale adjustment (mine's currently at 1.05, I think. YMMV) - NOTE: I find the advanced FPS statistics counter in OXRTK much better than the native DCS one for FPS testing. Alternatively, you could also use GPU-z (https://www.techpowerup.com/gpuz/) but you'll have to refer to your monitor for the stats. Q3 startup checklist: - turn on PC - plug in HOTAS - launch Oculus Link App on PC - put on Q3 (which will turn on the headset) - Plug in link cable to Q3 - "Enable" Oculus Link in Q3 headset UI - launch any 3rd party apps (DTC, SRS, etc.) - Launch DCS That's it. It's actually much simpler than the G2 setup in our opinion. And so far we’re getting a very smooth and solid 60+fps in 95% of all situations in sim right now. Biggest factor was matching hz and fps. We also suggest using DLSS Preset J, and QuadViews Foveated Rendering, which you can find in these forums. We don’t know best settings for Virtual Desktop, as we’re not using it. let us know if you have any questions!

Just a heads up that Windows Mixed Reality will be officially unsupported by Microsoft come October of this year. if you are on the latest Windows 11 update, it’s possible it’s already been removed from you system and cannot be added back. The Reverb G2 will not work without it, and nobody has managed to reverse engineer Windows Mixed Reality. if you’re still on Windows 10 (like me) it should work until October though. let us know if you start considering alternate headset options, as there are a decent group available today, all the their own benefits and drawbacks Now with that out of the way, here are my suggestions for getting a good experience: Increase performance and visual smoothness/anti-aliasing: Force DLSS Preset J (no need to do the regedit step) Enable DLSS Quality in DCS Settings (should enable DLAA by default, which will be the actual helper for your issue) QuadViews Foveated Rendering QuadViews Companion (for adjusting QVFR settings easily) Enable QVFR in DCS Settings

Same here, but on standalone

Good to know. And I haven't gotten a clear answer on this: Do you need to reset the DLSS DLL Override and DLSS Present every time there's a new NVIDIA Driver?

This looks awesome! My brother an I can now develop and fly our own ongoing coop campaigns together! WOW! A couple of requests for the next iteration: Switchology state saved (each switch in-cockpit's state saved: which MFD screen you were on, the brightness/contrast settings, each knob's state saved, markpoints saved, what mode your TGP was in, what mode your HUD was in and its rejects, Rad vs. Baro Alt, custom altimeter setting, etc... if you can set it/interact with it in the cockpit, it should be saved). Aside: it'd be amazing to have an option in the miz editor, even if its essentially coding a LUA, to be able to set the initial state of every switch, panel, system, etc. in an aircraft for all player/client slots for both single and multiplayer (I know the "Prepare Mission" option exists, but I have heard and experienced mixed results in it sticking for Single Player, and that it doesn't work for Multiplayer. I'd be happy to be corrected, though!) For .sav: saving all client/player states, and restoring those client/player locations if they choose the same slot and click spawn within a certain (adjustable) timeframe after .sav mission start. If the client/player does not rejoin within that timeframe, default to point-of-origin. (this all will likely require a menu option for clients that is "resume last flight" to make the UX for this easier and make it so clients/players do not need to find the exact same slot or wrestle with dynamic spawns). next iteration: allow host to choose between point-of-origin, nearest airfield/carrier, or get rid of the timer entirely and allow the clients/players to resume last flight, even if that area is now an unreasonable place to spawn. I also definitely recommend getting a general consensus from mission makers as to a standard way to handle used/expired/in-progress scripts and triggers and then just starting to go in a direction and letting to community adjust to that choice. If you have to pivot, it would be nice to provide a way to convert the old way to the new way whenever that happens, but I think missions builders would just like the functionality sooner than later. As it is said (and as you are doing with this release!), don't let the pursuit of perfection stand in the way of progress. Amazing work so far, and thank all the developers for continuing to think outside the box with DCS and not just releasing what you know/are comfortable with and continuing to push this product forward; even if most players take such advances for granted, we are all thankful for them! Keep up the hard work!

I have a Reverb G2, but plan to move to a MQ3, so I have been doing research and know what I am looking for. Below are the things I’d try, in order, if I saw what you are describing: Increase performance and visual smoothness/anti-aliasing: Force DLSS Preset J (no need to do the regedit step) Enable DLSS Quality in DCS Settings (should enable DLAA by default, which will be the actual helper for your issue) QuadViews Foveated Rendering QuadViews Companion (for adjusting QVFR settings easily) Enable QVFR in DCS Settings Brute-force aliasing into submission using resolution (may heavily impact performance) Increase Quest Render Resolution by a tick at a time to see if that helps (either in meta quest app, or debug tool depending on on Link Cable or VD) reset Quest Render Resolution and try increasing DCS PD setting by 0.1, then repeat last step. hopefully these ideas will get you where you want to be! if you want explanations as to why I’m using these steps, just let me know and I’m happy to explain