GrEaSeLiTeNiN

24 Dec Patch: Slightly faster now? Couldn't really be sure.

24 Dec patch -> Not fixed.

24 Dec Update: Not fixed.

24 Dec Patch -> Radio selector and radio channel selector for pilot and copilot fixed, thanks! Just a minor thing is that the animation for both pilot (collective) and copilot (side panel) channel selection Up/Dn is in the opposite direction.

24 Dec update: Fixed, thanks!

24 Dec updated - Fixed, thanks!

Anyone getting these strange white lines in the sky? Never had them before. (Latest update)

Just a quick check - FCR TPM mode isn't implemented yet right?

I noticed while in WACQ uncaged mode, if a target get's locked and then you SCS bump (<-) it, you lose lock and WACQ is recaged immediately. So then the 2s pause gets applied in WACQ caged mode. It seems to work that way when I was trying it out. Did I understand it correctly? Also, I wonder what is the logic for WACQ cage mode not being bumpable except, in a sense, in the above scenario. Thanks for following up on this. PS: About bumping, for easy reference.

Appreciate it thanks!

Are 3rd party module's weapons now under ED's control? If so, it may be ages before we see a fix.

VACQ is ok. But Boresight still not fixed as the 2 secs is still absent whenever HMD is on (HACQ mode). Track attached. ACM BUMP - BST 2s absent with HMD but VACQ ok .trk

Not a bug but using a HAT switch on my Warthog stick (that's how I like it mapped for radar cursors in all my modules) and with no slew speed adjustments in Special options (for such a flagship module?!), it can require quite a bit of effort and will probably wear out my HAT switch some day. Not that it's absolute necessary to do this as one can just click on the respective hot spots or use the DDI buttons. But what I realized is that you don't need to touch the edge of the screen during the process. Just be near enough. That helps make the to and fro bumping motion faster which is needed to change the range/azimuth. Bumping the cursor likewise to change the range in the SA page is relatively easier. Probably because there isn't all that scanning going on like in the RDR ATTK page. Just some observations. Users who have axes bound for this probably find it easier like in this video.

This was fixed (TDC depress to uncage and slew the WACQ box with the TDC) except that now I cannot recage the box with SCS left which was possible before. Not that recaging the box is that necessary but just wondering if this now is by design.

Was just about to reply after some extensive testing. Yes! Like you said, one must not box all 4 stations under QTY before the designation process. Doing so causes all 4 JSOWS/JDAMS in TOO1 to use only the last (4th) designated coord even though each target designation shows a new coord. But when you step through the 4 stations, you'll see only the last coord is used. The same problem will happen when you designate the next 4 JSOWS/JDAMS in TOO2 where again only the last (8th) designate coord is remembered. Seems rather strange.

Does this work for 8xJSOWS as well? (Update: Yes it does.) I followed Tricker’s video tutorial which is basically as described above but all 4 JSOWS of TOO1 hit the last designated point of TOO1 and the next 4 JSOWS of TOO2 hit the last designated point of TOO2. Seems like all the previous 3 coords are replaced by the 4th coord in each TOO set. (Update: Do not box the 4 stations in QTY before the target designation process. Only after. See here.)

Thanks Kinkku, noticed and appreciate your presence and quick response in this forum lately.

Look for "MMS FOV Narrow Toggle Down" and "MMS FOV Wide Toggle Up". They are only under the Copilot controls.

Post 4 Dec 2024 patch, still no fix. Getting loud static noise in F16.

Warthog hotas also: On the Master Arm Switch example (I use the 3-way Autopilot switch also), what happens for me is that if I turn it to say STBY while in the pilot's seat using my physical hotas, I cannot click the switch with the mouse to another position. But if I hop over to copilot seat, I can use the mouse (or physical switch) to move the switch, and vice versa. OR, if I hop over to the copilot seat and hop back to the pilot seat, I can mouse click the switch. I only bind the pilot's switches mostly as they work for copilot as well (I don't repeat the same bind in the copilot controls). Also, I prefer the individual Armed, Standby, Off options versus the <> and / options for switches because it keeps them in place as per the physical switch position better. Not sure if that is causing the switch to be 'stuck'. (I don't have "synchronize controls between hotas and cockpit" on.) On MMS stutter, are you on axis bind or HAT switch? I am on the latter and it is ok, just too fast. (I use the air brake forward so I don't have to hold down lase.) On the ACK / REC switch, I don't see any 20x a sec pressing going on. I am using throttle base switch 31 (up) ACK, 18 (down) REC. I think the only overhaul was on the new Kiowa sounds by Echo 19, not the switches which still needs some fixing.

It's basically a ghost drone lasing whatever enemy target it wants and completely ignores your ME drone mission design. In the feed, the target's coords are correct but the drone's coords are just misinformation because they are the coords of whichever drone you selected in the INIT page regardless of the target in the feed.

For me it's been this that has helped (on the ADI and doppler, as posted some time back in another thread).

A clean sweep of the buttons and switches to make they are all ok would be deeply appreciated.

Interesting...

Yeah, it's been too long. I don't understand why they won't fix it. They've had so many many months to do it.