Nickentik

I fixed it. It was indeed an issue with the space bar being used for events. I had rebound it before but not without completely removing the space binding first. space bar was actively blocking the trigger even when called by another keybind. After solely using a different keybinding, the trigger worked again.

Yeah, thought of this aswell. I tried alternatieve binds during the mission with no success. I'l rebind behore the mission and see if that does anything. I'l also disable vaicom but that would be strange as it works everywhere else. Thanks for the input guys

Yes it is. As i said. Cold start with same procedures outside the campaign results in a working trigger. None of the weapons fire. Rebinding does not work.

Hi, I cannot fire any weapons in these missions, guns, fox 1-3, etc. The trigger does not respond. Cold start outside the campaign both on field and carrier result in a working trigger so its not a skill issue. I have VAICOM activated for using Jester but that does not impede the gun from working outside the campaign

Turn of the flyable aircraft mods (uh60l, a4e , etc) and try again. They are not compatible with aero

I had this exact problem. The polling would happen every other press and would happen every time the "options" command was given. I was finally able to fix this by switching to "dynamic switching" in the mp settings. Please note that this affects SINGLEPLAYER so its a weird one. the actual problem, the polling with subsequent suspension of listening, still persist but for some reason the dynamic switching throws a listening resumed behind every suspension untill the tx button is released. this works with the options thing so singleplayer is saved at least I really dislike dynamic switching in multiplayer so that's still a problem. edit : if i decouple vaicom from srs by turning off the integration options in mp i might be able to just use both together if i use the correct options in srs

Thanks for the replies. It warms my old heart to know I'm not alone in this. Posting tracks is hard as its super frustrating to deal with and I have my hands full with RL stuff right now. In the little free time I have I just want to blow stuff up XD. Changing the moon and weather is a good idea that could work with some of free content, many of the campaign are locked however.

Thanks for the quick reply Hollywood. That did the trick !

After todays update my Vaicom is nog longer functional. Every open mike goes from "listening" to "suspended" after 0.5 seconds. The open mike sound works correctly i.e. it plays when i press the button and when i release the button. The listening function however only works for 0.5 seconds. If i'm fast enough i can actually send a couple of basic commands in this short period so everything else seems to work. This only happens when a module is loaded. Outside of modules the mike stays open an receives commands as normal. I have reset the lua settings of the app and also upgraded voiceattack to the lastest 64 bit version. DCS is Latest beta build which is now the same as stable. .

I use oben beta but that will be stable as from today.... I'm currently running through the A10c campaigns after finally learning this wonderful beast. Right now i have about 6 campaigns all stuck on their mandatory night mission because the night vision goggles just don't work. The world is a black void, only the stars are visible. I even crash into mountains if I don't notice the sudden cutoff of stars. I can use the targeting pod but guns or anything that requires an outside visual are a no-go. I know it was written up as a "known problem" with the 2.7 release but its far more serious than the small irritant its been made out to be. I see no-one complaining about this. Is anything being done about it ?

Due to sheer minded stubbornness, doppler nav usage and plain cheating (f10 map and logbook editing) I managed to finish the campaign. NONE of the 828 and UD channels work throughout the campaign. Please fix this because it was pretty frustrating.

Stuck here. The first house is not designated. Anyone know where I can find it ? there are no buildings that match the description (4 stories with flat roof)

I got the same problem..... 2 years later. Any update on this ? edit: according to an even older thread I need to trigger earlier events by flying close to outpost 3 along the route. this is also difficult as the 828 (and UD) navigation is broken for nearly all missions ! I just navigate using doppler navigation

I don't have airio. The setting is not availeble

Same. Check the voiceattack log. After a successful audio command (confirmed by the beep) it normally states the "command is constructed" or something similar. It doesn't anymore...

Same for me, couldn't get them working in the first mission. haven't flown the rest yet. edit : no luck in the second mission either. no arc ud (podkova) and no 828 navigation (fort 3)

I am not able to utilize the kmgu dispensers in this mission to destroy the reinforcement convoy. No matter what I do I always get instakilled the moment the first vehicles get hit by the bomblets. I assumed I was flying too low but I am able to destroy vehicles in custom missions from 50 m height with no problem. Meanwhile this bombing run destroys me from as high as 300 meters. The bomblets also seem to be unusually powerfull, destroying most of the convoy easely in one pass (including armor). I assume there is some scripting going on to make this happen. The same scripting makes the bomblets a suicide.

Hello Hollywood, I think there might be a limit to size of the command database when pasted in the "edit a command" fields of voiceattack. At around the 6400 character limit it just pastes empty fields instead of the commands. This quickly becomes a problem when the extra atc names and mission commands are added to the database.

I cannot finish the mission. it is exceedingly difficult to land on the roof. I keep bouncing off. There seems to be something wrong with the collision model. I finally mangaged it last time but i crashed again when i needed to pick up the troops.

I have encountered the same problem. I does not seem possible without crashing into the trees. Can anyone confirm its doable ?

Hello Hollywood, I had a problem with KURSANT campaign : I was not able to talk with ATC and AWACS. This was fixed by disabling the "force NATO ATC names" preference. I have not encountered this problem in custom missions on the same airfield/plane/ATC

I have corrected the problem. It was a conflict with the VAICOM voice software and the usage of the "force NATO ATC" names setting. I will inform the VAICOM programmer. edit : I now managed to finish the mission and it becomes clear that the info given in the briefing is indeed relevant as the mission objectives change after the target shootdown. Some remarks : -channel 9 is indeed the AWACS but is referred to as ATC in the briefing. -channel 17 and the RSBN 40 and 38 channels become relevant after the objective change. I assume these are spoilers unless the change in airfield is mend to be mentioned in the mission briefing. -the ATC of channel 17, KRASNODAR, is unresponsive even when the faulty VAICOM reference is corrected. The mission is finishable in any case.

Thank you for the quick response. Any idea why the radio does not function ?

In the kursant campaign the radio is not functional. There is no communication possible with ATC. When I create a custom mission on the same airfield, radio communications is no problem. There is something in the campaign preventing normal communications. Does it have to do something with callsigns ? I assume custom missions use the default ENFIELD callsign. These problems don't block campaign progress until I am stuck in mission 8 where I need to contact an AWACS to get a bearing to the flying target. This is also not possible. The missions briefing contains errors and is incomplete : info given : --- RSBN: 40-Navigation and 38-Landing Traffic controllers: - ATC Krasnodar: channel 17 - ATC Sokrat-Podhod: channel 9 --- normally RSBN channels are 34 and 36 for Maykop. channels 40 and 38 are for Krasnodar which is not used in the mission. The two ATC channels are also not used or incorrectly named as atc instead of AWACS. Please inform me of the correct AWACS channel to be used during the exercise.

Don't forget that TARGET will create a new controller called "Thrustmaster Combined" when you activate the profile. It is this controller that needs to be selected in the VA options.