wwWolfcom

Even it is incompatitable at first release, it would be easy to intergate their own product after few updates. Especially when they use same protocol/interface for their base-stick. Current warbrd d or t50cm3 supports TM grips, outdated/discontinued grips(vpc old t50cm grips etc) internally.

Possibly decoy or already unflyable condition F-14. Also you can see refule probe is extended on second plane, which might be not normal for parked plane.

F-14A RIO F-14B RIO F-14A front cockpit full view at Calverton - Cradle of Aviation Museum - New York Heritage Digital Collections F-14A front cockpit center console view at Calverton - Cradle of Aviation Museum - New York Heritage Digital Collections Danny Coremans Uncovering the Grumman F-14ABD Tomcat F-14 A B Tomcat In Detail Scale by Bert Kinjey (Vol.9) null Lock on no.18 by Willy Peters F-14B null From IRIAF's video. Pilot seat AAU-19A Partial 9 is visible above dash. nullnull Partial 1 is visible below dsh. I could not find any picture/video that shows 0 for 10,000ft scale.

1. things with no relative speed(closure rate = 0) relative speed between you and target is 0, this also means doppler effect is 0. Doppler radars are based on this doppler effect. 0 doppler effect returns are most likely noise and could not distinguish if it is returns from target or noise/error etc. So those 0 doppler shift signals are flittered out by Zero Doppler Filter(±100kts 0 closure speed) and this cannot be turned off at all. Simply, Zero Doppler is blind spot of PD radars. 2. things with no ground speed(or closure rate = my speed) These things make Doppler effect(unless Radar is not moving) unlike Q1. Returns at Clousure rate = my speed are usually returned signal of 'Main Lobe' that reflected from ground, which hinder normal detection for look down situation. These are called Main Lobe Clutter(MLC) (Image from FlyandWire, AWG-9 WCS Advanced – Part II) For look down situation, MLC is undesirable, MLC Filter will filter out those returns(±133kts 0 relative speed or closure speed=own ground speed) Notching is basically using this filtering. If target fly perpendicular to radar, it's closure speed of target will be same as ground clutters. From radar's view, it can not distinguish if it is returns from ground or target. Since amount of doppler shift is same as ground clutter(MLC) thus, filtered out by MLC Filter But if we are looking up sky, there will be no Ground clutter. That's why MLC filter is automatically turned off when looking up 3', or even RIO can manually turn off MLC filter. TLDR; Q1 is basically 'blind spot' of Doppler radars, no Doppler effects Q2 is filter for Quality of Life and this can be turned off by RIO, but has Doppler effects Some artcles by FlyandWire(Karon), which might help you understanding AWG-9 AWG-9 WCS Advanced – Part I – FlyAndWire AWG-9 WCS Advanced – Part II – FlyAndWire Detail Data Display (DDD) in Pulse Doppler mode – FlyAndWire and Another forum article.

https://www.reddit.com/r/Warthunder/s/XvHtBXnooF He just forgot some description/figures. It is taken from book 「The great book of modern airplanes」 PAL was introduced later, maybe book author didnt have info at that time.

This mod fixes mosaic pattern artifacts on F-14 TID/DDD. I don't know if the artifacts are intended.. i just didn't like it and made fix ago. -------------------------------------------------------------------------------------- DOWNLOAD v1.0 - initial release HOW TO INSTALL 1. UNZIP 2. Place F14A_Cockpit , F14B_Cockpit in.. Your\GAMEROOT\DCS World OpenBeta\Mods\aircraft\F14\Liveries Example will be Your\GAMEROOT\DCS World OpenBeta\Mods\aircraft\F14\Liveries -|--------------- |-F14A_Cockpit |-F14B_Cockpit ----------------- -------------------------------------------------------------------------------------- You can use this with other cockpit liveries(clean label, factory clean, etc..) if you replace Nrm and edit description.lua. 1. Place HB_F14_CPT_RIO_L_BREAKERS_08_Nrm under RIO/Nrm/ 2. Add these lines to your cockpit livery description.lua! {"HB_F14_CPT_RIO_L_BREAKERS_08", 1, "RIO/Nrm/HB_F14_CPT_RIO_L_BREAKERS_08_Nrm", false}; {"HB_F14_CPT_RIO_L_BREAKERS_08_W_ALPHA", 1, "RIO/Nrm/HB_F14_CPT_RIO_L_BREAKERS_08_Nrm", false}; --Normal replacement -------------------------------------------------------------------------------------- Screenshots: Original DDD TID MOD DDD TID Original Mod Normal map Comparison

AIM-7 shot in Flood mode will not alert Launch warning except F-16, F/A-18C. track file from shooter povserver-20250514-201752.trk track file from target povrwr testmiz-20250514-201906.trk Tested on : F-15C, JF-17,F-14,MiG-29,M-2000,Mirage F1 CE/EE, MiG-21bis,F-16C,F/A-18C

No, only rio(jester) can manipulate radar, except ACM modes

No, I don't have problem at such condition. AWG-9's azimuth resolution at 15nm is about 0.6nm, circa 3600feet.

My opinion about the situation... radar could not see trail targets in such condition(Co altitude, Co azimuth, Co speed). TWS is Pulse Doppler mode, based on Doppler effects. Co-altitude, co-speed head on, trail formation targets could be separated if distance is larger than range resolution. About your situation, formation is large enough to satisfy range resolution. Then why? 1. Signal strength Trail target have lower signal strength than lead one. AGC/PARAMP could results trail target drop out, since SNR can be biased on lead target(Higher signal strength). 2. If trail target's return signal is filtered out, FM ranging is no more an option. 3.Trail targets return signal could be physically masked by lead target's one. 3-1. or radar signals could not reach to trail targets, masked by lead target. 5. various TWS exclusive filtering/thresholds. Then why RWS detects but not TWS? Could be bug or simplified implementation. From what i've heard, F-14 RWS was more prone to primitive mode. Only range rate and FM ranging, azimuth is available. But TWS, much more computations, threshold were needed to built complete track file.

That seems odd. Check WCS - XMIT(jester should have already done this) Check if su30 were 'hidden on mfd' in mission editor The probe thing is called, MLC filter It flter out mainlob clutter or ±100knot relative velocity targets. If WCS XMIT and MLC is off, Radar should detect everything except Zero Doppler targets(which clousre velocity is ±133knot) Also, TWS only supports 2bar 40' or 4bar 20' Your azimuth volume setting knob will change between 2 settings. Make sure your elevation(consider bar settings relevant to your azimuth) scan volume contains target altitude.

Reported on HB discord, AB visual bug is still exist but little bit in different way.

I don't think it's really implemented. but, there will be minor degrade for AIM-7 guidance even if it's implemented. Lofting should be degraded or n/a. 1. Without INS, RADAR will be degraded in stabilization, drift compensation(using AHRS). Maybe, this could result degraded 'english bias' stated here. 2. Loft could be degraded. There is no data transfer between aircraft and AIM-7 after airborne, except AIM-7P for guidance correction. AIM-7 just need CW or PD reflected from target for guidance/navigation while in the air.

Thank you!

Hi, im helping my friend RIGHT_MFCD setup and need help Monitor native : 2560x1440 MFCD display : 768x1080 In game resolution : 1920x1080(downscaled for reasons) +768x1080 = 2688x1080 nullt Then, game does not fully fit on monitor, instead goes windowed. Another case, In game resolution : 3328x1440 null Same result but filled with black bars, still not using 1920*1080 my lua : Tested every GPU scale but still no luck. Is there no way to use export properly in downscaled resolution?

You can add 'existing' F14RIO controls to F14PILOT control or in reverse. ex)'Next launch' keybind on RIO keybinds can be added on PILOT keybinds. 'Master arm on' keybind on PILOT keybinds can be added on RIO keybinds Some added RIO keybinds on PILOT won't work if it is related to jester controled functions(mostly radar related) ex) azimuth scan volume, elevation bar added to pilot keybinds, those will not work unless jester is disabled I recommend to use this mod if you are willing to edit keybinding lua. It passes IC if used correctly.

You need to edit .lua to add some direct backseat control. You can't add new jester direct keybinds even with .lua editting If you are using voice attack, here is walkaround Say 'jester drop tank' Commands: Press Jester menu(A) 2 times Select tile 'Within Visual Range' Select tile Drop tanks You can assign tile shortcut, i use 1st tile-ctrl 1, 2nd tile-ctrl 2 . . . Think voiceattack as voice commanded macro. My example setting will be Say drop tank Press A 2 times Press ctrl 3 Press ctrl 1 will command jester to drop tank

That's not the case of airframe wear out. More of compressor stall issue.

Adjust afterburner detent on special option. around 40% will be MIL detent for TF30. Cockpit's MIL marking is correct for TF30 But incorrect for F110 and this can be corrected by livery editing(F110 had little more MIL range)

around 40% is TF30 mil detent (MIL marking position)null

Use afterburner detent adjust on Special option

It's DCS core side thing. Nothing HB can do.

@BIGNEWY Hi, can i get any anwsers from team?

Simple image quality comparison.

Sorry for violating rule. Thank you for looking into it.