JLX

@astazou Wonderful app! Just tried it out and it works beautifully. I'm running 1.2 beta and see that only certain panels for the Eagle, Mirage & Huey are available right now. I'm very eager to use this with the CDU on A-10C and hope you are able to make that available soon. Two things are particularly helpful about this program: The touch area to change a switch briefly lights up when activated. This is great visual feedback to see exactly where the touch area is and also let you know if there is one area to press (to cycle options) or multiple (for up+down, etc.) touch points. Some switches that look like they should have Up+Down actually just cycle through the options and seeing the registration area when you tap removes the guess work.   The Sandbox tab under Settings is great. I'd like to learn more about communicating with DCS externally and this will be very useful. Hopefully using this and playing with your export++.lua file, I'll be able to add my more on my own. Nice touch to include it! If you have any tips about how to find the argument values I see used in your Lua file I'd be curious to learn more. While the visual feedback is nice, perhaps for a future version you might think about adding both haptic and audio feedback. It would be nice to have the option for the device vibrate and/or hear a switch "click" as feedback when you use it. Thanks for an excellent contribution to the DCS community! Cheers.

Currently the program error checks the joystick/POV assignments to make sure they're valid and this screens out any normal AHK assignments. I'm assuming you want to do this as you may have letter keybinds to your joystick buttons. I'm still planning on adding easier setup and a menu detection scheme to avoid sync issues in a future version. I'll add allowing standard keyboard keys, rather than just joystick buttons, to the wishlist too. Thanks for the suggestion.

Apologies gents! The overlay is indeed not displaying in VR as intended. To address this, I've added audio cues to the program so you can use your ears, rather than your eyes, to navigate the menu. Hopefully, this will make the program useful in VR again. Let me know if this works for you or if you have any other suggestions for improvements.

I agree that multicrew JTAC unlikely which is a shame. Let's hope we're wrong :-) Thanks for mentioning the visual recon mode as I'd never used it before. While it seems like it was designed specifically for what I was asking about (contributing to a tactical overview for someone in a command role) I found it cumbersome to use. Admittedly I only tried it briefly but when the cursor is pointed below the horizon it disappears! This makes selecting the unit you wish to spot very difficult. Above the horizon, I get fine black crosshairs, but not below. It seems like the intent is to aim in the general direction of the unit and the software will search for a valid target. In my case, there were several units close together and while it did find (and announce) 1, no icon appeared on the tactical map (I have Combined Arms but was in a pilot role at the time). I tried spotting again to declare all the units but was unable to. Regardless, thanks for the info. I'm going to spend a bit more time playing with the feature and see if I can get it to work better for our needs. Cheers.

Overdue or not I'm still very grateful for the news! I'm so looking forward to trying multi-crew out. One thing I'm curious about: if you have Combined Arms will the co-pilot/gunner be able to use JTAC binoculars to spot/mark targets? I'd love to be able to use the Huey as a command heli where the copilot could switch between these two roles as I fly. There is a guy in our group who only does JTAC/FAC with some vehicle shooting. Being able to fly around together with him gunning and marking targets would be fantastic! Anybody have any info on this? Sent from my BTV-W09 using Tapatalk

Regarding multicrew, I would also like to take up a player to not only fire the weapons but also as an observer and act as JTAC (with Combined Arms) with binoculars, etc. Who could mark enemy positions with smoke etc. from the chopper.

Agreed. I'm also interested but do want to know how many modules it will apply to before purchase.

50. Ug. How the hell did that happen? Dabbled with earlier sims but the ones I first put time into were and

This works for me in the A-10A. Perhaps check to see that User Snap-View Saving is enabled in the settings. It's on the Misc page.

Can you please give me an example of when this happens? I'm working on a solution for this. It's a little tricky but if I can get it to work, DCS Menu Nav will be able to detect - rather than guess - the state of the menu. If successful, this should address a number of shortcomings as well as sync issues. Thanks again for the suggestions. Activating the overlay on a next/prev press is already planned. Auto-increment on hold is a good idea and I'll also likely add it as an option. Thanks for sharing your solution. My I ask why you changed the line spacing to 11 from the default 16? Have you changed the size/position of the menu? I'd like to understand various unanticipated use cases as this may be relavent to my next round of updates. Tnx. This is also on the todo list. To everyone else, thanks again for the kudos. It's always nice to get feedback for one's efforts. Cheers!

Hey ron533, How did you resolve the issue? Perhaps your solution could help others. Was the problem that you weren't using the correct prefixes or was something else amiss that you figured out? As a few ppl with multiple controllers have had trouble with the config, presumably because it's not obvious which deviceID a particular controller is using. I'm going to simplify the setup by adding device/button detection when I get some free time. Hopefully this will help. As usual I'll post here when it's ready. Cheers.

Hey hog_driver111th, If you're using prefixes to specify the joystick, please remember to check and make sure the modifiers (if you use any) are correct too. You may have changed the prefix on the buttons but forgotten to change the one the modifier? If you're still having trouble getting the stick recognized. Check to see if you've setup a preferred default in Windows. Try setting it to your TMW and then just use the default joystick (i.e. no prefix number) in DCS Menu Nav. You can see my test setup as an example below. Please let me know if this works for you. If so, I'll add a little blurb in the original post in case others run into the same issue. [buttons] BtnToggle = Joy10 BtnItemUp = Joy7 BtnItemDn = Joy9 BtnSelect = Joy8 [Modifiers] BtnMod1 = Joy4 BtnMod2 = BtnMod3 = BtnMod4 =

I've posted version 1.1 (download link updated in original post) with the suggested changes. You can adjust or disable the timeout in the INI.

Thanks for the feedback Frederf - they're good suggestions. I'll add both of those and post and update when it's ready. Edit: Are you aware that toggling the indicator off presses the F12 key for you? So, rather than scroll to the F12 EXIT option in the menu, just toggle the indicator off and it will hide the DCS menu automatically for you. This is even quicker than manually scrolling to F12 to exit the menu. Just a FYI in case you weren't aware.

Thanks for this. I fly mainly solo and, like you, prefer no labels. However, this is *much* better for those times where you do end up using them. I wasn't familiar with the labels.lua settings and this saved me time getting up to speed.

Most well written and helpful thing I've read on the topic! Not only do you clearly have the expertise but you ability to articulate it in a concise and helpful manner is very impressive. I really appreciate you taking the time to share you knowledge with us. This, is exactly the kind of information that fascinates me and I love learning more about it. Not to mention the fact that it just makes time spent in DCS even more rewarding. Thank you so much for all 3 parts! Cheers!

Yes, unless the joystick is your default device, you'll need to use a prefix. Sent from my SM-G930W8 using Tapatalk

Hi Verde, DCS Menu Nav doesn't automatically become visible when you activate the comm menu. It becomes visible when you press the joystick button combo that you set in the INI file (BtnToggle + any modifiers). If you'd like them to toggle on/off together (which is very handy) you need to set the Toggle action button (and any modifiers) in the INI file to the SAME BUTTONS assigned to the radio trigger (or comm menu) in DCS. If you look in the READ ME file, you'll see I mention this under the TIPS section. That said, if they are set differently to what is set it DCS, that's ok too. But you need to use the buttons set in the INI toggle it on/off manually after activating the comm menu as you usually do. If that is still not working (as you mentioned) then perhaps the default modifier (button 4) is NOT the brake lever but the "pinky" button. I use a CH Combatstick and don't have access to a Warthog stick. So, I can't confirm which button is #4 on the Warthog (perhaps one of you Warthog owners can help here?) But, from pics I'd seen online, it looked like the button mapping is similar on both sticks which would make button #4 = pinky. At any rate, please double check the button assignments, set them to what you prefer, and try again. If you have any more trouble. Please post again and I'll try and help you out further. Good luck!

Tnx for the kudos, guys. Glad to see there are a few out there who can benefit from this as well. @Sgt_Baker: Good idea. I assume that anyone who is very HOTAS focused (and thus a likely candidate to use DCS Menu Nav) would already be familiar with modifiers. However, for anyone who is not familiar with modifiers, I highly encourage you to look into them as they vastly increase the utility of your HOTAS. I use 4 modifiers myself but even using just one will double your available buttons. I'll add a blurb to the included READ ME too.

Hi @zaelu, Are you using Voice Attack for your voice recognition? If so, what you want to do is already possible and quite easy to do. If you're not familiar with setting it up, might help. Or, you may want to check out something like VIACOM if you haven't already and want something more full featured. If you're not using Voice Attack (Highly recommended and worth every penny) and just want to map a sequence of key-presses to a single joystick button as you mentioned. You could use AutoHotKey (Also excellent and what I used to make my utility). What you want to do could be done in AHK with a single line. For example: Joy2::SendInput, \{F1}{F2}{F3}... I made DCS Menu Nav to be: Quick & simple to setup and use. Be general purpose and not require "knowledge" of the existing menu structure. This is so it will work even with custom/unknown menu items that a mission designer might insert or if the menus change in a future version of DCS. Can be easily activated/deactivated on the fly so the F-Keys don't trigger view changes by accident. Has an on-screen visual aid. Only need a single 4-way hat switch rather than a separate button for each F-Key. Doesn't require voice (for those late night flights ;-) I couldn't find a good solution for these requirements which is why I rolled my own. But, for what you are trying to achieve, I think you may be best served by Voice Attack. Hope that helps!

Just wanted to add my support for the P-38 (L). Fav warbird of all time!

+1 This is a HUGE oversight and I also am not sure why this has not been implemented yet. Apart from the obvious convenience, it would make a big difference in getting new users willing to adopt DCS as their flight sim and lead to more sales. I understand the need to focus on the "big" things but DCS has reached a point where there are just SO MANY little things that need attention that they now just fall under the radar and never seem to get any attention at all. I would have hoped that with the 2.0 alpha out so long now, that we would see these type of issues implemented there already. Here's hoping they get some love... "soon™"

Wasn't sure of the best forum to post this and opted for Mods & Apps. But, as I think it's especially useful for HOTAS/VR users, I thought I'd mention it here too. If you're interested, check out this thread in the Mods & Apps sub-forum Mods: If this is considered unhelpful or too much of a cross post, pls move or delete as necessarly.

The "O" in HOTAS stands for ON. But, navigating the DCS Radio/Comm menu requires you to take your hands OFF the stick (especially inconvenient in VR) to either: Use the F1-F12 keys on the keyboard, or Reach for your mouse and click on the entry There are no internal DCS hotkey entries for navigating the radio menu and F1-12 are also used for changing views, making common workarounds cumbersome and often needing 12 button assignments. If you're not a fan of talking to your computer (e.g. Voice Attack) then perhaps this utility will be of help to you. DCS Menu Nav is a simple program that generates F-Key presses with onscreen and audible indicators to help you navigate the radio/comm menu with your joystick. Needing only 4 hotkeys that you can assign to a single hat switch, it makes menu operations in DCS much easier for HOTAS users. Hopefully, in the future these hotkeys will be added directly into DCS and this utility won't be needed. Until then, it get's the job done. WHAT'S NEW? Audio cues have been added to v1.2. They are on by default but can be disabled in the INI. As the overlay doesn't appear in VR (only tested with Vive), the new audio cues should be a good (perhaps better?) alternative to the on-screen indicator when in VR. CHANGE LOG 1.0 ( 2017.05.10 ) Initial Version 1.1 ( 2017.06.12 ) Autohide after timeout interval (in milliseconds) 0 = Disabled Selector hides automatically when F12 (Exit) menu option selected. 1.2 ( 2017.12.08 ) Audio cues added to address overlay not showing in VR. No longer sends F12 (to close DCS comm menu) when indicator is hidden as if not in sync, it can send an unwanted F12 view change. Please check out the included READ ME for more details. I'll post any updates to this thread. So subscribe to it if you want to be notified. Download v1.2 here

Hey @emolina, Just a quick ping to see if you're still developing your interesting mission generator as I hope to see it expanded even further. I still see huge potential here. There are a few features I'd love to see added but I know time for these side projects are not always in abundance. Anyway, just wanted to give an ping and let you know there is still interest in doing interesting things! Cheers.