Wrecking Crew

This ^^^ is what I have often done.

After reading your post I updated my server to 2.9.21.16552. The server started up fine on the last mission that was running. For a test, I clicked on the Save icon in the missions list. For quite a long time now, 10 months? longer?, I do that Save to overwrite the previous file and I get a lower left notification that says "Mission list is empty and cannot be saved." Now my server appears to be frozen on the mission that was running, ie the mission time is not advancing. From the server GUI, I did a Reconnect and I see that the mission was running and the time is now correctly displayed. I repeated the test by doing the Save and Overwrite and got the "Mission list is empty and cannot be saved." Now the Mission Time is frozen, again. In the upper right of the GUI it says in green "Server Active -- 00:08:47" and it is frozen. I pressed Restart on the GUI and the mission has restarted.

That's not going to happen.

Here's the skinny --> should dcs use "Run As Administrator" For the game Digital Combat Simulator (DCS) World, it is generally not advised to use "Run As Administrator". Running the application with elevated privileges can cause more problems than it solves and is unnecessary for most users. Reasons to avoid running DCS as an administrator Performance issues: Running as an administrator has caused significant performance problems for users, particularly with certain hardware like WinWing MFDs. Incorrect file paths: When you run DCS with administrator rights, it may create and reference configuration files in the administrator account's "Saved Games" folder instead of your normal user folder. This can cause your settings and custom files to not be recognized if you later launch the game as a standard user. Add-on conflicts: Many DCS add-ons and utilities, such as VoiceAttack or OpenKneeboard, are not designed to run with elevated privileges. Running DCS as an administrator can cause permission conflicts that prevent these companion apps from interacting with the game correctly. Security risks: As with any program, running DCS with elevated privileges increases your system's security risk. It allows the program to make system-level changes to your computer that could be exploited. When you might need administrator privileges While rare, you may encounter a specific situation where a one-time use of "Run As Administrator" is necessary for a specific task: Installation and repair: For the installation or repair process to successfully update files in the Program Files directory, you may be prompted for administrator credentials by Windows' User Account Control (UAC). This is normal. Hosting a server: Running a dedicated server for multiplayer might require elevated privileges to properly open ports and configure network settings. Troubleshooting legacy issues: In the past, older versions of DCS or specific module installation issues sometimes required a one-time run with administrator rights. However, for current versions, this is no longer the standard recommendation and should only be done if specifically instructed by official support. A better alternative: Install outside Program Files If you are running into permission-related issues, the best solution is to install DCS outside of the standard Program Files directory. This folder is protected by Windows and is a common source of permission errors for many applications. Placing DCS in a less-restricted location, such as C:\Games\DCS, will prevent most permission-related problems without needing to use the "Run As Administrator" option.

Yes. Let's say Flag 3 is for a random value between 1 and 3 inclusive. Set that on a Mission Start event. Then for the Condition of the aircraft start/activation you do this: TSF xx 1200 Flag 3 = 1 OR TSF xx 2400 Flag 3 = 2 OR TSF 3600 Flag 3 = 3 Is that what you are looking for? WC's Flags.txt

I had been troubleshooting various issues. I did reset DCS and all associated programs to not use the Run as Administrator option. No issues since.

OK, looks like it is fixed. I had set DCS to Run in Administrator mode, and TrackIR was not set like that. After I changed TrackIR Properties to Run in Admin mode the TrackIR button assignments work correctly.

1. Stopped iCue. Still no TrackIR Pause with the Mouse 4 or 5. The Left mouse button works for selecting things in DCS. 2. Reset the TrackIR Pause back to the default F9 (iCue is still off). This assignment also does not work in DCS. 3. Looked at all key and axis bindings -- no conflicts, and no mis-assigned mouse or TrackIR bindings. I can run DCS in Windowed mode and when DCS is not the focus then the TrackIR Pause works fine. When DCS is the focus the TrackIR Pause doesn't work. The Center is working correctly in DCS. After more experimenting, TrackIR Pause and Center work in DCS if I don't use the keyboard or the mouse as button assignments. Strange.

DCS - Mouse Won't Pause TrackIR Anymore, v2.9.20.15384 I use Mouse 5 on my Corsair mouse to Pause TrackIR. Recently this has stopped working. I'm able to Pause TrackIR with Mouse 5 when DCS is not running, and while DCS is loading. But once DCS does load, the Pause no longer works. This is a problem when using Mouse 5, and Mouse 3 & 4.

This is v2.9.20.15384. A couple of Repairs and Cleans and Reboots have resolved the DCS crashing. For now.

DCS Crash On Open Also Crashes iCUE DCS Client crash on latest version. Happened on DCS Open and also get an iCUE (Corsair lighting) crash at the same time. This happened on Monday 10/6/2025 and again on Friday 10/10/2025. dcs.log-20251006-185308.zip dcs.log-20251010-155052.zip

Well, this brought back to mind a possible solution for your Map Object Is Dead problem. There are comments in this ^^^ thread about initiator.id vs initiator.id_, and other points about avoiding errors. I will attach the mission and notes. Unfortunately, the images in my posts are gone as I had exceeded my file limit a while back... Confounded 02.lua Confounded Bridge 29C2e.miz

Nice! I've not used Hold in many years,, not familiar with it, did not even consider it.

It is definitely not working correctly. The ROE = Weps Hold should do the trick; I think you should report it as a bug. I added Alarm State = Green, and a Combined Arms Game Master and another heli. The Red armor forces shot at the Blue heli when they should not. You can get the 'no firing' condition by zeroing out the ammunition for each armor vehicle. PITA to be sure. See the attached modified mission. Mi-24 Gunnery WC01.miz

This is very much like the issue I posted --> NAVEX Caucasus 29C5g.miz