marzzz

perfectly clear same problem and already reported bug or realistic logic ?

hi the bug of the UFC radio - cold start isn’t solved yet …. could we hope ?

So This is a track replay (FLIR on Left DDI and A/G radar mode sea on Right DDI , with a ship target) 1 - Sensor switch right - create a TGT with the A/G radar (TDC depress) - a designation cross appears 2 - Sensor switch left - move the TGT with the FLIR - the designation cross on the A/G radar page, moves 3 - Sensor switch right- back the the A/G radar page and move the TDC on the target ship 4 Try to make a GMT track on the target ship (sensor switch right ), it doesn't work 5 TDC depress on the target ship : no designation cross (??!!) but now it's possible to make a GMT track with sensor switch right 6 Sensor switch left - back to FLIR page , the designation cross is now on the target ship I would have thought that the TDC depress would create a new designation cross GMT test.trk

Hi working on A/G radar- ATFLIR combo, i noticed a strange behavior with the radar when a TGT exists , a designation cross is present on the A/G radar page. right But if i make a TDC depress on an another target with the radar , no designation cross appears. however, a TGT seems to be validated in this case. Proof , the GMT mode track works on the second target ( sensor switch) I think that the missing designation cross is a bug what do you think about ? ( Ps : if i undesignate before validate the second target , it works perfectly) Thks

thanks for your post, bones i globally agree with you and it’s quite logical. but with my own tests , the MAVF follows the GMT track . And in this case , the MAVF update is automatic, you don’t need to TDC undesignate/redesignate

yes it’s true , Mav E works well with ATFLIR auto track but with ground radar too. it’s not the case with with Mav F

Hi i’ve noticed that an uncaged Maverick IR (AGM65-F) couldn’t follow a moving target designated by a ATFLIR pod (Auto track mode) while it works perfectly with the GMT/Sea ground radar. The only solution i’ve found is to uncage the maverick just before the launch ( inside maverick range , of course) 1- I don t understand why? is it a bug? 2- my feeling is that Auto mode of the ATFLIR is not very useful ( i didn t try the litening pod). So, except a bug, the best combo seems to be ATFLIR pod slaved to the ground radar , even with the AGM65-E (laser). What are your feelings about it ? thks

same problem for me. Tried with the instant mission fighter intercept. Strange thing, TMS right works the first time i played the mission. And after TMS right is broken

mods ? i am using SRS and tacview , nothing else i have the memory that with the F16 , i pointed a strange thing. i reported before i will send you my dcs.log tomorrow

Hi These are 2 tracks on open beta , one test with VHF and one test with UHF Thanks test UHF.trk test VHF.trk

ok i checked when i set the wrong position, the comm works but it is bugged ( ok for text but the voice is breaking) another strange thing when i put the fm radio on homing position , i can still communicate with the tower (fm radio) normal ?

ok i will check it

i know , i forgot to say that « easy radio » is disabled on my dcs

Hi i’ve just discovered the huey . i notice that the position of the intercom selector switch doesn’t change anything. For example , i can communicate with the tower during a cold start with the VHF AM receiver , even the intercom switch is on PVT, INT , 1,2 positions. The VHF AM should to work only with the 3th position of the switch. is it a bug ? Thanks

Hi guys i use the stable version. i ve just noticed something with ATFLIR. in INR mode , when i undesignate i go back to the snowplow mode. in scene or track mode , when i undesignate i go back to a pseudo INR mode without TGT. I don’t remenber how was the behavior before last updates. I think that it would make sense that undesignate from scene or track mode leads to snowplow mode Bug ? Thks