Jump to content

Wingman1387

Members
  • Posts

    11
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. The move to community supported (Great job getting this back to working guys! And thank you to Hollywood for moving this to opensource) prompted me update to the new version and try this again. I continue to have the same behavior. Every other PTT press results in a 'unit query' and ends with "listening suspended" message and the commands given will not be sent. The same with multi-part commands, i.e. "options" "Take one." The command will end after the first part is recognized with a "listening suspended" message. However, regardless of any other setting, if I have the VOIP Slider to "dynamic switching" it will still broadcast commands even with a "listening suspended" message. It will only happen with DCS in a mission. Any other time, everything works as expected with a PTT giving a "listening resumed" and release giving a "listening suspended." All I can determine is there must be something odd happening with the VOIP Control options. Wish that I understood how to code, and could help track this down myself. It is driving me nuts!
  2. After reading this, I was determined to figure out a way to make it work. I set all of the options completely back to default with the reset tab. In the MP tab I deselected everything and set VOIP to Broadcast parallel. Still had the same problem. However, when I went back and set Use with Multiplayer on and Dynamic switching, the listening suspended problem went away. I then went back and selected all of the other options one by one back to the way I had them previously. So far it continues to work. (and to make matters more odd, in the voice attack log, it still shows "listening suspended" after every other ptt press and hold, but it will still take and execute commands...) TLDR, try resetting to defaults, then Dynamic switching and use with multiplayer on. I'm not crazy about the dynamic switching, but I do very little MP so I can live with it for now.
  3. @Kila iceman If you haven't yet tried it, find the setting "verbose logging" and make sure that it is unchecked. I had a similar problem where an effect would get stuck and loop continuously if that setting was checked.
  4. Basically you need to create or modify the wave files that correspond to the best frequency range of your shakers. Then take them and put them into the custom folder for your simshaker sound module folder. Mine are found under /Documents/SimShaker Sound Module Samples.
  5. @Hollywood_315 @hornblower793 Did some further testing between 2.5.24 and 2.5.27. I don't know if there is something different in the polling of DCS or in how it interprets TX button presses, but in .24 a button press would always end in a "listening resumed" as long as the button was continually held. As seen in the log below, every other TX button press in .27 would initiate a poll for mission information and then end in "listening suspended" even as the physical button was continually held. (The top of the log was after I exited the mission and all the TX buttons were working as normal). From reading the manual it seems to be connected to the "TX Link" option for MP. I have tested it on and off, and with 'broadcast parallel', 'TX Link', and 'Dynamic Switching' selected with no change in results. Perhaps it would be worth pulling this feature out in a test build and see if the "listening suspended" issues continue? VAICOMPRO.log VAICOMPRO.log
  6. After a long hiatus, I came back to finish the Raven One campaign and have had this problem with the current version of VAICOM PRO. When trying to use the "options" command to display the F10 menu and selections, Voice Attack indicates "listening suspended," and further commands, (i.e. "Take One - Twelve") are not registered. The only way to start listening again is to release the PTT, which closes the comms menu in DCS. This is extremely annoying as it makes the "mystery/mission/server" and "options" commands useless. I tried in Through the Inferno single player missions and barebones missions I created myself to confirm. I have the same behavior with the F/A18, F16, and F14 so far. I did not test any other modules. After attempting most of the suggested solutions in this thread, I finally rolled back to 2.5.24. I tested with both the F/A18 and the F16, and both appear to be working with 2.5.24. I did notice something peculiar though. In 2.5.27 when initiating a command and holding the PTT button, VA would indicate "listening suspended" after the first command and would not reset to a "listening resumed" state unless the PTT was released and pushed again. In 2.5.24 VA would indicate "listening suspended," when initiating the first command, but then would immediately indicate "listening resumed," as long as the PTT was continually held. In short, it appears that in 2.5.27 "listening suspended" happens as soon as any command is recognized, and it remains suspended until the PTT button is released and pressed again. In 2.5.24 "listening suspended" happens when a command is recognized, but then it goes back to "listening resumed" without the PTT requiring a release and repress. Perhaps someone else can check to see if they are having the same behavior. Maybe this will help drill down to the bottom of the issue? For now I'm going to stick with 2.5.24, but I would really like to be able to use Vaicom with the Apache again! A fix would be amazing!
  7. I had a similar problem if "Verbose Logging" was enabled in SimShaker Sound Module. I would make sure that check box is unchecked
  8. First off, I want to say that I am really enjoying the immersion of a Sim Shaker set up. I added two Asura Bass Shakers to my cockpit and then bought the Sim Shaker Sound Module for output. So far it has been pretty good. Two little issues I've had though: I had the same problem, looks like the ideal frequency for these particular shakers is about 38-42hz for maximum force. With the default 20hz peak output force tuned for the buttkicker line of shakers, I was getting pretty weak effects for many things, and some strangely aggressive effects for the few things tuned for that ~40hz sweet spot. I went though and edited many of the effects from 20hz to 40hz and have had much better results. I'd be willing to zip them up and share if anyone would like. Also while experimenting with frequency shifting, I enable "verbose logging" in order to identify which effect was playing. Any time I had that feature enabled, after about 10 minutes DCS or SSM would get stuck in a loop and the last played effect continued indefinitely until SSM was force stopped though the task manager.
  9. Overall, I have to say that Vaicom pro is a fantastic piece of software! I have been using it for quite some time and for the most part it works just as it is advertised, allowing much better integration especially in VR. However, I've been having an issue with the AIRIO plugin and the manual radio tuning feature. Has anyone been able to make this function correctly? I can occasionally get the manual Tacan tune or the Link Tune features to work but the Radio Tune always comes back either recognizing "tune" as "two" in the output command list, or it simply states 'unrecognized command Radio Tune ###.### (with the #'s being the numbers I dictated) To try to rectify the misunderstood "tune/two," I tried to change the command in VA to 'Radio Tune;Frequency [0..3] [0..9] [0..9] decimal [0..9] [0; 2 5; 5 0; 7 5;]' thinking that would allow me to say ie "Radio Frequency 121.50" instead of "Radio Tune 121.50" but I still get an unrecognized "radio frequency" message. If I try to speak the "radio tune ###.## command I now get an output of 'AIRIO Radio Tune 000.000' and an in DCS message saying radio out of range. I'm at a lose with this one, especially because everything else in VAICOM that I have tried works pretty well.
  10. I run a 3 screen setup with NVIDIA Surround at 5760x1080. Using the 1 screen option makes the Radio Command Menu appear on the top right corner of the right screen and any radio messages appear on the top left corner of the left screen. Tutorial and briefing subtitle messages appear below the Radio Command Menu on the right screen. This is extremely hard to read while playing so I edited the Radio Commands Dialogue/CommandMenu.lua to move the Radio Command Menu to the center screen. Editing the gameMessages.lua allowed me to move the ATC/Radio messages to the center screen as well. Somehow though, this moved the tutorial and briefing subtitle texts completely off the screens. Does anyone know what ".lua" section I could edit to bring them back, preferably to the center screen, at least as an interim solution until the UIMainView bug is fixed? attached are my .lua files with the edits gameMessages.lua CommandMenu.lua
×
×
  • Create New...