Rinz1er

Definitely feels like a bug. My workaround to any situation where the radar is locked on to something or doing something I don't want, is to quickly hit the PLM button which always resets it.

This is intended. As per the manual PAL range is 15nm - https://www.heatblur.se/F-14Manual/general.html?highlight=pal#pilot-automatic-lockon-pal VSL HI/Low is 5nm - https://www.heatblur.se/F-14Manual/general.html?highlight=pal#vertical-scan-lockon-vsl

I've had issues engaging the altitude hold at anything higher than 35999ft on the tomcat altimeter

Has anyone else noticed an insane glare when looking at the sun with only the VF-32 Swordsmen AB200 (1976) F14A livery? I will post a picture soon of what I am seeing but it makes this livery almost unusable in dusk and dawn scenarios. null

So it is the GR1 Tornado then? Sad we won't get brimstone...

This exactly how I see it as well. The guidance issues, lofting profile, along with the AI's uncanny SA abilities. The lack of target size switch functionality, and more have all led to the situation we are in now. The changes to the pheonix kinematics are not the problem, most of my missiles go active on a target still going close to mach 2 from ~50nm. The target just has a ton of time ~20 seconds to turn cold or descend to beat the missile. It is truly unfortunate... I hope HB along with ED can sort out these issues soon.

Looks like grafana UI and https://github.com/DCS-gRPC/Telemachus

Hello, When realigning the tomcat after a shutdown post-flight, jester uses the original location's coordinates and not your current positions'. Possibly a coincidence, but he seems to always enter the 'ramp' coordinates from the kneeboard. Thank you very much for all the hard work on the module!

Personally from my own testing. With the suggested nozzle_exit_area change in this thread, the missile performs as expected. Without it, it does seem a bit slow...

I could imagine scenarios where you may want to carry a mixed mk47s AND mk60s. Is there anyway to weapon select between pheonix pylons? I know you can with AIM9s by hitting the weapon depress.

They already added engine stall from intake exhaust. Go ahead and launch an SD10 or LD10 and it will stall the engine.

When the JF-17 was first released, we could put the BRM-90s on the inner pylons but was later removed. Will this functionality be returning at any point? It was really nice putting those pods on the inner pylons so that more missiles could be carried on the outer pylons. Thank you for the module!

So according to that document, we would need OFP 321 which by then would have seen the PTID, PMDIG, Sparrowhawk, GPS, MIL-STD-1553B data bus, new mission computer, and AWG-15H FCS added. I remember reading that the PTID and PMDIG were not possible for HB due to lacking some info on the pages that made it up. I am guessing this is still the case and therefore the reason we will never see JDAMS on the tomcat...

Hey Guys, After watching the FAC-A Tomcast they mention using an IZLID (Infared Zoom Laser Illuminator Device) at 50:28 mark. Other jets (AV8B) have an IR illuminator and I would love to see Jester shining his 1W IZLID out the canopy down at ground targets so that folks with NVGs could see what we are designating. Speaking naively, but I would figure it would work in that if Jester can visually see the target on the ground out of the canopy, then he could potentially illuminate it automatically if the LANTIRN is designated on it (no need for a jester menu option). Kind of a fun concept that would make the Tomcat even more unique than it already is!

Loved hearing Nikolas say that he would want to do F14D if they could. Gives me hope that one day we may get it. I would pay some irresponsible amounts of money to fly that thing in DCS.

Could we get JDAMS on the tomcat without the sparrowhawk and PTID? Just use the kneeboard/F10 to preplan the JDAMS from the ground-crew (similar to the av8b does) and since the LANTIRN already has GPS just use it to designate JDAMS from <10mi since I remember reading somewhere (may have been that LANTIRN TOMCAST) that they just added a little digital bus controller which gave LANTIRN communication between the pylons and the cockpit. Seems reasonable to think with how Frankenstein the tomcat fleets were that this sort of thing could have existed? Note: I did attempt a mod for this and was able to get the JDAMS on the tomcat but ran into issues with the WCS not having the ballistic data and selectors for JDAMS. It is easy to add missiles to the tomcat but seemingly impossible to add NEW bombs on it

Hey guys, On other jets to avoid having to realign after a repair, I turn on the ground power before shutting the engines down to keep the alignment stored through the repair. Though on the tomcat when the plane is lifted up for the repair it disconnects the ground power and trashes my alignment. Anyway we could get this fixed? ... and also the repair bug that forces me to smash the wing on the side a building so that I can fix popped tires (think of the taxpayers)?

Confirm that TALDS work again. Attracted SA11 missiles with wings and all. Thanks!

I think it was similar to how the JF17 MFD's work where all the text is green on the menus but once you go into the flir pod it becomes greyscale. But also, HB has said over and over that they don't have the relevant information to model the PTID. Source:

Why not HB just do it themselves then?

I am not able to post a track right now (will try later tonight) but I have noticed that several SAMs (SA2, SA10) refused to launch on ADM-141A launched at 30k ft and from 40nm directly at the SAMs. Can anyone else repro this? Also, already reported, but the wings on the TALD still don't deploy after being dropped.

Confirmed this earlier. They fixed the auto throttle bug but the bug breaking ACLS from the AP changes seems to still be there. Pretty sure HB is aware.

This is my experience as well, with ACM cover up & no lock, I can't get it to hit anything, it just burns straight. It has even flown within a couple hundred feet of a bandit and didn't even try to guide. I did not try ACM cover up AND a lock though.

Just going to add my experience FWIW. I have probably put in about 40+ hrs in the Tomcat since this missile change went into affect, all online. In the beginning I was missing 3/4 mk60 phoenix shots from my usual launch params(30k+, .9 mach, 60mi). I have had to introduce 45 degree cranks, an extra 10k ft, above mach 1, and launching at 45mi to be able to do 3/4 phoenix kills with the mk60. In the mk47c, I have missed maybe every shot I have taken no matter what tactics I have done, mostly because against an amraam opponent, if I fire at relatively the same distance, 30-35 mi and hot aspect, I usually have to defend the amraam before my 54c has gone active and end up trashing the missile, and for whatever reason, when I take a longer shot it just gets too slow to hit a maneuvering target. The more upsetting thing that I have noticed is that after this update, I have not seen any phoenix track after launching them maddog (ACM cover up). Not sure what is going on there or if anyone else has had this experience. The last slightly annoying thing that I have noticed is that the TTI counter on the TID seems to always be off by about 2-4 seconds now. With most hits coming in at -2, -3, or -4. This makes planning my defensive maneuvering rather difficult because I can't determine if I splashed or missed from the TID counter if the missile is still in the air well after TTI. Anyway, still love the Tomcat and look forward to more updates, thanks for all the work!

Also experiencing this. It makes using the laser guided weapons impossible...