maxTRX

I ran an intercept at night. Once caught up with the hostile bomber I played around with ATFLIR for a while. One thing I stumbled on: When I had the target in STT lock, I put the TDC priority on the FLIR then I long pressed toward the FLIR. It seemed like all it did was put the FLIR in VVSL with the TD box on the target. Is this part of some mode that's under construction?

We have part of it. The AUTO bracket that expands with the target as you get closer.

Probably not, hehe. I was simply talking about a long SCS toward FLIR to engage AUTO. Once engaged, the bracket would grow as I was getting closer to the object. I think I know what you're talking about now since you mentioned 'capture box'. I don't think we have that yet.

I still can't figure out when and why it happens. I did notice one thing though. I did a test using IR Mavs on static targets. When I slewed the ATFLIR and put the INR diamond on the target, designated the target by pressing TDC then SCS to the Mav, all looked good. After I fired the Mav and SCS'd to the FLIR again, moving the diamond to the next target caused it to drift. Instead of going to 'Scene', I quickly undesignated and pressed TDC again and the diamond was stabilized. I could slew it with no problems. Now, if I just stay on the FLIR DDI, I can move the diamond forever. It stays put when designating, moving again, re-designating, so... it's still a bit fuzzy for me.

It did, whenever I used it.

I did see it already. Boxing vehicles and buildings. The box expanded. As far as whatever functionality goes with... I'm not that familiar with ATFLIR.

Now, that the Amraams work, I have no plans to have any available pylons w/o them. Give me triple racks . Arrgh... the RW books and rules and paragraphs (j/k)

Perhaps somewhere in the Setup, once it's functional? I'd lean on the side of less clutter... I guess it could be useful to see them all for whatever reason.

The way it works currently: When you undesignate and want to go back to VVSL you have to double click the pinky. Make sure your priority is on ATFLIR DDI. When you undesignate and want to lock something else or stabilize and slew: Press pinky once to undesignate and immediately bump the SCS switch toward the FLIR to put it in 'Area' stabilized mode. I don't know if there is a bug with INR or it has to fulfill some parameters to stay put. Sometimes I was able to keep it in INR rock steady and slew it at will, sometimes it drifted away but you can always catch it by bumping the SCS switch into 'Area'. You can slew in 'Area' with no problem. Designate or bump the SCS again to put it in AUTO.

Don't know but I had to find a way to deal with it. TBH, not a big issue for me. I never used snowplow anyway. Always kept it in VVSL.

If I want to undesignate and return to VVSLV: SCS to ATFLIR, press pinky (NWS) once to undesignate, press it twice quickly to return to following velocity vector.

I flew another hop just to work on muscle memory for this version of A/A radar button meshing. I placed one bandit flying at mid to low alt. hot. It was a fairly small target (Jeff). I wanted to recreate the same look down situation I setup in the first vid above. I noticed the same possible problem in TWS Auto scan center with the elevation dropping a bit too low. When I entered Manual control, I could reposition the the elevation with no problem. In this short vid, you can see this at the start of the vid. Following the engagement I attached some footage of me fumbling through all the modes in RWS and TWS. It's sees like it's workable. https://youtu.be/o-H5LfM2x-Q

It wasn't LTWS. As soon as the bandit popped up on RWS, I switched to TWS and L&S was created. When I have more time today, i need to do some tinkering with TWS Auto scan center. I noticed couple of weird things happening when I reviewed my vid.

I won't say I'm terribly disappointed The detection range... yea, then again I'm not an expert but the Amraam something changed for the better. I only did couple of engagements so I don't have enough data to run my mouth yet. This clip: Flanker size target with SPJ pods. The first 120 fired in TWS, look down situation. The lock was broken immediately but the bugger seemed to be flying to the predicted point and/or getting DL updates. The first Fox3 was a kill. Second clip: the drone size target. Hot and cold. Hot detection range in a look down was around 23nm. Cold, co-altitude was around 14nm

The buttons I'm talking about, in the SETUP sub-menu, do nothing, they're not implemented. But they still shouldn't activate functions not assigned to them, they should just produce zero output. 'Setup' is not doing anything yet... at least I wasn't able to set anything either.

That's me and my AI buddies

I did 1 test only - 30deg. strafe w/ 5knot crosswind comp. To me it looks like an improvement. I'll test it some more at different angles and w/o AGR. https://youtu.be/rNA0h2Po9fo Can someone post a vid. showing the bug?

I'd say they look quite a bit better. Not sure if the damage model has been adjusted for each weapon but the visual effects are definitely different... better So far I've tested Mk84x4, MavF, JDAMs, LGBs and all show this. For instance, 1 Mav fired at a buildings set off fires and exposions to nearby vehicles and small buildings. Yes sir!

I was just going to bring it up... agreed! I noticed the performance improvement on my rig tho' but the water in general looks too 'glassy' even with wind and the wake... I wish ED gave us the wake back from 2 years ago.

In a beak to beak with 9x I can't even imagine getting to the merge. Well, for training purposes I guess I could.

You're probably correct.

Old trusty file edit works

Yea, Mav F is very finicky. Once you get within 8nm you can cage/uncage quickly to get the Mav to follow the FLIR. ATFLIR IS A BLAST!

Well... I unchecked the box in DCS setup but the damn thing still pops up when I call the ball

Level. I smacked the runway at 900'/min but that's well within the 'norm'