ChariotOfFLAME

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

The bug has bitten. Welcome to the club! Tough time to join, given the state of the VR industry, but we’ll try to help out best we can!

Do I need to update NVPI every driver update?

Is there a reason there isn't a static speedboat unit? @Eight Ball

My performance is not as good with QVFR, as I can't limit the field of view like I can with OpenXR Toolkit. Here is what I'm seeing when I use HAM mode, which exaggerates the issue: And here's my log file:XR_APILAYER_MBUCCHIA_toolkit.log If anyone has any ideas on how to recalibrate what OpenXR Toolkit considers to be the outer ring, or where that value is stored, that would be very helpful!

I’m running a Reverb G2. QVFR won’t work for me

Hi folks. I'm having an issue where I'm seeing a portion of the center of my vision that OpenXR Toolkit believes is part of the Outer ring, see below (behind the menu, the triangle of culled pixel region): Note that menus and overlays are not impacted; only the game world. I have tried safe mode, uninstall/reinstall, with no luck. Is there some other config file I should get rid of? I have a Reverb G2, 4080 Super. @mbucchia I know this project is as dead as the support for my headset, but any tips on things I could try would be super awesome, but I'll understand if the answer is no.

But its through the installer itself that is throwing the error, not Windows Defender. I don't have an antivirus program... except Windows Defender. Would I just ignore/exception the downloads directory in Defender to resolve this?

I'm getting an error from the native updater that DCS World\Mods/aircraft/F-4E/bin/HeatblurJester.dll is a virus. Anyone know how to get around this? Tried both types of repairs. autoupdate_log.txt

Getting a message from the installer that HeatblurJester.dll is virus. Any ideas why this is happening and how to fix it?null

Hi @NineLine, Thanks so much for the update! In the message, it refers to the following map that does not appear to be included. Any idea where I could find it? The included map does not appear to reference the Channel map: Thanks again!

I'd say, apply DLSS to everything but displays. It's feasible and done with on-screen displays in other games that aren't flight sims

I'm just curious what settings you are running these days!

I know this comes up every patch, but I'm getting a sense that this may actually matter this time. Would y'all answer my poll about VR performance in MT in Win11 vs Win10? Trying to debunk a theory...

Ok folks, I need your help: I'm seeing some correlation, but I need some data to see if it's causation! Can you quote this message with the following: Windows 10 or 11? Have you seen significant improvement, especially in historically challenging scenarios such as Supercarrier, Mariannas, etc. If possible share your FPS or frametime differences from pre-MT to MT I just need those two questions answered. Thanks everyone!

Out of curiosity, Windows 10 or 11?

Any chance in a future update we could get a checkbox to toggle OpenXR from within the game, rather than needing a command line argument?

I concur: the smoke is much improved! Thank you, ED!!!! For all those looking to have longer hangtimes for the smoke, the mod above still works, but it breaks IC, so keep that in mind. ED cannot implement that long for smoke for various reasons, but Open Beta 2.8.2.35632 features a significant improvement!

Then there is hope for WMR Software updates yet...

@mbucchiadid you survive?

Your system will struggle with VR, but with a decent amount of compromises, you will be able to happily fly. but do note that at least a 3-year old i9 and a 2080 is recommended to get decent performance in VR without making too many compromises.

The V1 cable doesn't work on some AMD chipsets. Most external/add-on USB controllers use a standard ASROCK controller, which the V1 cable does work with. You likely have the V2 cable, which fixes this (particular) issue,

As of today, both builds of DCS Open beta/Stable 2.8.1.34667.2 still have not resolved the issue with the airshow smoke, even in the Stable build. modifying/breaking Integrity Check is still required to get smoke representative of how it was in 2.7. Something akin to what is needed to fix this was implemented in less than 12 hours by a community member. Any chance we can get this fixed for the next build?

See DCS 2.8 Multithreading Development Progress. (digitalcombatsimulator.com)