USA_Recon

I have TX1-3 working, radio 1, radio 2, MIDS A For MIDS B, which TX should I be using ?

"Unlike F-16, "just lock" in F/A-18's RWS and TWS MAN will not adjust radar automatically to maintain lock. Use TWS AUTO and it will try to maintain lock just like F-16 or F-15C." Also post about that RWS will drop a soft lock is bandit goes outside the radar beam. Easy to test, I softed lock pilot at 8k, my captain bars were at 10k and 6k, if bandit went above 10k or below 6k it drops the soft lock. That is what I see. Is this is a bug or how it works ? ie. if you want to track you use TWS auto mode (or STT)

In 2.7 in daytime noonish when su n is bright the MFDs are extremely hard to read in F-16 - several posts here confirm it as well as a miz I posted for BigNewy... that said ED hasn’t acknowledged the issue ignoring it. it’s definitely related to lighting - they fixed this in the F-18 but broke it in the F-16. it’s related to TOD - early morning / evening it looks fine

Agree 100%

Waiting for it to be acknowledged by the devs

Example .miz - sun, and TOD - the red datalink is very dim and difficult to see no matter how much I brighten the MFD. VAF_TestMFG.miz

it looks horrible in game for me - the rockers did nothing, this mod works great, but the new lighting causes the red datalink to disapear. Any way to mod that color ? Green is fine. I have a miz you can show how back the unmodded MFD's are. Try the F-16. TOD makes it nearly impossible to read.. Still buggy VAF_TestMFG.miz

“Those are the very basics, right now Jester uses TWS Auto and doesn't move the scan volume unless you tell him. TWS Auto isn't working properly yet” how many more dev cycles until Jester the RIO gets trained how to scan properly - radar 101...

Yes Heatblur treats Jester like some RIO who was never trained how to use a radar. Basic 101 is seeing datalink, getting the altitude and adjusting the radar scan. Instead as a pilot you have to tell him what to do. I love the F-14 flight model but HB gets a C- overall until they stop testing Jester like a untrained Rio...

This is exactly what my entire squadron sees as well 1. in VR 2. without VR 3. without MODS TOD and 2.7 lighting issues - was fine before 2.7 edit: I normally use 1.8 gamma, in these TOD like shown above, I have to turn it to gamma 3 just to see the red datalink contacts on SA and radar mfd's

I've sent you multiple screenshots, multiple times This is exactly what my entire squadron sees as well 1. in VR 2. without VR 3. without MODS TOD and 2.7 lighting issues - was fine before 2.7

Jester *should* be able to still use radar within 20 miles. It's a shortcoming that we have to switch to a 20 mile PAL lock. What is the default elevation range on PAL btw ?

To be clear, I'm not talking about LANTIRN, I'm talking about needing to constantly use a wheel to tell Jester how to scan. Honestly if he did his job properly in the first place, i wouldn't need to spin the wheel all around just to get him to understand, ie. we have a low datalink contact ahead, target it - vs. 'unable' etc.. that BS far outweighs this 'spin the wheel around' approach. If it means I can press a button to low radar range so be it. Reality is, I shouldn't be commanding a RIO to do his job in the first place. So the 'realism' folks are keeping a blind eye on the gaminess of the jester in the first place. It's 'neat' and all, but exposes the complete incompetence of the 'Jester'. Let alone his call outs that are always delayed and rather silly (by the time he says 'contact on your 3 oclock', the bandit is on your six, or telling you about something far away when you have an immediate threat).

I see, you enjoy spinning around a fake jester wheel and are critical of those that don't see much of a difference of pressing 3 buttons to bring up a menu, slider it around (and in VR its a PITA), vs. just being able to select a single button . We have quite a few dreamers around here - guess I'm just a practical person

I have to agree with this statement. What is difference of using an annoying wheel ui approach to press a button to tell him, vs. binding a button to same command to avoid the clunky interface (I mean, for what it does the interface was a nice attempt, but has serious shortcomings). Speech is much faster than the wheel. So again having button controls SHOULD be an option over the incompetent Jester As fancy as that all sounds, the reality is - you can sit there an spin a fake wheel implementation over and over again, which tries to replace speech - which is not realistic whatsoever, and ruins immersion, or you just enable controls . There is literally no difference, one just forces you to use a very clunky wheel interface. I think it's perfectly fine to be able to control it from the front seat as an alternative to needing a fake Jester AI wheel interface.

So when I fire at a TWS target, and it's solid white, with a flashing countdown - when it's flashing it's active ? I've seen it with like a 54 second countdown, surely it's not active yet. Some clarity here would be nice - thanks!

maybe someday Jester will qualify to be an actual RIO..... I'll be honest, when I first thought of Jester, I was worried he would be 'too good' - that has never been a problem with this F14 though is there a reason all of his callouts are so dated - he will call out something at 3 o'clock that happened 20 seconds in the past, he might as well not say anything at all!

I confirmed last night at 52/54% I was getting 90fps (F-16 quick mission caucas fighter mission). I switched to 100% and it dropped to 80fps. I would rather though lose frames than have 'shimmering' and DCS has too much shimmering - even BN attests to that shimmering. Regardless of settings, if I look at the 3 or 9 oclock and roll the aircraft it's not smooth. I don't know if that is a DCS issue or a G2 issue Note: agree with above post, use what works for you - I don't notice any barrel effect, but I do believe what is being said.

I've been having this same issue since the hotfix. I do not get this on other maps hosted by our server. Again, ONLY happens on Syria map.

I have noticed this as well - TTA should not disappears

decided it's not worry complaining.... carry on....

Wish aspect angle (as shown in radar) was in the HUD as well - guess it wasn't irl ?

it's basically broken. Hoping it gets fixed soon.

any chance this can be rolled into your mod (it needs updated to latest version though...) https://forums.eagle.ru/forum/english/dcs-world-topics/mods-and-apps/dcs-mods/284187-2-5-6-xxxxx-adjusted-shaders?t=281666

hmm. but that wasn't what you told your customers on release of the F-14. I don't know why your acting like it's free, when I bought this module at release, this is what I was told my $ was buying. Why you talking down to your customers ? If it's about the gloves, then just say 'it didn't have gloves' - but don't treat us like we owe you something for your marketing decisions.