captain_dalan Posted March 20, 2021 Posted March 20, 2021 This has been running through my mind for some time, but it never really came to me to ask the question when browsing the forums. Namely, with a valid ISL data stream, when clicking on the Awl/Pcd, the TID repeater shows data on the source (in this case carrier) position relative to the plane, as well as range. On top of that we get ILS needles on the hud and the VDI. But, sometimes, the range of the carrier doesn't show on the TID. And i can't seam to figure out why. I tend to follow the same procedure when approaching the carrier. Requesting inbound, see you at 10 when close, waiting for signal is Charlie, then going behind the carrier and starting the landing procedure. The needles are always there, but the range is sometimes not there. There seams to be a correlation between this and a lack of kiss off and call the ball options in the comms menu. Even when i do call the ball, i still get the no ball call (BC) in the LSO grade. So......am i missing some crucial step? Something obvious? Modules: FC3, Mirage 2000C, Harrier AV-8B NA, F-5, AJS-37 Viggen, F-14B, F-14A, Combined Arms, F/A-18C, F-16C, MiG-19P, F-86, MiG-15, FW-190A, Spitfire Mk IX, UH-1 Huey, Su-25, P-51PD, Caucasus map, Nevada map, Persian Gulf map, Marianas map, Syria Map, Super Carrier, Sinai map, Mosquito, P-51, AH-64 Apache, F4U Corsair, WWII Assets Pack
captain_dalan Posted March 21, 2021 Author Posted March 21, 2021 Quick update. Did some tests this afternoon. Same custom made landing mission, adapted from the instant action. The issue seams completely random. Step one, start mission. Switch to landing mode. Switch to AWL, range shows. Quit mission. Step two, restart mission, repeat procedure, range doesn't show. Quit mission. Step tree, Restart mission, repeat procedure, range may show, or may not. Same goes for Tacan range BTW. If range shows on AWL, it will on Tacan and the other way around. And there does seam to be a no ball call, when the range isn't there. But seeing how ball calls seam to register extremely inconsistently, i can't tell for sure. Modules: FC3, Mirage 2000C, Harrier AV-8B NA, F-5, AJS-37 Viggen, F-14B, F-14A, Combined Arms, F/A-18C, F-16C, MiG-19P, F-86, MiG-15, FW-190A, Spitfire Mk IX, UH-1 Huey, Su-25, P-51PD, Caucasus map, Nevada map, Persian Gulf map, Marianas map, Syria Map, Super Carrier, Sinai map, Mosquito, P-51, AH-64 Apache, F4U Corsair, WWII Assets Pack
Manhorne Posted March 21, 2021 Posted March 21, 2021 From what I have been experiencing and what happens to me is the system is seeing the F-14 as the F/A-18... When I "Call the Ball" I get "Hornet Ball" back and even when I am lined up perfect in the landing I get Wave Offs and poor scores. I believe the system is bugged and it has not been fixed yet.
The_Tau Posted March 21, 2021 Posted March 21, 2021 @Manhorne I think it works for F-14B, but SC still sees F-14A as F-18C 1 Tau's Youtube channel Twitch channel https://www.twitch.tv/the0tau
Manhorne Posted March 21, 2021 Posted March 21, 2021 22 minutes ago, The_Tau said: @Manhorne I think it works for F-14B, but SC still sees F-14A as F-18C I am sure you are right. I have not flown the B to check.I have just been flying the A lately.
draconus Posted March 21, 2021 Posted March 21, 2021 There's also ongoing bug with TACAN turning off randomly on carriers. AWL shows TACAN range so it might be that. Can you share a miz or track? Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria
captain_dalan Posted March 22, 2021 Author Posted March 22, 2021 (edited) Here's the mission. It happens on other missions too, but this is the one i usually use for training. And yeah, it's in the A. Haven't trapped in the B in .......well.....ages. F-14APG_case_1_supercarrier Black Lions.miz Edited March 22, 2021 by captain_dalan Modules: FC3, Mirage 2000C, Harrier AV-8B NA, F-5, AJS-37 Viggen, F-14B, F-14A, Combined Arms, F/A-18C, F-16C, MiG-19P, F-86, MiG-15, FW-190A, Spitfire Mk IX, UH-1 Huey, Su-25, P-51PD, Caucasus map, Nevada map, Persian Gulf map, Marianas map, Syria Map, Super Carrier, Sinai map, Mosquito, P-51, AH-64 Apache, F4U Corsair, WWII Assets Pack
draconus Posted March 22, 2021 Posted March 22, 2021 For a Case I training it starts too high, too close and too heavy for my taste but... it works. Remember the TACAN is not preconfigured in the mission so you have to tune 74X every time. ICLS 1 and radio button 1 are already set. Alpha Tomcat is also properly recognized and I get "Tomcat Ball". Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria
captain_dalan Posted March 23, 2021 Author Posted March 23, 2021 Yeah. But on occasion i don't get neither tacan nor ILS ranging. It's completely random. Just restart the mission a few times. Sometimes switching tonav-to-landing->ILS or nav-to-landing->tacan will work, other times it won't. Wacky..... Modules: FC3, Mirage 2000C, Harrier AV-8B NA, F-5, AJS-37 Viggen, F-14B, F-14A, Combined Arms, F/A-18C, F-16C, MiG-19P, F-86, MiG-15, FW-190A, Spitfire Mk IX, UH-1 Huey, Su-25, P-51PD, Caucasus map, Nevada map, Persian Gulf map, Marianas map, Syria Map, Super Carrier, Sinai map, Mosquito, P-51, AH-64 Apache, F4U Corsair, WWII Assets Pack
draconus Posted March 23, 2021 Posted March 23, 2021 (edited) What ILS ranging? There's only ICLS and it does not provide range. In AWL steering and landing mode you get the ICLS crosslines on HUD/VDI and TACAN range on HSD, but only if you tune both right beforehand. Yes, I tried restarting missions a few times, always worked... but then it might be that: https://forums.eagle.ru/topic/264223-tacanicls-stop-after-time-numerous-ac-connecting/?tab=comments#comment-4589703 Edited March 24, 2021 by draconus Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria
captain_dalan Posted March 24, 2021 Author Posted March 24, 2021 20 hours ago, draconus said: What ILS ranging? There's only ICLS and it does not provide range. In AWL steering and landing mode you get the ICLS crosslines on HUD/VDI and TACAN range on HSD, but only if you tune both right beforehand. Yes, I tried restarting missions a few times, always worked... but then it might be that: https://forums.eagle.ru/topic/264223-tacanicls-stop-after-time-numerous-ac-connecting/?tab=comments#comment-4589703 Wait, does that issue occur even offline in SP? Modules: FC3, Mirage 2000C, Harrier AV-8B NA, F-5, AJS-37 Viggen, F-14B, F-14A, Combined Arms, F/A-18C, F-16C, MiG-19P, F-86, MiG-15, FW-190A, Spitfire Mk IX, UH-1 Huey, Su-25, P-51PD, Caucasus map, Nevada map, Persian Gulf map, Marianas map, Syria Map, Super Carrier, Sinai map, Mosquito, P-51, AH-64 Apache, F4U Corsair, WWII Assets Pack
Recommended Posts