fargo007

No problem, it's really just a script I'm furnishing, so I want people to sort of "make it their own." The hot starts and air starts are there primarily for me to test the code. I didn't intend that people would fly them, but you could. Enjoy!

This version should be the easiest of all to port in. If you are talking about the loading of the sounds in the trigger, that doesn't matter at all. coalition, country, group, etc. All the same. So look in the Saved Games\Log\dcs.log file. At the start, you will see: **** TROOPS IN CONTACT LOADED **** After that statement, look for errors. They will likely start with "Mission Script error" or "Mission Scripting error." Like Krasniye, check the statics if you have renamed any. For some reason both the static's name, and unit name have to be the same, FRIENDLYSTATICS-1, FRIENDLYSTATICS-2, etc. Statics always get me.

I wish they'd fix that. It bites me in the butt too.

Try downloading it again and don't edit anything. If it works, your edits are messed up. Especially statics. When you change a static unit, the name reverts to something like "Static-this-and-that-001" or something.

It's a 7z attached to the OP. Wasn't big enough to require separate hosting.

Version 5 released. TROOPS IN CONTACT! is now entirely script driven, and requires no triggers other than to load moose, itself, and the sounds. Tons of new configuration abilities are available. Request new smoke, Cleanup, Distances, times, Heavy enemies possibly trying to flank the friendlies, all of this is fully controllable. See the script itself. Stub missions are just examples with knoob ME options turned on, and are meant for you to add your own aircraft, and move things around.

Thanks, Yes, I do plan to do this. I want to first wrap up a lot of the loose ends, such as converting the ME triggers to scheduled functions in the code, and offering a set of configurable parameters that a mission designer can tune, similar to other scripts. Tunable params I envision include: Time delay between TIC calls. Distance radius from friendlies enemy groups will appear (min,max) configurable flag numbers the script uses (so a mission designer can manually trigger events using flags) configurable zone prefix names for where they TIC events occur. Heavy class enemies can optionally split off from their support, and conduct a flanking maneuver after some time (this is coming in v4, and it is SUPER cool) . The probability that they do this (expressed as a percentage) and the min/max distance to the friendlies is configurable, as will be the formation they travel in. There is a decent amount of work here. You all are helping me to test.

It's already in our campaign! I broke it out into its own mission to get feedback and ideas on how to improve it and I haven't been disappointed here. You could put them anywhere since they are late activated. It's just handy to keep them all in one place. One of your groups is chosen at random for each category, each time. @Wood Way to go!

We've been invited in the past to a version of this on PG with Ka-50's, and it felt like an awesome responsibility to knock these sights down hard. They were a bit better defended than IRL, but we got it done, and it was a lot of fun. A great joint RW/FW mission for sure.

Planned for version 4: Switch to a CAS 5-Line format for voice and messages. I worked with a professional who both does and teaches this to get it right. Easier group management. Instead of a fixed number of rigidly named groups in each category, you control them by simply naming them by a convention. e.g. "HEAVY-" Groups with names beginning with this string spawn when heavy TIC is called for. "LIGHT-" Same concept. "SUPPORT-" Same concept for support elements to heavy units. Think trucks/troops that support a tank platoon, or provide recon/anti-air. Your choice. "FRIENDLIES-" These no longer need to be immortal or hold fire (now handled in code). "FRIENDLYSTATIC-" These must be blue coalition statics. There is no maximum, but you must have a minimum of 1 correctly named objects in each category or you will break it. Default coalitions will be Combined Joint Task Force blue or red (e.g. country.id.CJTF_BLUE) Thank you for all the feedback, this should be a big improvement.

Thanks, You can't change the coalitions (color: blue/red/neutral) but you can change the COUNTRIES that make up the coalitions. You are blue, bad guys are red. Whatever you decide that means country by country. Number of units can be whatever you want. The heavy setting spawns a "heavy" group, and also a supporting element, of the type in the "support" zone. It's more targets, and harder opponents. The distance is random, but within a radius (inner/outer). Basically enough distance that you can safely engage on the inside without hurting friendlies, but on the outside, still shooting distance of each other (by a DCS average).

You can kind of do this as-is by just manipulating the contents of the enemy groups. I wanted a light and a heavy deliberately because sometimes you want to roll with just rockets and guns, and I didn't want such a shooter to encounter hard armor that would prove impossible. Or when I go out in the 24, I go heavy until I'm out of ATGMs, then I choose a couple lights before I RTB to spend out the rest of the payload. Wouldn't be hard to do a "random" where it chooses for you. Just got done taking counsel on 5-line stuff with someone whose job that literally is. I'm moving the comm structure over to the 5 line format to see how that goes.

I'm in an all RW squadron so yes, this was built with helos in mind for sure. Under the hood.... the friendlies are immortal, and don't shoot back. This is by design, because most of the time one side will wipe the other out way before you get there. There are some statics used to create the appearance of damage and casualties. Those do get shot at, and they explode and burn. Yes, absolutely - if you are carrying CTLD or similar troops and insert them (e.g. and use CA to vector them accordingly), they will definitely either help, or wind up getting themselves hopelessly slaughtered thanks to the shitty infantry AI right now. Adding a CASEVAC based on a weighted randomness would be a neat feature. I could let a trigger control that via a flag, so you could adjust the percentage from 0% (never happens) to 100% (every time), so the script never needs touching. Come back once you've tried it out!

Thanks for letting me know that the integration went well. I really wanted to hear about a successful example of that. Looking forward and planning version 4, I'm considering changing to a five line format for the transmissions. Minor, but it's a small step toward realism so why not.

In the instructions it describes how you can change the enemies to suit your needs. You can't delete any groups, and you can't rename any groups or statics. Add any aircraft you want, set up how you like them. But you can absolutely change what they are. Anything except deleting or renaming is fine. There are lots of presentations with big groups of infantry involved. The only thing that's mandatory is you fly blue coalition and the enemy is red. You can put whatever countries in whichever coalitions you like though. Leave some feedback once you give it a shot.

Because most of what we see are vidyas of Apaches supporting troops on the ground that are in contact, I built a pretty robust "Troops in Contact" mission on 3 maps that I posted in the main Missions & Campaigns section. Just added version 3. I had this in mind for the 64, but it's great fun with the MI-24, Ka-50, 342L, and any fixed wing bomb truck you wanna bring. It is mostly script driven, fully multiplayer capable and includes instructions for consuming it into your own missions. https://forums.eagle.ru/topic/286538-troops-in-contact-v3-released/

Thanks @Stratos For helping to test. V3 released, which contains bugfixes that involved fixed wing. Now released as a zip that contains all three maps: Caucasus, Persian Gulf, Syria.

Thank you guys! For some reason I never considered that the switch worked also for bombs.

When dropping the FAB style bombs from the pilot seat, they drop one at a time. When dropping from the operator seat, they all go off the racks at once. Is this expected behavior, or am I missing something?

Thanks, I am on my way to sorting it out! Now I need to figure out why all the bombs drop when the operator does the bombing, and only one at a time drops when the pilot does it.

Thank you, same. I will check it out soon and see what can be expanded from where we are here. If an indexed, spawned unitname is exposed, I'm pretty sure we can get it and use it, at least with an event handler. It's cool stuff we're doin' bro. We toil for the glory of DCS.

Thank you very much for the reply. This does help a lot actually. I imagine with it I can track events by unit (rail car) as well, and have scenarios where single cars in a large train might be specifically targeted, or when attacked (hit), have enemies spill out from them with SpawnFromUnit() and start fighting back.

I'd just take the drive out of the old one, add it in to the new one and copy the stuff over locally. Then use the old drive as expansion space.

No need, I have those. They still don't make it clear how the equipment is to be used.

They've made the articulating front seat sight usable, and the bomb timer as well. Has anyone dug into how these are to be employed for bomb dropping? I'm staying away from the KMGU/USLP clusterbombs for now since they create a horrible frame rate issue. But we do see examples of dumb bombs being used IRL.