YoYo

I'm out and about. Honestly, start the mission fly up toward clouds.... Done I don't use Instant mission but yes, I see it too, I have MSAA so these aren't DLSS or DLAA artifacts. It's possible these are old cloud sets that haven't been updated or something else. @Flappie I think it can be treated as an issue to be checked. DCS Instant Action - F/A-18 Hornet - Ready on the ramp / mission. test4.trk

Time has been sped up x3 at least in the stopwatch. Before the patch it was ok, now there is a problem. DCS 2.9.10.3948. How to repeat this? Switch MODE (to clicks) to stopwatch, start it. Seconds will be counted at x3 speed or something like that.

As it was written before. This currently does not work if connected to keys or buttons, it only works as a mouse click. This has not been fixed but will be in the nearest patch. The topic has already been discussed many times in the bug and problems section here.

No, put a track, so I can check then how it looks like for me.

That's right. A few things could be improved and added, but there was no any tragedy, Im sure, the map is cool and interesting. Interestingly - the biggest problem, which I reported myself, i.e. "stickers" of hand-made textures on the photo textures, are not really such a big problem looking at historical maps for DCS. Some time ago I noticed that Persian Gulf is made identically (so I assume it's the same team). These sharp transitions near Afghanistan are simply more visible, because they often concern green fields and a different color than the surroundings. For this reason, they are more visible, but the same technique is on the PG map and somehow few people were bothered by it. True, there the base is more desert so it is less visible, but the transitions are just as sharp and angular. I'm all the more curious about what the new patch for Afhanistan is supposed to bring for the current part of Afghanistan. I can expect: - better texture resolution in some current part (because that was sometimes a problem), - adding bridges (which weren't there), - an update for roads, - some bugs reported by users (but these are small fixes), - optimalization in urban area (I noticed drop of fps with with a high saturation of small buildings, it's a bit strange because it's less complicated than e.g. airports and despite that there is a lot of performance stutter) But what else? After all, the airports are done 100%, as are the cities etc. (well, maybe there are no monuments and relics, but that's not super important to me). So will they give up on those sharp transitions between the "handmade" texture and the photo? In general, the work I mentioned above would probably take a team of several people 1-2 months at most I suppose. So what are they changing there, after all, you're not making the map from scratch?

Animation problem on some HATs on collective lever. Supposedly they are already solved in internal beta. We are waiting

Thank You!

The year ends in about 3 weeks. It will be great to finally fly over Iraq during these 3 weeks !

Unfortunately, that's a problem, right. After all, we're half a year after the release, and not only was there no update to Afghanistan, not to mention the next part, which was supposed to come out in 3-month episodes. Theoretically, we should get the last 3 parts in January/February. If this is a completely separate Team that doesn't work on anything else, then the question begins to arise: what will they do from June 2024? Since they supposedly "listened to the players' opinions", the question arises in what way? Better communication would certainly be advisable because here there has been a change of plans and a change of promise to users, so we as a customer may feel disoriented.

Did you buy it? https://www.digitalcombatsimulator.com/en/shop/campaigns/

You can use autostart, I prefer always for campaigns and missions Cold and Dark start for example, it improves the immersion a lot.

Hi, show your settings, did you use DLSS? Did you clean metashaders and fxo folders too? Which preset is it? Btw. No any issue for me so far, so looks really strange, however Im using MSAA. DLSS/DLAA is known for creating artifacts, and not only in DCS so maybe this?

It doesnt work on release version. WIP still as I know.

Gazelle example, the same: Here the weight is also below 100%. But I have a curiosity. When I gave max fuel plus the heaviest loadout (weight was 105%), the helicopter stood still, moved slightly but at an acceptable level. AI waited until I took off, then flew with me without a problem, so we can assume that there is something in this behavior depends on the weight as well.

Next patch means December I hope (it will probably be in December at 99%, because Iraq is still supposed to come out, let me remind you ).

I agree, noticed the same. Before it was faster.

It also took me a while to find what it was about, but I now consider the problem diagnosed. In my opinion, it concerns helicopters on skids, Apache is ok too. AI waits for Player and does not start on its own.

Its not true, you can mix shortcuts and DX buttons even on the same controller, you have even 120 DX buttons to set up with TARGET. You need to get to know the software more deeply I think ;).

I know VoiceAttack but I dont like it, TARGET is a „virtual keyboard” which Im using for every module, I dont set up a buttons just shortcuts for every module (separate profile) what is best option for me. It takes some time but in the future it saves a lot of time, because I have a profile outside DCS, even if I reinstall DCS or developer changes something unless there is a shortcut vs mouse click problem, as in a few cases in KW recently ;).

TARGET (Thrustmaster) software.

I have in my HOTAS inserted function as Win+Home and End (so like on keyboard) and it works still without issue so , maybe it isnt present as buttons but it works still as shortcuts.

Reported. I think this is a larger problem that affects all DCS and AI skid mounted helicopters now. The UH-1 and Gazelle have the exact same problem.

I also checked UH-1, same situation. Generally it shows that there is a problem with the AI model in the case of ground start clearly. In addition, the model passes through objects despite the crash option being on of course. In any case the weight is below the maximum, so it's not. Something happened and someone didn't notice it during beta testing. AI (skids copters problem?) should wait for the player to move and so it was before. I tested also Gazelle - the same issue! I ask that you treat this as a priority, because as I wrote, it affects the entire environment in the case of missions and campaigns.

CH-47F ground start, the same, strange behavior. AI wingman, starts doing something by himself, spins in circles, when player (flight leader) stands still. That wasn't the case. AI wingman only took action after player took off from the ground. Mi-8MTV and Ka-50 III. Interestingly, in this situation we have the "old behavior" of AI wingman. AI does not take any action without the Player. Until you trigger the AI does nothing, he waits for your move. This was before the patch of 10/30/2024 for all copters. I can give more examples, but the model of take off (even if "Prefer take off vertically" is checked) directly from the ground has been broken. It's a bit strange that no one has reported this yet, because it's a pretty serious problem that affects a lot of other things like missions and campaigns.

head2head.mizhead2head.trknexttoeachother.miz Next example (with Kiowa). Mission plus track. Also I added the video: Importantly, I have been in talks with Polychop, this is not a Kiowa bug, but generally something happened to the helicopter flight model for wingman AI, if there is Ground Start (from the ground), this applies to the behavior of every helicopter from what I currently understand. This is a pretty serious bug that breaks many missions and campaigns that start from the ground (outside of FARP or Airport), and that wasn't the case. The November patch broke something in this behavior (from October 30th I think). @Flappie Can I count on support? I think it's quite a serious matter.