Caesar

Any chance you can 7zip the .ini's from one of the planes that is giving you trouble? I'd like to check them against my files, because I have no idea what is causing this much trouble. Also, we had one other member loose expendable countermeasures before; it turned out he was missing four of the requisite folders. I don't know what caused that, but once replaced, they started working again. As for why your wingmen aren't attacking, that is beyond me, I can't recreate the problem.

The most current version of the F-14 Super Pack is v1.18, and there are two updates that were released in April - TMF F-14 Tomcat SP Update April 2012 in the Downloads/Aircraft section added the smooth wingsweep, changed the flight model a bit, loadouts and a few other things, then Avionics Update April 2012 (v1.1) in the Downloads/Cockpits section, which added the properly functioning VDI, functional TWS/multi-target engagement and general F-14 avionics by utilizing the AvionicsF14A.dll file. That version overall has one bug in F-14D_96's loadout where I assigned the Phoenix to the wrong stations by default in AirtoAir'96 (can be changed easy enough). We're hoping to release a new update this month which will use an FM based on but not identical to the ThirdWire F-14, add an F-14A_96, and fix the HSI wheel, among other things. It is hoped that this will all be combined into F-14 SP v1.19, the main reason for releasing a stand-alone update is so all those who already have the Super Pack won't have to download the whole file again. Until this is released, my best recommendation is to start with v1.18 and apply the two April 2012 patches. This will give you the radar/weapon functionality, smooth sweep, VDI, HUD with functional Vc, altitude and approach configurations, etc.

Okay, now I have to ask which version you're using, since we added the multi-target engagement, smooth wing animation, etc. back in April 2012, and haven't ever had problems with tasking wingmen to shoot at the player target.

You didn't happen to adjust the SpecificStationCode(s) in the countermeasures sections did you? The countermeasures are driven by a combination of the data.ini for the hardpoint and loading with the loadout.ini. This allowed us to make realistic loadouts depending on the mission the aircraft is flying (for TARPS, for example: Expanded Chaff Adapter with 120chaff and ALQ-167 jammer, and 60 flares in the ALE-29/39 instead of 30c/30f). An example from the loadout.ini - [AirToAir'82] StartDefaultDate=1982 DefaultFor=SWEEP,ESCORT Loadout[29].WeaponType=F14DDE <========That is your expendable countermeasures Loadout[29].Quantity=1 Loadout[11].WeaponType=AIM-54A Loadout[11].Quantity=1 ... In your weapons folder, you will see a folder F14DDE which is the 30 chaff/30 flare expendable countermeasures [WeaponData001] TypeName=F14DDE FullName=F-14 AN/ALE-29 ModelName= Mass=150.000000 Diameter=0.000000 Length=0.050000 SubsonicDragCoeff=0.000000 SupersonicDragCoeff=0.000000 AttachmentType=USN SpecificStationCode=D14 <================== Like the AIM-54, this has to match the data.ini's entry. ... Whose SSC links to the Data.ini - [DecoyDispenser] ReferenceName=AN/ALE-29/39 SystemType=WEAPON_STATION StationID=29 StationGroupID=0 StationType=EXTERNAL AttachmentPosition=0.0,0.0,0.0 LoadLimit=200.0 AllowedWeaponClass=EP SpecificStationCode=D14 <=============This dictates the specific station for the dispenser ... If any of the SpecificStationCodes were changed by accident, your related expendable countermeasures will disappear. Ensure all SCC's match up. The F-14 also has about 6 different countermeasure folders: F14DDE (30 chaff/30 flare), F14DDL (60 flares, for use with either ECA or Bol Chaff), LBDD (Left Bol Chaff - 1996 on), RBDD (Right Bol Chaff - 1996 on), ECA (Expanded Chaff Adapter for TARPS), and EFA (Expanded Flare Adapter). Ensure you still have these folders. The TCS camera is selected by pressing "]" (default) to cycle HSD modes in the F-14A_82 and all F-14B's, but is actually broken in the current iterations of the F-14D's and will be fixed with the next update that is currently being worked on (hopefully projecting in the VDI instead of the HSD, but that's proving kind of tricky at the moment, but progress is being made). The F-14A_74 does not have TCS. As it stands, the TCS is really just another forward looking camera repeating what you're seeing since it cannot be slaved to the radar in the TW series - at least not yet. TARPS is similar; it is just there for looks, you can't actually take pictures or see through its various cameras at this time. Assume your RIO has control over it as you fly over your target! Hope this helps.

We're working on a general update that will standardize all AIM-54's on the TMF F-14's. What you're going to want to do is change both your AIM-54's SpecificStationCode(s) to AIM54, and change the pylons in your F-14 Data.ini's from F14 to AIM54, but only do so on your Phoenix pylons (MissileStation1Ter, MissileStation2Ter, and PhoenixStation1-4), if you change all of the SCC's that list F14, you might loose LANTIRN, TARPS and the fuel tanks. So, on those stations, the SCC needs to match the AIM-54's SCC. The entry should read: SpecificStationCode=AIM54

Honestly, I noticed the opposite - the smaller, less powerful Soviet AA-8 air to air missiles (6.6lb warhead) would bag friendly and player aircraft every time compared to the AIM-9L and M (20lb warhead) which would regularly take 2 or more to down a single MiG-23 (I think I've had them take 3 before, which required closure for guns to finish them off), and were physically incapable of downing bomber and large interceptor aircraft - I've had Tu-128's eat 12 AIM-9's and not drop (my own, -2's and -3's, every one hit). That observation, however, is just that. I agree with StreakEagle 100% - All missiles should work based on how they are defined in their data.ini's, not based on "who" fired it.

Happy Birthday!

OK, gang, here's a general update. This is the still-beta version of the FM applied to all F-14's (A/B/D). Also includes changes to the jammers (dual mode). If you'd like to test, back up your data.ini's and copy over with the beta. Cockpit fix is not part of this (like what was stated, 2 weeks!) June 2012 Update.7z

HomeFries, Copy that, will start coordinating with the SP team to make that general update for F-14A/B/D. Romflyer, Yes, I did see that; I think the pit will wind up being updated, but IIRC that required a .max file update. Last I knew, the .max file has been sent to one of the cockpit gurus, so the update is a WIP. If it can be done with an .ini edit, it would be easy for me to do. Thanks for the feedback, folks!

What is it mapped to in your controls? You might need to reassign it.

I never ran into that issue before; normally if I have my AI F-14's using AIM-54's they'll ripple fire them at long range before switching to Sparrow. When did that start surfacing? I did notice you did a complete translation of the TW data; so I guess I should rename this test one as a "hybrid." The only surfaces I kept from the TMF Combined FM are the Flaps, Slats and Spoilers, and the aircraft handles similarly, slightly better roll rate, closer to the 180 deg/sec at cruise speed limited by Roll SAS without as much nose drop at slow speeds. Rudders, stabs, wings, fuselage, nose, etc. are from the TW bird. While tweaking I've been checking the charts and the F-14 never dips to a point where it can't reach/exceed its 6.5g limit in the high 4-low 500's KIAS like the TW bird (even at light weight, I've noticed with my beta FM using TW control surfaces it will drop to about 5.2 max g, which puts a real wrench in sustaining a 7g turn against an opponent!) Will keep experimenting with this. EDIT: Adjusted two values per stab in the CL0 Mach table to increase the stabs effectiveness at the affected region of flight; adds about 1.2g of authority at the "bottom" of that region, so you will be able to maintain at least a 7g pull in this region of the flight envelope.) The aircraft feels otherwise identical, it just doesn't droop below 6g at 5,000 feet with maximum available deflection at around .87-.92M. Check out if you'd like. F-14B_Trans.7z

That is a sexy pit. Keep up the good work, gents!

Huh, didn't know that, actually! EDIT: Will download and check out. EDIT 2: Checked out, doesn't seem to fully agree with the Super Pack (that is, some of the loadouts are changed and whatnot) so I am going to keep at tweaking this FM for potential release specifically for the SP. Thank you for bringing it to my attention though! Will check more on the stabs and departure characteristics in the near future...

Good Evening, ALCON, While reading the ThirdWire facebook page, I noticed a few people requesting an F-14B/D by ThirdWire. I doubt this is going to happen soon, if at all, however it got me to thinking, how would the ThirdWire flight model fare given F110-GE-400 engines? Rather than do a simple .ini edit, I wanted to see it on a proper model with a proper F-14B cockpit, loadout, etc. So, what I did was translated as much of the TW F-14's data.ini for the aerodynamic surfaces into a copy of the TMF F-14A+_87. Because all the parts do not directly translate (the TMF version has more definition for its flaps, spoilers, wings) I did my best to use everything that I could and found it actually handles fairly similarly to the TW Tomcat, but with the huge GE engines that give it better energy as they do in real life. The point of posting this? I'd like to share the results of my test with the community and check for feedback. As it stands, there are still some issues. The Stabilators loose a lot of authority at the low 500's of KIAS, and then rebuild later. The roll rate is atrocious without unlocking the spoilers (nowhere near the real-world 180-200+ deg/sec rate they could get. Spectre had increased the effectiveness of the TMF stabs which fixed this issue for the most part, but using the "vanilla" stabs, the same problem arose) so those have been unlocked at above .9M. The flaps and slats are the same as the TMF F-14 because of the extra definitions that I haven't worked out yet - they work well as they are with the TW FM to be frank. I have not been able to check this against the charts as of yet. Original sources for the FM are ThirdWire, Column5 and Spectre8750. This was based on the TMF F-14A+_87 from the Super Pack with both April 2012 avionics and FM updates (though the FM will be replaced, the other updates might affect gameplay). To install, copy your F-14A+_87 folder and re-name F-14B_Trans (for "Translation"). Drop the contents of F-14B_Trans.7z into the folder (will be an F-14B_Trans.ini and F-14BTrans_Data.ini). This concept was tested at May 2012 patch levels. Positives? Negatives? Death threats? Well, maybe not that. I'd like to hear it. F-14B_Trans.7z

Gotcha, Baby! (VF-74 pilot vs VF-101 student)

Best wishes to your dad, Dave.

Sounds like you downloaded one of the updates which doesn't include the aircraft. Check this one: http://combatace.com/topic/68044-tmf-f-14-tomcat-superpack/ That was the file with all the jets, which includes the Iranian Tomcat. Later files were updates to that baseline (avionics, cockpit, smooth wingsweep, etc. were added to the Tomcat Super Pack v1.18). I'd recommend checking that one out, should be in there.

The Tomcat Super Pack has an Iranian F-14 in it. File is F-14A_IR; haven't flown it much, so I don't recall all the skins for it, I know it has the standard desert camo, it might have the more modern blue scheme, but I can't remember off the top of my head.

Arthur, Just a note, the link you have to the TMF F-14's is for an update to the pack which doesn't include the airplane (that update was superseded by the basic Super Pack v1.18, and then the April avionics/FM stuff). The TMF Super Pack URL follows: http://combatace.com/files/file/12327-tmf-f-14-tomcat-superpack/

You can manually adjust the loadouts, switch the AIM-7E-2 to the F or M model if you wanted. I think the game knows to stay in family (if you do a mission prior to the introduction of the F/M), though it has been a bit since I've dealt with the SFP-1 series.

Actually, you might still have a problem. Sparrow didn't go out of service in the 1970's, nor did Phoenix leave service in the 1980's. Sparrow is still in service, and Phoenix didn't retire until 2005, one year before the Turkey left the decks - this is reflected in-game. What installs are you merging your aircraft/weapons into? What weapon packs are you using? Any other info you've got?

That's accurate, HF. When we added the functional VDI to the TMF Tomcat 'pit (ToS's work, actually) it required the new AvionicsF14A.dll to properly function. The way it is set up right now prevents the VDI from having any other functionality (TCS feedback, for example, is handled on the HSD rather than the VDI screen because of that limitation) - or we just couldn't figure it out, which is entirely possible. Like the modifications to the stock pit, too guys, good work!

That worked, Dave. So far, I have re-added the F-14, F-15 and F/A-18 effects with no crashes. Might take a bit to find the "bad" file.

Dave, which ships? Cargo, surface combatants, all?

I'm getting the "crash every time at 30%" problem, but that's on a heavily modded install. Will back up the folder and install over (semi) vanilla one and see what happens. EDIT: Yep, works on SF2:NA (few mods) - will have to investigate on what's breaking it.