Eagle7907

Ah, very good. This is what I was hoping to get. As to the technique IRL is yet to be determined, but this information does support the general understanding of it all. Thanks.

I asked the question, and all I got was use the G-meter. That’s pretty cut and dry if you ask me, but I was hoping to get an answer from someone who actually flew it and see if it was indeed a) real and complied, b) the technique taught, and if this was indeed something seriously limited then is our opponents (AI) just as limited by their own structural limits and is the damage simulated.

So this topic came up on Discord and I learned something new about this aircraft yet I’m blown away about this limitation. According to documents, the F-14 is limited to 6.5Gs. My question is how in the heck do you know you don’t exceed this limitation while dogfighting? IRL, was this limitation ever complied? If so, how in a close quarters fight? I’ve been taught “lose sight, lose fight” and watching a G meter will easily cause this as an issue. Also, does the AI comply with this limit as well?

Oh that?!? Hmmm. Okay. I wasn’t sure that was what it was referring to. Sent from my iPhone using Tapatalk Pro

I’m looking for someone who can answer what the “approach light” is on the Tomcat. A certain reliable manual mentions an approach light that functions bright when the master light switch is off and turns dim with the switch set to on. This manual isn’t very clear what or where this “approach light” is. I’d like input from a reliable source to cut out the hypotheticals. Thanks.

Said the same thing last April. Can’t really post the quote right now, but I said at the pace of things the E will be EA release in about 5-7 years. A certain inside RAZBAM person asked me how I came up with that. I then said, look at where it is now and how much more needs to be done. This module has been curbed so many times. Not completely at the fault of RAZBAM but just the bad luck of other changes and that happened like world 2.0 released, one developer picking up where another left off, etc. Sent from my iPhone using Tapatalk Pro

Transversely compared to the B, if using SC when taxiing over the shuttle for cat launch in the A takes less power. Sent from my iPhone using Tapatalk Pro

Oh okay, got it. Thanks!

I’m sure this has been answered before, and I’m sorry if this is redundant. Tapatalk doesn’t have search anymore and Wikipedia isn’t very clear. So here it goes. F-14A = TF30 engine F-14B = F110 engine What’s F-14A+? Is that a late A variant that had an engine swap to the F110? I know it’s an elementary question, but it’s eating my brain. Sent from my iPhone using Tapatalk Pro

Having a great time with A. It definitely has its own flight characteristics which in my view gives us two aircraft for the price of one. Great job! For some reason it’s satisfying to catapult full AB. IDK However, I’m just a bit disappointed with the B missing the appropriate engine gauges. Is there a time frame for that to be added? Sent from my iPhone using Tapatalk Pro

Oh, interesting. Does that apply to both models? Sent from my iPhone using Tapatalk Pro

Now that you mentioned it, I was using C. I just tried with Mk60s. Same result as yours. Thanks! Sent from my iPhone using Tapatalk Pro

Right, but what clock are you going by? The TTI clock or something else? Because if the TTI counter isn't right at launch, it won't be correct for pitbull or impact. That's why I'm saying to truly test if the missile does go pitbull 15 seconds before impact, then the only way to test is by using a stopwatch and viewing a replay on tacview. Is the jet coded to where the radar tells the missile to go pitbull, or is it just coded around the radar computation completely? IDK, maybe IronMike can answer that? From the looks of things it seems to be coded around it. How? Because the TTI calculation and -54 pitbull behavior are not in sync. Hence what you are getting at in your post above. I swear, I thought someone posted a bug report about this in the past. Anyways, we both agree on one thing, the AWG-9 indications are not correct. There is clearly an error in the TTI calculation, and therefore it doesn't give the player an accurate representation of when your missile does indeed turn pitbull. It seems closer to accurate when launched close, but the further away, the more inaccurate the timer gets, exponentially. However, my point is it doesn't necessarily mean the missile logic/behavior is 100% wrong. If it gets commanded to go pitbull roughly ~16 seconds before impact, and the missile reacts in such ways, then its correct, regardless of what TTI says. He's only asking about -54 behavior, not what the jet is showing you. Edit: I take back my statement, IronMike does mention specifically the 16s of TTI on the TID. If that's the case then yeah, there's still major problems with the radar computing TTI and commanding the missile to pitbull. Hmm, hopefully it will get sorted out soon.

Oh I agree with you. It's not right either and I get the same indication. I thought there was a bug post about this, but its being difficult for me since many use "TTI" for "Through the Inferno". LOL However, my understanding is this relates purely to missile behavior/tracking. The only way to really find out if its working correctly is by tacview and a stop watch.

Forgive me, but you're mentioning lots about the TTI and indications on the radar display. I think IronMike is talking about just the missile behaviors and that it tracks/doesn't track when it's supposed to. From what I understand, the TTI is still being refined and yet to be completed. Someone correct me if I'm wrong here.

Hey IronMike, Thanks for answering our questions. The team is doing great work and your communication is much better than other teams. Keep up the great strides. Looking forward to the great fun our beloved A will bring. (Did that sound weird?.....Nah!) Sent from my iPhone using Tapatalk Pro

My observations include engaging 2 Foxhounds. With jammer on (yes it keeps them from firing at great distance), I launch at them, one a piece, then crank to 45 angle because they shortly firing later, then go complete 90 because defensive, missiles lose track and miss. I’m very confident it was before the 15 second timer. Rinse and repeat, and I die. RIP Sent from my iPhone using Tapatalk Pro

Whoa!!!! Smashing news! What a great day. I noticed the digital engine display for the B wasn’t mentioned. Where is that on the priority list? Sent from my iPhone using Tapatalk Pro

Oh great news! I’m glad you got it sorted. That would make sense if the accuracy of the jet wasn’t tight, yeah it can throw off the releases as well. Good job! Sent from my iPhone using Tapatalk Pro

Ah I see. Hmm, I don’t know. I don’t really use 82 or 84s because they are inherently inaccurate. Rocks with the cluster seems to make up for that a bit in their coverage. But my experience with them have been mostly positive. Usually when I don’t get results is when I deliver outside the 20-30 degree dive, +400 knot profile. Sent from my iPhone using Tapatalk Pro

I always use CCIP for rocks. I don’t really like AUTO that much because it more time consuming for using it with them. However, I haven’t seen any accuracy problems with CCIP. How bad are you missing? Is it like tenths of a mile or less? Drifting? Sometimes winds can be very brutal and it will look like there is a problem. Sent from my iPhone using Tapatalk Pro

This I am not sure. All I know is -2 was in trail and then give him weapons free. I roll in for attack, drop one rockeye for a dual kill. Escape by circling climb for effects. Hear -2 say bombs away. See my kills. Then a carpet of bomblets way bigger/wider than what I did. I then roll out and fly away. The go to F2 view of -2 to see what the hell he dropped. He still had two rockeyes left. Wut? Sent from my iPhone using Tapatalk Pro

The C, penetrator (giggity), seems to work okay for me. However the A, cluster, seems to be having autopilot issues. I’ve set everything up the same as the C, but the A seems to pitch up at around 7k AGL and bank to either right or left 45 degrees and impact the ground, missing in its entirety. Sent from my iPhone using Tapatalk Pro

I agree with the above tips. 20-25 degree dive with speed above 400 knots does any single target a doable death. The softer the target and closer, the more probability to get multiple kills with one rock. In a side note, the other day I had AI -2 loaded with rockeyes as well for SEAD practice. Funny thing is when I released a single rockeye, it does the standard tight oval dispersion. But when -2 attacks, the rockeye dispersion was HUGE! It looked like he dropped all 4 in one pass, but he made several passes with rockeyes after, which to my elementary math says that doesn’t make sense. Any ideas? Sent from my iPhone using Tapatalk Pro

LSO communication For case 2 or 3, I see you didn’t mention “check in” or “platform”. I use those and have no issue. After “commencing” Marshall handoff to approach, you call “check in” then usually by the time he finishes you are already passed platform, then call “platform”. After that it’s either at 3/4 mile you see the ball “call ball” or not “Clara”. Anyways I don’t seem to have an issue. Sent from my iPhone using Tapatalk Pro