Fang333333

Hello Andre, I am having an issue where Simshaker Sound Module is no longer sending signals to Voicemeter. I had this problem once before and I reinstalled and all worked correctly. It was working yesterday than I restarted comp and it stopped sending signals. I tried reinstall but it did not work this time! I literally press test in sound module, it shows that sound is playing but I go in Voicemeter and it is not receiving any signal. Again this happened once before and I fixed it by reinstalling, now it won't work and I am worried. Fang

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

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.

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

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.

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

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

I'm having some big performance issues myself with the map.I hope they optimize

I too see major stutters on this map. Its not even FPS it is stutter. All other maps (I do own them all) perform nothing like this. As it sit's on my end right now, this map is honestly not good enough to record videos with. It is also not smooth enough to really train on, even though it seems like it should be. This is my 2 cents, personally I am hoping this is just Early Access woes, and an performance increase is in the works. Though I would like some confirmation on that. Fang

Same here. Was surprised to see others report good things

Thanks John! I have been reading it ove,r but I am still kinda confused as to what I am looking at? Could you elaborate what I'm doing here? Thanks for the response this looks like what I need too!

So I see many threads on this but I need an answer quicker. The new Syria Map has been released and I need to install the module on a separate drive. DCS has finally eaten through my SSD. How can I get this on my 2nd drive quick and easy? Fang

Hello folks, I have been away from DCS for maybe 2 weeks tops and I have noticed some peculiar issues. Can anyone shed some light on some of the following?: - F 18 missiles are chasing ghosts! (I've launched 20+ some Aim 7s and none of them hit! These are not bad shots (I have logged many hours with every DCS module), the missiles literally look like they are AVOIDING hitting Migs in "Ode to Mongo". They change direction drastically despite the enemy flying straight and dumb (no countermeasures). They look like they are chasing a ghost! - "Ode to Mongo" is shorter and kinda sucks now? - Some missions I made and saved in missions no longer exist, were there changes to the mission editor? I had shortened "Dawn Raiders" so i could start on waypoint 3. Now I cannot remake the mission becuase of a timing issue and I am stuck looking at the map waiting for AI to do their thing. - Bizarre shadow, the cockpit in the F-18 has a "shadow" that basically makes the cockpit go unnaturally dark and then bright in daylight. - F-18 DDIs are not as clear as they once were in VR. I pretty much have to zoom in to read them. - Also experienced a DCS crash I have not seen before. :noexpression: Thanks Fang

Rough ETA?

Hello all, So far since the latest patches I am having some issues with Simshaker. It seems certain effects (If not all effects stop working) and SSA needs restart when switching missions. So I go into the F-14b I put hook down and get a response but nothing for flaps or wing movement. Once I get it working by software restarts, I switch a mission and hey, no flap movement but the hook rumble is there again. I verified on voicemeter banana that no sound is being played. All test samples play fine, yet it seems as if specific sounds are not being qued by the sim. This is strange as Simshaker is literally the most stable module associated with DCS for me. I have not noticed any warnings or strange logs. I have also reset simshaker in the options and entirely deleted any luas. Also DCS repair I'm off to do a little work so if I do not respond right away know I will be back lol. Thanks Fang

well Viacom and Voice Attack have degraded again to the point of not accepting commands. It recognizes rarely and executes sometimes. Compared to a few days ago where it both recognized and executed brilliantly, but Voice Attack would stop accepting any commands, keyboard shortcuts after 5 minutes or later. The only thing that has changed is me constantly reinstalling/deleting/repairing all aps in random orders. The result is Viacom works but with horrible quirks usually. Now I cannot get it to work at all. Please somebody help fix this. Its been months. I know the software was stable in March.

lol Thanks All, I am not sure if it was a Viacom execution problem or if I'm losing my mind, but Jester seems to be working again. I didn't really do anything besides my usual uninstall reinstall of Viacom/VA ( I am having terrible Voice Attack Problems). Thank you all for the suggestions. Case closed. P.S I really love Jester, I hope we see more aircraft like this!

Never had to upload. Where is it?

Hi Hollywood, Thanks for the response. I have confirmed the radio is set to default. I am not sure if this is Viacom or what, but within the last 3 days Jester does not align the INS or even turn on the TID. The command is recognized, other command are working, but my F-14 cannot be started now without having to manually align. Thanks Fang

I have tested this for 2 days now, I am not sure when the last update was but within the last 4 days JESTER NOP LONGER TURNS ON THE TID or does the alignment! I have been flying the F-14 for a little while, I know its not anything I am doing wrong (parking brake etc.). When I tell Jester to align, I get the same breathy response thing but then he does nothing. I am using Viacom, but Viacom is recognizing the correct command. Again. Jester just never touches the TID or INS. Ideas? Fang

Hello Grey! Thank you for the suggestion. I would bet the roof over my head there are no inputs lol. Checked and rechecked. Then checked only to recheck. I also made a video showing no other inputs. Only issue is with viacom on. I am now having it where when I am in the F14 and VA just STOPS any user input. I sit on tarmac coladas and dark. It works, for one command, than xmit button no longer recognizes. Hitting Ctl C, Chatter shortcuts, nothing works. Restart. Say one command. Command complete. Transmit again, no transmit response. No response to any key presses although it is not frozen. Restart VA. Rinse. Repeat Lol, this is why I have to take some time away from these bugs, its o frustrating. The whole thing VA/Viacom combo is extremely unstable. It's like Viacom is constantly confusing itself. Lastly, I have a feeling we are gonna see more people getting this issue. I see a few here and there describing the same kinda stuff in the last few weeks. The problem is that the problem is MANY problems, so one person might have the xmit button issue while someone else is experiencing the delayed response issue. Thank you all Fang

I'm sorry all for not coming back here in awhile, but I have little news. Vaicom has been smoother for me out of nowhere but is not at all fixed. It seems the F-14 will just stop receiving commands period. It almost looks more like a Voice Attack problem for this specific issue but I cannot really tell. VA just stops taking Mic inputs completely midflight. (Press Mic= No response). Even restarting VA does not restore Mic xmit presses half the time. Also, on startup, VA bizarrely refuses to listen to my mic until I open the VA sound settings (Where you select audio input). I make no changes, press "OK" and my input bar then reads the mic. I have to do this on every startup of VA. Lastly it seems more people are starting to trickle in with the Mute/unmute problem, originally posted in this thread. Over on the Voice Attack forum, I noticed yet another thread claiming Vaicom is cutting off the Xmit button on it own. 2 more users have added to this already. https://forum.voiceattack.com/smf/index.php?topic=3314.new#new Please let me know if you have any theories for the above, Fang333333

+ 10000000000000000000000000000000000000! VR must be optimized.

+1

hello?