Home Fries

I know I'm late to the party here, but I've been so busy at work and my free moments have been building the TARGET profile and training dudes up on the LANTIRN system. That said, I had very high expectations for this module and you guys have exceeded them! We've been waiting for a good Tomcat since Fleet Defender, and not only have I been satisfied with everything I've seen, I'm still getting surprised by things I haven't seen before! You have raised the bar not only for DCS, but for combat simming as a whole. Oh, and the soundtrack does take this up to eleven!

You can turn off "CommState Allow" in the CTS Communications menu under the Values tab. You can also disable CommState on the fly pressing SYM Down on the RMFD when in the profile hotswap mode.

Version 2.31 is released, along with the Mighty Tomcat! For those of you who use MFD4CTS (aka MFDisplay), the F-14 update for MFD4CTS is forthcoming. In the meantime, to take advantage of the new features (most notably the changing of graphics when cycling cockpits), go to the mfdsettings.config using a text editor like Notepad++ and replace this line: <add moduleName="F-14" displayName="F-14B Tomcat" filename="F-14\DCS F14 MFD.jpg" /> with the following lines: <add moduleName="F-14P" displayName="F-14 Tomcat (Pilot)" filename="F-14\DCS F14Plt MFD.jpg" /> <add moduleName="F-14R" displayName="F-14 Tomcat (RIO)" filename="F-14\DCS F14RIO MFD.jpg" /> <add moduleName="F-14PHV" displayName="F-14 HiVis (Pilot)" filename="_High Contrast MFDs\DCS F14Plt MFD HiVis.jpg" /> <add moduleName="F-14RHV" displayName="F-14 HiVis (RIO)" filename="_High Contrast MFDs\DCS F14RIO MFD HiVis.jpg" />

Hi Fellas, I will put those issues in the bugtracker and address them in due time. Right now, I'm swamped at work (and it will be even more intense over the next three weeks), and every minute of my free time is dedicated to coding (alright, and testing :D ) the F-14 profile. The 2.31 release with a working Tomcat should be out very shortly with improvements to follow. :thumbup: At that point, I can split my time with the other bugs. @Cypher, I didn't notice any changes in the AV-8B controller lua files. Can you actuate the controls in the Options menu and just not in game?

It should already be compatible with the latest OpenBeta; the db_countries.lua hasn't been updated since before the Tomcat came out. And VF squadrons have been in the mod since day 1. :thumbup:

Never!

https://forums.eagle.ru/showthread.php?t=115538

Thanks, Neph. I've been spending so much time in the RIO pit i didn't even notice that switch (or thought it was RIO functionality with the exception of PLM). I'll add that to H3 in lieu of the display swapping.

I have a Cougar on my desk as well as a Warthog, so I do have the second stick for the RIO and it works well. Of note: if your spare stick doesn't have a 2-stage trigger, you will want to apply a modifier for the second trigger pull (to designate the target).

I'm looking to implement an alternative profile swap system that doesn't rely on MFDs (but MFDs will still be primary if you have them). Once I start developing and testing that I'll definitely drop you a line!

Oh, man, that sounds like a doosie! :doh: Here's a question: rather than restarting the profile, do you have satisfactory results by selecting a different module (e.g. F/A-18 ), starting that profile, then reselecting the Ka-50? If this works, this is a much more convenient workaround than restarting the profile, and it also helps to narrow down the source of the bug. If it doesn't work, at least it helps to narrow down the source of the bug. I'm knee deep in the Tomcat profile right now in the scarce moments I'm not working, but I will investigate once I have a Tomcat profile out. And for the Tomcat fans: :joystick::joystick: I'm hard at work on the profile, and I hope to have a releasable update next week. However, programming both the Pilot and RIO seats in the same profile has proven to be a bigger challenge than even the C-101 (which uses different mappings for the same front and back seat functions). This is because the HOTAS and MFD buttons map to fundamentally different functions, and some things (like Jester) require modifications to existing global routines. The Tomcat profile will need a closed beta test to make sure there are no showstopper bugs that break other modules, and then I will get a WIP framework out so you guys can enjoy the Tomcat now with features and smoothing to follow later. The HOTAS functionality for the Pilot is very similar to the default, though I have moved wing sweep to the China Hat (fwd/aft for moving the wings, S3+fwd/aft for Auto/Bomb modes respectively). Here's how the MFD functionality is grouped for the pilot: LMFD: ACM Panel top row, Autopilot/SAS bottom row. Left/right TBD. RMFD: Display mode left column, Steer Command bottom row, rocker switches toggle HUD/VDI/HSD modes. The RIO routine is a bit more fleshed out (as befits my real-world NFO background :D ). Here are the MFD mappings: LMFD: CAP console (left/right buttons and bottom row for modes). Top row has weapons employment, TCS/LANTIRN, and TACAN Command buttons. RMFD: DDD and TID. Top row is DDD Range, columns are radar modes, and bottom row are the TID buttons for screen display. The rocker switches cycle the TID modes, range, and waypoints, and the top row of rockers (including the LSYM) operate the Lobe, Aspect, and Vc switches on the DDD. Another feature I'm proud of is the LANTIRN mapping at the RIO station. The Warthog stick defaults to the HCU, but if you switch the laser to arm (APU on the Warthog Throttle) it remaps the stick to the LANTIRN functionality. APU off remaps the stick to the HCU again. This feature can be optionally disabled if you already have a secondary stick you use for LANTIRN. My desire is to get this profile out ASAP with no showstopper bugs, then continue to refine the profile (adding features and fixing less-critical bugs). My real life means I'm not in a position to make promises, but I've been waiting for a good Tomcat sim for over 25 years (since Fleet Defender came out) and I have every intention of making a product I want to use, then sharing it with all of you.

I've already cleared my schedule after 12:00 Eastern on Wednesday. :joystick:

I’ll start work on Wednesday. I already have ideas, but I need to see how the buttons are coded before I can start mappings and algorithms.

Thanks, Uboats! Great find.

Hi Dusty, I just need some information: First, did you install using the compact, full, or JSGME option? If Compact: Is your Saved Games folder in the default location (e.g. c:\Users\Username\Saved Games)? Did you allow the autoexec.cfg in the installer to overwrite your existing autoexec? If not, did you manually copy over the parameters to your existing autoexec? The installer was built before the OpenBeta became the de facto primary DCS build, and the textures are installed in Saved Games\DCS. If you only use OpenBeta, did you allow the Saved Games\DCS folder to be created? Also, are you viewing textures in DCS itself, or using the Model Viewer (which currently has issues)?

Any updates on MV2? Pretty soon we'll have some Tomcats that need skinning! :joystick:

Version 2.30 is available. Change Log: Updated station switching for multi-crew aircraft to be more consistent between VR and non-VR platforms. Removed need to double-tap H1L/R to cycle seat controls in UH-1 and Mi-8. Applied playing of Gear Up/Down wav files if Number of Thrustmaster MFDs is set to 0. F/A-18C: Added Station Select Switch Push to S3+H3. Cougar H2D replaced Cage/Uncage with RAID/FOV Cycle. AWACS: Allows LotATC 1.2.0+ Bullseye Reference and Range Ring hotkeys to be modified in CTS Settings.

If you know anybody at HB I’ll happily take my release early in order to get started!

I’ll have a MiG profile once I get the MiG. Right now the Tomcat gets priority. [emoji869]

Did you rebuild the profile after updating to 2.29a? I have Eng_Start_FC3 in my tmc file.

One would think that with the new non-star force DRM this would be possible to implement by just having the server ping the mothership. This would likely bring more people into getting the campaign after getting a sample in multiplayer. +1

I always thought it was the Hawaiian good luck sign! :D

I was reading that novel in November and thinking "this would be an awesome campaign." Glad you're the one taking point, BD!

Yes, this is in the next version. In the meantime, go to the DCS Options menu and just map the H3U/D/L/R key commands (not joystick commands) with JoyBtn30 modifier to the sensor select depress. This way S3+H3U/D/L/R will depress the button. For cougar users, just map JoyBtn30 and H3L/R.

TARGET only allows for two MFDs to be programmed, but the profile does incorporate the third MFD as a separate controller for the Hornet and the NS430.