boerdi

Any update on the missing CA engine sounds in multiplayer? (no problems with engine sound in single player missions) M1A2 without engine lacks mojo Attached log and track file from MP session on quiet server (Hoggit's PGAW) Tested near Al Minhad airfield. First I had to spawn the tank with crates via Huey + CTLD and then hop to JTAC/Operator role and take control of the tank. DCS Steam Edition Current Open Beta 2.8.5.40170 Multithread Build Persian Gulf At War 1.0.0_morning-20230526-153200 - CA M1A2 bug - no tank engine sound.trk dcs.log

Ok, forgot to remove Tacview and SRS (since these are so vital I didn't think about them as "unofficial" mods) Double and triple checked to make sure that everything is vanilla. And ran file verification in Steam, again. Like first time everything has been validated correctly. Set up a new mission, this time not on carrier but Kobuleti airfield. With two client slots to simulate respawn. Result? The same: Monochrome map on AMPCD during the "respawn" cold start. New track file and log are attached. [edit] added the mission file dcs.log trackfile.trk Hornet AMPCD Respawn Cold Start Test.miz

So that was not enough?

Wait what? Marked as "missing track file"? There is one attached to the opening post... And tagged as "remove user mod files"??

Greetings, This happened during MP sessions. Was able to replicate in SP (c.f. attached track and log files). After joining a server, the first cold start progresses normally. The second cold start suddenly shows the monochrome map. Created a mission with two spawn slots (No 1: Hotspawn on catapult. No 2: Cold Start on parking) - Select slot 1 to hotspawn - Then select second slot - Respawn in Hornet - Regular Cold Start - As soon as AMPCD screen turns on, a monochrome version of the background map is shown DCS Steam Edition Current Open Beta 2.8.4.39313 Multithread Build Prior to the test I also removed unofficial aircraft mods and ran a file verification (which found no errors) Hornet - Monochrome Map on AMPCD during Cold Start after Respawn.trk dcs.log

Sounds familiar, check this thread (problem is under investigation):

I found no infos on warmup time and I had several instances in MP where the pod took a long time to "react" and enter the Noise Jammer mode. That was well over 3 minutes at that time (cold start + entering waypoints etc etc) and let's just say that entering a SA-5 threat ring without noise barrage ain't so fun It may well be user error on my part but since I was able to replicate it, I thought I wanted to make sure and ask if it is working as intended or not. [edit] Also this: every weapon or system that has a "warmup" time (e.g. Targeting pods, Mavericks or JDAMs) has that warmup time mentioned in the manuals and guides. The ECM pod does not.

Greetings, With cold start either in SP or MP the ECM pod wouldn't start transmitting in Noise Jammer mode on the ground or even after take off. Does the ECM pod take some time to "warm up" before Noise Jammer Mode can be activated during or shortly after a cold start? DCS Steam Edition Current OB Version 2.8.3.38090 Multithread Build And yes, I paid attention to the correct settings of swiches/modes (c.f. official documentation, video by Wags and many others). The issue does not occur when doing hot ground starts or air starts. (e.g. Hot ground start allows activation of Noise Jammer Mode on ground with weight on wheels.) I was able to reproduce the cold start issue in SP (track file attached). The video is of that exact flight/track file. Timestamps/Steps: 00:00 - Regular cold start. F-16 equipped with ALQ-184 long pod. 01:00 - Switching on ECM and checking settings. Activate banks, XMIT to Pos 3, CMDS to MAN. Pressing CMS AFT does nothing. 01:22 - XMIT to Pos 1, CMDS to SEMI. CMS AFT -> Deception Jamming Mode is activated. 01:29 - XMIT to Pos 3, CMDS to Man. Pressing CMS AFT does nothing. At this point I am switching between Noise and Deception modes and test if Master Arm makes a difference (it does not). 02:47 - Still on ground. Switching ECM section off and on does nothing. 02:56 - Taking off to get weight off wheels (just to make sure) 03:33 - Same test to get Noise mode going. No joy. 03:51 - Switching ECM off and on again and trying to get Noise mode working. No joy. 03:59 - Deception mode working fine. 04:08 - Switching ECM off and on again. At this point Noise mode starts working. User error or something fishy in the switchology or working as intended? Video of the track file content: F16 ECM Pod Test Noise Jammer Mode.trk

[EDIT] There is definitely something funky when WPDSG is pressed and HMD is in A/G target designation mode Both ATFLIR and LITENING are affected [EDIT 2] Attached SP track file with LITENING test to this post Same result: Pressing WPDSG with HMD in AG targeting mode creates a bogus designation far off in the distance And in SP the HMD aiming reticle appears while in MP it does not (keeping visually the previous designation - c.f. MP video at 00:06) --------------------- I was able to reproduce the issue in MP (in the fashion that I first encountered it) No track file since it's MP. In addition to the problem mentioned above, in MP the HMD symbology gets wonky too. Steps in MP: - ATFLIR operational - A/G mode - WPDSG on target waypoint - Attempt to Undesignate (in video at 00:06) - Yet designation still remains? - SCS Forward to set HMD as SOI does NOT show the HMD aiming reticle - Unsuccessfully pushing SCS Forward (AGR also appears in HMD) to get the reticle while also trying to further undesignate - Then the same problem appears as in first post: When HMD is in aiming reticle mode (with the HMD symbology being wrong here in MP), pushing the WPDSG button will produce a completely false designation somewhere in front of aircraft (c.f. MP video at 00:35 and Syria Test in first post) Video of MP test with ATFLIR (bogus designation with incorrect HMD symbology) Video of SP test with LITENING (bogus designation) c.f. Track File Funky WPDSG with HMD in AG targeting mode- Syria.trk

Greetings, I had issues with designating/undesignating via HMD during a MP session with HMD as SOI (TGP was ATFLIR at that moment). The HMD aiming reticle didn't show and Undesignation didn't work. Was able to reproduce parts of the issue in SP. Problem: When HMD is SOI and in AG target designate mode and the WPDSG is pressed, funky stuff happens (c.f. video 1 and 2 at 01:08) DCS Steam Edition Current OB Version 2.8.3.38090 Multithread Build Track files attached Test 1: Caucasus (WPDSG on waypoint 2) Test 2: Syria (WPDSG on waypoint 1) Caucasus shows no designation but in Syria a point in a completely unrelated space is being designated (c.f. video 2 at 01:08) ATFLIR wonky waypoint target designation - Caucasus.trk ATFLIR wonky waypoint target designation - Syria.trk

Yep, MP respawning/hotspawning in Hornet on Supercarrier puts you on the cat with visible fixed wheel chocks and no means to release them (ground crew does not remove them) That's why I always quickly switch back to spectator and pick my slot again (in case I got shot down) To visualize the problem (I tried to warn that pilot)

Greetings I noticed the missing animation on a MP server and was able to recreate it in SP. The new salute animation works fine at first launch. But after a landing and at next cat lauch, the pilot does not perform the salute animation anymore. Just after launch, the animation changes suddenly to the pilot holding the towel rack and will remain stuck in that position. Track file is attached. (Hot-start on cat with two quick and dirty CASE I patterns) DCS Open Beta 2.8.2.35632 (Steam) No mods Video 1: First launch, animation ok Video 2: Second launch. No animation, then animation stuck Stuck animation after second landing: Hornet - Bugged Salute.trk

Still cautiously optimistic No freeze after a good handful of sorties in "carrier corner" on Hoggit's PGAW

Here is a short multiplayer track from Hoggit's PGAW with only a couple of players online. Quick and dirty startup and heading towards the Pyotr. It's the beginning of the first phase, so a lot of enemy SAM emitters are present. TRACK DOWNLOAD (Google Drive folder) Video 1 shows situation pre-lock/launch, switching the SEARCH button on and off Video 2 during lock/launch In default mode (Search off) you don't see what is locking you or launching at you.

Can confirm that RWR in MP is not working correctly. Here is the corresponding (hefty) MP track file (Google Drive folder): -> DOWNLOAD

Cautiously optimistic. Will visit the carrier "hot zones" on the mentioned servers to see if normal play is back on the menu. The freeze bug has (had?) one positive effect: To stay away from carriers, I delved deeper into F-16 and A-10 (with zero freezes while outside the dreaded "carrier bubble")

Greetings Learning the A-10C II and I don't know if I accidentally enabled Betty's VMU text to appear in the upper left corner or not. Is it possible to disable those VMU subtitles? My Google-Fu only unearthed references to the radio subtitles (which are fine and I want to keep) and I also couldn't find anything saerching through the keybinds (plane, UI layer, general...)

I should have landed on Bandar-e-Jask... New entry: OB 2.8.0.33006 Aircraft: F/A-18C (freeze happened in cockpit, light F viewing to see if carrier deck is clear) Server: Hoggit's Persian Gulf at War On my way back to the Washington (day, CASE I) Distance to carrier: 6 nm AI Tomcats present: Yes (duo of AI Tomcats doing CAP around carriers) Other carriers present: Stennis, Kuz Detailed log attached I also attached a "control" log of a round on GAW without freeze (flying inland in the F-16 far from the carriers...) DCS minidump created by Process Explorer (Google Drive folder) -> DOWNLOAD dcs.log dcs - control - viper gaw no freeze.log

Another data point OB 2.8.0.33006 Aircraft: F/A-18C (freeze happened in cockpit, no F viewing) Server: Hoggit's Georgia at War On my way back to the Roosevelt (night, CASE III) Distance to carrier: 25 nm AI Tomcats present: Maybe? (first phase of GAW where I suspect that AI Tomcats are present in the mission file but not "active") Detailed log attached DCS minidump created by Process Explorer (Google Drive folder) -> DOWNLOAD dcs.log

Today was patch day and game froze in the very first round OB 2.8.0.32937 Aircraft: F/A-18 (freeze happened in cockpit, no F viewing) Server: Hoggit's Persian Gulf at War On my way back to the Roosevelt after SEAD sortie Distance to carrier: 27 nm AI Tomcats present: Yes Detailed log attached DCS minidump created by Process Explorer (Google Drive folder) -> DOWNLOAD dcs.log

Motion blur is deactived One of the first video options that I disable in EVERY game

Man, the freezes really kick you in the nuts every time and I just want to wind down after work... Aircraft: in the F-16 this time (freeze happened in cockpit, no F viewing) Server: Hoggit's Georgia at War Played 2 rounds before this one without a hitch On number 3 the freeze hit Took off Anapa, followed a friendly Froggy a bit, dropped a couple of flares to say goodbye, turned my head to buster to the AO and bam... freezykovsky Distance to Roosevelt: in the 40-50 nm range Detailed log attached... And here is also the DCS minidump created by Process Explorer (Google Drive folder) -> DOWNLOAD dcs.log

And the next freeze In cockpit this time MP server: Hoggit GAW (phase 1 without visible/active AI Tomcats) Approaching the Roosevelt, 30 nm out Detailed log attached dcs.log

I for one LOVE all the doomy and gloomy stuff added for Halloween! Big Warhammer vibes (Morrslieb!). Together with the new clouds everything presented itself to put together a quick atmospheric scene. But I also understand those who got caught unaware and started troubleshooting unnecessarily. Maybe add an option front and center when the game launches that gives the players the option to OPT IN for easter egg stuff instead of having to OPT OUT via editing config files. Happy Halloween!