uther419

F18;was blue f,16 was red

Sounds good, I will add the track tonight

Not sure if this has been seen or is working as designed, Doing f16 vs f18 BVR, the interrogator allows a "god" view against the bandit. TMS left press causes yellow unknow to appear at ranges up to 100nm. The interrogator works during emcon quiet and jammer operation. When coupled with TMS up hold and press allows the f16 in a 1v1 BVR fight to have a massive advantage to search and find a target. I feel like the interrogator should make a null return / the range should be much shorter. At the very least, the interrogator should not work during emcon modes. Thank you! See attached screenshots for example Screen_221108_221545.jpg.url Further, it the interogattor seems to ignore terrains. Opponet was using terrain masking and i was able to find him while also flying NOE

Amendment to my claim on TDMA, 127 should drop the time feature of TDMA and act as a scan of the channels but that needs to be manually input. 127 is the default for some radios. If so I think their needs to be more guidance on basic DL config, especially with the radar adjustment.

in that case if ED can confirm that 127 is TDMA off, this would explain some of the hornets issues when it comes to AWACS and flight DL information coming up. If that TDMA is off, then the awacs would be the controlling station so the f18 is dependent on the awacs being present for DL, vs true link 16 does not need a constant host, it can adapt and heal.

I have no idea how it is in the real hornet, but I know for link 16 DL the nets are labeled 0-126 for a total of 127 nets. Currently the hornets DL nets are labeled 1-127. I don't think that's accurate based on Link 16 standard being the common operating picture for aircraft, and materials I have read saying the net naming is 0-126. Further # 127 when set as net number should be turning the TDMA function off for the DL. On a side note the Viper can do net 0 but it also gives 127, thus creating 128 nets, which is also not in line with the link 16 standard ( *Viper is correct, but #127 should turn the DL capability off*) Cheers

Roger, I have ran into it 3 time sin total in the past 20 days. I will try and go up tonight and replicate it, Have erased my saved game folder and let it repopulate to see if that was causing issues.

got screen shots! this one is as the *bug* began (note frame rate counters top left) The one below is after i hit the FCR button. I hit pod first and it had no effect. This was post landing being on the ground for about 5-10 minutes after repair and rearm while i was fighting my ins. After i HIT FCR FPS shot back up to normal range of 40-60 No new track, unless you want a 4 hour gameplay lol Furhter Screenshot of switches getting stuck

I was using 32 and 36 today, i also use 127 for my home base. TTI SOCAL 3

Sounds good, I'll see if I can reproduce and get some screenshots and another track

See attached Track File, as per title. TTI SOCAL 3 Syria. Reminiscent of the mig 21 Bis ground clashing with Radar bug. Landed master on radar on pod on ( but in Nav mode) Had to hit my throttle on / off detent to switch to turn the jet off to get out of it. (also minor bug with switches on startup. While holding FLCS Light test Switch that is momentary with left click, right click mouse on FLCS BIT it will lock the momentary switch into place upon release of both buttons. Once clicked again switch will return to postion.} Cheers. https://1drv.ms/u/s!Auwnxwsp8rdD8U-V97tMr_yyMRrc?e=Gg09Tw

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online. (live.com) Link to track file should be towards the end of the flight. Cheers.

I was playing OB and don't know if how to get track files, unsure what other info I can provide dev team

Was Flying Syria On the TTI SOCAL 3 PvE server the other day and ran into this jem. Took a manpad hit and at first glance lost my center and right wing fuel and my GBU 12 rack and 1x AMRAAM. Still flyable so finished air to ground mission. On RTB jettisoned all stores then decided to try A-A Pod mode out, locked my buddy then went into the F2 and saw my pod was gone. See screenshots attached.