WurzelGummage Posted February 16 Share Posted February 16 Reading Chucks Guide I was left with the impression that with the Litening Pod, that the RAID/FOV button on the HOTAS changed between wide and narrow FOV on a short press and CCD/FLIR on a long press, but I can't seem to make it do that. I have the screen with the pod display selected, the radar elevation does the zoom like it should, but RAID/FOV does nothing. Anyone experienced the same or know what if anything I'm doing wrong? Thanks Ryzen 7 5800x, RTX 4070Tti, 32gb RAM, Quest 2, Delanclip head tracking, Warthog throttle and stick with 100mm extension, TFRP Pedals, 34" ultrawide 1440p monitor. Av8b, F18, M2000C, FC3, F5, A4, UH1, UH60 Link to comment Share on other sites More sharing options...
AstonMartinDBS Posted February 16 Share Posted February 16 Check your bindings for the RAID/FOV/FLIR button and make sure that the DDI displaying the FLIR has SCS priority, which is indicated by the little diamond in the upper right of the DDI. I've tested it right now - changing FLIR FOV and switching CCD/IR works as described. [Modules] A-10C, A-10C II, AH-64D, F-14A/B, F-16C, F/A-18C, FC3, Ka-50, P-51D, UH-1H, CA, SC [Maps] PG, NTTR, Normandy, Sinai, Syria, TC [OS] Windows 11 Pro [PC] MSI Pro Z790-A, i9-13900K, 64 GB DDR5-5200, RTX 4090 24 GB GDDR6X, 2 x SSD 990 PRO 2 TB (M.2), Corsair 5000D Airflow, HX1500i, H150i RGB Elite, Acer X28, TM HOTAS Warthog (Grip@WarBRD Base), MS SW FFB2, Thrustmaster TFRP, TrackIR 5 & TrackClip Pro [Checklists] A-10C, F-16C, F/A-18C, AH-64D, Ka-50, UH-1H Link to comment Share on other sites More sharing options...
WurzelGummage Posted February 16 Author Share Posted February 16 Yeah, all set up correctly, I'll play about with it some more later. Ryzen 7 5800x, RTX 4070Tti, 32gb RAM, Quest 2, Delanclip head tracking, Warthog throttle and stick with 100mm extension, TFRP Pedals, 34" ultrawide 1440p monitor. Av8b, F18, M2000C, FC3, F5, A4, UH1, UH60 Link to comment Share on other sites More sharing options...
AstonMartinDBS Posted February 16 Share Posted February 16 Try to reproduce your issue and upload a short track of your try, so we can take a closer look. [Modules] A-10C, A-10C II, AH-64D, F-14A/B, F-16C, F/A-18C, FC3, Ka-50, P-51D, UH-1H, CA, SC [Maps] PG, NTTR, Normandy, Sinai, Syria, TC [OS] Windows 11 Pro [PC] MSI Pro Z790-A, i9-13900K, 64 GB DDR5-5200, RTX 4090 24 GB GDDR6X, 2 x SSD 990 PRO 2 TB (M.2), Corsair 5000D Airflow, HX1500i, H150i RGB Elite, Acer X28, TM HOTAS Warthog (Grip@WarBRD Base), MS SW FFB2, Thrustmaster TFRP, TrackIR 5 & TrackClip Pro [Checklists] A-10C, F-16C, F/A-18C, AH-64D, Ka-50, UH-1H Link to comment Share on other sites More sharing options...
Trigati Posted February 16 Share Posted February 16 Do you have mavericks loaded? I think when you do it doesn’t workSent from my iPhone using Tapatalk 1 Link to comment Share on other sites More sharing options...
WurzelGummage Posted February 16 Author Share Posted February 16 That might be it then. I did have Mavs on. Ryzen 7 5800x, RTX 4070Tti, 32gb RAM, Quest 2, Delanclip head tracking, Warthog throttle and stick with 100mm extension, TFRP Pedals, 34" ultrawide 1440p monitor. Av8b, F18, M2000C, FC3, F5, A4, UH1, UH60 Link to comment Share on other sites More sharing options...
Solution rob10 Posted February 16 Solution Share Posted February 16 To expand on the answer above: when you have a MAV SELECTED (IR or LASER) in STORES, it takes complete priority of the RAID/FOV button. Doesn't matter if the MAV is up on a DDI or if a MAV is up on DDI but doesn't have priority, the RAID/FOV button will work on the MAV (which really only does anything for the IR MAV since you can't change FOV/sensor type on LASER MAV's , but behaviour is the same for both). You CAN have them loaded and still use the RAID/FOV button to change FOV/IR/CCD on the pod as long as no MAV is selected in the STORES page. 2 1 Link to comment Share on other sites More sharing options...
WurzelGummage Posted February 16 Author Share Posted February 16 8 minutes ago, rob10 said: To expand on the answer above: when you have a MAV SELECTED (IR or LASER) in STORES, it takes complete priority of the RAID/FOV button. Doesn't matter if the MAV is up on a DDI or if a MAV is up on DDI but doesn't have priority, the RAID/FOV button will work on the MAV (which really only does anything for the IR MAV since you can't change FOV/sensor type on LASER MAV's , but behaviour is the same for both). You CAN have them loaded and still use the RAID/FOV button to change FOV/IR/CCD on the pod as long as no MAV is selected in the STORES page. This is exactly the answer I was after, thanks. 1 Ryzen 7 5800x, RTX 4070Tti, 32gb RAM, Quest 2, Delanclip head tracking, Warthog throttle and stick with 100mm extension, TFRP Pedals, 34" ultrawide 1440p monitor. Av8b, F18, M2000C, FC3, F5, A4, UH1, UH60 Link to comment Share on other sites More sharing options...
Tholozor Posted February 17 Share Posted February 17 In addition, the same is also true for HARMs. 4 REAPER 51 | Tholozor VFA-136 (c.2007): https://www.digitalcombatsimulator.com/en/files/3305981/ Arleigh Burke Destroyer Pack (2020): https://www.digitalcombatsimulator.com/en/files/3313752/ Link to comment Share on other sites More sharing options...
rob10 Posted February 17 Share Posted February 17 11 hours ago, Tholozor said: In addition, the same is also true for HARMs. Thanks for that. I hadn't realized that one. Link to comment Share on other sites More sharing options...
Recommended Posts