hornblower793

If you could provide me with the files in the linked post I will check my files to see if I can find what is causing this

Which mission(s) are you trying for the A-10c where the wingman never responds - I will see if I can replicate here

There is some technical reason why this cannot happen - there is a Vaicom version detailed in the manual

We are struggling to see what is happening, because I and other community troubleshooters cannot get this problem to trigger. I have tried all sorts of settings on my machine without getting listening suspended to happen until I let go of the PTT. I know you are experiencing it, but it is really hard to help when we cannot trigger it. Again, this is not affecting everyone - I did have an issue in the UH-1H just now so will test this some more, but both the Spitfire and P-51 work for me both in terms of talking to ATC and to my flight. In fact, my Spitfire and P-51 seem to be working flawlessly. I do still have an issue with the Dora where the radio doesn't work in the air but this is a long-standing issue If someone who is having the listening suspended issue could post the following files here I will happily compare them to mine to see whether I can identify anything: 1. Saved games > DCS > Scripts > Export.lua 2. Saved games > DCS > Scripts > VAICOMPRO > VAICOMPRO.export.lua 3. Your DCS install directory > Scripts > UI > RadioCommandDialogPanel > RadioCommandDialogsPanel.lua 4. DCS install directory > Scripts > UI > RadioCommandDialogPanel > TabSheetBar.lua 5. DCS install directory > Scripts > Speech > common.lua 6. DCS install directory > Scripts > Speech > speech.lua 7. DCS install directory > Scripts > UI > gameMessages.lua

Mappings sometimes do disappear (don't know why) - while it won't help you this time, most of us keep a back-up of our profiles once set. You can either do this exporting them from DCS or go into your saved games folder and take a copy of the Config folder (especially the input folder inside it) In terms of the remap not sticking I find it helps to make the changes and then close DCS down before flying

@Jimmer, @MAXsenna 's idea to use aliases is really good - you just need to know the correct order to do things when adding the command for foolproof adding (it is not quite as easy as click in the box and type). The steps that work for me are: 1. Select from the drop down list on the editor tab the command phrase you want to add an alias (Descent 10000) 2. Click ADD NEW to get Descent 100001 in the command phrase 3. Click on the alias box once to highlight the text and then a second time to place the cursor at the front of the command phrase (before the D) 4. Type your new phrase in (e.g. Drop 10 k or a phrase that works for you) and then use the DEL key on your keyboard to delete the original phrase 5. Once all aliases added press FINISH etc. As a thought if you add an alias for this you might want to do it for all Descent phrases so that you don't have to remember a mix of commands to do the same thing

What issue are you trying to describe - the picture looks good to me Sent from my SM-T835 using Tapatalk

@Flappie is one of the best for these things Don't worry about the error messages - we are all getting those at the moment

I was just about to post to say I have found the same thing - I need to initialise it to get the hot mic working I also found when I turned the hot ICS off I then had to turn HOT REL off to stop Vaicom picking up the commands with no PTT pressed. I will test this in more detail this evening to see whether it is reproducible

When you say hot mic switch in Vaicom do you mean 'HOT REL' on the PTT tab? If so, try turning this off to see if the behaviour changes to help identify the issue. Also, what settings do you have for the 'Broadcast parallel' set of options at the top right of the MP tab?

No - once you have finished speaking make sure you keep holding the PTT down until you hear the beep confirming the command has been understood (which is what I have always done). The REL HOT button is bottom right on the PTT tab and will be orange / red when activated. When I have this selected I have then tried releasing the PTT as soon as I have finished speaking and holding it until I hear the beep. If I release before the beep I get the 'Command disabled' message. New MP integration options have been added with this release that will have changed some things under the hood and may require adjustment to user SOPs

Best thing to do is raise a support ticket https://www.digitalcombatsimulator.com/en/support/?login=yes

I believe @MAXsenna now has his working. When are you letting go of the TX button - have you waited for the action beep after speaking before releasing the TX. In another thread @Hollywood_315 has said that the command disabled error occurs if you release to early and have REL HOT selected (I can get it to trigger if I do this)

I cope with this by twitching the collective up and down briefly as I go into the cockpit

Agree with @JNelson- especially when others with real world experience are saying it is the best FM of them all - I think some of the real footage might be a result of things like not wanting to stress the airframe too much to avoid reducing operational lifespan which is not something we need to worry about in DCS. I am sure there are things that need tweaking but, as with all DCS modules, they have had experienced Mi-24P pilots heavily engaged in the development process

At least you know you don't need to worry about them Sent from my SM-T835 using Tapatalk

I also use the MFGs with a damper fitted and combat pedals from@hegykc. I also helped him test some chopper foot pegs which I still have. I don't know whether he has gone into production with these. Sent from my SM-T835 using Tapatalk

Turn on Vaicom debug and then run the Test button on the Editor tab (black circle towards the top right). This should tell you which aliases are missing and we can then go from there. My guess is that one of them is 'for' - I regularly get this and just ignore it. Would be interesting to know what the others are Sent from my SM-T835 using Tapatalk

Assuming you have the DCS Sync controls option on do this

I don't know - it is possible that ED will add some more presets

The trigger happy is a known issue and will be resolved during EA

Deleted - answer in wrong thread

That is what I use - left hand side of the warthog for the throttle (collective) and right hand side for the collective itself What exactly are you wanting to do?

Looking at the log file the crash was in nvwgf2umx.dll which normally implies an issue with the nVidia graphics card drivers. Do you overclock your card? How far through the load of the planes does it get before crashing? From the log it looks to be just as you go into the cockpit at the start of a mission Have you tried running a DCS repair to see if that does anything Here's the standalone version repair procedure. For Steam, use the Steam files integrity check.

When does the crash happen - is it before the main menu loads or when loading a mission / getting into the cockpit?