Honey

Happens to me every time. F-18's throttle and stick don't react to controls after it's been launched from a carrier for a second time. Pedals do react to input though, and also input is definitely still being registered by the game as it's visually observable in options->controls->assign axis, while the bug's pushing the jet to the upper edge of the stratosphere.

Oh, I don't see his sig, probably due to disabled option in forum settings. But, yeah, there we have it. I had those micro-stutters in DCS when I had 16 gigs, yep. Well, my previous comment is a valid advice. Tests must be conducted in controlled and more or less reproducible env., to isolate the culprit. But it very much looks like there is just not enough ram and swap is on something rather slow. I myself play on 4770k with 32 GB ram and swap on raid 0 2x MX500, which are one of the fastest 2.5 inch ssd's on the market. And, I play on 4YA with no more than 18 players online. My pc gives out 45 fps st and up to 83 in mt. No stutters on Caucasus or NTTR. Syria on 4ya isn't really playable for me, need 64+ gb ram. Enigma is 20 fps, simply because the number of players is insane.

I had micro-stutters in DCS, but in st. fwiw: if you're playing in MP on a server running a complex mission, and/or many people are online, your system consumes around 50 GB of system ram. If you have less than that, you have to make sure your swap is located on the fastest ssd in your pc (and nowhere else).

Yes, we reported the issue within some minutes of each other. Moderators merged the topics and picked my title (possibly inadvertently). I'm gonna test it and report if it's present, when I get the chance. In case anyone wants to test it themselves: the encounter was Su-27 vs. Viggen. The RWR in 27 were going off for mid-range SAM, but there were no such launches anywhere. In MT.

I personally reported this bug. The title of this topic was typed in by me. I know what I'm talking about. They may have fixed it partially, or something broke along the way. Hence, it is related (if the issue is indeed present).

Has this been fixed indeed or not? I flew in a Su-27 in MP on 4YA cold war today and RWR in it signaled about an incoming missile from an X (medium range radar), while I didn't see any launches nearby visually or on F10 map. It requires further testing, maybe I'm wrong...

I believe he spoke about SAM's hit rate in the game, not IRL.

Russian SAMs IRL do launch in mode similar to TWS. And, if it was indeed implemented in game, even the magic RWR we have in DCS wouldn't notify of a threat until it's too late. Maybe, the bug fixing process with RWR has dragged for so long because they're reworking SAMs to implement them more realistically, who knows.

This was probably connected to the same regression that made RWR defunct and is probably fixed with today's patch.

Subject. Happened in MP in MT. So I was RTB after launching 154C's. I was landing on CVN-74. First gave ACLS a go, but it failed and I had to intervene. I went on another try, landed it manually. I positioned the craft on the catapult and issued a command to rearm (8*154C, 2 AMRAAMs, 2 AIM-9X, fuel tank). While at it, I flipped the Test Light switch (the one that's on the right, next to the pilot's thigh). Clicked the the two resets, set stab to 21, off I went, retracted the gear normally, faps auto. Weirdly though, the craft started to sink as if the STABs weren't set to 21 or as if I would've touched the stick. I didn't - the FCS page was on my right DDI and I verified stab was at 21 before pulling on the stick. Then, suddenly, the gear handle started to blink and the rapid irritating "lower gear" beeping commenced. I lowered the speed, flipped the gear handle down. Gear went down. Then I upped the gear, and the warning and beeping resumed. Just in case, I tried to turn off ACLS, ILS, TACAN. Flipped the light test switch again. Tried another time to lower retract gear. Nothing helped. In such state, the craft didn't allow to launch another batch of JSOWs. Alas, this happened in MP, so no track. Alas, it's 4:24 am, and I just can't run such a complex test right now. The rep. steps are thorough and correct. If I didn't miss something, there is a bug in the 18, or maybe it's because of MT, or MT in MP. A lot of vars, yes, but something went wrong. I was flying the 18 past couple of days intensively, in MP, with a lot of landings, and never encountered this behavior. This was my first session in MT. So maybe it's related to MT (in MP).

fwiw, just wanna report that fps improvement is colossal: from 45 -> 82 fps in mp on 4YA with 20 players. Brilliant job, ED!

16 gigs of ram on PS5. If there was a DCS for it it either would have to be something really limited, or DCS would have to be entirely reworked. I'd prefer ED to optimize the game, so we'd all benefit from it, but it's a lot of difficult work, if at all possible.

Subject. Happened in MP, had no warning from launches of S-300 missiles from ships, and, no active track warning too. Missiles were visible in the F10 map, and also tracking and killing quite well. Confirmed in F-18, AV-8, Su-27. By two separate players (Plisk and myself). No track right now, if anyone can test and upload, please do.

Can we have an option to not render Vikhr smoke, if smoke is indeed the issue? As a special option for Ka-50 and Su-25T modules. Let it be on by default. We'll disable it for ourselves then.

MAXsenna, np, I learned something new from your input. Cheers!