Home Fries

Thanks for the catch. The MiG-15 has its own braking routine that I overlooked. This will be in the hotfix.

Sorry everybody. The F-14 Pilot LUA export for the Warthog got corrupted into a hot mess. Here's a new diff.lua until I can get the hotfix out. TARGET F14Plt WH v234a.diff.lua.zip

Most RIOs take personal pride in handling all radio comms, and feel shame if a pilot catches a radio call that they didn't hear or forgot about. There are some instances where a pilot talking makes more sense (e.g. 2v2 WVR fight), but a RIO is close enough to the tactical situation to make just about every call required. The division of comms, however, is highly crew-dependent. Some crews develop a synergy where the pilot and RIO have different responsibilities, but there's nothing set in stone. Each community is also different. In mine, pilots would handle ATC and NFOs would handle tactical comms.

Please upload your dcs_world.tmc file so I can try to duplicate the issues with your settngs.

I'm unable to duplicate the error. Have you updated to the latest F-14 Pilot and RIO lua files? Also, do you have VAICOM enabled? I'm assuming you're using VR. Is this correct? If so, do you have the hat trim function set to 0 or 1?

In the meantime, use one of your "special" waypoints for Bullseye. You can see it on your TID and make visual approximations. If you use one of the selectable waypoints (e.g. IP or FP) you can get your own bulls position by reading the tail of the arrow and the DME on the HSD Dest page.

Version 2.34 is available for download. You need DCS 2.5.5 for this version. This is a big changelog, as I've been holding off on releasing this until 2.5.5 made it to stable release. Note that if you were using the AJS37 Custom Controller LUA (aka Funkyfranky's mod), this is obsolete with the latest version of DCS (these edits are now part of the default Viggen lua). Changelog: Fixed VR Hat1 functionality for Cougar users. Added ability to select profiles on the fly without using MFDs (for VR users). SA342: Added VAICOM TX5/SRS Intercom to MSP (Warthog). Mi-8: Fixed station selection orientation on Hat1 MiG-21: Added option for context-sensitive weapon selector based on AA/AG Master Mode. AJS37: Converted Custom Controller LUA option to forced default and fixed light panel mappings for 2.5.5 update. P/TF-51: Changed landing gear from toggle function to discrete state actuation. A-4E: Revised mappings for A-4E Community Mod version 1.3.1. NS430: Compatibility with Chic's GPS Rotary Encoder Fix (Optional). AV-8B: Removed two SnapViews and replaced with TDC Action and Cage/Uncage on H2U/D (Warthog). Added Flashlight to RMFD. F-14 Changes (worthy of their own changelog :D ): Swapped ICS and TACAN Cmd buttons, moved Emergency Stores Jettison to OSB18 on Pilot LMFD. Added Air Source selection on Pilot RMFD (requires included Controller LUA mod). Fixed Walkman volume control on RIO RMFD. Added VAICOM Pro AI RIO support (updated VAICOM Pro Import file). Added dynamic CAP drum and FLIR overlays for RIO MFDs in MFDisplay. Added short TEMPO for DLC Toggle to prevent inadvertent toggling during use (Warthog H4P Only). Remapped RIO HCU Selector (Hat3) from default DirectX to a more intuitive orientation. Added two Instantaneous (held) RIO SnapViews to H3L/R Long. Added support for H0RN4T's LANTIRN Pilot mod. Added option to remap Boat Switch as Master Arm + ACM Mode (Warthog Only).

Concur with WindyTX. It's all about crew coordination. The pilot needs to be predictable so you can keep the targets within the TWS cone. If he doesn't have his HSD on TID repeater, he should so he can see what you're dealing with. You give him a heading, and you give him a crank direction after shooting your Phoenixes. The pilot also needs to understand that he will not see any HUD or VDI targeting indications in TWS. The TID repeater is all he gets. Finally, you mentioned that Stab is In. FWIW, Stab In/Out only applies to Pulse mode. All Doppler modes are automatically horizon-stabilized.

The installer will create both of those files you describe, but there is nothing in the registry. It is looking for ctsversion.txt at the html link in version.txt. If it doesn't find it or the files in its list you get the "Server Not Available" message. Has anything changed in your firewall (software or hardware) since you updated last? Also, is anybody else having trouble updating?

So it creates a new version.txt, but doesn't actually unzip any of the files or create any folders? Do you get a message that says "Server Not Available"?

Oh definitely! We played for 5+30 and totally lost track of time!

I assume that when you removed everything, you then tried to run ctsupdate.exe rather than re-installing using CTS_2_10_Installer.exe. If you reinstall to the same location with CTS_2_10_Installer, you should be fine. Alternatively, you can create the DB folder again, then create a text file called version.txt. Then insert the following line: http://blackveal.dlinkddns.com/MyWeb/TARGET/CTS/CTSversion.txt Then that should allow you to update from scratch.

You still use the DLC button to dispense countermeasures. The RIO selects whether chaff or flares are dispensed with DLC.

Not your bad. I jumped the gun after testing it in SP. [emoji31]

Here's my $.02 on the clickable cockpits: If you like keyboard shortcuts, that's great. I use shortcuts a lot myself. However, having a clickable cockpit means that you don't need to map or memorize an excessive number of shortcuts. You have the option of either using the shortcut or the mouse. I like to use shortcuts for commonly used items, or items that I want to be able to use by feel instead of having to look away. Second, getting used to a mouse with the left hand is a great idea. I use a Kensington ambidextrous trackball with a scroll ring. This is the only reasonably priced ambi or lefty trackball with a scrolling action that I've found. I keep the trackball behind my throttle, so I can easily use it while keeping my right hand on the stick. Finally, since the sale is going right now, I would pick up the Mirage 2000C module. This is a very good module to learn the clickable cockpit because 1) it has an outstanding autopilot that will let you play around the cockpit without having to worry about crashing, and 2) many of the switches are single use "set and forget," so you configure things the way you like and leave them in place.

Wait! So I jumped in the back seat in the SP Take Off instant action mission and was able to actuate both chaff and flares both with switches and keystrokes. The counter came down on both. Am I missing something, i.e. is this only a Multiplayer bug?

Chaff bug is fixed.

@Everyone, It has crossed my mind that supporting CTS with a single thread is inefficient, especially for people who want to search for issues that may have already been addressed. I have a public bugtracker in place, and when an issue is mentioned here I make every effort to add it to the bugtracker. Similarly, anybody (even those of you without a free Trello membership) can email your bugs directly to the bugtracker. However, people don't seem to use it nearly as often as I had hoped. This could mean that the script is that stable and bug-free, but I don't believe that for a minute. I am open to suggestions for ways to open things up. I could start a Discord channel and apply subcategories for each module, but we would still have a linear discussion thread and the ability to search may not be much better. I could start a Steam group and add a public forum. I can't start a poll because I burned that option a few years ago when this profile was in its infancy. So please sound off in the thread about what you recommend or would like to see.

Hollywood, I say this in the best possible way: your success with VAICOM Pro has apparently outgrown your support model. In short, your dedication to supporting VAICOM Pro is outstanding, but a single thread approaching 300 pages is unwieldy for search purposes. Have you contacted the moderators about giving you a sub-category? That would allow people to start threads about individual issues, which also makes for more efficient searching for people with similar issues. @Moderators, please give this man a sub-category!

The black arrow to which you refer is for names on the canopy rail. I opt not to do names on my public skins so you can use them multiple times without loss of immersion (not much I can do about the BuNo on the tail though).

Submitted for approval.

Thanks, Apache600. We gave it a go last night. Started with 5 aircraft and shortly wound up with 3 (1 tomcat and 2 hornets) due to people dropping-off. We were still able to bag the targets and convoy at WP1, bag the HQ and vehicles at WP2, but with the Tomcat in an A/G role we didn't have the people to fend off the Tu-22s. That's where the fourth aircraft would have been nice, I guess. We continued to press after that (neither of the Nimitz class carriers were hit), but it got difficult when the tomcat went A/A and the SA-2 was preventing us from pushing north to engage bandits. We had a great time, and I look forward to giving it another go. Hopefully we'll keep people online next time.

Thanks, Dustoff. That should be an easy enough fix.

Hi Apache600, We're looking to give Crack the Channel a go, and I was wondering how many planes and what types you recommend. Or is it scaled?

Yet you refer to the LANTIRN mod as a cheat, but the mod does not add any capability to the F-14. I have argued that this mod is a workaround, not a cheat. There is no advantage to having a single pilot control the LANTIRN over a Tomcat crewed by two humans. I fail to see how a pilot with a LANTIRN would have an unfair advantage in a PvP environment, unless of course you're flying a helo. You should really tone down the pejorative tone, as it only cheapens your argument. People fly DCS to have fun, and operational flying, while it has its great moments, is often a miserable grind. Trust me when I say you don't want realism. Fidelity, yes, but not realism. A workaround to enjoy oneself should not warrant comparisons to War Thunder or Air Quake.