[Vaicom not transmitting]

Great stuff

[Vaicom not transmitting]

Having re-read your message you shouldn't have them bound on the control page for DCS so try removing those and see if there is any difference

[Vaicom not transmitting]

Is this the log after you have tried flying?

Try turning on Vaicom's debug option (top option on the Config Tab in the Vaicom control panel)  and then, without enterinmg DCS, use your PTT controls and try some of the commands. Do they register in the Voiceattack window?

Also, are you in a cold and dark aircraft? If so, you will need to use the ICS PTT button as the radio buttons are linked to radio power

[Crash Help Please.]

Do these crashes happen at the same point each time?

If you think it might be the psu (or any component) have you tried running a stress test program?

[DCS went from extremely stable to very unstable]

Or xmp - i have turned that off on my system because it gave me lots of crashes in various games

[Game crashes / freezing when loading]

Do you have hot plug enabled for USB devices on the botton of the Controls tab (the button will say Disable hot plug if you do)? If so, it is generally advised to turn this off.

The reason for asking is that your log has a series of Plug / Unplug events for audio devices when starting the mission, followed by a whole load of sound errors for the F-4E. Having checked my last log file (which was also an F-4E flight) I don;t have these. The log entries I am looking at are:

2025-03-22 18:48:32.675 INFO    APP (Main): Device unplugged: [SWD] Haut-parleurs (2- Logitech Wireless Headset)
2025-03-22 18:48:32.680 INFO    APP (Main): Device unplugged: [SWD] Microphone (2- Logitech Wireless Headset)
2025-03-22 18:48:32.686 INFO    APP (Main): Device unplugged: [USB] Logitech Wireless Headset
2025-03-22 18:48:32.690 WARNING LOG (24460): 1 duplicate message(s) skipped.
2025-03-22 18:48:32.690 ERROR   ED_SOUND (23168): IAudioClient::GetCurrentPadding failed: 0x88890004 (AUDCLNT_E_DEVICE_INVALIDATED)
2025-03-22 18:48:32.719 INFO    ED_SOUND (Main): Opening audio device "{0.0.0.00000000}.{39540191-9abc-4c61-8556-db0f58c7f29b}"
2025-03-22 18:48:32.719 INFO    ED_SOUND (Main): Speaker layout: forced_stereo
2025-03-22 18:48:32.719 ERROR   ED_SOUND (Main): Failed to init IAudioClient on device: 0x88890004 (AUDCLNT_E_DEVICE_INVALIDATED)
2025-03-22 18:48:32.719 INFO    ED_SOUND (Main): Opening default audio device.
2025-03-22 18:48:32.720 INFO    ED_SOUND (Main): Speaker layout: forced_stereo
2025-03-22 18:48:32.720 INFO    ED_SOUND (Main): Driver reports 8 channels with mask 0x63F
2025-03-22 18:48:32.720 INFO    ED_SOUND (Main): Using 2 channels at 44100 Hz
2025-03-22 18:48:32.720 INFO    ED_SOUND (Main): Channel layout: Headphones/Stereo
2025-03-22 18:48:32.724 INFO    APP (Main): Device unplugged: [USB] Logitech Wireless Headset
2025-03-22 18:48:32.732 INFO    APP (Main): Device unplugged: [HID] HID-compliant consumer control device
2025-03-22 18:48:32.736 INFO    APP (Main): Device unplugged: [HID] HID-compliant vendor-defined device
2025-03-22 18:48:32.743 INFO    APP (Main): Device unplugged: [USB] USB Composite Device
2025-03-22 18:48:36.119 INFO    APP (Main): Device plugged: [USB] USB Composite Device
2025-03-22 18:48:36.212 INFO    APP (Main): Device plugged: [USB] Logitech Wireless Headset
2025-03-22 18:48:36.241 WARNING LOG (24460): 3 duplicate message(s) skipped.
2025-03-22 18:48:36.241 INFO    APP (Main): Device unplugged: [USB] Logitech Wireless Headset
2025-03-22 18:48:36.248 INFO    APP (Main): Device plugged: [HID] HID-compliant consumer control device
2025-03-22 18:48:36.257 INFO    APP (Main): Device plugged: [HID] HID-compliant vendor-defined device
2025-03-22 18:48:36.264 INFO    APP (Main): Device plugged: [SWD] Microphone (2- Logitech Wireless Headset)
2025-03-22 18:48:36.273 INFO    APP (Main): Device plugged: [SWD] Haut-parleurs (2- Logitech Wireless Headset)

[F14 not authorized / antivirus / false positive]

1 hour ago, mazex said:

Well - if this a false positive I suggest that ED and Heatblur post this to Microsoft and not telling us paying customers to do it?

null

They could but these things take weeks to clear once submitted so each patch would be delayed. Your AV is painting a very black and white picture - the programme is only potentially dangerous because the AV cannot read it. Potholes in the road are also potentially dangerous and I have to report those, not the maker of my car

[Logged in and all my key mapping has gone.]

It is a good idea to take a back-up of your Saved Games Input folder once you are happy with the bindings.

[Impossible de ce connecté au compte dcs]

Is your computer time and date correct? This can cause issues with authenticators.

Can you connect if you turn 2fa off?

[Heatblur Simulation official patchnotes]

This is not true - they may not respond on all threads but they are active and respond to lots of bug reports / queries in a pretty rapid manner

[Heatblur Simulation official patchnotes]

Correct - this has been confirmed elsewhere. The cutoff for changes was just before Christmas when the team was on leave

[VR crashes out]

Does this happen in single player / standalone as well as when you are joining a server?

[F-5E Remastered FPS issue after the last patch?]

The reworked F5 is known to cause performance issues at the moment - hopefully fixed in the next patch

[DCS wont start anymore/ crashes upon loading]

Have you rebooted as the log is still crashing accessing msvcp140.dll?

[New patch showing a Trojan]

This will be a false positive from your AV  (it happens periodically). Exclude the DCS folder from your AV and then run a repair or update.

[Unable to start application (0xc0000142)]

If you go to E:\Eagle Dynamics\DCS World\bin-mt and then double-click on dcs.exe does it run?

The error message you are getting is to do with file permissions so knowing whether it will work directly is a starting point

[CTD with CH-47F only]

What are your system specs?

Are you running 2D or VR?

What settings are you using in DCS for graphics quality etc.?

[Range of AIM-9M tied to AGM-65D]

1 hour ago, orbmis said:

If the AGM isn’t required, then the AIM can be fired completely independently and then chase the opposing heat signal on its own? 
 

This is correct - the AIM-9 is purely a heat seeker so you cannot guide it. It guides itself to an appropriate intercept point based on target movement. While it is an all asepct variant the probability of intercept will still be affected by factors such as range, target aspect, closing speed, countermeasures, pilot competence etc.

[MFG Crosswinds not detected in CH-47F]

And mine

[[Known issue] F-4E]

It might be better to change the title / name of the thread to something like "Joystick models disappear". F-4E is less likely to get help.

[CH-47F Launch]

All the modules on the DCS standalone store are Steam incompatible since you need to purchase through Steam. I am sure it will be available on Steam once the patch is there.

[[Resolved] Cant get back to TV weapons after AA fight or dumb bombs employment.]

5 hours ago, normanleto said:

The timer is not the issue. I tried to get back to tv weapons after 15 minutes and there is still no way. I'll record the track tomorrow. You can always try to reproduce it before on your side.

Perhaps it is something with afghanistan map and the spawning in editor. What is interesting, the plane spawns itself with weapon selector already on TVs with such armament config.

 

As well as the track you could post the mission file here so we could try with exactly the same start conditions

[VR not working after latest hotfix update]

It is also working for me with a Crystal

[Is Bastion and Helmand supposed to look like this?]

Just for comparison - this is my view of the Camp Bastion Heliport from roughly the same spot as Gunfreak

[Possible radar render artifacts - vertical lines and strips]

I have the same experience in VR - I run QuadViews for performance reasons so will try it withh this turned off to see if that makes any difference