[DE] T-Bone

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?

After a long time of trying the solutions mentioned in the first post and others, it was finally the SSD on which DCS was installed. I got the idea that this was the source of the error when I copied mod files for another game to a folder on this SSD. I use this drive exclusively for DCS and for mod files. Here, the copying speed slowed down to a standstill from time to time, and after more attempts, caused the drive to become inaccessible. I installed a new hard drive and was able to copy DCS to it with some difficulty. After a subsequent slow repair, re-setting the page file and adding my old profiles, DCS is running stable again, no freezes, microstutters or BSOD.... Two thoughts on this: 1.Before the last patch DCS was running very stable and performant, apart from the known slow loading, and I also had no problems with the mods copied to disk.... it is illogical for me that the harddisk showed such a serious defect after the update. 2. A member of our squadron had the same phenomenon, and also here a move to another harddisk brought remedy for his crashes... and since his system is barely half a year old, I do not assume a hardware defect.

Problem solved, DCS runs absolutely stable and performant again.

I have only AMD 3000/5000 systems and here it says SMT, I will give it a try and disable it. If it helps with troubleshooting, I can do the saved game folder procedure again and create a log without copying anything into it. But the freezes and crashes were there unchanged, whether with or without mods. **UPDATE** SMT disables but still crashes and freezes. Logs.zip

Since I still had crashes with the new blank saved game folder, I copied it back in. Therefore, in the last log the path to the folders is given because I made several test flights afterwards. In the ST I also have the problems described above. With the last crash came now additionally a BSOD. Logs.zip

I did this after the release of the F-15E to fix the desync problems. This helped with the desyncs, but not with the freezes/crashes.... Edit: I tried again and recreated the save game folder, was hoping that after the DCS repair that would still help. Unfortunately no success, still crashes and freezes. Logs.zip

I am using DCS MT and since the last update I am having massive problems with crashes and freezes. So far I have tried the following: - increased the size of the page file - added regedit entries (TdrDdiDelay,TdrDelay) - run memtest86 for several hours, no errors found - deleted fxo/metashader folder - removed mods and did a slow repair of DCS - Uninstalled video card drivers, ran cleaner and reinstalled. Now I have several DX11BACKEND errors in the log and DCS generates freezes and crashes as well as stutters of several seconds. I am running out of solutions... Whatever was done with the last patch has resulted in me not being able to use DCS on my system anymore. dcsLog.zip DxDiag.zip

I also have a 5700 XT and multiple CTDs, do I have the same error or is something else the problem with my log? It is no longer possible for me to fly continuously, because the crashes sometimes appear after 2min, sometimes after 20. And all this started after the last update. dcs.log-20230701-202425.zip

I also have constant crashes, sometimes after 3-5min, sometimes only after 20.... A repair had had no success. dcs.log.old

For example, everyone in our group has this blurry picture in MT.

It would be great if we could get a solution or at least an improvement for this.

For me to understand, what does this have to do with the different maps?

Bug is still present, but only occurs in MP when a player joins. TSD-UTIL-LOCAL-ZULU time.zip

To pick up the thread again here, what is the progress of the ACM fix? Is there an improvement coming in the foreseeable future? Background is that yesterday on a night mission we had massive problems with the PNVS and its FLIR settings. We had to spend some time before landing getting the right setting for a reasonably good image, and even then it went completely black 10ft before touchdown. Is there a problem with the contrasts in general or is it still in development? Do you need additional trk files?

Cool, were you a pilot yourself or a crew member?