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.

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!

MAXsenna, I checked it out and if I understood correctly, it doesn't do what I was talking about. Specifically, it just shows nearest ATCs and their frequencies. It's the same as it is in DCS currently, but through kneepad and voice. It doesn't really address the issues I raised. But thanks for the tip.

Currently, as far as I can tell, Comms -> ATC menu list is populated with contacts based on proximity to player's aircraft, regardless of frequencies player's aircraft radios are tuned to. This, on a popular server with complex missions, like say 4YA, often causes the ATC you're tuned to actually not appearing in the list (it may be just a busy area, with numerous aircraft carriers, or when you've travelled a tad bit too far). Plus, the current behavior is plain and simple immersion breaking. I very much would like a rework of comms, that would take into account, when I want to initiate a communication: 1. the radio I'm using to initiate contact, may it be radio 1 or 2 in Bluefor, or the currently selected radio in Russian aircraft (on Mi-8 there are 5 radios to choose from, but the currently active is selected with a switch); 2. the frequency of the active radio; 3. the distance between my aircraft and the possible responders (ATCs, other aircraft), registered on selected frequency of the active radio; 4. line of sight between my aircraft and the possible responders (ATCs, other aircraft), registered on selected frequency of the active radio. So that the Comms menu then would be populated with only those contacts, that can be reached. Even if they're 900 km away (Yadro-1A says hello). Probably, it would be easier to pull the comms out of the / menu and make a separate widget for it. Because that would allow to draw like scratch pad for FC3 aircraft and thus fixing comms for those too.

Ramsay, That's the point, sometimes TPOD won't look at the point you're telling it to. But, nonetheless, I just flew a good sortie in mp in this aircraft, and stumbled upon the same weird behavior. I had 4 TPs created on the map, and one of them the TPOD wouldn't turn at. I was in INS, pressing MAP DESG pointed the TPOD entirely at random. I switched to T2 and that worked. Unfortunately, that was in MP, so no track. I think this erratic behavior is related to the op. BIGNEWY, sorry, the bugs are just really annoying.

Flew the harrier for a couple of days and it's still full of bugs. Targeting with TPOD was extremely frustrating though. I put up a quick night mission, placed targets at a location without any known to me visual references, put up a waypoint onto them and off I went to rely on EHSD DESG to do its trick. I flew around for maybe an hour before by some miracle TPOD actually was pointing to the waypoint and showed the units on the ground. It was pointing at anything at random, including points outside the map, and the sky. Eventually, I just decided to cycle waypoints with wink, while map desg was on, and once in a blue moon the tpod actually pointed at the waypoints. Will the harrier ever actually function?

It looks like hud projection doesn't work the first time I run a mission, but does work with all consecutive runs. No idea if this is on my or module's side. It is what it is.

Yeah, it works/doesn't work every other time. Here's a track of my next try, and now it worked. Same was with the bundled in night time mission, as I initially reported: at first try it didn't work, on second did. av8works.trk

Ok, what am I missing? Everything is on, video brightness and contrast max, flir works - you can see it on the right mpcd, and, again, long pressing the hud reject scene just slightly changes the brightness symbology on the hud, just as when I initially reported it. Track attached, screens with hud projection on and off, respectively (guess which one is which, lol), attached too. av8flirdoesntwork.trk

Uhm, nevermind. In "pinpoint strike night" mission, on Tarawa, it's very hard to see if it works or not. It actually does work.

It's in night mode, long pressing Sensor Select DOWN (HUD Scene reject) doesn't enable FLIR projection on the HUD. Instead, it slightly changes the brightness of symbology on the HUD. FLIR projection on MPCD does work.

Thanks, Luke! I vaguely remembered there was some trick to it, saw it in some guide on yt, but this is so much more clear. Found the note in Chuck's guide: part 14, 4.1 Waypoint navigation.

Subject. Targets are created on the F10 map, I'm able to hit them with GBUs, but switching EHSD in TGT doesn't work. It's just stuck in WYPT. Even though targets are loaded into the plane's system CAS, RCALL, all checked active, all enabled TRGT, weapons aligned, - everything's done - the TGT option on the EHSD doesn't even appear, hence, unable to switch to it. This used to be a bug in multiplayer, but I just checked in sp, and it's there too, so, unless I'm missing something, this could be a regression.

Like Raror said, go to axis assign and make sure you have just one device assigned per control surfaces/engine/nozzles. You can't have multiple different devices set to control the same thing.