wwWolfcom

1,2.The jester menu states 'SET JAMMER XXX'. It's SET, directive call. So the current state of jammer will be inverse of XXX. 'SET JAMMER XMIT' means jammer is STBY 'SET JAMMER STBY' means jammer is XMIT 3.Jammer works. HB F-14 jammer is blinking jammer unlike other F-16, F-15C noise jammers.

I know that's not safe and operational parameters. I do trim per weight on carrier ops, or just to trim on runway. I did test on purpose wheter checktrim advisory remain after take off is accurate behavior. Thank you for investigating.

According to NATOPS, 'CHECK TRIM' should be appear only when sensing WoW. 1. Currently, DCS F/A-18C, CHECK TRIM remains no matter sensing WoW(Airborne). And Player cannot address CHECK TRIM caution if they are airborne(no WoW). Player must land and set appropriate take off trim to remove this caution. or lower gear and flaps, trim for 15 AOA units. 2. Another problem while on ground. Get 'CHECK TRIM' caution and set take off trim. Caution will be removed and never appear again even if player trim down to 5'NU.

F-14 Flight Model Update – Part I – Heatblur Simulations

On performance manual, check out 'specific excess power' chart. This will give you a hint. Ps=0 line will give a fastest speed at its parameters.

Known issue. Nothing we can do.

I'm not having any issue while using AB detent. If you are playing in single thread, thry multi thread.

F16 DL HOJ.trk contains 1. With the datalink, FCR correlates jamming targets. Gives full track information to FCR, DLZ/a-pole also works. 2. With / Without datalink, TWS/RWS-SAM gives ability to employ amraam HOJ without STT. 3. FCR correlates jamming targets with datalink when bugged even if datalink is turned off(MIDS-LVT off). This looks like bug. F16 NO DL HOJ.trk contains 2. Without datalink, TWS/RWS-SAM gives ability to employ amraam HOJ without STT. Thanks. @BIGNEWY F16 DL HOJ.trk F16 NO DL HOJ.trk

I don't have saved track now, but i can reproduce it. I will attach them soon. Thanks

@BIGNEWY @NineLine I'm so sorry for pining, can i get anwser from ED team or SMEs?

1. With the datalink, FCR correlates jamming targets. Gives full track information to FCR, DLZ/a-pole also works. 2. With / Without datalink, TWS/RWS-SAM gives ability to employ amraam HOJ without STT. are those intended(or realistic) behavior? 3. FCR correlates jamming targets with datalink when bugged even if datalink is turned off(MIDS-LVT off). This looks like bug. Honeycam 2024-08-20 17-53-23.mp4

Seems like it is ST bug. MT works fine

Check the Case2 especially, AIM-7 Position and F-14 Position and RWR position.

TL;DR JAT-FOX1/3 will give Launch warning regardless of F-14 Radar status. This only applies to F-14. No other modules(F-16,F-18,F-15C) have this issue. out of context : If launched in TWS, jammed middle of tracking, AIM-54C will automatically change to HOJ and keep guiding itself. This does not give Missile warning until Pitbull range or 2~3nm. This video is Test summary. (Video is processing)

So,this issue is still on going?

1. Flap lever position need to be tweaked. Current in-game up/down position is Emergency up down position. 2nd. Mil/afterburner throttle range incorrect The MIL detent is away from where it should be, (See the RPM with throttle at MIL marking) too short mil-max range

It's a bug and will be fixed with next patch

Sparrow is not affected but phoenix does. Worst thing is, AIM54A is not guided on TWS

Before 2.9.5. From GS server Tacview-20240313-084242-DCS-Host-Server_1_Operation_Urban_Thunder_V7.7.34.zip.acmi null +AIM54A is not guided on TWS

TEST: shutdown radar/beak lock after launching missiles R-3R STT AIM-54C TWS AIM54C STT R77 STT VID.mp4 R-77 STT R27ER STT VID.mp4 R27ER STT Missiles pull up like 20G, 20' when they lost guidance(no matter guided by aircraft radar or missile own radar) no matter how target maneuver. Very critical bug for BVR engagement. This behavior did not appear before 2.9.5 patch. HOT FIX is demanded asap Most of old API missiles are affected. Other IR missiles are also effected such as AIM9M,L,X, R73, R60 etc have same issues. Honeycam 2024-06-01 23-22-30.mp4 9X pull up behavior Other missiles in multiplayer Honeycam 2024-06-01 23-16-10.mp4 Honeycam 2024-05-28 04-09-36.mp4 AIM-54C Honeycam 2024-06-01 23-21-30.mp4 R27ET PL-12,SD-10,AIM-120,AIM-7530 are exception. They behave normally like before 2.9.5. AIM-120 normally behave in 'Memory track mode' Tacview-20240602-124344-DCS-Missile TEST3.R27ER STTzip.acmiTacview-20240602-124109-DCS-Missile TEST3.R77 STTzip.acmiTacview-20240602-122815-DCS-Missile TEST3 R3R STT.zip.acmiTacview-20240602-121906-DCS-Missile TEST3 AIM54 STT.zip.acmiTacview-20240602-121718-DCS-Missile TEST3 AIM54 TWS.zip.acmiTacview-20240602-124648-DCS-Missile TEST3 AIM120 NO PITCH UP.zip.acmi TACVIEW for Test mission R27er STT.trkR3R STT.trkAIM120 TWS NO PITCH UP.trkAIM54C TWS.trkAIM54C STT.trkAIM7 STT NO PITCH UP.trkR77 STT.trk Trackfile for test mission including aim120/aim7

Sorry for bothering you, but can I ask you some questions thru Discord DM?

Thank you guys! The Normal map was the cause. I think there are some problems on F-14's normal map.

I will try that. But is it possible to edit already baked normal map?

Hello guys, i'm trying to adjust F-14's rough met. But could not progress. If you are willing to, I would like to get some advices. Thank you

TID reflection: DDD reflection: DDD/TID have mosaic shaped-reflection. I dont know if real-TID/DDD would be same, but it is annoying me. I'm trying to get rid of it, but could not find any solution. HB_F14_CPT_RIO_L_BREAKERS_08.dds and HB_F14_CPT_RIO_L_BREAKERS_08_Roughmet.dds determine texture/reflection of TID/DDD I tried: 1. adjust TID/DDD texture to pitch black. No luck. Still gives mosaic reflection 2. TID/DDD counter part roughmet to 100% red, No luck. Still gives mosaic reflection 3. TID/DDD counter part roughmet to 100% yellow, Totally remove reflection but this is not what i'm looking for. What i want to do: adjust TID/DDD reflection like Gauges' clean reflection. Like this: Can i get any advice?