Jump to content

Recommended Posts

Posted
Hehe thanks!

BTW. Do you have the JF-17 or FC3?

I'm asking becsuse there was this dude ranting about he couldn't get VAICOM to work with the J-11. And myself haven't used the Jeff since before Christmas, and also couldn't get VIACOM to work with it.

But made it work last night, just by fluke. Will def test it with the J-11 come Sunday open modules.

I'm just corious if it should work normally, or if I found a work around. Was away due a couple of months, so I might have missed any 'bout it.

Cheers

 

Sent from my ANE-LX1 using Tapatalk

 

I have FC3, but not JF-17, although the trial month starting tomorrow shouldn't be an issue. However, I did try the JF-17 briefly, with the last trial and although i didn't focus too much on VAICOM, i do always attempt landings with a new aircraft and will usually go through ATC to do so. I don't recall any issues with the inbound call and responses, but will give it another go tomorrow. I'll try the J-11 later today.

Posted

I have it working fine with the JF-17.

 

Sent from my SM-T835 using Tapatalk

Windows 11 Home ¦ Z790 AORUS Elite AX motherboard ¦ i7-13700K ¦ 64GB Corsair Vengeance DDR5 memory @ 5600MHz ¦ Samsung 990 Pro 1TB SSD for OS, Samsung 980 Pro 2TB SSD for DCS ¦ MSI GeForce RTX 4090 Gaming X Trio 24GB ¦ Virpil WarBRD base with VFX grip, Thrustmaster A10c and F/A-18 grips ¦ VKB Gunfighter Mk4 and MCG Pro ¦ Thrustmaster Warthog Throttle ¦ VKB STECS Throttle ¦ Virpil TCS rotor base with Shark and AH-64D  grips ¦ MFG Crosswinds ¦ Total Controls Multi-Function Button Box ¦ Pimax Crystal

Posted

@Greyman @hornblower793

Thanks guys!

Cool to know.

I must have done something wrong before then. Wouldn't be the first time!

 

Sent from my ANE-LX1 using Tapatalk

Posted
@Greyman @hornblower793

Thanks guys!

Cool to know.

I must have done something wrong before then. Wouldn't be the first time!

 

Sent from my ANE-LX1 using Tapatalk

 

From a couple of rapidly created quick missions, it would appear that VAICOM Pro works fine with the J-11. I managed to fly around and control flight formation with 3 AI comrades, talk to ATC to get me down at a couple of airfields and ask the flight to engage and destroy a couple of A10Cs, the second one of which was taken down in a rather creative manner that killed both planes, but that's another story. (AI = Abnormal Intelligence methinks).

 

Having said that, i did have a vague recollection of a previous issue, from when the J-11 first came out and a search of this thread confirmed that., However, it looks like it was either just a one-off issue or Hollywood has sorted it out with a subsequent version.

Posted (edited)
Since the last OB update, the "loud and clear" command from AIRO doesn´t work anymore.

NavGrid commands also struggling.

 

 

I have 2 problems with Jester since last update: "Loud and clear" and "Check"

 

4:13:58.876 TX5 | ICS: [ ] , [ Confirm Checkpoint ]

4:13:58.872 Recognized : 'check'

 

4:36:55.928 Done.

4:36:55.928 Constructing message...

4:36:55.927 TX5 | ICS: [ F-14 AI RIO ] , [ Confirm ICS test ]

4:36:55.926 Have result, identified as command: Loud and Clear

4:36:55.925 Captured sentence: loud and clear

4:36:55.921 Recognized : 'loud and clear'

4:36:54.237 (awaiting additional input)

4:36:54.236 Have result, identified as recipient: Jester

4:36:54.235 Captured sentence: jester

4:36:54.231 Recognized : 'jester'

 

No reaction. If I say "assisted startup" instead of these words he goes along with the checklist.

Edited by Doctress
Posted
From a couple of rapidly created quick missions, it would appear that VAICOM Pro works fine with the J-11. I managed to fly around and control flight formation with 3 AI comrades, talk to ATC to get me down at a couple of airfields and ask the flight to engage and destroy a couple of A10Cs, the second one of which was taken down in a rather creative manner that killed both planes, but that's another story. (AI = Abnormal Intelligence methinks).

 

 

 

Having said that, i did have a vague recollection of a previous issue, from when the J-11 first came out and a search of this thread confirmed that., However, it looks like it was either just a one-off issue or Hollywood has sorted it out with a subsequent version.

Cool! Thanks!

 

Sent from my ANE-LX1 using Tapatalk

Posted
I have 2 problems with Jester since last update: "Loud and clear" and "Check"

 

 

No reaction. If I say "assisted startup" instead of these words he goes along with the checklist.

 

 

Confirmed. Same over here

Posted
Hi,

 

I have Vaicom Pro with AIRIO and it has worked fine. But now, when I open the configuration window, I just get a blank white box opening instead of the configuration panel.

 

Can anyone help me?

 

Thanks

 

Renzo

 

Renzo, have you been able to fix your problem? I started having the same issue yesterday and so far I have not figured it out.

Posted

ITS WORKING!!

I got frustrated and re-downloaded DCS Open Beta Uninstalled Voice Attack then reinstalled and its working.

Now to try it in VR.

 

 

Thanks for all the help.

13700K, MSI Z690 D4 Edge wifi, Swiftech H360X3 Cooling with Corsair Water Block, Gigabyte 4090 OC, 64gb Trident Z 3600 CL16, Evga 850W G2 power supply, Moza AB9, Virpil Apha Prime, Winwing Orion 2 Viper, TM Warthog,  MFG Crosswinds With Damper, TrackIR 5, HP Reverb 2, Pimax Crystal

 

 

 

 

Posted
ITS WORKING!!

I got frustrated and re-downloaded DCS Open Beta Uninstalled Voice Attack then reinstalled and its working.

Now to try it in VR.

 

 

Thanks for all the help.

Great!

 

Sent from my ANE-LX1 using Tapatalk

Posted
Renzo, have you been able to fix your problem? I started having the same issue yesterday and so far I have not figured it out.
You guys mean the VAICOM control panel?

 

Sent from my ANE-LX1 using Tapatalk

Posted

Hi everyone,

 

It's my second day with Vaicom Pro. I've completed training the Windows 10 speech recognition but VoiceAttack simply doesn't understand the difference between *AWACS*, instead it thinks *AMEX*. :(

 

Is there any way to solve this issue?

 

Thanks.

Posted
Hi everyone,

 

 

 

It's my second day with Vaicom Pro. I've completed training the Windows 10 speech recognition but VoiceAttack simply doesn't understand the difference between *AWACS*, instead it thinks *AMEX*. :(

 

 

 

Is there any way to solve this issue?

 

 

 

Thanks.

Train more! Add AWACS with pronunciation recording to MS Speech Dictionary. Add AMEX to block list.

 

Sent from my ANE-LX1 using Tapatalk

Posted
Yes. The vaicom panel is not opening
Just to make sure. VA, is of course running as admin? I think I heard on the Discord that it had reverted for somebody for some strange reason.

Try to re-download and replace the VAICOM dlls.

 

Sent from my ANE-LX1 using Tapatalk

Posted

This is not a bug per-say it's just odd; viacom seems to leverage the registry key:

 

HKEY_CURRENT_USER\Software\Eagle Dynamics\DCS World\Path

to store its files in DCS

 

JesterAI_Page.lua
sounds\Speech\common.lua
sounds\Speech\speech.lua
D:\Games\Eagle Dynamics\DCS World Openbeta\Scripts\UI\gameMessages.Lua
D:\Games\Eagle Dynamics\DCS World Openbeta\Scripts\UI\RadioCommandDialogPanel\RadioCommandDialogsPanel.lua
D:\Games\Eagle Dynamics\DCS World Openbeta\Scripts\UI\RadioCommandDialogPanel\TabSheetBar.lua

 

does this path "matter"? it doesnt seem to? I have both beta and stable versions installed and it seems to work OK, it doesnt even seem to make a difference if the game is installed in that directory or not(the reason i found it was i kept on finding files on my D: drive which doesnt have ED installed on it anymore), it doesn't even seem to mind if the registry key is blank, and nor does DCS...

 

My questions are these:

 

- is there a preferred path for these files?

- is this the reason some of us get odd "broken" behaviours when we upgrade? running both stable and beta and this set of files some of interacting between versions/viacom and this path?

- where does it create these files if the path isn't available? (e.g. its blank)

- know this regkey used to be used for starforce activation, i think, does anyone know what it is for now?

SYSTEM SPECS: Hardware AMD 9800X3D, 64Gb RAM, 4090 FE, Virpil T50CM3 Throttle, WinWIng Orion 2 & F-16EX + MFG Crosswinds V2, Varjo Aero
SOFTWARE: Microsoft Windows 11, VoiceAttack & VAICOM PRO

YOUTUBE CHANNEL: @speed-of-heat

1569924735_WildcardsBadgerFAASig.jpg.dbb8c2a337e37c2bfb12855f86d70fd5.jpg

Posted
@Hollywood_315 hey, are you OK man? It's since ages you last posted here... I hope all is well.
Second that! I'm getting worried. No posts since early March!

 

Sent from my ANE-LX1 using Tapatalk

Posted

Hollywood, I have had VAICOMPRO for a long time. Couple years or more? I was never able to get windows voice recognition to work. Turns out it was my shitful Asus sound software that I installed as part of the mobo setup. At wits end, I removed this, and voice recognition worked instantly! I couldn't believe it, but there you go. Installed VAICOMPRO and now it's working really well. Didn't even need to voice train.

Just wanted to say thanks for keeping up the support on this, I can finally enjoy this great app!

 

A hands off "ready pre contact" is worth its weight in gold lol.

7700K@5Ghz, 32GB 3600 CL16, 3080.

Posted (edited)

The C-101 has a radio setup with universal PTT buttons. The button on the stick and the button on the throttle in the front cockpit keys the mic for the form of communication specified by selector switche on its console which chooses between Intercom, UHF, and VHF radios. The rear cockpit has the same two PTT buttons locations that are tied to its own independent mic mode switch with the same selection options. It would be really cool if VAICOM could map one or more HOTAS inputs to a common PTT or support multiple inputs being mapped to the same TX functions and then use the position of the selector switch to determine which TX is activated by the mapped inputs. In this case, two independent pairs inputs and mode selections are needed to support front and rear seat controls.

 

I am pretty sure there are other aircraft with similar setups (i.e. all available PTT buttons are key whatever radio is selected). I think in most of those cases, VAICOM Pro shows only TX1 or TX2 enabled and automatically chooses the correct radio based on the voice command issued. Such aircraft would benefit from similar functionality.

Edited by streakeagle

[sIGPIC][/sIGPIC]

Posted
The C-101 has a radio setup with universal PTT buttons. The button on the stick and the button on the throttle in the front cockpit keys the mic for the form of communication specified by selector switche on its console which chooses between Intercom, UHF, and VHF radios. The rear cockpit has the same two PTT buttons locations that are tied to its own independent mic mode switch with the same selection options. It would be really cool if VAICOM could map one or more HOTAS inputs to a common PTT or support multiple inputs being mapped to the same TX functions and then use the position of the selector switch to determine which TX is activated by the mapped inputs. In this case, two independent pairs inputs and mode selections are needed to support front and rear seat controls.

 

I am pretty sure there are other aircraft with similar setups (i.e. all available PTT buttons are key whatever radio is selected). I think in most of those cases, VAICOM Pro shows only TX1 or TX2 enabled and automatically chooses the correct radio based on the voice command issued. Such aircraft would benefit from similar functionality.

I might misunderstand you. You would like VAICOM to be able to change the selector switch in the cockpit?

Have you tried single to multi?

 

Sent from my ANE-LX1 using Tapatalk

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...