JLX

I want to do many things: Helicopter rescue of downed pilots (Looking into CTLD and perhaps others for this) Save mission results to file so they can be loaded into a following one Easier scripting of ground battles - particularly infantry. (Thus my interest in AGFT) See if it's possible to block line of sight with smoke Etc... But at this point I'm just looking for general information about the various frameworks/scripts. Thank you. I will do this. This is more in line with what I'm looking for - thank you! Can you briefly give me an idea of the difference between MOOSE and MIST? When would you use one vs. the other? Do they excel in any particular area? How specialized are they compared to one another? etc. As a framework, I imagine that you'd use one or the other, not both. Is there a reason I'd want to learn both? Thanks for all the info so far!

I prefer to keep all my custom skins in the ...\SAVED GAMES\DCS\LIVERIES folder and NOT modify the DCS game directory for all the obvious reasons. In particular, I have English Cockpit skins, many of which were designed to work from the DCS game directory via JS/OSGME but actually work fine when put in the ...\SAVED GAMES\DCS\LIVERIES directory instead. For example, English cockpit skins in all of the following work fine: C:\Users\...\Saved Games\DCS\Liveries\Cockpit_Bf-109K-4 C:\Users\...\Saved Games\DCS\Liveries\Cockpit_Ka-50 C:\Users\...\Saved Games\DCS\Liveries\Cockpit_Mi-8MT C:\Users\...\Saved Games\DCS\Liveries\Cockpit_MiG-29S C:\Users\...\Saved Games\DCS\Liveries\Cockpit_SA342L C:\Users\...\Saved Games\DCS\Liveries\Cockpit_SA342M C:\Users\...\Saved Games\DCS\Liveries\Cockpit_SA342Mistral C:\Users\...\Saved Games\DCS\Liveries\Cockpit_Su-25 C:\Users\...\Saved Games\DCS\Liveries\Cockpit_Su-25T C:\Users\...\Saved Games\DCS\Liveries\Cockpit_Su-27 C:\Users\...\Saved Games\DCS\Liveries\Cockpit_Su-33 C:\Users\...\Saved Games\DCS\Liveries\Mig-21_CP However, what is the directory name for the Fw.190-D9 cockpit skins?!? I've tried (by guessing) the following but none of these work: C:\Users\...\Saved Games\DCS\Liveries\Cockpit_Fw-190D9 C:\Users\...\Saved Games\DCS\Liveries\Cockpit_Fw-190-D9 C:\Users\...\Saved Games\DCS\Liveries\Cockpit_Fw-190D-9 C:\Users\...\Saved Games\DCS\Liveries\Cockpit_Fw-190 C:\Users\...\Saved Games\DCS\Liveries\Fw-190D9_CP I know that cockpit skins can work from the user directory as it's fine for all the other planes. I just can't get it to work for the Dora. Can anyone tell me what the correct directory name is (and for bonus points, how they found out)? Tnx!

I'm exploring the capabilities of the mission editor and would like a comparison between the popular community libraries/frameworks that are available. There are quite a few options and I'm not clear on where their functionality overlaps and/or how well they play together. The ones that have come to my attention so far are: MOOSE, MIST, CTLD, AGFT. Are there other noteworthy ones I should be considering? What I'm looking for is a very quick summary on the scope of each, their strengths/shortcomings and the merits/complications of using several at once. Venn diagrams welcome ;-) For in-depth info, I'm happy to read the docs for each. I'm just trying to decide which one(s) to start with. Thanks!

Thanks for the input guys! As rearm/fueling tops up coolant, etc. It's not really a big deal. Seems to me there are good odds you'll run out of fuel before you run out of coolant and have to set down anyway. Also happy to know that the fuel tank order is automatic. Thought I must have been missing something. So, I'll just watch for the empty tank lights and jettison as I go. Appreciate the missile tips, too. Both for which types to use and to ripple fire in pairs at first opportunity. I'll try that and see how I do. I haven't looked up stats for the R-13M1 but from your comment Martin, I'm assuming it's faster and/or has longer range to be able to chase. That's interesting. Maybe I will switch to a couple of those and not take any R-3Rs at all. I'm just starting out but as someone who's used to manoeuvring low and slow, being strapped inside rocket is taking some getting used to. My instinct (poor as it may be at this point) is to get into a turn fight rather than extend into an energy fight (as I'm not quite sure how to effectively do that yet). Once an enemy goes even moderately defensive, it seems keeping a radar lock long enough for a SARH to hit home would be tough. Getting a window to snap off a couple of IR seems much more likely. All things in good time. I'll learn. I haven't been on any MP servers yet. I don't mind getting blown to smithereens while learning tactics, but I'd rather not get blown to smithereens while learning systems. Once I get those down a bit better, I'll see about jumping into the Piranha pit! Cheers.

Picked up the 21 over the holidays and am really enjoying it so far. This plane has character! Not only am I new to the Fishbed, but I'm also new to air combat, having stuck to helicopters and ground pounding to date. I'm hoping some of you more experienced pilots can save me some research time as I get up to speed (pun intended ;-) Is there a way to add missing joystick binds for existing key binds? They are currently greyed out and cannot be assigned. I know some can be bound to an axis but I want to use a button. Is a patch incoming? Is there a workaround? Intercept Angle: I/LAlt+I Target Size: S/LAlt+S Show Controls Indicator: RCtrl+Enter KPP Set Pitch: LCtrl+K/LShift+K Toggle Mirror: M Toggle Briefing: LAlt+B SPO-10 Volume: V/LAlt+V   I see the radar needs alcohol to cool and thus has limited/finite use. When you rearm/refuel is this replenished? Perhaps when you repair? Is there any way to refill this without getting a new plane? Same/Related question with compressed air for landing gear and pneumatic brakes. Any way to top up? I guess the parachute falls into this category too. What if you need it on your second landing?   How do you ensure fuel is taken from tanks in the right order? Wing tanks first, then ventral, then internal. Is this automatic? Do you have to do it manually by turning pumps on/off? Is there a fuel tank selection switch (I couldn't find one)?   Preliminary digging leads me to think The R-60M is the go-to IR missile (over the R-3S) and the R-3R is the go-to SARH missile? Is the R-60M somewhat comparable (if lesser) to an AIM-9L? I'm looking for an optimal air-to-air loadout and am currently trying 4x R-60M and 2x R-3R with a big center tank. What do most of you run with for A2A?   Lastly, any general tips for being effective in the MiG-21? Thanks for any help with the above! Cheers.

F10 User Marks are little red circles with a note attached that you can place on the the F10 map with a new button at the top. These marks are visible by other players. As they can been seen by others, they (like the F-10 map itself) may be considered a "cheat" in the strictest sense which is why there is the option to turn them off if you want to enforce a more realistic play style. They are (to the best of my knowledge) a fairly recent addition which is why you don't see reference to them in the manual. They are very useful when communicating ground positions between players including JTAC type roles. Especially useful for older planes that don't have a TAD like A-10C does. They can also be created by trigger events in the mission editor.

@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.