Exorcet

Missiles have reaction times, which can be in the tens of minutes. To make sure that they're not working, place them alone in a mission and speed up time to see if they do anything after about 20 min. Some weapons also have a minimum range. The SCUD is one of them. If the target is inside the min range ring, it won't fire. Check that the point to fire on is between min and max range rings. Lastly when targeting a unit, that unit needs to be detected. Add an AWACS to help the Silkworm or see if there is a "visible" checkbox in the targeting task. This forces the target to be detected.

I'm not dragging anything off topic, at this point you don't really have to reply, I'm just trying to raise a concern so that we don't end up with a minor problem upon making a change. By the way, I am one of those mission designers.

I'd consider this a component of revamping the briefing/mission planner systems in DCS. By intel markers I mean icons on the map that represent where friendly intel thinks enemy forces are. Right now, everything on the map is shown in its exact position and includes waypoints. That's a bit too specific for many situations. I get around this by hiding some units on the planner and then placing dummy units that don't spawn which represent intel. This works well enough, but real units looks the same as intel on the planner. Also for things like SAM's that appear on MFD's, you also need to add multiple units to make the SAM rings show up. This could be simplified a bit by having an intel layer on the map, or by having dedicated intel markers that are distinct from real units, perhaps with additional details like radii showing uncertainty in positions or timestamps showing when the unit related to the intel was last spotted.

Also try changing Alarm State to green, this will slow the reaction time of SAM defenses.

It's more that most people might be used to the default as it is, rather than the impact on a specific module. But if you want an example, currently with unit info on by default, someone placing down SAM's for a F-16/18 mission where intelligence on the enemy is strong doesn't have to mess with the checkbox at all. If the change were to go through, making a new mission would have everything hidden on the MFD's if they didn't realize that the default had changed. In this simple case a global checkbox would make things easy to fix. However you can make things less easy to fix if this was a mission in progress from one patch (with MFD hidden unchecked) to another patch (with MFD hidden checked) and the visibility of units in the mission wasn't supposed to be uniform. A global checkbox wouldn't fix things if you didn't notice the change, you'd have to manually go through the list to fix stuff. But I think this is kind of going off topic a bit. I'm not against the spirit of the request. I'm just trying to make sure it's done carefully to avoid creating unforeseen problems. That's all. If I have anything to say about the idea directly, I think the most flexible option is to provide a separate checkbox for "internal aircraft data" that way hidden on MFD can be left alone. I don't think that's true. In a training mission for example, you could very easily expect full visibility of enemy forces. Even in a real combat mission, you could be creating a follow up strike where the player is tasked with flying a mission over an area where other aircraft have already found the enemy and can relay their positions to Command and Control. In general for me, not everything on the enemy side has a known location, but at the same time that is not always the case 100% of the time. No offense to ED, but they can't do that. What's best is going to depend on what mission designers do and how they use these features, and that can vary from person to person. We absolutely should not trust that ED are mindreaders that can predict every possible drawback with a given solution. We need to actively communicate with them to help them find a solution that works in as many cases as possible.

The whole civil traffic feature could probably use an overhaul at somepoint and include options for animal spawns. X-Plane randomly spawns wildlife across the map, so it's hardly unheard of in a flight sim. I know "DCS cow" has gotten flak in the past, but things like wildlife are nice to have in enhancing scenery and immersion depending on the mission. However the downside with making them available only as static objects means that a mission maker has to go through the effort of manually placing them everywhere. Some automation would be nice to have in regards to this stuff. Of course it should also come with some user controls so as to not be completely random. Whether auto generated wildlife can penetrate airports and by how much should be a setting for example.

I understood, the thing is just as easily as the default behavior is a problem for Apaches, it might be a good thing for other airframes. That's why changing defaults in software is something that should be considered carefully. It will solve problems for one side but could make problems for another group of users. Adding a separate option or checkbox to clear Apache data would have the least negative side effects (basically none) for other users. A toggle all option would be nice to have too, maybe with sub options to limit it to coalitions, countries, and unit types (ships, SAM's, etc). Or perhaps this is a good time to even revamp how intelligence is presented in DCS. From the mission briefing you can tell that DCS was not built with limited intelligence in mind since it lists every single unit on the map unless hidden. And the mission planner even shows you exact routes for enemies units which you would be unlikely to know. In general we need more control over what is supposed to be known/unknown/partially known, etc.

F11 > L-Ctrl F3?

I am currently testing a mission. I launched it through the ME and for no particular reason I opened the mission planner before launching. I noticed on the map that I forgot to hide a couple of enemy static objects. When I clicked on one I found that I could move it, even place it in the water (it's a building). This is obviously problematic. So far this seems limited to static objects. I could not move friendly or enemy groups. I did not test on friendly statics. The repositioning of objects is not limited to the planner either, they were relocated in the mission as well. No track since the cause is outside the mission.

Just FYI here, this shouldn't cause any problems until the game is updated. Recording inputs is standard for video game replays and many many developers have systems that don't go wrong except for extremely rare occurrences. This is also nothing new, reliable track style replays go as far back as PS1 games and probably even earlier.

Boom is pretty much exclusively the USAF. F-15, F-16, A-10.

Yes, I agree that there is a problem here. I think it comes down to over effectiveness of chaff in DCS for the most part.

I'm mostly SP and use Stable. While many people just treat the OB as default, I find that ED's intended use cases make more sense. I see a lot of people complaining about bugs and such when new updates arrive, but I very rarely have this problem as I just keep my stable install on whatever patch it happens to be on until I have a reason to update. My OB install is usually updated as soon as possible so I can test new features. Not every change is positive, but since I don't use OB seriously, I'm not often impacted by major issues.

Eh, we have forecasting. Basically there is a link between what is likely in terms of weather and how the mission is planned. If weather were truly random and unpredictable, flying would be very different. We can't predict the weather perfectly of course, but it's unlikely that if the forecast is a clear day, and the mission is planned around that, that a hurricane will move in and make flying impossible, which is a possibility with uncurated live weather.

If the ranges are wrong, you might want to submit a bug report (with evidence) instead of a wish list item.

It's always good to be careful when flipping a default setting, especially one that has existed for a long time. It might be better as a checkbox in the ME instead of a change to the default. Or just give the AH/KA their own checkbox. The hidden on MFD thing came about because of the F-16/18.

For me some of the big items: Triggers and trigger conditions: Detection triggers (Unit/Group/Country/Coalition detected and Unit/Group/Country/Coalition detected in Zone and Unit/Group/Country/Coalition detected by Unit/Group/Country/Coalition) Add generic classes to missile/bomb in zone (ie ANY MISSILE, ANY AAM, ANY BOMB, ANY GUIDED BOMB, ANY BLUE MISSILE, etc, also allow ANY for quantity of bomb/missile/etc) Task ended trigger (ie trigger activates when a specific AI task is complete, so if AI is set to orbit for 10 minutes, this trigger would go off after 10 minutes) New random trigger variant that rolls just once, not once per second (I don't want one to replace the other, having both is best) Flag between values (example ONCE > Flag value between 6 and 10 > AI Task push...) Disable civilian traffic in zone Switch waypoint on group alive less than and RTB on group alive less than (So if a group takes a certain amount of losses, they can be commanded to RTB or change route) Add a delay option to all triggers, where it makes sense (example delay 20 seconds to RTB on group alive less than 50%, group will only RTB 20 seconds after they take 50% losses) More detailed trigger event checks (currently triggers can be evaluated on events like SHOT, EJECT, etc. This could be expanded to include SHOT by BLUE SIDE or SHOT by Group X, etc) Losses and kills trigger (simply count the losses to or kills made by a given group/country/coalition) Outside of triggers, some new features would be really nice User placed airfields Wingmen obeying tasking set in the ME (when you order them to engage mission in flight) Control over individual active runways without needing to edit wind Neutral Coalition treated as neutral, right now AWACS will declare it hostile which is not right SAM improvements - ideally this means IADS but some quick simple things can be added if that is too complex a goal, namely SAM radar flashing on/off with the ability to set timings and tying SAM to EWR/AWACS so they only use radar for attack (like fighters) until the EWR or AWACS they are linked to are destroyed. Also the capability for SAM's to detect, hopefully realistically and not just by missile in zone, SEAD launches and shut down to try to prevent their destruction. Realistic detection is key here for two reasons: reaction time and the SAM should sometimes fail to detect the incoming missile and be destroyed. Greater Command and Control elements, especially from AWACS and GCI Some more ground unit automation, give them a goal in the ME but make them a little smarter than just rushing to a waypoint no matter the threat New RoE option, Visual ID New minimum range before extend option for fighters (ie if set to 20 nmi, AI will try to extend when less than 20 nmi from enemy, instead of flying into WVR) Change Air to Air missile range option for fighters to be a slider Tweak airbase capture settings - Force airbase to remain with a given coalition even if enemy ground units enter the base, also have the ability to close a base off to specific coalitions (so for example neutral bases can be set so as not to be valid for Blue or Red fighters to land at) Automated airbase defense task - Similar to GCI task from LOMAC, place fighters at a base and when given this task they will automatically takeoff an intercept enemy aircraft at a specified distance in the ME. Also consider having two specified distances, one that will trigger takeoff and then orbit around the airbase and a second distance that will trigger engaging enemies, this may be needed because of the time it takes to get fighters off the ground. Common radio frequencies - currently AI only use one freq at a time, but something like AWACS should be on a common freq and the AI should switch channels as appropriate to communicate with desired parties. This would also allow things like groups calling for help (example Strike group is attacked by fighters, it would call for help on the common AWACS frequency)

I'm not against live weather as an option, it's just that despite so many requests for it, there doesn't seem to be much consideration for the problems it causes in mission building. If a mission is set to just copy realtime weather, the weather in the mission effectively becomes random, and this could make the mission unreasonable or impossible to complete. I just wanted to point this out so that it's taken into consideration with the live weather feature. For example things like wind speed/temperature/cloud density limitations that can be turned on or off as needed.

It sounds like you're making missions already. The ME has all the tools needed for a dynamic experience, it just comes down to how you design the mission. For example instead of placing a single enemy CAP flight in your mission you can place multiple and then randomize what spawns via triggers. If you want to go to the next level scripting allows even more precise control and there are tools like MIST/MOOSE/etc that are designed to make harnessing the power of scripting a bit easier. You can also try making larger missions that make use of DCS's airfield and warehouse system if you want to feel more like you're fighting a war. With triggers or scripts you can automate airbase defense and unit reinforcements. Then as you fly mission across the map you can target airbases and other facilities to influence enemy force strength, basically similar to what Liberation does, but the goal would be to have very large mission instead of multiple smaller ones. The DCS ME is very flexible and powerful when you learn all of its ins and outs.

The plane has to be capable of being a tanker. Countries also only have access to certain planes, except Combined Task Forces, UN, and USAF Aggressors, which can fly any plane. If you have historical mode on (watch icon at the bottom of ME) this limits your plane selection according to the mission year. Tankers in DCS include: KC-135 (boom) KC-135 MPRS (drogue) KC-130 (drogue) S-3 Tanker (drogue) IL-78 (drogue) I may have forgotten one or two, but I think that's most of them. They should all works like the KC-135.

Next time, post your mission for people to look at. There are multiple ways to do this, the simplest is probably: ONCE > Group Dead (the AI group) > End Mission

Possible work around, place copies of your planes in formation with the tanker and when you go to refuel, you can leave your current plane slots and switch to the copies. If they are all set to client you won't need to fiddle with late activation or anything.

Perhaps something is up with Switched Condition. I think I made a unit spawner that had to randomize the order of 4 groups, but it used Continuous Action if I recall. Maybe that trigger type will work as expected?

If we were to have defaults for 1C1F, Program 1/2 wouldn't be the way to go. It would require you to switch programs. Prog 1/6 would map both to the HOTAS at once and remove any need for switching while also retaining the slap button for flare dump in a WVR emergency.

Until it changes because the weather is dynamic. AI override makes sense as an option.