Recluse

Thanks for checking. It is so odd to me since DCS uses that for all sorts of AI communications one would think it was available somewhere..but it is not the oddest thing about DCS

LOL... one of these days I will FINISH a mission before a new DML iteration is released Quick question regarding Wildcards for Messenger, Usher, Valet: Quite possibly I missed it but: I know you can pass the name of the PLAYER callsign, UNIT, GROUP, but is there any way to pass the DCS assigned callsign of an aircraft e.g. "ENFIELD 1-2"

Exactly what I had in mind!!! Will test it later today. Thanks!!!

@cfrag Another Reaper suggestion if you are going to look at that module for future updates: maybe a bit of a cheat, but could you consider adding an "invisible" attribute so the Reaper can be used over SAM cover without getting shot down? Noticed that the Foothold/CTLD Reaper SEEMS to not be attacked by SAMS so are probably set to INVISIBLE or similar. I would think these drones have a pretty small radar and IR signature, so MAYBE not totally unrealistic. I think the DCS SAM operators ARE unrealistically effective....

Yeah I did notice that. Luckily it seemed to work for the Harrier, Mirage and UH-60L. Didn't get to test the Strike Eagle

Thanks for the information. Will wait until those modules are ready for Prime Time. Meanwhile, I will soldier on. In my Flight Simming career, I have ALWAYS been more interested in Building Missions than actually flying them. Lately, other than training scenarios, I have been enjoying actually FLYING more. This little project of mine has me backsliding to the old ways..

Appreciate you trying!!! Working well for many aircraft already.. LOL too bad the Hornet tends to be the one I fly most often, but I NEVER expected this implementation, so it is a total NET POSITIVE

Not DML related, per se, but so as not to re-invent the wheel, I was wondering how people handle things like (pseudo-dynamic) CAP, Tanker, Attack, Capture scenarios. I have started mapping some out via Flags and Cloners/Spawners, but it is kind of cumbersome when one takes into account WHO OWNS what BASES to determine where to spawn and what to attack/defend. Kind of leaning toward just cheating and spawning out of thin air on a randomized timing instead of building in logic to select certain bases for spawns. @cfrag any insight you can give me (here or privately) on the basic usage of the undocumented features you use in EXPANSION (milHelo, milWings etc..) would be welcome!! I suspect they will save a lot of time and hair pulling!

Well, unless i did something wrong, it seems to work OK for AV8BNA, F-15ESE, M-2000C and UH-60L but NOT FA-18C_hornet For the Hornet, after giving the TYPE specification and selecting a map point, I do not get the 3rd line starting with the @|#| Haven't tried the Apache or the A-10C I also didn't try to actually input the coordinates after spawn, but I THINK the coordinate system shown on the last line were correct for those aircraft as far as I recall, but pretty sure it won't work without that line for the Hornet. EDIT: Entered coordinates into AV8BNA and M2000-C fine

I have been manually adding the way points from the scratchpad data generated from the Dynamic Spawn map as, usually I am only adding a few. Helps to have all the coordinates ready to go. LOL remember the OLD DAYS when this is all Scratchpad did anyway??? Good times!! If it is a longer route, or a ton of targets, I'll just wait til I spawn, though lately, going to the F10 map too much in VR often gives me trouble.

OK!!! Learned something that perhaps should have been obvious Will have to create some more messengers all around

OK I think I found a clue! though I don't quite understand it. I included both the messenger attributes in the ownAll zone. IT seems that only the FIRST one triggers, either GoodGuys or BadGuys. Can I not have 2 Messengers in a zone? I thought I had done this in the past. Whichever one is FIRST shows a message and the second does not. Maybe I need to stack the Messengers directly under the banged flags? null

I can send you the mission but it is pretty much spaghetti code with me throwing everything at the wall to see what sticks. I may create a new mission with ONLY some zones and ownAll to see if I can get it to work and see what I missed or did wrong in the main mission.

Indeed, Holmes, your monograph was quite clear on this and I have endeavored to follow it Or should messenger load even before cfxZones? null

Nothing is silly when trying to diagnose my errors or misunderstandings -This was at mission startup. From the docs, I believed that when all zones were initialized, the appropriate flags were banged and should generate outputs. I assumed this was both Red# and Blue#. In the list supplied to ownAll, there were 4 zones, 3 owned by the "Bad guys" (RED) and one owned by the Good Guys (BLUE). - I did check Message History and there were no clear view commands (though I usually put one in once I am convinced everything works and I know everything loads correctly) - My INTENT is indeed to use ownAll to keep track of stuff as it is captured by Red or Blue. As those # flags are banged on zones changing hands. Also added a Blue! and Red! output to report total WIN or LOSE conditions, but haven't tested for that yet. For now I was just testing at mission start to make sure I configured all the zones and flags correctly. Have a few zones configured and testing on one zone to make sure everything works whereupon I will copy everything to the other zones and adjust the parameters accordingly. - In my nascent mission, I have 3 methods for capturing zones (Airbases for now with Airfield zones to track ownership, FARPS to be added). Human BLUE Player captures a zone which has been cleared of defenders by inserting helo Troops. AI BLUE Helo commanded to enter the zone when cleared, (clear message triggered by a unit zone with exitZone! * (filter for ground units output)) and triggering a cloner of BLUE units when the particular helo group enters a unitZone (e.g. enterZone! BlueCapHelo*) AI Red Helo triggered to enter the zone when cleared and triggering a cloner of RED units when the particular helo group enters a unitZone. (e.g. enterZone! RedCapHelo*) I worry I have too many zones configured on each base - Airfield zone for ownership - 2 x Unit zones to cover exit and entry - RedSAM, RedArmor, BlueSam, BlueArmor cloners (yeah I know I could just use a Master Owner to change the affiliation of the clones, but I wanted RED to have Russian equipment and Blue to have Western equipment.) - Willipete zone -ReaperZone