maxTRX

My question was about having override function boxed across master modes not weapon release buttons. ...and without drifting off too far from OP... Another question: Should EW page pop up on RDDI whenever PBLK is active?

Couple of things I noticed: In TOO mode we have number of very useful filters we can apply, including 'HOS' (hostile). In SP, the processing is obviously more involving. I'm definitely not an expert but I think the threat radar should at least be in pre-launch tracking mode on own ship to be included in threat ranking and allow the HARM launch. 2 pics showing Class Scan we have now in TOO: Another thing, or a question rather: Currently, when HRM OVRD is boxed in NAV or A/G master modes, switching to A/A unboxes HRM OVRD. Is this correct?

Thanks.

Track attached. 2 HARMs launched in Self Protect mode. I also tested the PBLK function in this track (from A/A). This part worked fine, except... I still had the HRM OVRD boxed but that's another issue, hehe. The first HARM launched before full lock on a threat. The missile makes 180 toward my CBG. The second missile fully locked on, hits dead on. No launch inhibit.trk

Currently we can launch HARMs in SP at any time, as long as master arm and A/G master mode are on. I don't think it should be possible until the target 'box' is visible. The mission track is too long. I'll make a short one later on. Another 'funny' thing: When I launched a HARM in SP a bit too early (threat emitter tracking, just before my HARM got a solid lock), the missile made a 180 and headed for my carrier battle group, 120 nm away. This could be related to an issue described in an earlier thread in this forum and already reported.

I 'almost' thought one of my missiles dissapeared but after a replay I noticed that my target (SA15) stowed its radar few seconds after I launched my HARM in PB HRM and raised the radar up again after my missile exploded on PB WPDSG (located 500 m. away from SA15). A question for ED, if I may: In a situation described above, shouldn't HARM aim for the last known location of a target emitter instead of PB waypoint? There were no other SA15's in the vicinity. The SA15 vehicle did not reposition after shutting the radar off. @Harker: did you see the missile disappear (visually) in F2 or replay?

not bad

...and from gamer's perspective... let's not forget cycling through your own Amraams (if not lofting high enough) and...

I can't get enough of this weapon in DCS. The effects are scary (even the RW footage is not as spectacular, hehe)

Are all these issues popping up in MP missions only? I didn't encounter any problems with HARM's in any mode in SP. 15 custom missions flown recently.

Sounds like it could be related to transition to PA mode with AP engaged. Were you using any AP mode and didn't disengage it before dropping flaps? It thought this bug was fixed already... if that's what the problem is in your case.

I wasn't really reporting a bug, just sort of asking/confirming/observing... perhaps my 'smirking' emoji threw the mods off so they shoved the post from the Hornet general discussion. Cool.

Is it 90 sec.? (current DCS modelling). I did some testing at extreme ranges. Target co-altitude @48k ft. In the first test I launched the first Amraam way before R-aero and due to significant lofting, the missile was coming down on a target Tu160 like bat out of hell but... it didn't make any effort to intercept. The battery was dead?

2018... that's about right I remember, at that time I could also pull off some radical rudder turns that currently would not be possible... and for a good reason according to more knowledgeable folks. There should be couple of vids on YT showing nose slice departures and the dreaded 'falling leaf'. (in pre-10.7 prom?) that were not modelled then and now either.

When the Hornet's FM (w/ FCS) gets a promised rework this might apply. Currently, in a upright spin, neutralizing controls then following the arrow did not get me out of the spin. Moving the stick in the opposite direction did, especially when augmented with asymmetric thrust. As soon as the opposite stick is applied the rotation started slowing followed by a slight nose down. With couple of thousand feet to spare, the recovery is fairly easy. I'm talking the spin rate of 50, 60 deg/ sec. Back to OP: in my opinion, there is no pirouette mode, one way or another.

Well... I believe we're getting somewhere. I did 5 sorties against 4 maneuvering J11's (unarmed of course) and they all cooperated nicely by staying in my scan volume. In all 5, 4 kills. I watched every missile in replays (in F2). They updated nicely. Going pitbull was noticeable. Also, there was a 'wobble' when missile was notched (I'm speculating on this one) but none of them got spoofed. Now, I'm really anxious to see what the devs come up with with this 'range and angle gating'

Yep, they got that one wrong too. (No... Gripes and Hulkbust44 are wrong ) Also, as you said there is no pirouette mode. I took it for a 'spin' and I was able to drive it into sustainable rotation. No gyrations in pitch, not sure how Hornets (lot 20) should behave but ... it was fun. https://youtu.be/Xw4z-94IESo As I mentioned in my first post, I ran my mouth before reading... The arrows are correct (Figaro9 did some reading for us in the post below ), for upright, for inverted the arrows would point in the opposite.

Just running my mouth before testing this... do you mean you saw the arrows on DDI's? I tinkered with this few weeks ago and it seemed like entering with proper stick and rudder inputs produced the same results as entering with only rudder (at AoA >25) or the stick only. I'd have to read up on this again but from what I remember, using full rudder at high alpha and slow a/s or using full stick left or right should produce the same results: a slow bank. The pirouette logic changes that from what I understand. I haven't seen the spin arrows in a long time. I'll play with this later and see what else comes up... hopefully not the ground.

Yep, it's a chitchat. You never know, a random test or observation might contribute to someone's detailed and systematic work already in progress... Anyway, here's a clip with 2 CCIP drops I was referring to in my previous post and 1 AUTO loft. Targets designated: https://youtu.be/e7biWohRmAw BTW, AUTO mode still doesn't calculate solutions for movers so CCIP + Kentucky windage is a valuable tool for now . I dropped couple of Mk20's on a speed boat just eyeballing the lead. It worked... this time: https://youtu.be/K-ExcBgIfwY?t=46

CCIP + AGR takes the cake in my recent experience. I used Mk83's for the tests. I usually dive at 20 deg., a/s around 480- ish. and as long as I pickle exactly when CCIP cross is over the target, the bombs are on top of the target or very close. In all of these tests I had the FLIR looking at my target w/ forced AGR. The AUTO almost always causes short hits, except when I use it in a 15 deg. loft. I tried it 3 times and 2 were direct hits, 1 close enough. Go figure that one... The wind was 6 kts. from 90 deg. left or right. I didn't notice any issues with wind compensation. I'm not sure whether HUD indications are correct but as long as the ASL is on the diamond, the bombs are lining up on the target... just usually short I'll post a short clip tomorrow.

No difference between Reverb G2 and pancake. MavF seeker logic and integration w/ Hornet's MC and other sensors sucks on both . Well, that reminds me... before I decide to update to 2.8, it might be a good idea to wait for some feed back, since I only fly Hornets and supposedly the Amraams have been fixed, some other 'balancing' factors might have kicked in. If the Amraams have been fixed, it might be a worthy trade-off Now, I'm getting way OT.

I sort of gave up on DCS version of Hornet's radar (ground and A/A) but after a while I decided to check it again, motivated by wishful thinking... In this test I wanted to see if designating on a frozen EXP3 image was possible. Well, it is. I was able to slew over the new target but after releasing TDC, the designation 'cross' did not move to the new target. The FLIR snapped to it or... very close to it and I was able to refine and launch a JSOW. The FRZ function is still linked to active radar somehow. After passing the target the radar switched to EXP1 away from the area. Speaking of EXP1... when flying around with the radar scan offset to either side, the image didn't really look that bad. I had to play with contrast a little. https://youtu.be/5qgzmi8e_Xs

AI logic took a big step backwards... I tried fighting AI Hornet set to 'trained', hoping that dumber AI will stick to basic, less creative maneuvering and at first I though 'Hey, this guy flying a solid BFM' but... soon after, his creativity kicked in and I was forced into A/G gunzo: https://youtu.be/KEtOk2c1wfI

Yes, I'd say you keep the hook up... You also might want to flip the 'hook bypass' switch to 'FIELD'. (located at the bottom left corner of the left quarter panel) This way your AOA indexer will not blink when you have your landing gear down. When you decide to lower the hook, the 'hook bypass' switch will snap back to 'CARRIER' (electrically held).