sleighzy

That API layer comes from ReShade. If you yourself did not explicitly install ReShade then another application must have installed it (which seems odd).

Yes. Motion reprojection comes with it's own set of problems though, i.e. injecting "fake" frames, so you can still get artifacting from that which is different than DLSS ghosting.

You have ReShade installed which is causing your OpenXR runtime to fail. Install this tool and untick the box for the ReShade OpenXR API layer: https://github.com/fredemmott/OpenXR-API-Layers-GUI 025-01-17 03:17:58.457 INFO VISUALIZER (Main): [22:17:59.347][Info ] OpenXR: Available Layers: (1) 2025-01-17 03:17:58.457 INFO VISUALIZER (Main): [22:17:59.347][Info ] OpenXR: Name=XR_APILAYER_reshade SpecVersion=1.0.0 LayerVersion=2 Description=crosire's ReShade post-processing injector for 64-bit 2025-01-17 03:17:58.457 INFO VISUALIZER (Main): [22:17:59.347][Info ] OpenXR: Available Extensions: (14) 2025-01-17 03:17:58.457 INFO VISUALIZER (Main): [22:17:59.347][Info ] OpenXR: Name= SpecVersion=0 2025-01-17 03:17:58.457 WARNING LOG (17628): 13 duplicate message(s) skipped. 2025-01-17 03:17:58.457 INFO VISUALIZER (Main): [22:17:59.347][Info ] OpenXR: Enabled extension: XR_KHR_visibility_mask 2025-01-17 03:17:58.457 INFO VISUALIZER (Main): [22:17:59.347][Info ] OpenXR: Enabled extension: XR_EXT_hand_tracking 2025-01-17 03:17:58.458 INFO VISUALIZER (Main): [22:17:59.347][Info ] OpenXR: Enabled extension: XR_EXT_eye_gaze_interaction 2025-01-17 03:17:58.459 ERROR VISUALIZER (Main): OpenXR failure XrResult failure [XR_ERROR_FILE_ACCESS_ERROR] Origin: xrCreateInstance(&createInfo, &instance) Source: Projects\Visualizer\Source\OpenXR\openxr_program.cpp:410 2025-01-17 03:17:58.459 ERROR VISUALIZER (Main): OpenXR exception: XrResult failure [XR_ERROR_FILE_ACCESS_ERROR] Origin: xrCreateInstance(&createInfo, &instance) Source: Projects\Visualizer\Source\OpenXR\openxr_program.cpp:410 2025-01-17 03:17:58.460 INFO VISUALIZER (Main): render thread initialization.. You can remove those parameters from your shortcut as they are not required. They'll also force VR if you attempt to run DCS not using VR. Note, your issue is not related to the original post so in future you should probably raise a new one of your own.

Based on the error in the log it appears that this is the known issue in the Apache with George slaving and deslaving. This has been fixed and will be in the next patch

Given you're using PimaxPlay's, I would. Removes any potential problems or masking of issues. EDIT: the logs show that this isn't installed anyway so nothing to do here.

Ahh, looks like you've attached a log from 2023-06-15 ... maybe you have two DCS Saved Games folder (one for DCS and one for DCS.openbeta)? So yes, the old log showed that version. Might need to attach the latest log from the right place. Also from your screenshots you're using the PimaxPlay Quad Views. The Tallymouse Quad Views Companion app does not control the settings for that. It only updates the settings for Mbucchia's Quad-Views-Foveated.

Additional settings on the VR tab as well: Turn on Use DCS System Resolution Turn off Enable HMD Mask Turn on Crop Source to Rectangle Set Mirror Eye Source to (whatever works best for you)

This log also does not show a game crash. If this was from when the game "crashed" then may be Windows itself "killing" the process. Run the Windows DxDiag tool and attach the output of that here as well when this occurs next.

Your DCS log says you're on version 2.8.6.41066 (really old). Try upgrading to the latest version. The latest version will mean that you'll be using the multithreaded version, which may help with the CPU issues you're seeing. Right now this was being masked when attempting to help as assumptions were made that you were using multithreaded when you weren't. Make sure to create an exclusion in your anti-virus software for your entire DCS installation directory for this. Also delete the fxo and metashaders2 folders after the upgrade. With regards to being on the latest version; single threaded version has been removed now as well, and your "E:\DCS World OpenBeta\bin\DCS.exe" --force_steam_VR" short cut does not need "--force_steam_VR" as everything is now using OpenXR.

For VAICOM for you need to be using VSPX, and hence don't use the sender in the sentence, just the recipient and the command. VoiceAttack does not support wildcards (*) syntax to be used in the profile for key words when using with Whisper. This is not a Whisper issue per se, just that VoiceAttack does not support matching on wildcards when being executed with a passed in command text, which is the way this Whisper integration works and how it passes the transcribed text). The VoiceAttack folk have added this to their feature suggestion list (fingers-crossed for a release). The syntax used in key words by VAICOM's VSPX mode better match what is expected, and I have made updates for the ones that don't (these are available in my provided profile). I have yet to document what updates are needed but you could refer (or directly use may be easier) to my profile for the base set and then just update with any missing recipients. I'll grab a complete set and update with any missing anyway. If there are recipients missing from the "When I say" key word collection in VoiceAttack then this will also not match. Just add the recipients to the list of strings in that VoiceAttack key words collection. Recipients containing any dashes, e.g. I see "X-Men" was mentioned will need to have those changed as I believe those are replaced with space characters out, e.g. this may become "X Men". We do replacements before that so you can add "X-Men=Xmen in the word_mappings.txt file, granted I haven't tested this so not even sure what Whisper is transcribing that one too, will need to test. May need work in that area. I'll look at the VAICOM source code again to see what handling it has around that. Numbers are converted to their numerical value by Whisper so my recipients list has been updated accordingly, e.g. your wingman supports "winger, bozo, two, 2". This requires the VAICOM key words database to have that "2" also added as an alias for that wingman as far as I'm aware (I have the alias but need to 100% confirm it works with it and doesn't work without it). (...still a work in progress so still ironing out the kinks, apologies for grey areas/confusion, and anything I may have missed out at this stage) EDIT: Maybe I'd misunderstood X-men. Was this supposed to be "Axeman"? Then yeah, just add X-men=Axeman to the word_mappings.txt file.

The DCS log analyzer shows this to be a GPU issue: There is a GPU-related error Remove any overclocking from your GPU. Uninstall your GPU driver with DDU and install a clean one.

You should drop another log file here with a successful start up now. The previous log showed your OpenXR runtime was failing to start for some reason. Should be completely unrelated to saved games.

You have a number of mods, some of which are known to cause issues. Please remove your mods, run a slow repair of the game, delete your Saved Games\DCS\fxo and metashaders2 folders, and then try again. In addition to this your preload radius is set to 150000 which is really high and you're unnecessarily loading a lot of stuff. The DCS log analyzer recommended to drop that to 60000, as well as turning off SSAO which is a performance hit with little benefit. Looks like there is a track (.trk) file in that zip already so may or may not (if crashed without a chance to write this correctly) be from this occurrence.

This is a pretty common solution for VR players when they get FPS drops due to having used the F10 map (which loads in all textures around that area) and is the current hypothesis that this is freeing up VRAM resources.

Your log file shows an error in the logbook for the Mission Editor. Try renaming your C:\Users\username\Saved Games\DCS\MissionEditor folder to MissionEditor.old (this will get recreated when you next start the game). If you haven't already then I'd also recommend deleting your fxo and metashaders2 folders in the Saved Games\DCS folder as well. If that still fails then: Next, delete %LOCALAPPDATA%\TEMP\DCS and try again. Next, try renaming Saved Games\DCS to DCS.old and try again. (it's important to rename so that you can copy back config afterwards to get your bindings if this works) In addition to this you have heaps of mods so failing that try removing the mods and run a slow repair of the game. You can add the mods back again if that fixes it (may need to do one by one to figure out which one caused the issue if that was the case. Mods can often break between upgrades) You have an existing page file set to 16384. I'd recommend increasing that to 32768. Some additional tuning items reported by the DCS log analyzer for your log file: Disable civil traffic. Set Preload Radius to max. 60000. You currently have a preload radius of 109700 which is really high, especially given your RAM and VRAM, so you are loading a bunch of unnecessary stuff. Decrease Terrain Textures. Turn off Depth of Field. Set Water to Low. Turn down Anisotropic Filtering. Drop another log file here if this continues to happen after you've tried the above.

Awesome, glad it's working. Yeah normal start process would be to connect your headset via Link and connect that first, and then go to your desktop and start DCS. Happy flying!

Those shortcut parameters don't have a space between them so aren't doing anything anyway, you can delete them. Your DCS settings obviously have "Enable VR Headsets" turned on which is why it launches in VR. It doesn't matter that the other one goes to "DCS_updater.exe", this just checks for updates and then will go to DCS\bin\DCS.exe automatically. If you go into that DCS\bin directory and double-click DCS.exe (don't use the shortcut) what happens? Does it still fail then? Both of the DCS.exe files in bin and bin-mt are identical so it shouldn't make a difference. Are the file sizes of the DCS.exe identical in both of those directories?

Can you please attach another log file for this working now for comparison purposes. Both bin\DCS.exe and bin-mt\DCS.exe should be the same as there is only multithreaded now. You also don’t need those command line arguments. The —force_OpenXR one is redundant as there is only the OpenXR version so this is the default.

This log shows that you do not have an OpenXR runtime installed or configured properly. What headset do you use? What is the app you are using for your OpenXR runtime (depending on the headset, e.g. for Quest you need Meta Link app or VirtualDesktop, Pimax will be PimaxXR or PimaxPlay etc.)? 2025-01-05 00:49:23.845 INFO VISUALIZER (Main): [19:49:24.465][Info ] OpenXR: Environment Access Check timeout is: 25047 milliseconds 2025-01-05 00:49:23.845 ERROR VISUALIZER (Main): OpenXR failure runtime is not available Source: Projects\Visualizer\Source\OpenXR\openxr_program.cpp:433 2025-01-05 00:49:23.845 ERROR VISUALIZER (Main): OpenXR exception: runtime is not available Source: Projects\Visualizer\Source\OpenXR\openxr_program.cpp:433

Your issue is unrelated to this post. Please raise another post, or alternatively take this to the Eagle Dynamics Discord server. You can drop your log into the #dcs-log-analyzer channel which will provide feedback, and/or ask in the #dcs-help-channel

No "fix" required. Drop your dcs log file here as it may give indications as to why it's falling back to 2D. I'm assuming you're attempting to launch in VR, e.g. have ticked the "Enable VR headsets" box in the DCS VR settings, or selected the little man in the goggles by the big orange button in the new launcher (which does the same thing). What is set as your OpenXR runtime? You have PimaxXR installed, or have PimaxPlay installed and have selected Pimax OpenXR within it? The dcs log file will help identifying more of that info as well.

Interesting. Potentially the request from PimaxPlay will state the resolution and focal area it requires. The QVF API layer sits between DCS and the runtime, so in theory will be converting the 4 views per frame back to the stereo 2 views prior to it hitting the runtime, in which case the conversion occurs in the API layer and not the Pimax runtime. I can edit this comment later with a link to a good diagram from Mbucchia on this topic. QVF and DCS logs would indicate more. Don't know if you tried with turbo mode turned off in QVF as well?

Check what I was responding to. If Mbucchia's Quad-Views-Foveated layer is still installed, and you enable Quad Views in PimaxPlay, it will still use Quad-Views-Foveated. It doesn't "take over from it".

This is not the address for credentials but can you run the below two commands (run each one seperately) from a command prompt in Windows and drop the results here: ping cdn.digitalcombatsimulator.com ping www.digitalcombatsimulator.com EDIT: and just to be 100% clear, should be run when NOT on the VPN.

Mbuccias QVF API layer still needs to be uninstalled though if you were previously using it otherwise it will use that.