[DE] T-Bone

Look in the rearm menu for MMA

Can you please make a short trackfile of it? I personally find the stability very good since the last patch.

Thanks

One idea for the Chinook's sling load would be if it were possible to change the cable length and attachment points via the armament menu, like the Apache's internal tank/FCR(soon). You could create a "Cargo Station" field in the menu and select different configurations there: - 1 Hook: 10m - 1 Hook: 15m - 1 hook: 20m - 2 hooks: 10m - 2 hooks: 15m - and so on... Just as a thought

Good to know, thank you

I just tested it myself, same behavior as you and AndreNL, only when the Hellfire tracks a laser is it possible to switch the ACQ to SKR.

Test it with an active laser from a drone or similar, then the selection of the SKR will work. I think there is a dependency on whether the missile follows a laser or not.

With reference to the following bug report: TSD Point Rings - Bugs and Problems - ED Forums (dcs.world) If the bug of the TSD rings will be fixed, it would be good to check the behaviour when sending via datalink. As described above, the TG arrives but no rings are displayed even though they are set.

Can also confirm the bug, no more circles are displayed around your own created points. missing_rings.trk

Possible state bug when switching the radar ELEV between AUTO and MANUEL: - In AUTO mode, targets are detected and displayed. - After switching to MAN and changing the ELEV, FCR no longer finds any targets - Reset to AUTO -> Ping again -> No results - Change again to MANUEL -> ELEV remains the same as before -> Targets are recognized again. fcr_manual_range.trk

See last FCR-Video in the description: NOTE 3. We will add the FCR to the reloading pop-up.

Roger

Bug is still present in 2.9.1.48335 zulu_local-time_bug.trk

Bug is still present in 2.9.1.48335 mi8_multicrew_slingload_2.trk mi8_multicrew_slingload_1.trk

When transferring target information via a data link, an error occurs in the distance circles of the created target points. Settings: TSD -> ATK phase THRT DISPLAY -> THREATS & TARGETS COORD SHOW -> ENEMY UNITS As an example, an S6 is created in the TSD, the creator displays both the red and yellow circle as well as the symbol correctly. This TG is now sent to another Apache via POINT-XMIT. This receives it and also sees it as a declared S6, but the two circles are not displayed. The error is generated in the same way if the other Apache also generates such a TG and this is subsequently sent to . Trackfiles: datalink_bug_cpg.trkdatalink_bug_pilot.trk

I have noticed a strange behavior when refueling with the full auxiliary tank Tank. As soon as it is equipped and flown empty, only 410lb instead of 660lb are refueled. To have a full auxiliary tank again, you have to deselect it in the armament menu and re-equip it, then it has its full capacity of 660lb again. ah64_aft_bug.trk

Why don't we need it?

Du kannst z.B. bei Cutworks deine DXF-Dateien hochladen und Materialien auswählen: https://www.cutworks.com/de/materialien-laserschneiden.html

Thank you for your detailed explanation @Gunslinger52 & @FalcoGer, everything has now worked with the Datalink.

We were recently able to use the Lima in flight against ground targets without any problems, but noticed that our TG points were slightly different from the CPG to the pilot TSD display. I created a TG on a building using a SAT card in the TSD. My CPG also saw the TG, but not on the building, but to the left of it. To me it looks like with CPG and Pilot we have two separate INS systems communicating with each other and then with Desyncs we have this discrepancy.

Thank you for your explanations, we will try to set up a datalink via FM2 this evening.

We know, we have also tried to solve the problem using the TSD settings but without success. We haven't been able to reproduce it yet, but we definitely had the same problem as Mivina.

I tried the ATT mode yesterday and also noticed that the correction did not bring any improvement.

We also recently had the case that the pilot did not see the CAQ of the CPG.

Bug is still present in DCS 2.9