Home Fries

+1. While this would require tweaking of missions, you could do this with a Tomcat without any modification.

Tried this and still have the same issues. The only difference now is that the PTT page actually shows Easy Comms Off. EDIT: I'm a Windows 7 holdout. Could this be a factor?

Interesting. When I doubletap it gives me the same seat again, which is because it's a global routine that's also used for helicopters with 4 stations. S3+H1L/R Long is what allows me to change seats. Based on your hardware in your signature, I assume you're using TrackIR and not VR, right? Are you able to run the hornet in DCS without using the TARGET script? This may help narrow down whether it's a hardware or software issue (versus a script or config issue). EDIT: Re-reading your comment, I interpret that as the throttle acting up without TARGET, with TARGET, and with CTS. Not sure what the answer is for that, except maybe a driver issue that doesn't exist for Win7.

Hollywood, I'm having issues similar to what Ghost Recon Dad is experiencing. I have VAICOM Pro and both the Chatter Pack and AI RIO, all three are the latest versions (and VA is 1.7.5), and all three are verified as licensed. I have reinstalled the DLLs, cleared the config folder, rebuilt the LUA files, and reset the keywords. I have VAICOM set to import aircraft, easy comms off (though it indicates easy comms on on the PTT radio display), and SRS PTT Enabled. VA is running as administrator. Here is what I still experience: I can get the "standard" AI RIO commands to work, such as "go angels 25" and "heading north", but I cannot get the expanded commands such as "link tune xx.x" to work. I get the note that but immediately following I get the note Incidentally, I also cannot get the chat to toggle, nor can I activate Hot Mic for AI RIO (even selected it requires PTT to work). I'm at my wit's end, and any advice would be appreciated.

Then assign a button on your stick or throttle. If you don't want to hold it down, make it a "switch" instead of a modifier, which turns it into a toggle function.

Looks like the script still thinks you're in the pilot seat. The commands you listed are for commanding the ground air on/off. You need to switch to RIO using S3+H1L Long to remap the controls to the RIO seat. You can then use S3+H1R Long to go back to the pilot seat. Incidentally, you can also remove the communications function keys in the pilot profile by setting "APU Switch Engine Start Functionality" to 0.

Ok, now I see from where the confusion originates. The CAG and DCAG are Captains (O-6, like a Colonel in the Air Force) that are post-command (i.e. they have already commanded squadrons). The CVW is a "Major Command", and the CAG is equivalent to the CO of the aircraft carrier (the term "Super-CAG" was originated a while back once this distinction was made, as CAG used to be subordinate to the carrier CO). The CAG and DCAG are selected specifically as carrier air wing commanders, with the DCAG becoming CAG once the original CAG rotates out of his billet, and a new DCAG coming onboard to learn the ropes from the new CAG.

Glad to hear TriggerZoom is fixed. For the rest, please check PM. :thumbup:

Al Bhundee Returns! :beer:

Hi Mower, If you don't want to use TARGET, you can just use my graphics as inspiration for mapping. For the LANTIRN (RIO settings), I recommend setting the dogfight switch as a modifier, then assigning the LANTIRN commands to the stick while the modifier is active. This means that you assign dogfight forward (Joy_Btn26) as your modifier, then remap all of the LANTIRN functions to your hat switches (make sure you apply Joy_Btn26 as part of the combination so you don't overwrite other controls). This way, whenever you push the dogfight switch forward, your stick will act as LANTIRN and when you move the switch back to center, the stick will act as the HCU. @Dudikoff, thanks for the props! :thumbup:

All we are doing now is getting pedantic about a colloquialism. The birds are still referred to as "CAG Birds" in conversation, regardless of whether the CAG flies them. Case in point, if the CAG is a NFO (think RIO/WSO instead of pilot), he won't be able to fly helos or C/E model Hornets, but his name will still be on the side of those planes and the squadrons will still refer to them as "CAG birds."

The official term now is CVW for Carrier (CV) Air Wing (W), but "CAG" is an expression steeped in tradition. The US Navy is nothing if not traditional. The Air Wing commander is still personally referred to as "CAG" and his deputy as "DCAG." I clarified this because you asked about multiple birds for a single CAG. Again, steeped in tradition.

Also, just because a bird has the CAG and DCAG names on the canopy doesn't mean that they're the CAG's personal birds. Similarly, CO birds are not only flown by the CO. All birds in a squadron can be flown by any aviator, and it all depends on which birds are "up" and what the flight schedule requires.

The key is assertive crew coordination. There are times to ask questions and times to be directive. Those times aren't set in stone, but depend on with whom you fly and your comfort level with them. A pilot should always announce when he's taking the radar. Otherwise, a RIO going into super search can ruin a pilot's track. Similarly, a pilot should announce when he no longer needs the radar, either because the target is splashed or he lost lock and can't get it back. Similarly, if a pilot takes the radar, the RIO should go to the ATTK display so he gets a repeater of the STT symbology. However, if the RIO goes to TCS mode (which is normal in WVR combat), the only way to know if the lock is broken is to look at the DDD, and even then it's quicker and better for the pilot to tell the RIO so he doesn't have to interpret the DDD. If I'm RIO and I notice that the bandit is splashed, unless we're still in WVR with tally on multiple bandits I notify the pilot that I'm taking the radar. At that point, he can be directive with me if he wants to keep the radar. If a pilot is maneuvering and isn't specifying what he's doing with the radar (or if I see us still in TWS), I'll tell the pilot that I'm giving him VSL High unless he wants VSL Low. Then all he needs to do is put his lift vector on the bandit. Sometimes the pilots are too busy maneuvering to think about the radar, and this is where a good RIO can help in WVR. Finally, if a bandit breaks 10nm, I'll notify the pilot to go to ACM mode and have him start thinking about taking the radar. The closer the bandit is and the more vertical displacement that exists between the F-14 and the bandit, the more difficult it will be to get the bandit on radar from the back seat. Times like this I'll recommend VSL high, then be more directive as we approach 5nm. Hope this helps.

If you have the Phoenix, you'll shoot it against a BVR capable aircraft even if it isn't a bomber. A $1M missile is wasted just as easily if it is left on the rail when the Tomcat is splashed in BVR.

CTS 2.33 is now available. It fixes the issue with resetting the Ka-50 after ejection, makes improvements to the Tomcat profile, and makes the AJS-37 Viggen compatible with the Openbeta. I normally try to time my releases alongside DCS Stable releases, but in this case I didn't want to hold back the features any longer. If you run the DCS Stable release and FunkyFranky's keybinding mod, don't update the version included in this pack until the latest beta is released as stable. Similarly, stable release users may need to remap the Tomcat ICS/UHF mic switches by hand since the new version uses SRS Only/No Menu variants only available in the Openbeta.

I just tested using your config file and was able to center trim with no issues. I also compared your file with the one I use for a primary test platform, and I didn't notice any major differences in configuration. I'm not sure what the issue is. Your TriggerZoom datapoint is also interesting, but I'm not sure what the connection is, if any. I'm putting the bug report on hold; in the meantime I would just use Control+t. :(

If you have to do AAR, it might as well be the Hornet, i.e. the easiest aircraft to tank. Thing is that once you get the sight picture down, it doesn't matter if the tanker enters a turn. I've found myself on the basket just holding position, and I didn't even realize I went into a turn until I glanced at the pitch lines on my HUD.

Yeah, the crud was something fierce this year. +1 on a speedy recovery. :thumbup:

Please upload a copy of your DCS World.tmc file so that I can test with your configuration.

Can't disagree with either of these for the long term. I would love a -33 for the A and a -68 for the B. I just asked for something that could be handled in the immediate timeframe.

Right now, we can have separate helmets for the pilot and RIO on a skin, but I would like to be able to take it a step further and have separate allowable textures for both the flightsuit and head/face. People who don't care could use the same texture for both (like with the helmets right now), but I would like being able to customize the flightsuits to include individual patches and nametags (as well as pilot vs. NFO wings). Obviously not a dealbreaker, but a request nevertheless.

There is a countermeasures panel on the right side of the RIO cockpit with two spring-loaded three-position switches for releasing chaff and flares. Forward releases the applicable program (which can be set in the panel immediately aft of this panel), and aft releases a single chaff packet or flare. These can (and should) be mapped to a controller. Since the functionality of the hat switches by the handle are incomplete (jammer packages aren't modeled), the chaff/flare mappings are all you need and you could map an existing hat switch to dispense chaff/flare program/single. If you have a Warthog Throttle, I recommend the Coolie switch for this functionality. Regarding the pilot, there is a three-position flare switch set to mult, norm, and pilot. setting this switch to Pilot means that when the pilot pushes the DLC button he will release flares. If the switch is in any other position, DLC will release chaff. For my Warthog Throttle, I have this mapped to the pinky switch on the left side of the throttle.

FYI the velcro is there to attach a strobe so SAR can see you while you're treading water. The velcro will be on every white helmet, and is also in the normal and roughmet textures. Your best bet is to work around it.

When I say "cringe" I mean it in the best possible way. You guys have the right amount of camp to make it work! :thumbup: