sleighzy

You should follow the instructions I linked above to the other forum thread that shows installing ReShade with Add-ons support (the "Download ReShade 6.3.1 with full add-on support" button on their website) and using the Add-ons tab in the ReShade menu for synchronising changes with your runtime. This means when you hit the reload button in the ReShade menu it will update both files and you'll see the changes in VR immediately. Alternatively, it'll be as you describe, changes you make will update the ResShade.ini file but won't update the ReShadeVR.ini file (should be able to easily confirm but enabling an effect and changing something and see if the file is updated). Because of this you'll need to make the changes, then exit the game, copy ReShade.ini to ReShadeVR.ini and then start the game again. And no, the Home menu won't be shown, it will always be shown on your monitor, but you can still use it to configure everything. This is because ReShade does not have an OpenXR overlay to display this within VR.

Yup, make sure you have both files like you said. When you installed ReShade did you choose OpenXR when selecting the rendering api? If you run this tool does it show a reshade OpenXR layer and it’s ticked? https://github.com/fredemmott/OpenXR-API-Layers-GUI Is the ReShade menu shown on your monitor when you press the Home key even when in VR? Does the reshade log (think it gets created in the same dir as bin-mt?) show it starting up etc. when you start the game in VR?

You mean the shader effects aren’t showing in VR? When you installed ReShade did you select the OpenXR option for the render API as well, not just the DirectX libs? Also if you don’t use the add-on (install the version with add-ons) so you can sync with your runtime then the ReShade.ini file that gets created in your bin-mt will need to be copied to ReShadeVR.ini so you have two files with the same config, one gets used for 2D and one for VR. See here for what I mean about installing with add-ons, note that you’ll need to configure this by looking under your goggles if that’s the case as the ReShade menu will show on your monitor but not in VR.

@SPARE 11, you ran the disk tools above as I requested, but I think you've only run chkdsk against your "C:" drive and not your "D:" drive, based on that scan log you pasted above earlier. Can you run this against "D:" as well please. (believe you need to specify the drive letter after the command).

Still known issue with being broken in the launcher itself. Just install them using the module manager instead when you open the game (the box at the top of the menu made of three squares).

Can you try installing this and choosing the install or repair option. https://aka.ms/vs/17/release/vc_redist.x64.exe EDIT: removed the above as the game is running fine on your "C:" drive, and presumably this would have been an issue for that as well. Jump into the official DCS Discord server https://discord.gg/JzEAYHne in the #dcs-help-room channel with the info you've provided so far. There may be deeper technical issues here and folk there can dive further into those, likely SpecialK. The dxdiag output will be good as well to see if there are any other Windows issues.

Can you try renaming your options.lua file to options.lua.old and try again. This'll keep a backup of it so you can rename back again afterwards. Failing that try renaming your Saved Games\DCS directory to Saved Games\DCS.old (so you can rename back again, or copy back your config if it starts working again). It'll create a new one when it starts up. Curious if the launcher, which gets its settings from the options.lua file and other config files, is failing due to a corrupted setting in one of those.

Can you run the Windows dxdiag tool and then save the file and then drop it here. This may help identify any underlying issues when running these process, e.g. driver issues etc. Also remove any custom mods you may have and run a slow repair, you may need to run from the commandline from within the bin dir of your game installation directory: "DCS_Updater.exe repair" Rename your Saved Games\DCS directory to "DCS.old" so that it creates a new one when the game is started again. Do a rename (not delete so you can copy back in any config, e.g. key bindings, once we get this going again).

One thing I note from that log file is this: 2024-09-24 17:57:33.351 INFO ASYNCNET (Main): Server version: 2.9.7.59074 2024-09-24 17:57:33.352 WARNING ASYNCNET (Main): App version mismatch. Client version: 2.9.7.59263 You're on the latest version of DCS, but that server isn't it. Given it's working on your "C:" drive fine, but not your "D:" drive are you sure there isn't an issue with that drive? Can you run Windows hard-disk tools to verify that there's nothing wrong there. Can you also try deleting the below directories and trying again: %TEMP%\DCS C:\Users\<username>\Saved Games\DCS\fxo C:\Users\<username>\Saved Games\DCS\metashaders2 Drop another log once you've done that and tried again and it crashes or hangs again, before restarting the game as it will overwrite the log.

This problem had already been solved. Also reinstalling is not advised, performing a slow repair of the game (or verifying files for Steam) achieves the same thing without needing to download the entire game all over again.

The force_OpenXR isn’t needed as the MT version of DCS is OpenXR by default. The force_oculus one isn’t needed as you should probably be using OpenXR and not the old Oculus runtime. The new launcher will run the game in VR if you have the little man with googles selected by the Launch button and have a headset running, otherwise it’ll use 2D, or you can select the computer icon in the launcher drop-down by the big orange Launch button and it’ll force use 2D instead regardless of headset on or not.

@edvard, I've run your log file through the DCS log analyser and these are the below results. It looks like your system is quite underspec'd. You could try adding a pagefile to your system to help with the RAM load, but can't promise anything. Make sure you have only one set, and that it's on your fastest SSD, and that you leave at least 10% free space. null

One thing to be aware of with VRToolkit is that they have a number of preset files documented on their site. For those preset files we have found that you have to download their Zip file, open it up, and then copy the preset files to your "bin-mt\reshade-reshaders\Presets" directory (create this if it doesn't exist). Then within the ReShade config menu at the top beside the Preset dropdown click the folder icon to browser to those preset files, can then select the one you want, e.g. generic_filmic_vr++

Thanks for that. Ok, I can see from the log that it isn’t detecting a connected headset. So we don’t pollute this thread of the original poster, as we’re talking about different issues now, can you message me directly and we can investigate further.

Believe you need to be a Discord user. Go here to the DCS Discord server https://discord.gg/zxSgT9W3. Might need to go to Channels and Roles in the server to get access to the channel https://discord.com/channels/542985647502393346/1179171301651402802 #dcs-log-analyzer Can't speak as to where the logs get sent when the games crashes and you click the send crash log button. For the DCS log analyzer however it will display this information to you, and then the logs are removed after 5 minutes.

One thing I would recommend is removing your mods and running a repair. I also notice that you have the OH-6 mod installed, which has a known issue performance issue with the gunner_export_hook.lua file in your scripts directory. The mod maker advises removing that, although I see there is a new release of this 3 weeks ago which may have a performance fix, try removing it anyway. (There’s an error in your log for it too). You can also try dropping your Dcs.log file in the #dcs-log-analyser channel of the official Discord server https://discord.gg/eagledynamics Your specs sound fine so I don’t have a perfect answer for you.

Follow the instructions here to set the global nvidia preset to F or E. This will greatly reduce the ghosting introduced by DLSS.

Is VDXR set as the runtime in the desktop streamer app? Are you on Steam or Standalone? Are you running the MT version? Is it just launching to 2D? Drop your C:\Users\<username>\Saved Games\DCS\Logs\dcs.log here for review. Make sure you launch all the way into the game, even if it’s going to 2D. Also make sure you’re using the recommended video card drivers for VirtualDesktop. If you’re using the new DCS launcher make sure the little man with googles is selected by the big orange Launch button. You can confirm by looking at the VR menu in the game to see if the Enable VR headsets box is ticked. I can probably feel from the log at least one or more of potential problems, so drop that here and validate the other items I’ve listed.

While it may be a hassle I recommend trying the latest patch once it is released. The DCS news letter states that they've made a bunch of optimizations in the upcoming release. Might be worthwhile trying these when it comes out to see if you still get the same old issues, can always roll back to 2.7 if you do. The terrain engine will receive notable optimizations, including better VRAM usage, disk streaming, and CPU utilisation for rendering scenery models. This enhances performance across maps, especially in VR. Additionally, issues like crashes at mission start in certain maps (Afghanistan, Kola, and Sinai) and graphical artefacts when zooming or panning in map modes have been addressed. These optimizations will contribute to a smoother and more stable gameplay experience, especially in complex and processor intensive situations.

Apologies for the late response, not sure if you're still having issues or just uninstalled. Interesting, I was expecting XRNecksafer to show up in there as well. Is it under any other the other tabs? Check to see if you've installed the latest version of XRNeckSafer as well. If you unselect the OpenXR Toolkit from within that tool does this start up as expected? Can you drop a dcs.log file here, after completly starting the game, not just the launcher. Log file will be in "C:\Users\<your username>\Saved Games\DCS\Logs" , it will be called either "dcs.log" or just "dcs" if Windows is hiding file extensions on your machine.

One item that shows up in your log is a client/server version mismatch. Looks like you're not on the latest version of DCS. Should try upgrading to that and retry again, not saying that this'll fix your problem though.

If you're talking about the "The application was unable to start correctly (0xc0000142)" error then download the X64 version of the MS C++ redistribution from here and run it and repair/install https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170#latest-microsoft-visual-c-redistributable-version If you're having other issues then attach your C:\Users\<username>\Saved Games\DCS\Logs\dcs.log file here for review.

@Red_Dragon, you need to scroll down further in DLSSTweaks config tool, you're only seeing the first couple of sections. The global section is at the bottom. The top part of that tool scrolls further, even though the "Welcome to the DLSS Config Tool" section stays there. In the global overrides section you'll see the GlobalHudOverride option. Change the value in the dropdown to "Enabled (all DLLs)" and then once you're in the game and plane you should see that overlay like in my screenshot which will show the preset you're using.

Status is nothing has changed from the DCS end. Doing both won't hurt, grab the latest one from here, it's up to 3.7.20 at the moment https://www.techpowerup.com/download/nvidia-dlss-dll/ . You'll still need to update your Global Nvidia Profile (via DLSSTweaks) to set it a better preset (E or F) to reduce ghosting though.

Drop your zip file in the #dcs-log-analyzer channel in the DCS discord, https://discord.com/channels/542985647502393346/1179171301651402802 and it will provide some advice. I dropped it in there for you (but you’ll need to do yourself as well as it only last 5 mins) but it highlighted a potential crash with a RAM memory timing issue and to remove overclocking XMP on the RAM. There were a few other options for troubleshooting as well.