sLYFa

Guys can you please look into this? I've had this bug now everytime I got "delayed" when spawning on the SC. I'm not able to reproduce unfortunately since I can't get behind the SC's respawn delay logic. Really messes up squad missions when the deck is populated

No. Believe it or not, F-14Ds did not have PTIDs initially, but the good old "fishbowl". PTIDs were only procured for B aircraft and eventually found their way into A and D models also. It was only after enough A/B airframes got retired that the whole D fleet got equipped with PTIDs

I've also found them very disappointing. Maybe it has to do something with burst altitude but I don't think there is setting for that(or is there?) I remember them being quite effective though in LOMAC.

I hope they also do something about the TTI indicator. Right now, the time is way off especially for medium/long shots. So by the time the TTI hits 15 the target is already destroyed or the missile has went several miles behind it.

They're already there in the B.

+1

Intersting find. I also noticed that TTI is way too high most of the time. I sometimes get the missile hitting the target with 40s on left on the TTI counter(45nm mid altitude TWS shot). Sometimes the difference between projected and actual impact time is less but TTI is always too high in my experience. Is this realistic or will this change someday?

Cheers to that! Hope you don't retire from virtual flying though :)

The RWR can be displayed on the HSD by putting the HSD switch into ECM. Not sure what the ECM switch to the right of the mode switch does though.

The ACLS needles got better but they are still off. You should be intercepting the glidepath at 3nm when flying at 1200ft. With ACLS needles however, glidepath is crossed at 4nm and 1200ft, meaning the ACLS provided glidepath is a little too shallow.

The A is also approx. 1500lbs lighter then the B. So if you care about not taking more ordenance than you can recover without exceeding maximum trap weight, the A will give you a little more payload.

This: It doesn't matter what sensors you have in your aircraft if you have to focus on flying/shooting. Also keep in mind that the pilot does not have the periscope sight. Even if he did (like in the Ka-50), using it while flying NOE is suicide. I know, I translated it myself :)

"Ми-28 с двумя лётчиками, идя на предельно малой высоте – 5–10 метров, отыскал все цели, не будучи обнаруженным, а значит, сбитым средствами ПВО. А вот лётчик Ка-50, летая значительно выше, сумел найти лишь две цели, зато сам был обнаружен, едва взлетев. Выводы делайте сами…" Translate: "The Mi-28, having two crew members, flew at an extremely low altitude of 5-10 meters, finding all of the 25 targets without being dectected (and thus not being engaged) by air defenses. The Ka-50 pilot, flying substantially higher, was only able to make out two of the 25 targets while being detected by air defenses early on. You can draw the conclusion yourself..." Sounds rather critical to me. Although its arguable whether the typical attack helo mission involves flying below 5m in search of targets. Personally, I would very much like to have at least an AI looking for targets and warning me of incoming missiles/AAA. SA was always a problem in the Ka-50 (at least for me), especially when heads down aiming with the Shkval.

I've had this issue too. Jester definitely switches to RWS in this case as all track disappear. Had this issue a couple of times. I suspect its related to changing radar modes/going STT while still having a PH in flight. If I don't touch the radar while the TTI counter is still above zero, I don't get any issues. If I get impatient and go STT on a bogey before the PH has hit him or the timer ran out, I get issues (can't change mode or go STT, Jester will go RWS from TWS right after PH launch).

Whats your point? I'm not questioning his authority on the matter, as he appears to know what he is talking about. I'm also not discussing the Mig-29 FM accuracy, I merely added a follow up on his rather bad review on the DCS Mig-29, in which he revises his negative first impression and argues how normal flightsim hardware can make a plane "feel" wrong although the flightmodel itself is probably spot on. Regarding to landing "in accordance with manual parameters", I can assure you that keeping proper glidpath and airspeed is very much doable after a few hours of practice, but again, GIVEN you have the appropriate hardware.

Good news for the CV(N) people!

The fact that you need above 80% rpm to keep the jet rolling also does indicate some exegarrated friction.

Thats not the whole truth. In a later post, he said that these discrepancies are a result of flight sim hardware not being able to replicate the feel real life Mig-29 flight controls, both in deflection and force. FWIW I have no problems landing the Mig-29 owed to my stick extension and heavy spring set. But I see how people with lower grade hardware (presumably like the guy who wrote the post) have lots of difficulties, as the Mig-29 is insanely sensitive in pitch.

Some more findings from my side: If you spawn in a running jet, the AoA indexer will work with the light test. If you however spawn cold and dark, the AoA indexer will remain dark during light test (see screenshot).

IMO flying the turn properly and getting yourself a good start is harder than flying the ball.

I've had this bug yesterday for the first time, so still not sure how to reproduce it. For what its worth, it only occured during the second sorite, i.e. after landing and rearming at the carrier. First sortie was OK.

I thought so too initially but then I tested at night where they should be definitely visible.

I think that depends a lot on ambient conditions (pressure, temperature). I heard that Hinds sometimes struggled to maintain hover out of ground effect when fully loaded in Afghanistan.

As the titles says, performing the lights test with the master test switch does not light up the AoA indexer lights. IIRC it used to work up until the interior lighting overhaul.

What speed are you flying at? If you are in the transsonic range (Mach 0.9-1.2), aircraft will vibrate even in level flight.