The_Tau

As a workaround I highly recommend this https://www.digitalcombatsimulator.com/en/files/3319633/ It doesnt give you DDD but for 80% of time its ok Probably you have to update it though if you want new commands like bingo set bindings...

Remember you have to repeat procedure after each update

People have wrong idea of what Jester can do. "Lock up target ahead" means lock ahead radar track. So no track = "No can do man!" Jester can only lock targets that have track on TID. So you need to babysit him with radar elevation as well. AWG9 has narrow scan volume in closer ranges (<25nm), so I often tell jester to switch to RWS at those ranges to get biggest scan volume possible. Only exception is "lock specific track" command. Which allows Jester to lock datalink tracks even if there are not currently in AWG9 scan volume (but within gimbal). This feature is really powerful (Some could say its borderline OP) especially if you combine it with some shortcut for Jester menu like VoiceAttack.

Tacview are in the comment I was responding to

to me they looked notched :(. So missile doesnt pull up when notched anymore, but instead it just flies next to target "blinded" for some reason. So it seems ED just fixed "visual" bug of missile pitching up, but they didn't touch the main problem - 54 being unable to find target again after target leaves the notch... Wow I am so disappointed...

You can resize header/title bar as well if you hover mouse over the edge and GPS adjusts when you hide it and show it again. So yes there is new problem with GPS and its a little pain to set it up, but in my case, after I set the size I want on ground then I dont need to change it, so its not that a big a problem for me . And current fix is way less annoying than brightness bug. So two steps forward, 1 step back

In MT NS430 works now. It doesnt get dim anymore and its awesome.

MiG31 and R33 have similar behavior. MiG was cold and R33 acts like phoenix

Its just when engine overspeeds and goes dangerously close to 3000 RPM then Prop lever becomes unresponsive even when fully back, but manual RPM still works and you can still decrease RPM below critical level. Maybe its DCSism. And yes, i did map manual pitch to my HOTAS. You can dogfight with 190s but not really with 109s and diving is really only thing you can do to survive, when jumped.

Right now with current modeling when I am going to dive I use Manual prop pitch and decrease RPM to 2500 and RPM tends to stay there throughout the dive. When I start "Zooming" I put prop back to auto and Bob's your uncle.

Veteran AI is much more forgiving and realistic for Red force average pilot skill level

Also I would add that ground crew repair for gear doesnt work properly in P47. The "floating" part of repair (when damaged plane is lifted in air) is too short for repaired gear to fully deploy, damaging it again after repair is completed and plane placed on ground again.

I did just that. @NineLine your input? Marianas mission, after 1 min hyd failure is enabled and you can see hyd pressure going to 0 in cockpit. Gear doesnt deploy fully in emergency, even with hand pump and flaps neutral. Interesting that flying upside down, allows you to retract gear and even lock it in place. I guess good to know P47 gear no hyd.trk

Personally I like to set Chaff program for Jester. Uses much more chaff than Singles, as jester is very conservative with chaff

Considering this 18:15 Maybe this topic should be moved to Bug section. rocking, yawing wings do nothing

yeah i tried that, and it doesnt work. I tried flaps to neutral too.

Hello, Is there any emergency gear deployment procedure in case of lack of hydro pressure? I thought that in this situation gear should deploy under its own weight and if its stubborn then rocking wings should help gear get lowered in lock position. But in DCS it doesnt seem to happen, gear gets stuck halfway and no rocking or hand pumping would do anything to help gear get lowered Am I missing something?

I dont know if you used any more advanced tools to calculate traveled distance. In Tacview I just added waypoint on spot where 54 ejected the F14 (40k ft, 0.9-1.1 mach) and measured straight line to the 54 impacting target (or spot where 54 gives up tracking and simply falls down ballistically) and that distance was about 80ish nm. So I talk more slant range, as its much more useful for pilot to determine when in range

In my personal experience maximal range of AIM54C is 70nm-80nm of actual missile travel distance. Battery dies at longer distances. Tested with circling E3s

Depends if hostile is Fox 3 capable or not but generally I use TWS ranges >35nm, 30-20nm hold fire, 20nm and less PDSTT. AIM7 is great at tricking enemy. Sometimes I fire aim7 at 15nm to make bandit go defensive, close in and fire 54 at closer range and skate.

I use JSGME or OvGME to manage my mods

You can press stuff with human RIO too so don't press them

Thats why I use that mod to map RIO controls, like HCU, NEXT LAUNCH, MLC, CAP NUMPAD for target data, CAP TRG DATA page and that one CAP button for DO NOT ATTACK. So I have control over all of those from front seat. And its awesome. https://www.digitalcombatsimulator.com/en/files/3319633/

No, there is no Jester command, at best you can STT specific target. So either you have to jump to back seat, hook track you want and press "Next Launch button" Or you use mod like this one to get RIO controls in Pilot seat, and you just map it https://www.digitalcombatsimulator.com/en/files/3319633/ Also there is option "DO NOT ATTACK" on CAP under TARGET DATA category. It makes AWG9 ignore tracks, and its excellent to simplify AWG9 TWS scan to make it focus on one maybe tops 2 targets. "GND MAP" supposed to give track "Mandatory Attack", but I am not sure it gives track some priority over centroid of radar. So what I do when attacking multiple targets is to set do not attack on other targets with low pk (like they fly at low alt), so that awg9 focuses only on tracking 1 track with high pk (target flying high)

I use those tactics