Home Fries

Some of the OSBs use keyboard commands to deconflict with persistent DirectX commands (like held switches). You may need to be deliberate in your presses so the commands recognize the modifiers as well as the keyboard commands (which are keypad and keyboard numbers that would map to the UFC with different modifiers). In the Controller References (Warthog or Cougar), there is a section for VR Deviations near the top of the Table of Contents. They say to S3+Double Tap left/right to get stations 3 and 4. If this doesn't work, please let me know as I don't have VR and I don't test this very often.

Getting this now as well. Recognized by VA, but no actual response with TACAN Tune or Link Tune. TACAN Mode works fine. Manually reinstalled latest versions of VAICOM and AIRIO, reimported the latest VAICOM/AIRIO vaps, using x64 version of VA in the default install folder.

#4 for me, I'll command something else (not necessarily QSNO or QHUD, but Area Track does this as well) and Jester will immediately return tracking to the last selected (usually QWP1).

It's pretty straightforward once you learn the commands. Much more natural than using the wheel. The only downside is that when you have multiple targets and you want to STT one of them, it's not as easy to call the number as it is with the wheel (which tells you the BRAA in each pie slice).

+1, though this should really be an ED-wide request.

Getting Voice Attack to work with the Jester Menu makes my brain hurt more than getting VAICOM with AI RIO to work. The reason is that Voice Attack by itself will take your voice commands and translate them to keystrokes. When you have a dynamic menu system where the keystrokes change, this is a non-starter unless you do the Voice Attack for each item on the menu (e.g. Jester Menu, Option 1, Option 3, etc.). BTW you can already do this with VAICOM. VAICOM has a lua plug-in component that communicates directly with DCS, rather than using the menu system. This means that dynamic/changing menus are a non-factor, you don't have to watch the text menus cycle through, and it's a lot faster and more seamless. Because it uses the in-game engine, you have more options (use of callsigns, frequency changes, etc.). Bottom line: it's a game changer and a massive step up from just regular voice recognition. As for learning it, it can be tricky at first. Do a few minor things to make sure you get the steps down (you have to do some copy/paste because of how VoiceAttack works), so do small updates at a time, then once you get comfortable with the idiosyncrasies you'll wonder how you got along without it.

Thanks for your interest, Ruger. I'll forward the info to the channel host.

After arming the LANTIRN laser: "Now witness the firepower of this fully armed and operational battle station!"

It's really not that bad. Just remember to control your inputs and roll with rudders at high AoA and you'll be fine.

Dos Gringos nails it! JDAM is capable, but sterile. All things equal, I'd rather carry JDAM into a real-world strike, but LGBs are just more fun in-game. The hornet can do more things with more systems, but the Tomcat is just a joy to fly! She handles well, but will keep you honest if you abuse her. You learn measured control and you look/listen for feedback rather than watching a speed or AoA indicator to see how you are doing in a turn. You also get used to the steam gauges, to the point where you just look at the position of the needle to know your speed instead of having to read a number. The Tomcat is not as intuitive to fly as the hornet, but it is a lot more visceral and will force better airmanship on your part, which will translate to other airframes (including the hornet). The Tomcat can also do precision air to ground using LGBs, and is the only platform right now that can use the Tactical Air Launched Decoy (TALD) as part of a coordinated SEAD/DEAD mission. If you would rather be the HARM shooter in SEAD, than the hornet is for you, but the Tomcat is just a lot of fun. And when you do things like tank or trap on the boat with the A model, you get a real sense of accomplishment. I really enjoy tanking with the Tomcat; I actually have more plugs than landings in my logbook.

Check out the end of the video for the spoiler.

I was doing about 250 with a 35 bank angle, and I did not at the end.

The F-5 is a great plane for learning good airmanship for reasons that have already been covered. It is a fun plane to fly, but frustrating to fight for someone new to DCS. The full-fidelity module I recommend starting out with is the M-2000C. It has a great HUD, the best autopilot in the game (which allows you to play with the cockpit without hitting the ground), it has an intuitive radar, the systems are fairly simple, and it is fun to fly. The delta wing will also teach you energy management. You will bat-turn until you find yourself in a stall, but then the controls are fairly forgiving and you can easily recover (with enough altitude).

Version 2.62 is released for DCS 2.7.7. Stick with 2.61a if you're using the 2.7.6 stable version of DCS. Change log: Updated CTS GUI to make long edits on Values page (e.g. paths) easier. Added support for MFD Management Framework. F-14: Added HSD CRS/HDG to LMFD. Updated diff.luas for 2.7.7. UH-1: Added Flashlight to RMFD. Mosquito: Updated Engine Cut for 2.7.7. Updated Observer SnapView9. Updated bindings since 2.61a: F-14 Pilot/RIO, Mosquito, UH-1 Updated bindings since 2.61: AV-8B, Mi-24 Updated SnapViews since 2.61: Both Updated Custom Luas since 2.61: F-14, UH-1

I just confirmed that the server is working, so DNS might be the ticket here. 2.62 (which fixes the Tomcat with the latest beta patch) is in testing right now and should be available soon.

I had to rebuild both the Pilot and RIO profiles for everything. CTS 2.62 is in beta testing right now and should be available shortly pending a lack of bug reports.

Version 2.7.70 is updated for DCS 2.7.7.14727.

I actually lost quite a few, but here's what you can do to make sure you get them all back without having to start from scratch. You'll want to do this for keyboard, as well as your other controllers: Take your existing diff.lua backup (hopefully you have one) and open it in Notepad++. Save your existing controller configuration in 2.7.7 to another diff.lua. Open the new diff.lua in Notepad++ alongside the original. Use the Compare plug-in to compare the files side by side. You'll likely see different controller codes on the top line (which is what is causing the deletion), but in the original file you'll still see the description of the control in the diff.lua. Find this in DCS and apply the mappings used previously. After you do a few changes, save your diff.lua again (same filename). Return to Notepad++. NPP should recognize that the file has been updated and prompt you to reload it. Do this. Run Compare again and make sure the changes took. Just keep doing this until you have rebuilt your controller profiles. It's tedious, but at least you don't have to remember what you were doing with what combinations and rebuild from scratch.

My contribution to the TMF Tomcat was the kneeboard/bluebrains graphic that substituted for the NATOPS manual on the knee in later versions.

Wow you were TMF? That's awesome. I did the same kind of thing with the A-6 Superpack. I also loved that you could put decals anywhere with coordinates based on the CG of the aircraft.

To me the solution could be somewhere in the middle: Take the most popular sizes and allow them on the object. Italics may make for wider kerning, but that's something we would have to live with. The 90% solution would be good enough for most people who want dynamic Modexes without having a lot of skins on the drive. For numbers that don't conform to the 90% solution, nothing is stopping people from doing static modexes and applying "blank" to the dynamic modexes in the description.lua files. It's no worse than what we have now, just a few more lines to put in the desc.lua. EDIT: another solution could be to put a big block as a decal on the fuselage, tail and wings, then put the entire modex (whatever size or font you want) as a decal. It wouldn't be a dynamic modex, but you could have a whole squadron of aircraft with one or two skins and decals. Same with canopies and BuNos

Shout out for VF-142!

2.61 Hotfix 1 is out. Change Log: AV-8B: Converted Airbrake to analog momentary Mosquito: Set /I for toggling SnapViews and /O for momentary Mi-24: Fixed Kneeboard and NVG mapping on LMFD. Updated keybindings: AV-8B, Mosquito, Mi-24

Congrats on the new PC! Device Analyzer can be very prickly, so if you can find a configuration where you can see your devices, be sure to set a restore point or backup your system! As far as the CTS script goes, I need to know which profile (i.e. aircraft) you're using. I know V and C are used for the Tomcat, and you need to hold S3+China Hat Long to cycle the gear (Short will only cycle wing sweep).

As Montrose specified, we usually have people on quite a bit, especially on evenings and weekends. We do training on a weeknight (depending on airframe) and we try to do a formal event on Saturdays at 8pm Eastern. But we usually have people on our server all weekend regardless of formality.