Jump to content

Terrible programme - waste ?


Recommended Posts

Posted
5 hours ago, Hawkeye_UK said:

Yea im sure if you just do single player and dont want to talk to other people then its fine, im really struggling though (and not the only one) re multiplayer and SRS.

The question I answered was generic "i still cannot see the advantage of having the programme over a self made voiceattack profile" It may not work well for your specific case but that doesn't render it to not be of great benefit to others. Perhaps you should make a constructive suggestion rather than rubbishing a product with an attention seeking thread title...

  • Like 3

AMD 5800X3D · MSI 4080 · Asus ROG Strix B550 Gaming  · HP Reverb Pro · 1Tb M.2 NVMe, 32Gb Corsair Vengence 3600MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · VIRPIL T-50CM3 Base, Alpha Prime R. VIRPIL VPC Rotor TCS Base. JetSeat

Posted
10 hours ago, Hawkeye_UK said:

If thats the case then please can someone explain why having radio 1 button bound for SRS and the same button for Viacom radio 1 then doesnt allow SRS to work.  when you push the PTT it opens briefly and closes itself.

...

The only way can get SRS working is to turn off viacom and do not have the same radio 1 and 2 keybinds.  As in making viacom pointless. 

I have the same buttons bound for SRS and VAICOM (SRS radios 1, 2, 3, and Intercom bound the same as VAICOM TX1, TX2, TX3, and TX5 respectively) and have used them successfully together for years now. All I did was use the instructions that came with each. I use the Broadcast Parallel method in VAICOM since I found the other implementations in VAICOM to be awkward. A year or so ago I decided I did not like having my VAICOM commands going out over SRS and so I turned off the "radio switch works as PTT" in SRS and bound a separate button for SRS PTT. However before doing that, VAICOM and SRS would both happily transmit at the same time when their common radio button was pushed and held.

If you are looking for help here then I'm sure you will find it. No one who helps here is paid. We are just enthusiasts. So some patience might be required. Your attitude in this thread seems to be about criticism rather than seeking help, however. It is not true that VAICOM and SRS require separate keybinds. But even if it were true, this would not make VAICOM "pointless." At best it would mean it is not the right tool for you, and it would not make it a "terrible program" as the title of your thread implies.

If you want help you might start by providing a lot more precise detail about your setup and exactly what goes wrong. For example, when you say "the PTT opens briefly and closes itself" that is not precise. What exactly opens and closes by itself? Surely the button is not moving by itself! And which of the several VAICOM options for SRS integration are you using?

BTW, it's vAIcom, as in voice AI communications, not vIAcom, which is a large telecommunications company.

  • Like 3

I'm Softball on Multiplayer. NZXT Player Three Prime, i9-13900K@3.00GHz, 64GB DDR5, Win 11 Home, Nvidia GeForce RTX 4090 24GB, TrackIR 5, VKB Gunfighter III with MCG Ultimate grip, VKB STECS Standard Throttle, CH Pro pedals

Posted
22 hours ago, Hawkeye_UK said:

If thats the case then please can someone explain why having radio 1 button bound for SRS and the same button for Viacom radio 1 then doesnt allow SRS to work.  when you push the PTT it opens briefly and closes itself.

In the spirit of providing help, after running a few experiments, I think I can explain what you are experiencing. You are almost certainly using the Dynamic Switching mode of VAICOM for SRS integration. When you use that mode VAICOM expects you to first give a VAICOM command, and then possibly follow up with a voice broadcast over SRS. It therefore mutes the SRS channel as soon as you push the PTT, so that your VAICOM command does not get broadcast. (SRS appears to open very briefly then close the channel because VAICOM apparently cannot mute the channel before it opens.) Once you successfully give a VAICOM command it will re-open the SRS channel automatically if you have "Auto Switch" selected. Or you can give a "Switch" command to reopen the SRS channel if "Use Switch Command" is selected. All of this assumes you are still holding the PTT key down. Experimenting, I found that if the VAICOM command fails then you might need to use the Switch command to open the SRS channel. And if you just want to talk on SRS without giving a VAICOM command first you need to say "Switch" at the start to reopen the SRS channel.

Does it work as documented? Yes. I tested it myself this evening. Is that procedure awkward? I believe it is, so I don't use it. Instead I turn off SRS Integration in VAICOM (which is essentially the same as using Broadcast Parallel mode). If you do that then the trouble you are experiencing should go away, but you will then have your VAICOM commands going out over SRS due to using a common PTT, which actually is more realistic if you think about it. (Certain VAICOM commands such as Select are the exception.)

Most of what I just wrote is well-documented in the VAICOM manual. The developers of SRS and VAICOM have worked together to provide a degree of integration, but they are still separate programs and this limits somewhat how realistically they can function together. But they can function together and many people are using both.

  • Thanks 1

I'm Softball on Multiplayer. NZXT Player Three Prime, i9-13900K@3.00GHz, 64GB DDR5, Win 11 Home, Nvidia GeForce RTX 4090 24GB, TrackIR 5, VKB Gunfighter III with MCG Ultimate grip, VKB STECS Standard Throttle, CH Pro pedals

Posted

It is all about the Mic!

I had a nightmare using the kneeboard with my VR G2 head set mic!

Now I have a pair of headphones that I bought on the Mic review alone.... kneeboard works perfectly every time.

  • Like 1

HP G2 Reverb (Needs upgrading), Windows 10 VR settings: IPD is 64.5mm, High image quality, G2 reset to 60Hz refresh rate. set to OpenXR, but Open XR tool kit disabled.

DCS: Pixel Density 1.0, Forced IPD at 55 (perceived world size), DLSS setting is quality at 1.0. VR Driver system: I9-9900KS 5Ghz CPU. XI Hero motherboard and RTX 3090 graphics card, 64 gigs Ram, No OC... Everything needs upgrading in this system!.

Vaicom user and what a superb freebie it is! Virpil Mongoose T50M3 base & Mongoose CM2 Grip (not set for dead stick), Virpil TCS collective with counterbalance kit (woof woof). Virpil Apache Grip (OMG). MFG pedals with damper upgrade. Total controls Apache MPDs set to virtual Reality height. Simshaker Jet Pro vibration seat.. Uses data from DCS not sound... goodbye VRS.

Posted

No problems with my G2 Mic. 

Everything works as expected. 

 

Regards 

Frank 

System: Asus ROG STRIX X570 , Ryzen 9 5900X , ASUS ROG STRIX LC 240 , 64 GB GSkill 3200 Trident Z , Powercolor Red Devil RX 6900 XT , Running SSD only

Input: Thrustmaster HOTAS Warthog , Saitek Pro Flight Rudder Pedals , Track IR 5, VoiceAttac with Vaicom Pro, HP Reverb G2

DCS Open Beta , Nevada NTTR Map, Persian Gulf Map , Syria Map, F-14 Tomcat , F/A-18C Hornet , F-16 Viper, AV-8B Harrier, Supercarrier

Posted

I use speakers which obviously is the worst option for using a mic. Bought a headset to replace my G1 headphones but was a bit of a faff wearing two headsets. After upgrading to Win11 I tried the G1 mic again and it has worked perfectly, even with the Mossie Merlins cranked up on the speakers!

I can't categorically say it is Win11 but something changed that made the mic work much better in my G1.

  • Like 1

AMD 5800X3D · MSI 4080 · Asus ROG Strix B550 Gaming  · HP Reverb Pro · 1Tb M.2 NVMe, 32Gb Corsair Vengence 3600MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · VIRPIL T-50CM3 Base, Alpha Prime R. VIRPIL VPC Rotor TCS Base. JetSeat

  • Recently Browsing   0 members

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