Muchocracker

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

very much should have been included from the getgo

you can hit the salute key at any point as soon as you're under tension. When throttle goes to at least mil then it starts the launch sequence. The AB Detent special option was the one causing the bug where it required AB to launch.

There's symbology that appears when you DO bug them while having a weapon selected chief. Safety doesnt automatically mean you cant do it. It's launch and steering for a reason. Finding a tanker, obscured vision (clouds), or just general rejoining with formations after you get separated. There's plenty of reasons to want to track a friendly.

The atflir never had the bullseye reference on its display, at the very least in our OFP hornet

Legact hornet never used the D-704 refueling pod. Only an added capability with the superhornets

There's so much missing from MSI that it compounds on the issue of the system ranking friendlies as the priority 1 trackfile. Right now it's only considering the radar trackfiles in the ranking when it should be all sources including C2 donations. If we had this a friendly would pretty much never be ranked #1 unless there's literally only friendlies to rank. You shouldn't be using TWS as the primary mode anyway. The system is going to automatically switch from RWS to TWS on the first amraam shot and then you're fighting the remainder of the engagement in TWS.(we still need this too) bottom line tho, it is correct that friendlies are counted in the MSI threat matrix and will be ranked accordingly, they are just at the bottom of the list. The problem is that threat matrix is wrong, on top of all the other features of MSI not being present contributing to it. Hopefully it won't take 6 years to at least fix that matrix.

lol. Maybe in another 5 years they'll do it

If you are still within the seekers FoV, then you're still getting hit with emissions and It's going to keep setting off the RWR, this is basic functions. It doesn't know if the missile has lost you or not. If the indication doesn't change azimuth as you turn the jet then that is a separate issue.

hey @Buzzer1977, is this a new bug that you've encountered after the most recent patches or is this reocurring?

so with the airio extension i cannot get the "Radio Tune" commands to show the hell up in the editor. Im trying to train the voice recognition so i can actually use the command. How do i reset the keywords so i can start from scratch on this

i wanted to train the voice recognition system on the radio tune command because it doesnt ever get it. But i cannot find the command in the list in the editor tab