mkel2010

The first image below is with DCS in 2d from VR, with the settings the way I want them. The second image without the overlay is the same place in the same mission in full VR. To me, the image seems lighter, like there's not as much contrast being applied. I'm pretty sure the overlay is working other than the overall brightness of the image.

You might want to post this in Virtual Desktop Discord. You might also want to try changing some of the settings in the VD app once inside Vr before you start Dcs and see if that effects anything.

The Alt-F5 still has no effect. I also noticed last night that the effects don't seem to carry over from session to session or to different maps. I'll need to play around with it some more. I'm using Virtual Desktop and still waiting an answer from them on how it's Gamma setting works with the Gamma setting in DCS.

After a complete re-install of Reshade and the add on, I think I've got it working correctly. One question thow: Does using Technicolor 2 VREM override the color correction in the add on?

I think I've got Reshade set up correctly. That said, Alt-F5 does nothing in-game.

I understand about accessing the overlay in VR. As for the Haze, after much experimenting and changing settings in a number of places, I've discovered that if a mission is set with "no clouds" I get the fog ring/haze. But if I set some clouds in the mission the fog/haze is pretty much gone. The super white clouds in DCS really mess with the HUD, hence my next question. Question: Are there any of the parts of ReShade that could be configured to as as a sun visor or sun glasses? Similar to a polorizing filter. I know there is one for the F-16/F-18 in 2D but apparently there isn't one for VR.

I'm trying to use Reshade with Quest 3 and virtual desktop. How can I bring the Reshade overlay up in VR? Trying to figure out why every map has a thick, circular haze ring when I have Haze set to Zero in Reshade.

I've been having an issue with the moving map inside of Open Kneeboard. Whenever I would start a mission, the map data would never load, just give me a world view with all the map outlines and names. In reading through this thread, I saw a link to the earlier version (3) of the web editor lua file and thought I'd see if that fixed the issue. I downgraded from version 4 to version 3 and had no issues with the map loading correctly in OKB, even when changing missions to a different map, which wouldn't work with version 4 on the rare occasion that the map loaded the mission data at all. Note: I am using the Patreon version of the map. I've posted this on the discord channel as well.

It seems the mission file is corrupted. The mission was generated by the Briefing Room web site. I have others generated for the same map (Syria) that don't have this problem.

I have some of the missions I use in VR showing a thick, circular haze/fog layer that I can't seem to get rid of. The mission is set with no clouds and base and thickness set to the minimums. It makes if very difficult to see the F-16 HUD symbols as they get washed out against the white background. It doesn't happen as bad in every mission, but the haze is there at a much greater distance in all of them. I use the Re-Shade mod and have the haze set to .10. Here's a screenshot to show what I mean.

Are you talking about the Heads Up Display (HUD) or the Multi-function Display (MFD?) At any rate it sounds like you need to adjust your Snapview Settings. Here are links to a couple of videos on how to do it:

I've added several squadrons and a fighter wing to the USA Troops.Lua file, along with the corresponding unit patches in the correct folder. However, the new units aren't showing in the logbook list. Is this the correct place to add these? I've posted the troop.lua file below. My changes are at lines 19, 40 and 79. USA.lua

My exact experience with this MB/CPU combo.

I just built a very similar system using the same CPU and motherboard (I'm using the Ryujin 360 Water Cooler, 96GB of RAM and a RTX 5070 Ti OC.) I had a hell of a time getting the motherboard working correctly at first. The first board had to be returned because a of a memory slot issue. The second board initially gave me CPU errors which I later determined was caused by an older BIOS that came with the board. I had to flash the BIOS three or four times to finally get everything working correctly. I have not changed any settings to memory or CPU overclocking and my CPU at idle is running about 43 degrees Centigrade. When I load a mission or start DCS it might briefly spike up to the mid 70s and then drop back down for the rest of the session. I would suggest re-flashing the BIOS with the system shut down and see if that changes anything.

That seems to have fixed it. Thanks.

@cfrag I used DML to create an air to air training mission today. Before doing so I downloaded the latest version of DML. When I started testing my work, the Clone Zone routine started generating the error pictured below. After spending some time trying to figure out what the error was (and not having any success,) I switched the Clone Zone routine to version 2.4.0. That fixed the error and the mission works. Just passing on the information.

For some reason, the mod is not saving the options I've selected. For example, activating the Color Change requires a game restart. I've used the save at the bottom of the add-on as well as the preset save button on the home tab. However, when I restart the game none of the options are saved. I did test with your options.lua file and get the same behavior. I've attached the log file. Let me know if you need anything else. ReShade.log

That was the first thing I checked: Anderson AFB frequency is 250.1 which is what the mission set for Comm 1. The most recent version of the mission is from this month, I believe.

Getting back into DCS after almost a year off. I'm using the latest versions of VoiceAttack and Vaicom Pro which seem to work correctly on other missions/maps. However, when I fly the F-16 on either of the Marianas Proving Ground Missions, I can't get a response from ATC either on the ground or in the air. I have the main DCS menu set to Easy Comms off. I've tried initiating calls to start engines, taxi, take off, etc. from both the menu options and using Vaicom Pro. I get "my" voice repeating the command, but never get a response. I initially thought my version might be out of date so I downloaded the newest version and get the same behavior. Any ideas how to fix this?

F-16 Lesson 13 - Air-Air TWS and TNDL Use only progresses as far as the first set of targets for the TWS portion of the lesson. Once those targets are shot down, the next part of the lesson never appears. I flew it twice with the same result. The Track file is from the second time through. Lesson 13 - Air-Air TWS and TNDL Use.miz_14082025_14-28.trk

I think I've resolved the issue by switching to MSAAx2 and turning off DLSS. The only things Ive set inside the NVIDIA control panel are the power setting to Performance and prerendering 3 frames. I'm using Virtual Desktop to connect. And yes, the Gamma slider does react in-game. With the changes I made today, the HUD colors are now consistent regardless of the background.

1 & 3: Meta Quest 3 (VR) 2: New system, but I had a similar issue on the old system with a RTX 3060 Ti card. On the old system, resetting Gamma pretty much took care of of it.

I built a new system for playing DCS in VR which incudes an RTX 5070 Ti OC graphics card. When flying in the F16 and there are clouds/haze in the background, I find the HUD colors to be washed out and difficult to see. I've played with the Gamma setting (currently at 1.3) and while it helps, it really darkens everything else. Are there any other settings in VR that can address this issue?

The only Winwing base that is force sensing is the MFSSB base; the Orion II base is the analog base. The shaker kit is meant to give feedback through the stick when you're pulling Gs, firing ordinance, landing, etc. I've had the Orion II base with the F16EX grip without the shaker kit for awhile. I recently got the shaker kit and had the same question about getting it to work. The video below explains how to get it to work about half way through. Basically, you have to have SimApp Pro running, go to the Dynamic Vibration Motor page and chose the game and aircraft. On the Game icon there is a Settings option. Click on that and you get a window that lets you chose Default or Advanced. Default gives you basic shaker behavior while advanced allows you access to downloading other profiles from users or creating a new one on your own. I ended up using a profile uploaded by Reflected. Once downloaded, you will have a run button and three dots. The three dots will open another window with an Edit tab. This allows you to adjust the settings. I haven't a clue what the best settings are. You'll find that the shaker is very subtle. It's not going to even come close to vibrating the stick out of your hand. Unless you have the MFSSB base, set the settings in the Special menu to on and the dead zones to Zero. If you need dead zones for the Orion base, set them in the Controls section.

I'm not sure how I fixed the issue, but everything is working normally following the last DCS update as well as a Windows 11 update.