captain_dalan

Good stuff! You're ahead of me then. Though i can hang with Hornets and on occasion even with M2K's at low speeds ("old age and treachery...."), i'm from from consistent, even against myself (like in aerobatics). Too often (about once in 4 or 5 attempts) i find myself with wings wiggling when very slow. I think i has more then a little to do with my turn coordination, or better said, lack if it. But then, i don't have rudders and use a rocker pedal to rudder.

Yep, it's set. That's ok mate, much appreciated!

To this i would add, it also depends on how YOU fight. On paper, there's enough authority in the pitch to go one circle against most planes present in DCS. But, can you actually maintain control at very low airspeeds? If you can, then you can use it as a one circle fighter. Even against Hornets. Against Mirages.....not so much, at least not it my DCS experience. You are better off going up then. But that's like 1 plane out of what, half a dozen full fidelity modules? As for energy VS angles, IMO EVERY fight is an energy fight, that is, managing your energy is a key skill in deciding if you should turn or climb.....and when. You need to know how your aircraft behaves along the entire envelope to know when one is applied and when the other, or better said, when is one preferred over the other. And it is here that the A and B wildly deffer. A turning fight, be it one or two circle, is by no means an STR fight. Bleeding and unloading play a bigger role then STR, if properly applied. My 2 cents......

I just can't tell. I've called the ball anywhere from 1.0 to 0.5 NM and get the [BC] regardless of distance. But if it's bugged......

Like our colleague above mentioned, no curves at all! It's the only way to go. And don't yank the stick without a good cause.....

Ah, thanks guys! I thought i was doing something wrong!

Hmmm...... i must be doing something wrong then, as from time to time, i do get the (BC) notification in the grade

My pleasure. Do write how it works out for you.

That is a very weird gun track

I usually test every patch in the same mission, so minimum variables change, either one of my own training missions or one provided by the developer. In this case the Persian Gulf BVR mission is a good start. You start far enough from the MiGs and with altitude to spare. I start by cranking left or right, plugging a full burner (in the A), trying to get the bogies (at this point they are still bogies) 20-30 degrees to either side and i descent into a shallow dive to some 3-5000ft bellow them. I think they start at angels 19 or something. As the range closes and my knots increase, i go nose level and crank (gently) into the targets (i usually start this 37-40NM away), reset the radar and wait for Jester to sort them. Once they are confirmed hostile (by this time i am almost nose pointed at them) i launch and continue the crank to the opposite 20-30 degrees. If a track is lost along the way i launch again. In this particular mission, i usually get around a 50% kill rate with this method. STT...... 0%. I've never hit an AI with an STT fired Phoenix.

Curious. In SP (the only time when i tried an STT shot) the TWS shots work or don't (essentially a die roll), but STT shots never work. Try launching from inside 40Nm and from a mach1+ platform.

SP or MP?

My next question would have been if the asymmetrical air flow would cause a compressor stall or worse. I have caused partial not fully developed stall on several situations when i introduced enough sideslip during hard aggressive ACM.

Hey lads, i never really payed too much attention to the LSO grading as i didn't consider myself to be that good at trapping before. However, a couple of weekends ago i started working on my CASE I's, and i can't seam to get the aspects of the ball calls quite right. We are supposed to call it wings level, behind the boat, 3/4 to 1 NM from the deck, as soon as we spot it right? But, what if we bank afterwards? Is the ball call nullified? Or what if we we sink/float bellow/above the glide path? Do we lose the ball call then? Does it have to made again? Can it be made again? Do the wings need to be completely level when we make the call? Does the comm menu need to be open? I have the ball call command assigned to a button BTW. For some reason, i often get the (BC) in the grade, as if i hadn't made the call at all. Could it be a matter of comms procedure? Am i omitting some step? I usually go: 1. Request inbound, wait for the pilot to acknowledge bearing and instructions; 2. See you at 10 within 10NM; 3. Wait for report to tower and tower to declare Charlie as automated steps; 4. Leave the holding pattern and go behind the boat 3-5NM 5. Start the upwind-downwind approach 6. finale break and enter the groove 7. call the ball and fly the ball Thanks in advance for tall the hints and corrections. Mastering this is a real joy! Happy flying and a lovely weekend everyone!

That would be great mate! Looking forward to it, thanks!

Thanks mate, i owe you one!

Nobody has any info? Oh well, a new SSD it is then....

Will this coincide with the clouds?

Hey guys, i had to uninstall the Syria map due to lack of SSD space on my gaming drive, but i'd like to reproduce this mission on some other map for training purposes (i have a friend new to DCS who might need some theoretical guidelines before engaging in PvP). So if not too much of a bother, can one check it out in mission editor and post both plane's configurations here? Thanks in advance! P.S. i think i remember the F-14 had two bags and 12-13000pds of fuel. I may be wrong though. The F-15 was clean, but i have no idea of its fuel state. I also can't for the life of me remember the starting altitude and airspeed!

Wait, does that issue occur even offline in SP?

Yeah. But on occasion i don't get neither tacan nor ILS ranging. It's completely random. Just restart the mission a few times. Sometimes switching tonav-to-landing->ILS or nav-to-landing->tacan will work, other times it won't. Wacky.....

Here's the mission. It happens on other missions too, but this is the one i usually use for training. And yeah, it's in the A. Haven't trapped in the B in .......well.....ages. F-14APG_case_1_supercarrier Black Lions.miz

Quick update. Did some tests this afternoon. Same custom made landing mission, adapted from the instant action. The issue seams completely random. Step one, start mission. Switch to landing mode. Switch to AWL, range shows. Quit mission. Step two, restart mission, repeat procedure, range doesn't show. Quit mission. Step tree, Restart mission, repeat procedure, range may show, or may not. Same goes for Tacan range BTW. If range shows on AWL, it will on Tacan and the other way around. And there does seam to be a no ball call, when the range isn't there. But seeing how ball calls seam to register extremely inconsistently, i can't tell for sure.

This has been running through my mind for some time, but it never really came to me to ask the question when browsing the forums. Namely, with a valid ISL data stream, when clicking on the Awl/Pcd, the TID repeater shows data on the source (in this case carrier) position relative to the plane, as well as range. On top of that we get ILS needles on the hud and the VDI. But, sometimes, the range of the carrier doesn't show on the TID. And i can't seam to figure out why. I tend to follow the same procedure when approaching the carrier. Requesting inbound, see you at 10 when close, waiting for signal is Charlie, then going behind the carrier and starting the landing procedure. The needles are always there, but the range is sometimes not there. There seams to be a correlation between this and a lack of kiss off and call the ball options in the comms menu. Even when i do call the ball, i still get the no ball call (BC) in the LSO grade. So......am i missing some crucial step? Something obvious?

Give that man a medal guys, the heat death of the universe won't stop his persistence