mkel2010

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:

Have you checked your dcs.log file for any errors? The DCS Discord channel has a feature that allows you to upload and analyze the dcs.log file for any errors and will give recommendations for fixing or optimizing your setup.

Probably. You should be getting about 2400 mbps transfer rate to play DCS without a lot of issues. Every once in awhile I drop to 1200 and have to shut everything down and reconnect.

I use Virtual Desktop, which is about $25 from Meta. To do that you also need to download and install the VD Streamer app. You could use AirLink or Live LInk with a cable. For either VD or Air LInk you're going to need a dedicated wireless router within about 5 feet of your headset. I use the Puppis S1 which is the least expensive option and it works well once set up correctly.

Next to the Launch DCS button, there is a small icon that looks like a computer screen. Click on it a you should see a second symbols tha looks like a human head. Select that and then launch DCS.

I also have a Quest 3. I use a dedicated router that sits about 3 feet from the headset. If you don’t have a strong connection, it could be that too much data is being pushed to the headset by that map. Best way to test it is to connect the headset directly to the router with a network cable just to test it. You’d need an Ethernet to USB- C connection to do it.

How are you connecting the Quest 3 to VD? Do you have a dedicated access point? Look into connecting your Quest 3 directly via an ethernet cable to see if the problem still exists.

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