VAICOM 2.0 for VoiceAttack

[FeistyLemur]

So the newest version of Voice Attack is safe to use with Vaicom? I'm using 1.5.8 and I know at the time I got started the beta version 1.5.10 I think it was? didn't work right with it.

 

I'm loathe to update something that's working. But direct joystick binds would be nice in this case, because then I could leave the default numpad keys alone. Which is preferable because if you're setting up custom snap views you have to use those functions they are normally bound to.

[Hollywood_315]

Yes current release 1.5.12 is stable and joystick direct PTT works nicely with it.

Indeed you can skip the keyboard (NUM keys) for PTT altogether and free them up again for snapviews or the like.

[FeistyLemur]

As far as updating goes, do you know if you can install voice attack overtop of itself in an upgrade fashion and have vaicom still work? Or is it pretty much install from scratch and re-import all the profiles.

[Hollywood_315]

You can just install over the current install and it will retain settings afaik, I don't recall ever having had to re-import profiles.

[FeistyLemur]

It took me some time to figure out how the joystick binding works in it, but I got it updated and I like it.

 

One thing I came across in .12 that didn't cause issues in .8 is I had my profile switching set up where calling the existing profile from itself just does the "load profile" feature and loads itself. That seems to cause unhanded exception errors at random.

 

This was out of pure laziness mostly to make it easy to copy my load profile commands across all profiles and rather than switching it to _Menu_Initialize for the in profile call.

[Bottle-RUM]

 

Oke after updating Voice Attack it get a problem lauching the VAICOM_fetch_data.cmd ?!

I reinstalled VA, to it's default path (due to relocating the path of Chatter sound folder, in the profile settings).

 

but i'm lost now, can you help me with this?

 

EDIT;

A windows 10 reinstall (it was on my to do list anyway) fixed this for me, due to several windows Corrupted files it couldn't reach the folder where at was trying to fetch data!

Edited August 31, 2016 by Bottle-RUM

[FeistyLemur]

I've been practicing with the JTAC flow in the A10. I seem to always get stuck on the same issue.

 

I've been practicing with the default "shooting gallery" mission. I can get up there, call JTAC, do one successful run right to the letter as per the instructions. All the steps work along the way. Once the target's destroyed the JTAC calls in and says target destroyed.

 

At this point this is where it gets stuck. It refuses to work without the brute force command force next. If I call "ready for 9 line" to get my next task I hear it beep successfully, then the menus flash and it makes it as far as the JTAC menu where I see the options. But I can't call commands properly at this stage. I have to force my way through the rest of the mission. It's as though it's one step behind where it should be and just not executing the command.

 

I'm not sure what I'm doing wrong at this stage.

[Hollywood_315]

@RUM Which VA version are you using? Make sure it runs as admin. Send me a PM if that doesn't fix it.

 

@FeistyLemur The trick is to confirm the operator call before proceeding. On operator call ' target destroyed' reply with 'copy kill' or 'confirm kill'. On call 'target is not destroyed' reply with 'copy miss'. Then proceed with next pass. Some more details on this in the user manual.

 

 

 

Verstuurd vanaf mijn SM-G935F met Tapatalk

[FeistyLemur]

I had been doing that but it wasn't helping. I notice the a10 profile on the downloads page has been updated since the one I have for type 3 jtac. So maybe that's it. I've downloaded the newest one to try but was unsuccessful in the first attempt last night.

 

Voice attack crashed and I gave up for the night. I seem to be having a lot of issues with unhandled exception crashes with the .12 version from the site. I thought I had it solved with the calling a profile from itself thing but apparently not. There continue to be random crashes and freezes. Some of the searching I've done on that has turned up threads linking unhandled exceptions to the joystick ptt, so my dreams of continuing to use that may be dashed.

Edited August 29, 2016 by FeistyLemur

[Hollywood_315]

Those crashes sound nasty. I cannot reproduce it myself, 1.5.12 on my rig is all stable (I'm on win7).

 

Shooting Gallery has multiple JTACs in the area, one of them a Predator, which may needlesly complexify things for flow training.

That is you may need to dynamically keep track of which JTAC you're talking to, and use the JTAC Select command.

For basic JTAC flow training with VAICOM I recommend this mission JTAC Live Range and the night version JTAC Night Range.

You can tweak them in mission editor for different scenarios.

[FeistyLemur]

Hmm, still no luck with the new profile. What I'd done to make it simpler was copy the Shooting Range mission, and I just deleted the predator so there's only Darkstar on the mission.

 

Basically it appears to be stuck thinking it's at the inbound stage. As soon as I readback remarks JTAC says clear to engage. So I engage, kill the target, JTAC says target destroyed. I say copy kill, the menus flash but that's it. Then its stuck again. But... If I say IP inbound at this stage, it actually calls ready for nine line by hitting f4, f2. So that's where it thinks it's at in the flow.

 

But there is no IP inbound stage for this type of JTAC, so im not sure what to do. Basically after readback, it's right at the stage where f2 calls target destroyed. So if you call ip inbound, it calls target destroyed. I had hoped the updated profile addressed exactly this by the notes but it appears it didn't.

 

I downloaded that training mission linked and practiced with type 2 jtac with smoke. It works perfectly. It seems to be just the other kind I'm getting stuck with.

Edited August 29, 2016 by FeistyLemur

[Hollywood_315]

Thanks for this, I'll have a look and see if I can figure it out. Will send a PM after I've done some testing. I need to check what the exact steps for Type3 actually are again lol I now realize that may not have been properly documented anywhere. If I'm not mistaken it's this: (briefing stage) > clear to engage > call 'No Mark' > target destroyed > call 'Confirm Kill' or 'Attack Complete'.

 

Verstuurd vanaf mijn SM-G935F met Tapatalk

[FeistyLemur]

No Mark were the magic words I was looking for. It's working as expected now. I don't believe that was documented. Only the type with a marking stage was.

[Bottle-RUM]

Oke fixed my previous problem now the next :doh: , everything works (it puts in commands, it recognizes it) but it doesn't put the commands in the Communication menu but it changes camera views, so the F keys are being used but not into the comm's menu?

 

- VA Runs as Admin ( v1.5.12 )

- M-2000c profile

- Default VAICOM 2.0 Profile, by the book ( or at least i tried to :music_whistling: )

- Used ''Start Mission'' Command at start up

as you can see the VA log shows no errors^^

 

EDIT;[FIX], My \ key was not working properly in DCS App due to not setting my Logitech Gaming Software as run as Administrator. But After restarting my pc the problem was still there! My final fix for this is to swap the default AUTO comm's key [ \ ] to a unbound key in DCS controls & edit the VA command ''_Menu_Execute'' http://i.imgur.com/xT9g50A.png, in my case it's the [L] key. now it works like a charm.

 

BIG thanks to Hollywood_315 & FeistyLemur for helping me

Edited September 2, 2016 by Bottle-RUM
Fix found for problem

[FeistyLemur]

Make sure you unbind F11 and F12, this will cause view swapping, also if you are using the numpad keys for push to talk unbind numpad 0 1 2 and 3, and make sure your intercom and cockpit ptt functions are default. \ and RAlt \ usually.

 

When starting mission call "start mission" to start as a habit rather than clicking fly on screen.

 

Often in game you can call "profile reset" if having issues to resync.

 

Caling Nalchik ATC is also broken in all the profiles. See the note on install page about fixing that.

Edited August 31, 2016 by FeistyLemur

[Bottle-RUM]

Hey FeistyLemur, thanks for helping :thumbup:

 

I'm just ruling out the possible mistakes an error's here;

 

-F11 & F12 where not bound

 

-I'm using the VA Use Joystick buttons option for my MIC switch(es)

(this case only Mic Switch forward works on Easy communication) \ ''AUTO'' com menu.

 

It works fine when i press it Manually on my keyboard;

 

''\'' for main comm's menu selection > ''F5'' ATC menu selection > ''F1'' ATC selection

> ''F3'' Request Start up

 

but like i said, it's only swapping camera views F5, F1 & F3, so VA it seem to skip the \ key?

 

- i checked into the VA mirage profile and the \ button is Mapped for a 0.05 sec keystroke

 

i tried to make the keystroke longer by up it from 0.05 to 0.07, i did not work.

 

- i start every mission with the command ''START MISSION'' instead of clicking the fly

button. this works perfectly, if the game immediately set to pause afterwards?

 

- i tried to what you or someone else? already suggested earlier in this Thread (forum

search Function is our best friend :thumbup:) to use the command ''Profile Reset''

 

- Nalchik ATC never took off or landed there, but it's noted thanks for the heads up.

 

So i really tried to resolve this by my own, but no succes. i even tried to understand the command structure in the VAICOM 2.0 VA profile but 75% looks like gibberish to me i can't get grip on whats going on in there?

 

as always, my thanks in advance

 

FIXED > https://forums.eagle.ru/showpost.php?p=2889598&postcount=415

Edited September 2, 2016 by Bottle-RUM

[Hollywood_315]

Hi Rum,

 

- Holding PTT long enough, i.e. until you've heard the beeps?

- Using US international keyboard layout?

- Are both PTT Press and Release commands properly bound i.e. to the same joystick button?

 

I'll catch you on PM.

[Bottle-RUM]

Hi Rum,

 

- Holding PTT long enough, i.e. until you've heard the beeps?

- Using US international keyboard layout?

- Are both PTT Press and Release commands properly bound i.e. to the same joystick button?

 

I'll catch you on PM.

 

Hey, Hollywood_315

 

sorry for the trouble, thanks for helping

 

- Holding PTT long enough, i.e. until you've heard the beeps?

>yes, i always wait for the confirmation beeps

 

- Using US international keyboard layout?

>\ ] [ ; ' / . . , - = ...... Yes its selected and working ;)

 

- Are both PTT Press and Release commands properly bound i.e. to the same joystick button?

> yes the are, on with my knowledge it working (Released joystick button the ''Shortcut is invoked only when all buttons are released'', Box it ticked)

 

FIXED > https://forums.eagle.ru/showpost.php?p=2889598&postcount=415

Edited September 2, 2016 by Bottle-RUM

[Hollywood_315]

Fixed as per above https://forums.eagle.ru/showpost.php?p=2889598&postcount=415

@Bottle-RUM thanks for updating. Grtz

[BSpike]

Hello Hollywood,

 

Tried to do some JTAC practice with one of the original A10C missions with single JTAC. Checking in and Briefing goes as expected till JTAC says "Standby Data", soon after JTAC aborts the task and asks if I'm ready for another task, my next command must be "Ready to copy" but it doesn't work nor "Copy hit" and "Copy kill", "Force Next" still does the job and sends "Ready to Copy"command.

 

the mission is "Surrounded" in the list of A10C's mission, if you give the JTAC a little time he will abort the task so you can check it out.

[FeistyLemur]

As I've been practicing with JTAC it seems kind of like it triggers stages based on distance to target, like popping smoke etc.

 

I was doing a practice one with the generic practice mission that's linked a few posts above. Anyway it seems to work best if you fly out a couple miles, request target while orbiting, acquire the target and do all the appropriate calls. There are quite a few steps.

 

However I had a similar issue with my last target last night, even doing this I would approach the target and JTAC would call abort. But I think this was because they had given me an expected attack vector as well. They can also do this and then you're expected to attack from a specific direction. Use your course set knob when they do this. I was using the attack vector, but I was definitely not right on it.

 

It's possible another unit destroyed the target already. That happens a lot in "shooting gallery" because there are a lot of other planes in the air.

 

One thing to look at is the problem I was having. For type 3 JTAC after they say clear to engage you must call "no mark" to skip the IP inbound stage. Basically if it's type three and it goes right to clear to engage after the readback, immediately call no mark to progress the call. This is not documented in the manual. But definitely works with type 3.

 

I went and tried that mission just now, it's type 3 JTAC, so you have to call no mark after clear to engage. That mission is also probably not the best for training, its fast paced with moving targets and it looks like it hardly gives you enough time to attack each group. If you miss or take too long JTAC seems to abort and go to the next. I managed to make an attack run on the first column, but missed, they called abort and I still got stuck anyway.

Edited September 2, 2016 by FeistyLemur

[FalconFSX]

Newbie Questions

 

I've been giving VAICOM a try and have a couple questions. Specifically, I'm using the P51D module with Easy Communication = OFF.

 

1) When I say start mission, it always auto-pauses (and then I have to hit PAUSE/BREAK to actually start the mission). Is this expected and is there a way to disable the pause if so?

 

2) I'm using the NUM1 key to talk to ATC when on the ground which works fine. However, I really should be using the Push To Talk button i believe. This shows up when in the air as the NUM1 button doesn't communicate with the ground. However using the Push To Talk button succeeds. Am I missing something in the setup where VIACOM should be using the Push To Talk (defaults to "RAlt + \") instead of the Communication menu ("\").

 

Thanks in advance.

[FeistyLemur]

With realistic communications the \ menu works on the ground, and in the air you must use the in cockpit ptt, Ralt \. Or in the case of the warthog there are multiple PTTs. This seems to just be how DCS works.

 

Like how when you're on the ground you can communicate with the ground crew just by pressing \, but if you close the canopy they can't hear you and you have to use the intercom. (at least this is how it works in the KA-50 and A-10).

 

Vaicom I believe uses \ for all ground crew calls with easy comms off, and Ralt \ for everything else.

 

Yes the auto pause appears to be default behavior. I added a bunch of other commands to my profile though for pause, resume, external view, cockpit view, map view. Nice to not have to reach forward for the F keys. I think you can change the auto pause behavior on the start mission command by simply editing that command. Not sure what the reason for it being there is.

[FalconFSX]

With realistic communications the \ menu works on the ground, and in the air you must use the in cockpit ptt, Ralt \. Or in the case of the warthog there are multiple PTTs. This seems to just be how DCS works.

 

Like how when you're on the ground you can communicate with the ground crew just by pressing \, but if you close the canopy they can't hear you and you have to use the intercom. (at least this is how it works in the KA-50 and A-10).

 

Vaicom I believe uses \ for all ground crew calls with easy comms off, and Ralt \ for everything else.

 

Yes the auto pause appears to be default behavior. I added a bunch of other commands to my profile though for pause, resume, external view, cockpit view, map view. Nice to not have to reach forward for the F keys. I think you can change the auto pause behavior on the start mission command by simply editing that command. Not sure what the reason for it being there is.

 

So is my problem that VIACOM is always using "\"? Meaning it thinks Easy Comms is on? How do I disable that? Again, using the P51D module if that matters.

[FeistyLemur]

Maybe you have setup issues and it's not correctly detecting the comms mode. International keyboards can be an issue also. Make sure vaicom is correctly reading the game data and setting the comms mode. It tells you in the voice attack window, easy comms on or off, and whether its having errors reading files and stuff.