AMVI_Hawk

MULTYPLAYER -> Hi, Is there any information / update about the issue of the VASI / PAPI not switching ON / OFF according to the calls to ATC? I refer to HATZOR where any call on ATC frequencies remain without reply. Maybe wrong information on Airport map (250.600 and 118.550)? In single player the lights go ON but ATC still no reply to the calls

This happens with GBU38 also

Yes, the problem of the terminal guide of SLAM still exists. On the changelog of OB update 2.8 you find: DCS: F/A-18C Hornet by Eagle Dynamics Ongoing tasks for later updates: Correcting AGM-84D, AGM-84E, and SLAM-ER behaviours. We just need to wait Kind regards Hawk

Hi, maybe it is better to not circle around the target because you are stressing the TPOD to search and maintain his look on a point while you are continuing to change your offset related to it. It is better to slave first the TPOD on WYP while you are going to it and after that circle around it, if necessary, not the opposite. My two cents

https://forums.eagle.ru/showthread.php?t=283532 New improved INS alignment

Pur selector on IFA

Well, I am able to get the coordinates from the map but the informations I need are in a different format than the ones shown in DCS: Refer to the data exposed in my first post. Coordinates are not in degres.decimals and referece of easting and northing ....where to get them? I think I need some words for the developpers if possible. Awyway, thanks for your interest Kind regards

Hi, is it possible to get some information about the map? Ex: inside the Caucasus Theater there is "Caucasus.MapCoords.lua" file with useful data : a = 6378245 b = 6356863 k0 = 1 long0 = 33 feasting = 499600 fnorthing = -1800 dcs_origin_x = 599517 dcs_origin_y = 4998115 LatitudeCenter = 43.6966666666667 LongitudeCenter = 32.96 WinterTimeDelta = 3 SummerTimeDelta = 4 utmzone = 36 Can we have same data about Syria? Thanks a lot for your collaboration Kind regards AMVI_Hawk

:thumbup: Thanks a lot Swift, all clear :thumbup:

Yes , surely ok with LGB but how to use AUTO with the MAV-E? Is it possible? I saw that now only TRIG option is available if MAV-E selected and for me it is not so user friendly a) lock a target in OPR MODE (so you maybe can slew the TGP again) b) swap SOI to MAV c) start Lase with Trigger in order to lock the MAV since here all OK Consider that your lock is made far away from the target and, while your are approaching it, you maybe need or want to refine your lock, helped by the increased image on the FLIR. At this point you need to slew again with the TDC. So: d) stop triggering e) change SOI to FLIR f) restart triggering/Lasing g) refine your lock h) in the same time trigger and fire the MAV (not so handy) Well, last but not least, it would be very helpful if ED will publish a Weapon Check-list so we know how the POD is intended to be used, according to the documentation in their hand. So many tutorial on youtube (thanks to all for your good job) but at every patch most of them become outdated. Kind regards

Hi, I did not find something related to this issue so, I post this one. First of all, on previous video about MAV-E, from 12 to 8 months ago, I noted that the second MAV to be fired is CAGED. This seems to be correct because the cover shall protect the camera/sensor of the closest MAV from exhaust gas or dust becoming from the fired MAV. But now, after uncaging the first MAV, all the other remain UNCAGED , notwithstanding trying to CAGE them selecting the MAV page with the Sensor Control Switch. Sure not related to this, I also noted that sometimes with TDC depress when on FLIR page (SCS diamond on FLIR page) to select one target, this action fire the laser. Is the CAGE/UNCAGE issue a bug or simply a switchology matter? Thanks for your attention. Track enclosed AMVI-DCS-C-AGM65E-TRAINING.zip

All clear Thanks

Hi gentlemen, Sorry to re-open this issue. I do not understand why if my sensor is on the FLIR page, the hotas command RAID /FLIR FOV does not function correctly. I am operating over the FLIR not over the MAV65E. Furthermore, the DDI buttons operate correctly: it is only the hotas command which is inoperative. Notwithstanding the rule that the MAV65E take priority I think that the hotas function RAID/FLIR FOV should work. Kind regards

Hi, Unfortunately you're not alone. Yesterday, during a multiplayer mission over NTTR: takeoff regular for all people while someone experienced an "underground landing". We hope to receive a fix soon.... Regards