sleighzy

DLSS + J? Tried with the hud overlay enabled to verify that it's correct? If incorrect then DCS will fall back on the old C preset which is bad.

You don't need to move anything around with DLSSTweaks. You can run the DLLSTweaksConfig file to open the config. Then at the bottom you'll see a section of global overrides. You can change the hud one to "enable for all dlls" and then save. It'll probably display a message saying to run as admin, click ok, it'll reopen and then make and save that change again. Check profile inspector in case it's updated the preset, in which case change to J again. That DLSSTweaks setting will then display the hud overlay in game so you can confirm the DLSS version and preset. You can then turn it off again using the same process. This is completely optional, I just use it in testing to validate the various defaults used by DCS, and whether or not I'm doing stuff right before posting instructions/information. Do not put the DLSSTweaks dll in DCS, and definitely do not replace the DCS DLSS dll with that one, they are completely different and for different purposes.

No you’ll still need those steps to set the preset. DCS by default uses the C preset. You don’t need DLSSTweaks for this one, it’s just helpful for the hud overlay for verifying you’ve made the correct change.

3.8.10 used E by default so didn’t need to update the preset, it just works. With the DLSS 4 one you will.

You should use the no hanger mod from Rapierach to get rid of the hanger. It'll save you VRAM, the hanger is still present even in the F10 map.

I've dropped some instructions here that might help out

Screenshot for that one wasn't taken in game, was just to demonstrate the debug overlay and not the game's clarity (was screenshot from my laptop remoted into my PC at the time), so may have lost some clarity there. Not the same blurry DLSS mess it used to be. I'm a VD user with res at Ultra, DCS PD is 1.0. I also use Quad Views as well with the focal multiplier set to 1.4. I'll do some further testing and reduce the quad views multiplier, but honestly I'm happy with everything so far.

Been playing with this DLSS 4 today. Downloaded the nvngx_dlss.dll file (there are links available in other comments and the Reddit post) and replaced in the DCS bin and bin-mt directories. First thing noticed (was also mentioned in the comments on the Reddit post) was that the old presets have been reintroduced. Tested this by ensuring I was using the default preset. This meant that DCS started using the old Preset C again, v.s. the E we got with 3.8.10 (if you didn't override it). Because of this you can't just switch the dlls and get what you used to. Perhaps the new C is better...., but I don't care. Secondly, DLSSTweaks couldn't be used to override it from C to J. So, installed Nvidia Profile Inspector from here nvidiaProfileInspectorForkAIO (.Net.Framework version) so that the DLSS override options are available in the config screen. The new Preset J did not show up for me in the dropdown of available presets, some folk have mentioned that it did for them, maybe it does for you too. I updated the CustomSettingsNames.xml file that comes with Nvidia Profile Inspector to add this new option instead. Search for the other presets and then add the below entry, see screenshot as well. <CustomSettingValue> <UserfriendlyName>Preset J</UserfriendlyName> <HexValue>0x0000000A</HexValue> </CustomSettingValue> The Preset J option is now available in the dropdown. Turned on the debug overlay (I use DLSS Tweaks for this) and jumped in a plane. Confirmed that the overlay showed the correct DLSS 310.1.0 version (weird number) and was using preset J Ghosting was gone from MFDs, and everything looked really crisp. Flew in formation with another plane and did not experience the normal ghosting/blurring I used to around their wings and other areas. The blurring around wings etc. used to be present even with later DLSS versions and on presets E and F so this was a vast improvement. It's more of a performance hit, I have a decent machine but could feel it a little bit. Tested changing the DLSS setting from Quality to Ultra Performance, and this still felt better than Quality with the previous DLSS version. The Performance setting was pretty much the same. Final outcome, I highly recommend this and will be staying with this. EDIT 31/01/25: Bunch of tools got updated last couple of days to better support this, and fix some bugs. I'm now using the following only: DLSS Swapper: The latest version of this added support for manually adding games. I added the top level DCS game folder so it automatically swaps the dlls in both the bin and bin-mt folders for me. DLSSTweaks: Now supports setting the J and K presets as well. Whilst I use this to override the Nvidia Global Profile, it also contains a fix to preventing crashing for people who use the dxgi.dll wrapper approach with it.

You’ll need to manually update the presets, eg using Nvidia Profile Inspector, as unfortunately it appears that this reintroduced the older presets that were removed in 3.8.10. This means if you do a straight dll replacement with no updates then DCS will use the older preset C instead of E (which you got for free with 3.8.10).

Unfortunately that appears to have reintroduced the older presets that were removed in 3.8.10. This means unless you’re overriding them then you’ll be back on the older C preset. I’m currently looking to use Nvidia Profile Inspector to test preset J to see how much better it looks.

The attached log file is incomplete. You need to log completely into the game, not just the launcher, before grabbing the log. Possibly unrelated but make sure you've deleted your fxo and metashaders2 folders in your DCS saved games so it can recompile any out of date textures since the latest patch.

Try disabling Hardware Accelerated Graphics (HAGS) if you haven’t already.

Turn off DLSS/DLAA and see what it looks like for you. Try also MSAA and see how that looks (this one is a performance hit and I don’t like the shimmers).

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.