dutchili

@BIGnewy: the combination Quest 2, Open XR as active runteam, DCS steam edition, run from steam by selecting MT preview results in crash during startup: # -------------- 20230310-170211 -------------- DCS/2.8.3.37556 (x86_64; MT; Windows NT 10.0.22621) C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\bin-mt\dx11backend.dll # C0000005 ACCESS_VIOLATION at 00007ff90f8c7407 00:00000000 SymInit: Symbol-SearchPath: '.', symOptions: 532, UserName: 'xxxxx' OS-Version: 10.0.22621 () 0x300-0x1 0x0000000000017407 (dx11backend): RenderAPI::DX11Renderer::setNewFrameBuffer + 0x37 0x0000000000016188 (dx11backend): RenderAPI::DX11Renderer::pushFrameBuffer + 0x68 0x000000000000bac0 (GraphicsCore): enlight::AtmosphereWrapper::precompute + 0x450 0x00000000000681db (GraphicsCore): render::CopyPass::doCopy + 0x14B 0x00000000000675b3 (GraphicsCore): render::CopyPass::operator= + 0x4A3 0x000000000004343f (GraphicsCore): render::BaseRenderingPass::execute + 0x1F 0x000000000003d9f0 (GraphicsCore): render::RenderGraph::~RenderGraph + 0x29B0 0x00000000000445f2 (GraphicsCore): render::RenderGraph::render + 0x292 0x0000000000116e35 (Visualizer): smSceneManager::regLua + 0x1005 0x0000000000103d09 (Visualizer): smCamera_Implement::getClipRegion + 0x16259 0x00000000000f3916 (Visualizer): smCamera_Implement::getClipRegion + 0x5E66 0x0000000000106a42 (Visualizer): smSceneManager::DestroySceneManager + 0x1542 0x0000000000031fa0 (edCore): ed::thread::_get_current_thread_id + 0xA0 0x0000000000029363 (ucrtbase): _recalloc + 0xA3 0x00000000000126bd (KERNEL32): BaseThreadInitThunk + 0x1D --------------------- I does start when Oculus runtime is selected, but i see no improvement in frametime at all

nullI recall this issues was fixed in a previous OB. Am i wrong? Could this also be a reason for reduced MP performance while 'on the server'? I experienced 18 fps yesterday in MP with about 30 other players and some AI. I've never seen FPS stay that low after take-off. i should add, i was recording with Tacview locally, switched it off now but haven't tested yet. But that should not influence the server list screen right?

Can somebody check in task manager if the thread 'DCS release process' is still running?

PD and MSAA have the most impact on your CPU. The 90 hz refresh rate also requires a lot of frame generation. I'd suggest to set 72hz (gives you 36 fps which appear to be fluid), set PD to 1.0 and to compensate increase the Oculus render resolution. Reduce Textures to medium. you should be able to set visible range to high. Let's us know if this helped.

Hi @SkateZilla, The roadmap newsletter created high expectation (for me) on what to expect this year. Setting forward release dates creates issues with expectation management. But, you don't have to. Given the feedback here i suggest: - release features when they are ready instead of making monthly promises (with all the risks) - increase the release frequency as every feature is a win for those waiting for it.

https://discord.gg/dcaf This is the place to be.

Whether MT and DLSS are in the update or not (i really hope so), an update on the status would be nice. Adding new features that eat CPU time are not welcome IMO without MT.

It slips when you roll quickly. And if it doesn't: it is still not what i want it to do. @BIGNEWY: is there an option / script to disable it?

The rudder seems to deflect automatically when rolling. This causes a lot of unwanted slip during rolls. Can this be switched off?

Is there a way to control volume of uhf and vhf separately when using the ky-58 encryption radio? The normal volume knobs seem ineffective.

Don't you have a contact at the development team for questions like that??

Something is definitely wrong. Looking at the south west part of the island of Guam is causing low FPS> My buddies report the same thing.

@BIGNEWYthe command line parameters don't work for the Steam addition, in combination with Oculus Quest 2.

@BIGNEWY I see a lot of questions here to ED on how to configure for various setups. But no response from ED yet. I would appreciate it if you could provide guidance or state that it will come some day, instead of ignoring the questions.

nullWhen I look heading 240 from Anderson AFB, FPS drops. See the FPS chart with dips and frametime spikes, versus 'constant FPS' for other directions When flying around the island, the problem seems to occur from the center regions (hills) on the western part of the island. Especially the brownish ground elements on the hills.

null

Thanks. I need a solution for steam. These command do not work in steam. @BIGNEWY

@BIGNEWY

I am actually using a quest 2. So the log is definitely wrong. If i set the picked software to use Oculus runtime performance is slightly worse. This also makes me think that they log entry is wrong or... All is wrong

DCS never seems to start in openXR mode for me. Please advice. What i get: Launching via SteamVR with openXR runtime configured (it says in the developer options: "windows mixed reality") DCS log file: VISUALIZER (Main): LAUNCH IN VR OpenVR: OpenVR : Oculus Quest2 Launching via Oculus Home with OpenXR set as the active runtime (not Oculus runtime) VISUALIZER (Main): LAUNCH IN VR OculusRift: OculusRift : Oculus Rift S I've tried using the command line options both through a shortcut and configured in steam. --force_openXR is never respected. Obviously the Companion app overlay is never shown. Please help.

If this all looks fine and the layer is not coming up with ctrl-f2, how can you fix that?

@BIGNEWYPlease provide instruction for using OpenXR tools for Oculus Quest 2 users. I don't see the pop-up when starting DCS anymore, nor can I show the menu with ctrl-f2. After the update i noticed it when starting DCS via the Oculus Home (normal procedure). After switching to the Oculus runtime and back to OpenXR (through Oculus tooling) i don't see the options anymore.

How do you show that config screen for Foveated rendering? (Oculus Quest 2, OpenXR is selected as runtime. I saw this once after the update, but i can't get it back after switching back and forth between Oculus runtine and OpenXR runtime)

Runs fine (same performance as previous version) with OculusVR or OpenXR set as the runtime in Oculus. Haven't tried SteamVR yet with all the fancy tweaking options

i 'fixed' it by setting Oculus back to OculusVR and than enabling the OpenXR runtime again.