sleighzy

This log is when using the SteamVR OpenXR runtime. I've listed the issue below. Would be interested in seeing a similar log when running the Meta OpenXR runtime to see what the root cause is in there as well. VirtualDesktop does actually support hand tracking as well. I've run your log through the DCS log analyzer which has identified this as a GPU error: There is a GPU-related error Remove any overclocking from your GPU. (some GPUs come with a factory overclock if you are not doing this yourself, check with MSI Afterburner) Uninstall your GPU driver with DDU and install a clean one. This can also be seen in your log with the spammed DXGI_ERROR_DEVICE_REMOVED errors. See the article below on this as well. Errors or Crashes on startup or gameplay of DCS World Looking at your log I see you also have a dxgi.dll file in the DCS\bin directory. I know of only two reasons why you would have put that there, it does not come with the game, and that has also been known to cause crashes. Remove that as well. Additional performance tuning items, note that SSAO and SSLR are performance hits with little benefit. Turn off SSAO. Turn off Depth of Field. Disable civil traffic. Turn off SSLR. EDIT: Realise this is for a completely different problem. @PatMcKrotch , if problems persist after this then raise a new post vs. piggy-backing off this one.

That’s fine, just leave that Window open and you’ll see the transcriptions of your recorded voice logged there.

I see you have the SU-30 mod which has been known to cause issues, recommend removing that and running a slow repair of the game (Verify Files for Steam). I've run the logs through the DCS log analyzer which indicates that this was due to a memory timing issue. Remove any overclocking, e.g. XMP profiles, from your RAM. null You should also add a custom page file on your fastest SSD, removing any existing ones, e.g. system managed. Set the Initial and Max values to 32768, click Set, Apply, and restart your PC. Your preload radius is also maxed out at 150000. This will be loading a lot of redundant stuff into your RAM. Drop this down to 60000. Some additional performance tuning items. Up to you if you choose to change them. SSAO and SSLR in particular can be a performance hit with little benefit. Turn down Anisotropic Filtering. Set Shadows to Medium. Disable civil traffic. Turn off SSAO. Decrease Visib Range to Ultra or lower. Decrease Terrain Textures. Set Clouds to High. Turn off SSLR. Set Water to Low.

Your DCS logs don't appear to contain crashes, which is normally indicative that Windows itself is killing the process. Looking at the DxDiag reports however they contain numerous BlueScreen events with an error code of c0000005 and 3b. Based on a quick internet search it would appear that this is potentially related to RAM issues. Can you remove any overclocking you have on your RAM. Can you also run a memory test, this link contains some info on how to do so using the standard windows tools How to Test Your Computer's RAM for Problems There are also a few errors in the logs, appear to be possibly unrelated, but run a slow repair of the game and delete your C:\Users\username\Saved Games\DCS\fxo and metashaders2 folders. You don't appear to have any mods other than Tacview and SRS but try without those as well. Some additional feedback, some from the DCS log analyzer. Your preload radius is really high at the max of 150000. Drop that back to 60000 as you're loading a bunch of stuff into RAM which may be redundant. Consider using DLAA. Turn off SSLR. Turn off SSAO. Disable civil traffic. Disable Game Mode Disable Hardware accelerated GPU scheduling Disable Core Isolation

Raise a new post and attach your DCS log to that after replicating this again. Folk can have a look into reasons why and help troubleshoot.

Believe you, or may have been somebody else asking the same question, in the Eagle Dynamic Discord server. This was the response:

Are you still using the OpenXR Toolkit? If so then disable it. It doesn't work with PimaxPlay Quad Views as the OpenXR Toolkit expects 2 views, but will be getting 4. EDIT: I see you've said you've uninstalled the OpenXR Toolkit, worth double checking though as this was definitely a cause of black screens based on your description. You can also install https://github.com/fredemmott/OpenXR-API-Layers-GUI to see if it's still there, or are any other API layers that could be causing problems. If the game is crashing then create a new post along with your DCS log file as that is unrelated to this post.

You can use Nvidia Profile Inspector (the Orbmu2k one) and then in the Other section set Enable DLSS-SR Override to 1 and Override DLSS-SR presets to 0x000000A for J or 0xFFFFFFF for latest (preset K). This means you don't need to swap dlls as it will use the one from the driver. If you want to use OVGMe then in the folder you currently keep your mods for this create a DLSSTweaks folder, and then a bin and bin-mt folder under that. Put the dlls in that folder. When you enable the mod it'll put them in the right folder, basically it overwrites stuff based on the same folder structure as the core games folders. DLSS Swapper is also really easy for this and you can download and switch dlss versions without manually copying stuff. If you followed that video you would have created a new registry key that turned that text (the hud overlay) on. Just remove the registry key again.

Unfortunately not. Trial and error process of putting them back in to see which one is problematic. Given this doesn't occur with Standalone then I'm assuming not the case. What's the DCS FILMING template that requires Steam? I've used Xbox controllers in the past using Tuuvas's profiles (without Steam). I know Steam was required for PS controllers as their triggers don't work properly for rudders unless you use Steam, unlike Xbox controllers. I also noticed that neither of the Steam logs show an actual game crash, which would insinuate that Windows itself may be killing this process. What is your actual experience when it crashes, what do you see? Can you run the Windows DxDiag tool, save the report from that, and also attach here. Do you get a full dcs.log-<datetime stamp>.zip file created for any of these crashes? Drop here as well if it does. For the DCS log analyzer you can take your log files and drop them into the #dcs-log-analyzer channel in the Eagle Dynamics Discord server. The bot there will give immediate output so you can get feedback.

Super interesting. How does this differ from say disabling hotplug devices in the DCS controls settings?

I haven’t compared the two logs completely line-by-line yet, but one difference is that the Steam one is launching bin\DCS.exe and Standalone is launching bin-mt\DCS.exe. It shouldn’t make a difference but can you update Steam so that one also points to bin-mt\DCS.exe

Your system ran out of memory like @rob10 said. Looks like you have a page file of 20Gb. Update that to 32768 for the Initial and Max values. Your log is also spammed with this message: failed to create index buffer. Reason: DXGI_ERROR_DEVICE_REMOVED This is normally a GPU error. Remove any overclocking from your GPU. Reinstall your GPU driver. If it continues then perhaps uninstall your GPU driver with DDU and install a clean one. Some additional tuning items from the DCS log analyzer based on your specs. Note that SSAO and SSLR are performance hits with little benefit. Turn down Anisotropic Filtering. Set Shadows to Medium. Turn off SSAO. Consider using TAA instead of MSAA. Turn down MSAA to 2x. Turn off SSLR. Set Water to Medium or Low. Disable civil traffic. Some additional items: Disable Game Mode Disable Hardware accelerated GPU scheduling Disable Core Isolation And disable Core Parking, which is currently enabled.

Attach your DCS log file so we can see what your crash is as well. This works fine for other folk. Also my 2c worth, some folk prefer K to J so might require some evaluation to determine what is actually the best/preferred. People can, and still will, override this to their own preference though.

Your log is from Standalone not Steam. However there are a bunch of problems. Firstly it looks like a least one config file is broken, from the DCS log analyzer: Config File Corruption Delete or rename Saved Games\DCS.openbeta\Config\options.lua and try again. This may be related to the below error you see in the logs: 2025-02-04 23:33:32.778 ERROR Lua::Config (Main): load error Config/main.cfg:[string "C:\Users\kston\Saved Games\DCS.openbeta\Config/autoexec.cfg"]:3: '<name>' expected near '\' stack traceback: [C]: ? [C]: in function 'dofile' [string "Config/main.cfg"]:142: in function 'reloadOptions' [string "Config/main.cfg"]:155: in main chunk. 2025-02-04 23:33:32.778 ALERT APP (Main): Config/main.cfg loading error: [string "C:\Users\kston\Saved Games\DCS.openbeta\Config/autoexec.cfg"]:3: '<name>' expected near '\' stack traceback: [C]: ? [C]: in function 'dofile' [string "Config/main.cfg"]:142: in function 'reloadOptions' [string "Config/main.cfg"]:155: in main chunk You also have tons of mods, some of which have errors. Try removing those and running a slow repair of the game (Verify Files in Steam). If removing the mods and running a repair works then you could look at readding them one-by-one to see which is broken, and looking for updates. Your preload radius is currently maxed out at 150000. You'll be loading a lot of potentially redundant stuff into RAM. You can drop that back to 60000. EDIT: do what @Flappie recommended as well re: the autoexec.cfg file.

Try with DLSSTweaks. I normally recommend using tools for the job, v.s. registry hacks, as they do the job and are intuitive. Registry edits are less familiar to folk, and the full list of values and what they represent aren't always known.

Reduce the Preload Radius to 60000 as you are currently loading lots of stuff into memory which is potentially redundant. What is the refresh rate of your headset set to? Make sure the max fps matches at least that. Note, this is now going off topic so let’s not get distracted from the topic of this thread. Go to the VR4DCS Discord server for more feedback.

DLSS 3.7.0.0

Awesome. Yes, I just tested now and you can override just for DCS by selecting the "Digital Combat Simulator: Black Shark" profile in Nvidia Profile Inspector to set those Enable DLSS-SR override and DLSS-SR Preset values and it will apply to DCS. This does not require you to put the latest DLSS dll files in DCS, either manually or via DLSS Swapper. DLSS Tweaks can just be used for enabling the hud overlay to verify your changes were successful.

Not quite, we might be confusing two things here. Which steps are you referring to from my original post? If you are referring to put DLSS Tweaks dll and dlsstweaks.ini files in DCS (which will only be for DCS and won't apply to other games) vs. the Nvidia Global Profile, then the steps would be as follows (there is no need for Nvidia Profile Inspector): - Install DLSS Swapper, add the top-level DCS games folder and then you can use DLSS Swapper to easily change DLSS versions in DCS. Alternatively just manually copy the latest nvngx_dlss.dll files to the bin and bin-mt folders. - Use the DLSSTweaksConfig.exe tool to set the preset to J (of K) for each of the quality levels, and enable the GlobalHudOverride so you can see the overlay in game (need to be in the plane) so you can verify that its using the right DLSS4 version and preset you set. - Click save and then put the dxgi.dll and dlsstweaks.ini file from DLSSTweaks (the dlss tweaks file is named nvngx.dll so you need to rename it to dxgi.dll first) into the DCS bin and bin-mt folders - Start DCS and then check to make sure you got a DLSSTweaks.log file created in either bin or bin-mt and has the expected logging re: the preset etc. If you are referring to using Nvidia Profile Inspector, but only for DCS, then I believe you can select "Digital Combat Simulator: Black Shark" as the Profile in NVPI and then update the DLSS-SR override and Override DLSS-SR presets in there. Note, I haven't tested on a per profile basis other than seeing this referenced elsewhere. This approach would also mean you don't need to use DLSS Swapper to replace the DLSS dll files as it will override and use dll version and presets from the driver. You can confirm that via enabling the GlobalHudOverride in DLSSTweaks.

If you are referring to putting the dxgi.dll and dlsstweaks ini files in the bin and bin-mt dirs and updating the preset in the ini files then the answer is Yes, this is still valid. DLSS Swapper can be used to replace the nvngx_dlss.dll files to the latest version as an easy preference to manually copying those latest dll files in.

It should do. The documentation lists the G2 as being a supported and tested headset for FFR for non-eye tracked headsets. Home · mbucchia/Quad-Views-Foveated Wiki

Is there a way to confirm that? (Possibly the hud overlay with a bit of maths on the render resolution and upscaled resolution?). The docs in the ini file indicate that you can override the quality ratios, but only if you also set the enable flag in the DLSSQualityLevels section to true (which would be if you were using the dxgi.dll wrapper vs the global preset override). This would imply it's using whatever the normal settings are unless you explicitly override yourself. Overriding the scaling for all can also be done globally. The GlobalForcedScale for me is 0 (which is disabled) so shouldn't be changing the scalings, of which you are correct, if that is not 0 then it will apply the scaling to all. I see a difference in the image quality when changing between Quality and Performance in the DCS dropdown so it doesn't appear to have a fixed value.

Not sure if that applies here as DCS doesn't do frame generation.

The DCS log analyzer for this ones shows a corrupt file as well. I don't know if this was previously corrupt and the deletion of Saved Games you did earlier helped clear it up at the time. Config File Corruption Delete Saved Games\DCS\MissionEditor and try again. Some additional notes as well, note the reference to the core parking. Verify that this is configured correctly in Windows: Game Mode disabled Hardware accelerated GPU scheduling disabled Core Isolation disabled And disable Core Parking, which is currently enabled. The DxDiag shows primarily app crashes for DCS. There are however two in there for LiveKernelEvent with a code of 141. This is normally indicative of a GPU issue. You could try reinstalling your GPU drivers, may need to use DDU to cleanup the old one. There are other Microsoft help references around the LiveKernelEvent 141 and some additional steps, but start with the above first.

Should be the way you're doing it. Drop your C:\Users\username\Saved Games\DCS\Logs\dcs.log file (may just be a text document named "dcs" if your Windows is hiding file extensions) after you've attempted to load all the way into the game. We can check the log to see what the issue is.