Need To Wipeout Viacom Start Again

[Fang333333]

I've been on here before with Viacom issues that originated from an update in Feb. Viacom has slowly degraded over time and now no longer works even after clearing LUAs, reinstall, DCS Fix, Selecting every option "Openbeta", Stream" etc. (I am Openbeta-non-Steam). Also have given exclusive antivirus permissions, UA control, Run as Administrator, etc

 

Viacom turns on. It lags for (at least) a minute before going "BOOP" and accepting commands. It takes another minute to recognize and accept the command. (Press TX 1 no response/unrecognized response). It then will accept ONE MAYBE 2 commands after its lengthy boot up, and then Viacom ceases ALL functions. (No transmit. No menu via alt+ctl+C) BUT background chatter does still plays. Voice Attack is not frozen.

 

I need help wiping out Viacom and trying again. Before the update back in Feb Viacom ran great. It has slowly degraded and now literally no longer works accept for 1 or 2 commands at start. If it continues to work like this I have no choice but look for a refund. I love this software and the community but ONE OR 2 COMMANDS per mission is hardly worth the money and time I have put into this.

 

Please help help me figure out what this issue is. Please

Fang

Edited August 31, 2020 by Fang333333

[MAXsenna]

Did you try the ARIO temporary fix?

 

Look at @hornblower793's last post in the main thread.

Cheers!

 

 

Sent from my ANE-LX1 using Tapatalk

[hornblower793]

I also have a delay in startup - it came after the last update to VA.

 

 

 

As for the rest it would be useful to know a lot more about your current set-up Fang (in case anything has changed). What other software are you running and what hardware

[MAXsenna]

I also have a delay in startup - it came after the last update to VA.

 

 

 

As for the rest it would be useful to know a lot more about your current set-up Fang (in case anything has changed). What other software are you running and what hardware

Delay in startup with large profiles/plugins has been confirmed in the VA Discord if I remember correctly. VA needs 5-10 seconds on my system as well.

 

Sent from my ANE-LX1 using Tapatalk

[hornblower793]

I dream of 5 to 10 seconds - on mine it is closer to 30 - 45 seconds:lol:

[MAXsenna]

I dream of 5 to 10 seconds - on mine it is closer to 30 - 45 seconds

Whaaaaat?? Hmmm... I need to time it. Maybe I'm wrong. I actually start the VAICOM tray app, and then it starts VA.

 

Sent from my ANE-LX1 using Tapatalk

[hornblower793]

Whaaaaat?? Hmmm... I need to time it. Maybe I'm wrong. I actually start the VAICOM tray app, and then it starts VA.

 

Sent from my ANE-LX1 using Tapatalk

It isn't a big deal - i spend the time firing up my rift s headset

 

Sent from my SM-T835 using Tapatalk

[Fang333333]

Yes but can anyone help me because MINE stops working after 1 or 2 commands tops.

Voice attack runs but Viacom gets stuck. No commands. No Transmit Beep. No alt ctl C menu. I'm not using the F-14 right now, my main concern is that Viacom is no longer working for me after 2 commands.

Thank you friends

Fang

Edited September 2, 2020 by Fang333333

[Fang333333]

Did you try the ARIO temporary fix?

 

Look at @hornblower793's last post in the main thread.

Cheers!

 

 

Sent from my ANE-LX1 using Tapatalk

 

Good to see you again Max.Can you point me to that link, I get easily confused lol. It is a problem with Vaicom not Ario, but perhaps I need to see what your talking about.

Edit I do have ARIO installed and own it.

Edited September 2, 2020 by Fang333333

[hornblower793]

Yes but can anyone help me because MINE stops working after 1 or 2 commands tops.

Voice attack runs but Viacom gets stuck. No commands. No Transmit Beep. No alt ctl C menu. I'm not using the F-14 right now, my main concern is that Viacom is no longer working for me after 2 commands.

Thank you friends

Fang

Fang,

 

As requested earlier in this thread, can you tell us about the rest of your setup (hardware and software you are running at the same time, how you are controlling Vaicom etc)

 

Does Vaicom stop responding if you don't have DCS running?

 

What settings do you have in VA and Vaicom configs?

 

Sent from my SM-T835 using Tapatalk

[MAXsenna]

Good to see you again Max.Can you point me to that link, I get easily confused lol. It is a problem with Vaicom not Ario, but perhaps I need to see what your talking about.

 

Edit I do have ARIO installed and own it.

Hi Fang! Post your setup per Horn's suggestion and we'll see. Okay?

Cheers!

 

Sent from my ANE-LX1 using Tapatalk

[Fang333333]

Fang,

 

1. As requested earlier in this thread, can you tell us about the rest of your setup (hardware and software you are running at the same time, how you are controlling Vaicom etc)

 

Does Vaicom stop responding if you don't have DCS running?

 

What settings do you have in VA and Vaicom configs?

 

Sent from my SM-T835 using Tapatalk

 

Hi Hornblower I have posted this (Including the following) but in all the conversations I can see how it has been misplaced. I run Vaicom through keyboard mode so my x-55 HOTAS buttons can be assigned through emulation. THE TX ISSUE HAS NOTHING TO DO WITH CONTROLLER INPUTS OR ANY INPUTS. IT IS ONLY WITH VAICOM OPERATIONAL. I confirmed this via Youtube vids. Specifically I run my TX commands via (Right Shift + 0-6 ). Remember the problem now is that Vaicom just stops. No commands or anything are recognized.

 

The settings I have switched around as mentioned above, it is nothing set because Vaicom no longer works. I run latest Openbeta Non Steam. In the past, I have found that actually selecting the opposite of those settings in Vaicom (Steam not standalone as I own) had help prolong crashing and phantom TX presses (Again Phantom Presses done by Vaicom and no input on my computer). It did not help much, but a little.

 

I have only one version of DCS and have always been the same. I am running the latest Windows 10 but remember my woes with Vaicom started in feb. It was literally working. Got Updated. than started phantom transmits crashes etc as shown in videos. I figured it was a bad update but it never recovered.

 

As described above Vaicom does not freeze or have any problems besides long bootup. When DCS loads a mission, Viacom in the past became unstable. Now when mission loads, It ceases function after 1 or maybe 2 commands tops. Voice Attack is operationsal but I can not even access Vaicom menu via ctl + alt + C.

 

I own EVERY module in DCS and this is the same across the board.

 

Operating System: Windows 10 Home Insider Preview 64-bit (10.0, Build 20190) (20190.rs_prerelease.200807-1609)

System Manufacturer: HP

System Model: OMEN by HP Laptop 15-dh0xxx

BIOS: F.32 (type: UEFI)

Processor: Intel® Core i7-9750H CPU @ 2.60GHz (12 CPUs), ~2.6GHz

Memory: 32768MB RAM

Available OS Memory: 32644MB RAM

Page File: 17472MB used, 22596MB available

Windows Dir: C:\WINDOWS

DirectX Version: DirectX 12

Card name: NVIDIA GeForce RTX 2060

C: = 500gb SSD (DCS installed on)

D: =1 TB

 

Please get back to me Hornblower, I know one time I responded to your questions and you never came back. I understand you are busy.

 

Thank you all for taking this seriously

Fang

Edited September 4, 2020 by Fang333333

[hornblower793]

Hi Hornblower I have posted this (Including the following) but in all the conversations I can see how it has been misplaced. I run Vaicom through keyboard mode so my x-55 HOTAS buttons can be assigned through emulation. THE TX ISSUE HAS NOTHING TO DO WITH CONTROLLER INPUTS OR ANY INPUTS. IT IS ONLY WITH VAICOM OPERATIONAL. I confirmed this via Youtube vids. Specifically I run my TX commands via (Right Shift + 0-6 ). Remember the problem now is that Vaicom just stops. No commands or anything are recognized.

 

The settings I have switched around as mentioned above, it is nothing set because Vaicom no longer works. I run latest Openbeta Non Steam. In the past, I have found that actually selecting the opposite of those settings in Vaicom (Steam not standalone as I own) had help prolong crashing and phantom TX presses (Again Phantom Presses done by Vaicom and no input on my computer). It did not help much, but a little.

 

I have only one version of DCS and have always been the same. I am running the latest Windows 10 but remember my woes with Vaicom started in feb. It was literally working. Got Updated. than started phantom transmits crashes etc as shown in videos. I figured it was a bad update but it never recovered.

 

As described above Vaicom does not freeze or have any problems besides long bootup. When DCS loads a mission, Viacom in the past became unstable. Now when mission loads, It ceases function after 1 or maybe 2 commands tops. Voice Attack is operationsal but I can not even access Vaicom menu via ctl + alt + C.

 

I own EVERY module in DCS and this is the same across the board.

 

Operating System: Windows 10 Home Insider Preview 64-bit (10.0, Build 20190) (20190.rs_prerelease.200807-1609)

System Manufacturer: HP

System Model: OMEN by HP Laptop 15-dh0xxx

BIOS: F.32 (type: UEFI)

Processor: Intel® Core i7-9750H CPU @ 2.60GHz (12 CPUs), ~2.6GHz

Memory: 32768MB RAM

Available OS Memory: 32644MB RAM

Page File: 17472MB used, 22596MB available

Windows Dir: C:\WINDOWS

DirectX Version: DirectX 12

Card name: NVIDIA GeForce RTX 2060

C: = 500gb SSD (DCS installed on)

D: =1 TB

 

Please get back to me Hornblower, I know one time I responded to your questions and you never came back. I understand you are busy.

 

Thank you all for taking this seriously

Fang

 

 

If you just run VA / Vaicom without DCS running does it still crash after a couple of commands or can you keep issuing commands for a longer period of time with them appearing in the VA log window.

 

 

 

As you are using the keyboard for your TX inputs, does it work if you launch DCS without the x-55 connected and no emulator software running - you can hit active pause once in a mission to avoid having to fly the plane using keyboard buttons but VAICOM should still work.

 

 

What other software do you have running in the background?

 

 

The above will help us try and isolate the problem step by step

[Fang333333]

If you just run VA / Vaicom without DCS running does it still crash after a couple of commands or can you keep issuing commands for a longer period of time with them appearing in the VA log window.

It will not crash like when DCS is on. It still has a long boot up time followed by a long :"wake up period" period. The wake up period is where I hit xmit say command "Chief turn on ground power" and it sits confused. I say again and this time it shows the mic bar red (not listening), like it is digesting the command. Say again, still no response, it thinks, than all at once shows the 3 rejected commands. From there it works more or less. Until I decide of course to use it with DCS. Than 1 command and it just sits forever after completion, or not completing the command.

 

"As you are using the keyboard for your TX inputs, does it work if you launch DCS without the x-55 connected and no emulator software running - you can hit active pause once in a mission to avoid having to fly the plane using keyboard buttons but VAICOM should still work."

 

Viacom becomes noticeably different when DCS runs. It does not matter if the computer is stripped of ALL peripherals, it has the same results. In the past (when it worked a little before freezing) I tested and would still get phantom button presses. I ran against a test program and no inputs were received during the phantom Xmit. Vaicom still locked up, just later in a mission, unlike now.

 

 

"What other software do you have running in the background?"

 

I do have alot, Oculus, Simconnect for 2 buttkickers. Tacview (though normally never running) controller software/emulators for x-55, x-65, flight panel, strategic commander, 4 throttle quadrants (If you count the 2 HOTAS), rudder pedals. I do have Voice Attack/Vaicom set to ignore any controllers except keyboard in case you wondered...

 

All that being said, I have long since tested Vaicom without anything running in the background. Field stripped. There is NO difference. None. As mentioned above I also tried all sorts of things on my own, granting special permissions, antivirus (which never hurt it before this), you name it.

 

"The above will help us try and isolate the problem step by step"

 

I will try to do everything I can to help you get Vaicom back working.

Edited September 5, 2020 by Fang333333

[hornblower793]

The lines with red squares are interesting - are you saying anything except 'Chief ground power on' since it oooks like the microphone has picked up the start of an attempt to write a novel.

 

What sort of microphone are you using and is it hooked directly to your soundcard or via USB? Is there external sound while you are playing?

 

Do you have any profiles daisy-chained to the Vaicom one? It might be worth setting up a new profile and adding some different commands to see whether they are clearly recognized by VA (for instance, i have a Current time one so I can keep track of real world while in VR).

 

Sent from my SM-T835 using Tapatalk

[Fang333333]

The lines with red squares are interesting - are you saying anything except 'Chief ground power on' since it oooks like the microphone has picked up the start of an attempt to write a novel.

 

What sort of microphone are you using and is it hooked directly to your soundcard or via USB? Is there external sound while you are playing?

 

Do you have any profiles daisy-chained to the Vaicom one? It might be worth setting up a new profile and adding some different commands to see whether they are clearly recognized by VA (for instance, i have a Current time one so I can keep track of real world while in VR).

 

Sent from my SM-T835 using Tapatalk

 

 

Hi Hornblower, I am sorry it is taking so long to get back to you. Its a busy workweek with a busy birthday (mine unfortunately). If I disappear for a few days (which I am trying to avoid) just know that this issue is really something I want fixed and I am going to be back lol. I am even thinking of taking a risk and wiping out DCS and reinstalling, but I must find the time for that.

 

My Mic is hooked to a well powered USB hub through to USB 3.0. The best answer I have is that the mic only messes up (The above issues screenshotted) when Viacom is messing up. The mic just seems to have no issues. When I first set it up I had VA listening through Voicemeter which it did not like. I then set it to listen to the mic directly and recognition was fine. Also no changes have been made to setup. I do have videos somewhere on this.

 

I will try testing a separate profile if I can. I do not specifically remember doing this however, I must strongly state that it reeeeally looks like the issues happen when Vaicom turns on and DCS is running.

 

Thank you for working with me on this Hornblower, it is such a nice change to have someone go step by step with me

 

Thank you

Fang

[hornblower793]

Don't worry about delays in replying and hope the birthday is / was good.

 

 

For the screenshot above, was anything else running?

 

 

If you right click the Windows 10 volume control, select sound and then click on the recording tab, which items are enabled?

[MAXsenna]

Fang, stupid question. But Microsoft Speech Recognition is not running, right?

What about Cortana? She gave me some grief once. Sort of conflict, but you shouldn't see that text in the VA log in any case. I agree with Hornblower. That seems to be the issue, that your mic pics up something it shouldn't be.

You don't have another mic you've forgotten about?

Sometimes my headset and Windows don't like each other, and Windows assigns my PS3 cam I use for TrackIR instead.

Really hope you will sort it out soon!

Cheers!

 

Sent from my ANE-LX1 using Tapatalk

Edited September 9, 2020 by MAXsenna
Spelling

[hornblower793]

A quick thought following on from Max's post - are you trying this with, or without VR running (Oculus) - mine has a nasty habit of resetting microphones whenever it updates (Rift S)