[DE] T-Bone

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

Question, it is possible to use the datalink only on VHF SC? We tried today to use a preset on FM2 SC, here we always got a XMIT NAK FM2... after switching back to VHF it worked without problems. Edit: .miz-file where i tryed to make a datalink work over FM2. datalink_test.miz

One question is this bug reported or not? Could it be reproduced in the trackfiles? I can provide more trackfiles if needed, that's no problem at all. It would be nice if in 2.9 this could be fixed.

We almost always have the phenomenon that the cargo sometimes sways back and forth too much when we fly in MP with separate machines and carry cargo. It just looks weird, but it's never been a problem before. But in this case, when we fly in multicrew and attach cargo, it is absolutely stable for the pilot, but for the co-pilot it is a rocking and wobbling phenomenon. This also causes it to bang at some point in flight and the whole ménagerie falls out of the sky....

The picture I posted is directly from the DCS website, still available and with cargo hooks. But you are right, the CMs have been removed...

Ok, that sounds like a plan, then we won't have to work with the track file. I'm looking forward to the update.

Absolutely, an expansion of sling-load capabilities should be a MUST for the Chinook. At least you should be able to transport a howitzer with 2 hooks properly, as it can be seen in many videos. https://forum.dcs.world/topic/316912-variable-use-of-the-3-load-hooks/#comment-5128791

However, the big difficulty here is that the INS drift occurs only after a long flight time (for me and my cpg) and thus a "short track" is almost impossible to create, this should be taken into account. We will try to create a track file where the error is traceable, but I think it will be very long. If this is not possible because the track is not usable in its size/length, then we need a strategy how to track the bug.

I just wonder if we will have the possibility to work with the winch. The idea of being able to pick people up and put them down with it would increase the immersion factor even more.

Attached are the track files from both clients. I can reproduce this bug at any time. Mi-8_Pilot.zip Mi-8_Co-Pilot.zip

Was there ever a bug with this behavior?

We wanted to transport various objects by sling load in the multicrew with the Mi-8, and there was massive bouncing/swinging of the load and the rope every time the load was picked up. The video was taken from the co-pilot's seat, for the pilot himself everything was normal. After a few minutes in this condition, the attached load suddenly exploded and caused us to crash. slingloadbug.mp4

The L118 no longer falls through the floor, but dances around wildly when connected. See the track file in the attachment. Where is the sense here to leave such a faulty part in the DCS environment for almost 8 months? Even if it is from Razbam, where is your quality standard for DCS here and your standard against third party vendors? If it can't be fixed in the foreseeable future, then please remove it temporarily. Sorry for the harsh words. I know very well that an open beta is a test environment and bugs can happen, but this example just doesn't make sense to me. sling load bug.zip

I don't think this bug has been fixed yet, at least I can't see anything in the changelog. But as the title shows it is already reported.

We had the case yesterday that our target points drifted over time, so the bug is still present.

With the IAT, when a target is selected, the target box is first created behind the target and then "jumps" to the target shortly after. With the IAT there is also a problem when the LST is set to manual. As soon as LST-manual is activated, an immediate desync is noticeable for the pilot, in which then the TADS either stops, looks around wildly and partially shakes around. If a target was selected with the IAT during the LST-manual, the IAT can no longer turn cleanly to the target after switching the LST to off. LST_IAT-bug_cpg_seat.zip LST_IAT-bug_pilot_seat.zip

The fact that various vehicles can fire guided missiles is neither a core problem nor a comparison to a SAM position... If you move in their firing range and do not notice that you are illuminated, the opponent has the best conditions for a hit. That is why these systems have been installed.

Laser warning receivers should definitely be implemented before anything else, especially the large complex FCR We need more survivability against the missiles of e.g. T-72/BMP and co...

And what improvements for the flight model are currently being worked on?