Steggles

New Version Changes: - Added setting to be able to limit the amount of threats displayed in a picture report - Added option to enable Bogey Dopes --- Mission designer can turn on / off in script settings --- Pilots can request thru the F10 menu and it will show the BRA to the nearest hostile aircraft that has been detected. It will always reference the requesting pilot's own aircraft. - Finally implemented a cleaner workaround for some ground units being detected and listed in picture report https://github.com/Bob7heBuilder/EWRS As always, any issues or suggestions, let me know. Cheers Steggles

This solves one of my issues with EWRS. Thanks!!!

If you want triggers for each player, it's a pain in the rear, but you need to have each airframe in a different group then use the group in zone condition in the triggers. Message to group will then also only display to 1 player.

Not statics. They are under 'unarmed' category in the ground units list.

Mapobjs_dead_zones is for map objects - buildings, bridges, etc, not for actual statics and units. Not to sure how to handle the statics, but if everything is in 1 group for the units, use a group alive less then trigger. The value entered with this trigger is a percentage of the original groups size. So a group with 10 units, group alive less then 30 will activate after there are less then 3 vehicles of that group left. http://wiki.hoggit.us/view/DCS_editor_conditions Edit: You could use mist.flagFunc.group_alive_less_than as well instead of the ME trigger if you wanted to stick to scripting. I havnt worked much with statics, but the few times I have I've noticed a lot of bugs with them when it comes to interacting with them with a script.

If you're willing to do away with voice BRA and don't mind a text display, you could use my EWRS script and remove the AWACS task from the unit. Link is in my signature if you want to take a look.

rvotri, In the ME, you need to have MIST loaded into the mission. Do this via triggers preferably at the start of the mission with ONCE - TIME MORE THAN 1 - DO SCRIPT FILE, and chose the MIST file. This will embed mist into the mission and be available to use by yourself or any other script after that trigger has been run. A mission with a script that requires a certain version of mist or above, and you do not have the correct version loaded, the mission will still load, but your script will not run correctly and will receive errors. To see if mist is already in your mission - check the triggers in the ME to see if any load mist. An alternate way is to open the .miz file (in windows explorer or something alike) and check manually inside if the script is there. Now for my original reason for my visit here - mist.dynAdd - adds the units it creates to mist.DBs.dynGroupsAdded. A few things I wanted to ask - Does it add the units to DBs.aliveUnits as well? Do they get removed from DBs.dynGroupsAdded after they are killed? Edit: Think I figured it out myself.

http://wiki.hoggit.us/view/DCS_mission_editor Namely the Trigger Basics, Trigger Conditions and Trigger Actions page. Hope this is what you were chasing.

Oh cool. Glad I asked now, that actually solves a few problems for me. Cheers for taking the time to reply.

If I have a group set to late activation, am I correct in assuming that it will not be in mist.DBs.aliveUnits until after it's activated? I'm at work and can't start DCS to test it.

TBH, if you want to use it in multiplayer, you should need multiple players. Isn't that the idea of multiplayer? I'm against a single person being able to operate in both seats in multiplayer.

I don't have the knowledge to answer this, but I think it has something to do with detection of the beginning of communication between the launching aircraft and missile it just launched. I'll look around and see if I can find a definitive answer.

You will get a launch warning almost 100% of the time with Fox 1 launches as you have to be 'locked' (think STT) by the hostile radar. You will not receive warnings for Fox3 launches until the missile goes pit-bull unless the hostile aircraft has you 'locked' (radar is in STT). Flood mode mentioned above is different from STT as the radar beam is point forward of the aircraft at all times. STT mode, the radar focuses its energy on the target and will move withing the gimbal limits to hold the lock.

Su27 has no active missiles. The F15 has the 120s. The migs have theirs but I don't know Russian weapons to be able to name it.

You do know that a Fox 1 is SARH? Fox 2 is infra-red. Most fighter aircraft (that i know of) have abilities to detect Fox 1 launches from the point they are fired. Yet another radar mode. Flood may as well be STT for my purpose I'm explaining. The difference with Flood Mode is I believe they will get a launch warning as soon as the target is 'flooded' / getting painted, even if a missile hasn't been launched.

People feel free to correct me if I'm wrong, but I believe RWRs can pick up on the command launch from the hostile aircraft. With the active missiles, when they are launched in TWS mode, the target will not receive the launch warning until the missile goes pit-bull as like you said. When a target is locked in STT they will receive the warning as soon as its fired. SARH missiles are unable to be guided outside of STT mode, hence the warning as soon as its fired. Someone with better knowledge of radar modes etc will be able to explain further.

Do you have the beta or release version installed? For now its only available in the beta version. Release version should come on Friday with the update. Edit: If you updated the beta today, and still can't fly it, I'm not sure what your issue is. It all worked correctly for me.

Awesome. Wasn't sure if I missed something. Seems I did. Cheers for the reply.

Jumped into the ZA for a quick fly before work today, spotted the engine exhaust temp gauge in the rear seat not working (front seat was). Did I forget to something or is this a bug? No track sorry, but was just a quick mission from the ME with an L39 placed on a ramp start.

The AWACS still works for FC 3 aircraft. I was only pointing out that the High fidelity modules will need the frequency to use the AWACS and FC3 aircraft don't. As for the SAMs, depends on what type you are using. SA15 (I think it's the 15) launchers have their search and track radars built in, while the SA10 has a search radar, track radar and launchers all seperate. Just do a search for what types require what. I havnt fiddled much with SAMs recently, but I believe some now may need a command post too. I know the hawk requires one. The USA SAM systems are lacking compared to the Russian. Try the hawk or patriot system. And I can't see pics on your post

Sam ranges depends on type. Use Sa-6's or 3's for shorter ranges or the manpads. As for the AWACS, the only way I've been able to get them to work is to delete the item in the advance waypoint actions for the first waypoint, set up a 'Start Enroute Task' - AWACS, and add a second one, 'Perform Command' - Set Frequency. This will be the frequency that an aircraft has to tune to to use the awacs. Take note that FC3 aircraft do not have to tune radios and will have it automatically.

Not only do they need a backup process, I think it's a good idea to release an offline installer each minor version too. With games that provide it, each minor version installer I normally chuck onto DVDs as I prefer to do it that way. What I'm saying is have an offline installer for 1.5.0 so if something does happen, the upgrade to 1.5.2 isn't such a big of a hit as the web installer is right off the bat for 1.5.2. I HATE web installers, and if DCS wasn't what it is (only combat flight sim of its quality), I wouldn't be playing it for that exact reason.

It was my understanding that 3rd parties are waiting for the tech to be available before they use and expand on it for their aircraft.

Nope, wont be a problem as the info is in the mission file. Answered your other question above too.

jaznit, db_countries.lua in your DCS directory. check out this thread. Just repeat the process for the F15 instead of the A10. And don't use the files attached to that thread, they are 1.2 versions, but instructions are correct... If you want more info, just let me know. E-2 / E-3 are western AWACS, A-50 is eastern AWACS. Use the above info if you want the same type on both sides. Change TASK to escort, then use an advanced waypoint action to escort the unit you want escorted.