Anubis_94

Hello, A week later, do you need more infos on these 3 reports? A thread per bugs ? The range issue is painful to sort targets in close formation.

We also encountered this render limitation. So I would like to add a voice to this issue, as we can use and guide a SLAM-ER beyond the 50Nm mark. Not being able to see the targets via its seeker nullify the ability to do man in the loop guidance.

Added another side report for the tracks range that isn't stable. Tell me if you want a dedicated post (but it will be the same replay).

Hello We spotted what seems to be a variant of this bug : After firing multiple 120, missiles flyout don't align correctly with the target of the missile when we switch LS-DT2. Side report: The range of the tracks isn't stable Side report2: The lock/shoot indicator only briefly flash "SHOOT". It should remain steady as target is locked and within Rmax when A50 is hot (at 1min). Manual : Track done on 2.9.20.15384 test_RDRMissileFlyout.acmi test_RDRMissileFlyout.trk

Hello, While playing with MS on the ground, we spotted that MSI trackfiles were showing speed 0. Digging into, it seems that the speed of a MSI track is dependant of our own plane speed. Here: an A50 orbitting FL250@M0.7 MSI trackfile display first speed 0 while on the ground After takeof, at 280kts, MSI trackfile displayed M0.5. Then I slowed down to stall around 160kts, speed of trackfile slowed down too, to a M0.3. This was also the same M0.3 seeing when I was taking-of (when plane crossed the 160kts). It never displayed real expected M0.7 Track done on 2.9.20.15384 test_MSI_speed.trk test_MSI_speed.acmi EDIT: Added that oberservation trackfile speed <-> place speed when crossing 160kts

Thanks As in entering CAC mode lift the SIL, I guess firing a missile is also an action that, while not lifting SIL as is, explicit ask to transmit over SIL I don't know about IRL RWR, but do DCS RWR pickup such transmission ? I cannot test right now

Hello, After testing the launch on MSI only track file, I observed that fox3 are well updated in flight on the track file with the radar in SIL mode. I pushed the test by puting the radar in STANDBY mode (with the rotary), and here, the missile is no more updated. Is it normal? (plane -> missile emission aren't affected by SIL ?) is it a bug ? (SIL should stop all emission ?) Doc isn't explicit about it Video: 5 120C fired on a circling target, always on the hot leg. First 3 in SIL mode, they change their trajectory to the right last 2 while puting the radar in standby after launch. They do not change to the right test_MSI.acmi

As simple as it is. F18 manual here, the launch constraint circle is explained, a 15° circle (mav launch above was 24° according to tacview): I though that MAV LKD was enough, should have re-read the manual to avoid a RTFM answer Thanks .

Hello, Sometimes, the maverick E doesn't track the laser even after : a well "MAV LKD" on the hud (anyway, the mav won't go if not locked) a target in front of the plane (~ -10° down) Laser code mav-TGP OK Here is a track on the 2.9.18.12899, as well a video and acmi. The issue is observed with the 2nd mav (2min30 mark) test_mavE.trktest_mavE.acmi

Hello, When exporting a .stm of a flight group with custom callsign label/number The .stm embed well the new label/number. But at import, newly created group based on .stm doesn't relfect label and number Group exported: Group after import in a new mission: Here are the .miz used to export, and the .miz after import. As well as the .stm (where BO 01/02/03/04 are well seen) Observed with F18 and F16. test_DL_Group_after.miz test_DL_Group_before.miz I would assume that all are generated at groupe creation.If yes, why include them in the .stm ? Maybe use the one in the .stm if numbers are free, then generate if number are already taken ? EDIT: I didn't see at first glance that STN is also not imported.

Adding one voice to a default.dtc, avoiding to go through the "open DTC" UI that is overkill when you just want to load an already setup one.

Thanks @Flappie It seems that on F18 the issue is also visible on the HMD. Would you be able to add it to your comparisons ?

Release at max range OK now. Thanks

Hello, I know that disk space isn't a great concern, but the .dtc is taking a lot more space than what it should. The exported json use way more space than needed, and take up to 270KB. It can be indented with a 2 or 4 space tabulation to easily use half the current space, 146KB. It can also be stripped from all these space and CRLF to take a minimal 32KB. Files attached, tested OK in game. JSON_Default.dtc JSON_Indented.dtc JSON_Stripped.dtc

Hello, F-18 manual, page 154 : The DTC manager input is a frequence, also seen in the json export : Understanding, there is nothing to pre-configure in the DTC for this radio mode.