The_Tau

Idk if its a bug or HB have different source material but in number of NATOPS one for F-14A from 1970s NAVAIR 01-F14A-1 (1 June 1972) and F-14B NAVAIR 01-F14AAP-1 (PTID upgrade 1 AUGUST 2001) there is common information about internal lighting which is different from what we have in DCS It gives info about rotaries for instruments, console and formation lights going from 0-14 (0-1 turns lighting off/on) and not 1-9 like we have in DCS. Additionally "The INSTRUMENT thumbwheel also controls the intensity of the CAUTION ADVISORY panels and the digital data indicator lights, which consist of high and low-intensity lighting", which in DCS currently have fixed intensity, and are almost unreadable due to its brightness in the night operation On top of that F-14B NATOPS mention "Lighting for the pilot turn-and-slip indicator is controlled by the INSTRUMENT lighting thumbwheel" which currently in DCS is not light up at all which is a pain in CASE III procedure as its invisible in night unless flood light is on (which gives glare on canopy making much harder to see outside) Also Formation lights brightness can go to 14? Wink Wink make external lights brighter for night operations please?

I guess not, they were fixed brightness and colour

@bonesvf103 https://flyandwire.com/kneeboard-pack/ here is kneeboard pack

You can't. Isnt first screenshot from 1st post from F14A and second screenshot from F14B? F-14B EIG lines are always white you cant change that

In DCS that TTI blinking light its not 100% accurate of when missile goes active (aim54 C variant - A variant is works much closer like in RL). Also depends what target you shoot at. VS AI, bandit will know the missile is coming at him at 10nm no matter the position of target size. Its hard coded by ED in AI logic. VS people someone did tests and it also came out that no matter the position of target size the C variant of 54 will alert bandit RWR at 7ish NM. mk 60 motor burns for 20s and mk 47 motor burns 27 s. Its accurate, so I am not sure how you got 9s

Is it just me or BK90 is almost uselessly inaccurate? It always flies left or right of target waypoint. I thought its wrong at calculating wind as it seem BK90 drops into wind, overcompensating for it but there is something else at play here as well. I tried to mark target waypoint coords taking wind into consideration but there is something else at work here as well. Tacview-20230205-013432-DCS-Flashpoint_Levant_v1.9.4.4X_morning.zip.acmi Taking this tacview. Wind was like DCS 081 for 3m/s at 0ft (meteo wind from 261 )First 2 BK90s launched by me were supposed to drop at offset target waypoint taking only wind (green arrow) into consideration (Yellow X as M3). As you can see first 2 BK90 dropped north of target Only after I did BDA and moved M3 coords to Red X Bk90s landed directly on target. But what is the reason for this drift? I was forced to cheat to get those BDA so in RL settings it would be very hard and dangerous. TERNAV was on, was working (indication 5), drift was 0.

Thats my snack box!

TF30 at F14 introduction was always seen as "5 years tops" solution. Grumman knew TF30s were horrible choice but thats what Navy wanted and paid for. But they designed F-14 in a way that it was easy to do engine upgrade on it. Too bad USN waited 12 years to actually fund the thing though. If only USMC stick to original F-14 procurement plans...

Thats assuming Iraqi Signal Intelligence did its job and acquired AWG9/AIM54 radar signals for scan/track/lock to add to RWR threat library. It may only happened later in war, as Iran had a lot of 54 success early in war but later them and USN in '91 had much less glamorous track record ('91 Iraqis were running away as soon F14 radar was detected)

That is PAL (Pilot Automatic Lockon) it got range 15nm. VSL (Vertical scan lock), range 5nm, as name suggests scans up and down, not horizontally.

Please fix! Or give option to disable sun effects on it

But isn't most AA guns HE filed? I am pretty sure shrapnel from 20 or even 30mm HE explosion on canopy would do bad things to pilot

Bug seems only appear in the air. Light test on ground with dimming seem to work

Its in other skins as well. Also I think #4 Splinter F7 Skaraborgs Flygflottilj 76 is wrong. It uses F21 squadron number null

its VSL low

Found tacview file Tacview-20221124-200927-DCS-CVW-66_CRUISE_2_CHARIOT_D0E3.zip.acmi

Very interesting. However I had different experience with PDSTT 54C launch vs 2 AI bandits. I fired at Lead, who notches it at 10nm (no surprise there) and missile reacquires at wingman, who simply just fly straight and did not do any maneuvers even though missile was well within 10nm

They use a lot of missiles, but they work IDK, why they ignored low flying F15s... Its AESA radar isnt it? It should see everything in the same time? Tacview-20230125-211611-DCS-PATRIOT test.zip.acmiPATRIOT test.miz

If home on Jam would so good in RL then everyone would developed dedicated missiles for it wouldnt it? USA, French, British, Indian, Chinese, Israeli? And not just mythical R27P which from I recall never was actually used or even mounted on anything. Attacking E3s with their super powerful 360 degree coverage emissions is one thing but targeting small, self-defense fighter ECMs is very much different in RL. They have much less power and have limited coverage. Its very much DCSism that they are 360, noise barrage functionality. Besides how HoJ could calculate Lead on fast targets? Wouldnt just simply go pure pursuit on jamming source in best scenario? Or just simply fly past the cone of jammer coverage...

Well as indicated with RL blinking Jammer 54 test HoJ seem to be a thing. Its just I think in DCS its waaay too good. IMO missiles with HoJ should just fly in general direction towards jammer, hoping for launcher aircraft to achieve burnthrough or missile own radar to acquire target and not tracking it passively perfectly with leading how it is currently in DCS.

What were you shooting at? AI in DCS is all seeing detecting all tracking missiles at 10nm, even MiG21. VS people though target switch for 54C seem to work too as bandits I splashed do seem to react later on tacviews...

Idk about 54A in STT mode though. It may have silent HOJ. Years back it surely had silent HOJ as I died to it once

In RL it should but HB already said that due to limitation of DCS missile API current 54 doesnt behave like this. Dead tracks make missile go active only if the target stay within very narrow "box" of air of that track. If bandit deviate even a bit and will be outside of box at TTI 18-20s (for target Large) then missile will not go active due to AWG9 "go active" command (even though it should in RL). Best way is to "cut" missile support if its 54C with PAL and make missile go active on its own. Jammer changes missile logic though and in my experience in pvp, turning jammer on when 54 is in the air in TWS will greatly decrease chance of missile go active....

Sorry what? I dont really understand... from your vid, your missile is in TWS, so you fired in TWS But I see the jammer strobe coming from him too isnt ? So you fired in TWS, you lost track (its crossed out) and after couple seconds strobe appears. Isnt that what happened?

Yeah, it seems bandit turned on Jammer on while your missile was in flight. Unfortunately it makes 54s in TWS while in air much more stupid. Its ED side I am afraid, DCS's ECM implementation. Best advise I can give is that as soon you can see bandit starting to jam while u guide missile in TWS is to break lock ( quick PAL on/off) 54C hopefully goes active and finds him or/and STT him, manual loft and fire in STT