Muchocracker

You're overriding the waypoint selection and the autopilot by actioning the TGP into an AUTO track. Any designation source will do this. The whole system revolves around having one or the other as the primary selection. You have to undesignate the SPI in the HSI to reset everything and use auto sequence again. Turning off the TGP is not going to do that. Nor is changing master mode

Maximum trap weight is the #1 cause that i am seeing from most people crunching their gear, the other part is people slamming it on the deck and not flying the glideslope. -You have get the jet under 34 thousand pounds (use the checklist page, it also accounts for external stores automatically) -Follow the glideslope all the way down. Easing Guns is a very common bad habit that a lot of people have (inlcuding me sometimes). Easing Guns over the roundown above the unrestricted weight is also going to exceed the strength safety margins of the gear. Keep that one also in mind.

Aircraft only auto trims to 1G when the flap switch is set to auto. With Gear and Flaps down it's more trying to nullify pitch rate instead of targetting a specific G load. And you are correct. Airspeed should be the last thing you look at when getting the jet on speed. The VV and the E-Bracket are the most important, while airspeed is almost entirely dependent on your gross weight.

that's why the deck has marker lights on the landing area perimeter and the centerline, that is what you're flying off of. Not how illuminated the deck is. When the carrier switches to case 3 approaches it automatically turns those lights on when somebody calls in. Some servers will turn those lights on manually through scripting. Was added in recent updates.

huh. I knew about the stick being locked. Never noticed the throttle was. Replicated it myself and reported that additional issue.

So something i wanna understand (been reading for some time now into radar theory to understand most of the concepts) is the pulse intregation schemes between HPRF and MPRF. What's the reasoning for HPRF using less CPI's and not using binary integration vs HPRF with uses much more and but only effectively requiring 3 detections out of 8 with binary integration? Could never really find an answer on this.

you'll know the jet isnt in A/P when nothing is colonized on the UFC page. CSS you'll only know if it's engaged when the jet "feels" sluggish in the controls, CSS dampens the inputs in both pitch and roll. Hitting the paddle switch exits both.

I've used it a couple of times on grayflag but no when other people were trying to land at the same time. There were issues with it straight up not going into ACL RDY at the lock on point after it was released. But idk if that's around anymore, will have to check that out. As kind of my final piece here. I'm almost certain that the cause here for some of you is you're just out of TILT limits as wags and i mentioned previously. You have to be much closer to centerline for the ACLS controlled phase of the approach or else the jet is going to be commanded to roll super hard and get kicked out of A/P. You have to remember that the ship is moving away from you and slighty left to rightbecayse you are following a bearing line that matches the angled landing area. You have to constantly adjust to the right to keep on centerline. If you're trimmed out and on speed it's very easy to do. But if you're fighting to stay at altitude and be stable trying to use forward stick to stay on speed i can see why you're having a hard time. Before trying to attempt carrier landings, get comfortable with flying on speed and the transitions between. It will help tromendously.

i already see it You are so out of centerline that the autopilot system is freaking out when engaging it and it is kicking it out out coupled mode. See that line to the right of the velocity vector? You need to have the VV on that line. That is the centerline of the landing area on the ship.

If you are in an autopilot mode before the ACLS latch you have to completely disengage autopilot and then reengage coupled mode to get it into CPL P/R. Otherwise it stays in CPL HDG or it freaks out and kicks the jet out of AP

This is not a bug, you are making a feature request. Avionics behavior is intent to match the OFP's in accordance to available documentation and that alone. Not to "personal needs"

....why? In case 1 pattern's your rolling out into the grove at most 1 mile aft of the boat. There are so many issues with try to doing it this way let alone getting the ACLS to stabilize before you're already right up on the ramp. All of case 3 happens at 50 DME and in. Not "300" where are you even getting this from??

Care to send that source?

If you have links to said papers and brochure with relevant info, post them! if they shed light on info that isnt already in the 742-100 or the 600-100 then it's all the better. Especially if this debate on no radar amraam shots can be put to bed

post a track please. Nothing can be looked at otherwise

i don't think that strongly implies anything. There's lot of distinction in the available manuals between MSI trackfiles and the A2A weapons operation. Would we not see a lot of the language here interlink these things? Especially the amraam. There's no references to any other "type" of trackfile tho. And again my question is why would NO RDR be a highly visible cue that's displayed in your face to tell you this if it wasn't important for post launch amraam support. i don't see that as particularly relevant. We know that the amraam stops taking into account the mothership support past a certain point in the terminal homing stage. Even then support by even slower updating offboard tracks wouldn't be helpful at all, detrimental really. Notching isn't relevant for the ownships sure, but it's still very much an issue for ARH seekers (definitely to a lesser degree than we're dealing with in DCS tho imo) That's not quite what he said tho. He goes even farther to say that the radar could be silenced and still transmitting midcourse datalink. I'm not as knowledgeable on how the MDL is transmitted, whether that's done by FM encoding the information into the pulses or by some other antenna. But you'd think this would have been at least vaguely referenced somewhere in the maintenance principles of operation manual no? Overall i don't see any meangingful or convincing references for this. And at minimum one piece of reference that would point to the contrary.

I mean it could be argued that IS the inhibit. Think about it this way, why would you need to know that the L&S did not have radar contribution if it didn't matter for an amraam shot. L16 track quality is also pretty trash with slow update rates. @Harker has done more research on MSI than me, he can chime in on this.

Best way i've found to do it is to have your TGP selected, and then slew it to the position of the TXDSG on the SA page using that small box that shows the designation position. far as i know selecting a members designation is a much later OFP than our hornet. Think it might have even been as late as the rhino

There's no actual source i have ever found to prove this. The assumption is the radar still needs to be a contributing source to that trackfile to shoot an amraam at it. But even just having anything else that we're missing from MSI would be a huge addition (mainly the trackfile ranking from other sources that onboard)

no, this is not true. And is an issue with TNDL All link-16 donated tracks contribute to MSI regardless of source(which that part is true, we don't have this part of MSI yet). Link-16 itself is limited in bandwidth so it cant support everybody donating to everyone at the same time. It's the reason why the DONOR list exists, so you can allocate track donation bandwidth to relevant aircraft. C2's donate to everyone per its Jset, F/F's have to be opt in.

There is a confirmed issue with OAP's and has been reported

Aircraft not set as donors do not contribute donated radar tracks to your MSI. You get their PPLI and only their PPLI Donors contribute trackfiles. Members transmit the SPI's and such

yeah that about tracks with the notorious irl unreliability. It's not gonna do well in high cross winds

I know there used to be an issue in the past with both HB and ED's wake turbulence being doubled and amplified, that's probably the case with the burble as well which was added specifically to the SC module quite a while ago. As above advised, turn off the base game wake turbulence.

Because you were also slotted in the hornet. You could have set the LSO platform view keybind under the hornet settings