hornblower793

I didn't go for a flight last night, but sitting on the runway was a perfect (and instant) response from the tower Sent from my SM-T835 using Tapatalk

@MAXsenna - welcome to the world of variable geometry (finally)[emoji3] Sent from my SM-T835 using Tapatalk

You probably need to set a deadzone in the aiming station mappings for whichever controller you are using. You will always need to adjust it slightly to compensate for the movement of the helicopter

When you say it pauses does that mean DCS freezes? If so, can you kill it with task manager or do you have to log out? What airframe are you trying? If you load the .miz file up here I am happy to take a look at it for you

Are you trying with 'old' missions? I have had this issue in the past and opening the mission in the ME and then flying it from there solves the problem. The Hind is a new module and not officially supported yet so I wouldn't be surprised if there are currently issues

All - the 25.3 update today should have resolved your listening suspended issues

Are you trying this with the inbuilt quick missions? I started off by trying one of these (Caucasus takeoff) and it was a 50 second delay between speaking and the command processing. I then created a new takeoff from Batumi mission in the ME, dropped on to the runway and the response was instant. Following this I then opened the Instant action mission via ME and hit fly without saving any changes, once again the response was instant. I then saved a copy (without changing anything else in the ME) and have attached it to this post to see if it works for you Yak-52 Caucasus Takeoff - Copy.miz

Is this on the ground, in the air, or both? Will hopefully try mine this evening Sent from my SM-T835 using Tapatalk

One thing has just been suggested on Discord from someone who had this problem. They said that it cleared when they reassigned their joystick in VA (not just the button but the whole, enable joystick) - could someone who has the problem try this and report whether there is any difference?

@=Panther=Do you have an Interphone (TX5) switch mapped? If so, does that talk to the ground crew without the suspended issue?

When you said you did the delete of the shader files in the wrong place where was that?

I have just tried this mission and it works as I would expect Are you trying to do your radio check with the wingman before takeoff? If so, this is a DCS limitation that wingmen do not talk to you while on the ground. If you try radio check the moment your wingman tells you they are airborne you should get a response

Yes - I meant to mention those in the initial response but they obviously got lost when I changed what I was saying (memo to self - concentrate on one answer at a time[emoji3]) Sent from my SM-T835 using Tapatalk

@Flappie - thanks for the education - everyday is a schoolday (and I will give up when this is not the case) The interesting thing here is that I don't think @kux has actually made it in to the mission (unless perhaps the load is from the ME). The log doesn't contain a 'Dispatcher: loadMission Done: Сontrol passed to the player' entry

Thanks - will have a look at these tomorrow and see what I make of it all

Have you raised a support ticket with ED? The log and DXDiag are confirming that all memory has been used. Is this only on the Syria map or do you have problems on the other maps as well? Just before your crash you get the following lines in the log 2021-06-18 17:48:46.285 INFO EDTERRAINGRAPHICS41: instancer factors has been changed. Update lod buffers. 2021-06-18 17:48:46.285 INFO EDTERRAINGRAPHICS41: distanceFactor = 1.000000 2021-06-18 17:48:46.285 INFO EDTERRAINGRAPHICS41: instancerDetailsFactor = 1.000000 2021-06-18 17:48:46.285 INFO EDTERRAINGRAPHICS41: forestDistanceFactor = 0.500000 2021-06-18 17:48:46.285 INFO EDTERRAINGRAPHICS41: forestDetailsFactor = 1.000000 Having just tried loading mine up into Syria I don't get anything like this so don't know whether this might be a clue to what is going on. What graphics settings do you have in DCS

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