Recluse

I have to say that MenuNav has largely been superseded for me for a long time by DCS adding the capability to use a button/hat to scroll through the comms when the menu is up via the Command Menu mapping: null

@crazyeddie Glad you got it sorted!!! That's what matters! These kind of things are always so hard to diagnose and fix since they are often depending on lots of individual configurations.

Ahhh I didn't realize you were talking about AI....Agreed that it should work the same, but let me test that as well!!.... Still works as expected for me...

Your install must be messed up. I just tried it and it works fine. ME screenshot taken immediately after placement. null

Ahhh!!! Thanks!! I saw the scribe loaded but I didn't think to explore it. Always something new in the M to RTF!! Thanks as always for your constant DML maintenance and tireless support here!! Sorry that DCS keeps breaking stuff that you have to fix!! I was anxious to try the new SAVE module, but after reading your take on it, I decided HARD PASS for now especially since DML does it all, and more, and better!!

@cfrag Quick question, though I may answer it myself by just TRYING IT OUT...but just in case: I was messing around with the CFRAG Marianas Proving Grounds, and noticed that when starting up, the Valet module (I assume) provided stats on the aircraft I had flown previously (even previous sessions, via Persistence). I didn't notice anything special in the valet statement, so is this automatic when persistence is enabled or did I miss another Trigger zone somewhere?? Thanks!

Not sure if it is related, but fairly recently (well a year or so) new functionality was added to allow you to scroll through and activate the COMMS menu with Trim Hat or other control that could be used when the Comm menu was up. I have seen often that the TRIM HAT gets bound to VIEWS instead so maybe this is what is going on with you. Check this COMMAND MENU These controls should ONLY be active when the COMMS menu is up, and should not conflict, but another thing to check if you have double bindings for VIEWS on some of these keys. If nothing else, setting these might let you get away from the F keys themselves. It is odd since in my GENERAL settings, I have all the F keys mapped to the views, but when the COMMS menu has the "FOCUS" the F keys still work to select stuff. EDIT: LOL In fact It commonly happens that I am heading home and have the Comms menu up and I decide to take an outside view, so I hit the F2 key and hear "ABORT INBOUND!!!!!" OH CRAP, NO!!! Also it might help to make sure you are invoking the COMMS menu with the RALT and RCTRL + \ commands vs the \ only to properly invoke the radios.

Click the Green CODE Button and DOWNLOAD ZIP HINT: Inside the zip, in addition to the modules you will find EXTENSIVE documentation. null

Not sure exactly where to put this: - Mission Editor -Game Crashes -Kola Map Bugs so I tried to make the title inclusive of all 3 Often, when on an airbase that doesn't support certain aircraft, the Dynamic Spawn menu will not show that aircraft as available (even if it is present in the Mission Builder WAREHOUSE screen). We have observed, however, on the KOLA map that at least at BODO and ANDOYA, C-130 Hercules (the ANUBIS Community MOD) shows as a Dynamic Spawn, but the game freezes and crashes as soon as it is selected and attempted to SPAWN. Seems to work fine on other maps insofar as when the C130 appears, it can spawn. Other aircraft including the OV-10 Bronco (another community MOD) spawns fine from KOLA bases. IT seems to be an interplay between the KOLA map and the C130 mod not being a supported aircraft for a given airbase which leads to a CRASH, where it should just not be available. - The mod is present for Host and Client - The mod appears as a dynamic spawn for the coalition at the airbase - The mod spawns and works as expected on other maps on airbases that can support it, and does NOT appear on the Dynamic spawn list if the aircraft is not supported (too big) for the given airbase Thanks for any insights..

I honestly don't recall EVER getting any response to a Declare request from a BLUE AWACS either.

Love the Dynamic Spawns!!! One thing I have noticed is that when there is a Dynamic Spawn Template placed on the Map, the F/A-18 HOME FUEL warning will appear based on the TEMPLATE location vs. the actual Spawn point. Have not tested exhaustively, but this is my impression based on multiple instances where HOME FUEL warning is appearing when it shouldn't. I know the Home Fuel WP can be edited on the FPAS page so it is not such a huge deal, but I wonder if Dynamic Spawns can be modified to use the Spawn Point vs. Template point for this calculation.

Hi, We just encountered this. From the limited testing, I believe this is due to the the HOST (either Player hosted or Dedicated Server) not having the mods installed. All aircraft available to the CLIENT will show on the Dynamic Spawn page, but if the HOST does not have it installed, that message appears.

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!!!