IVC Problems in Flight - Outbound Only
-
Hi All,
Currently experiencing IVC issues in flight with IVC. I can broadcast fine on F1 and F2 but as soon as I enter flight I push UHF or VHF verifying the frequencies are correct. I can hear other players fine but they can’t hear me.
What I’ve done so far:
- Ports forwarded
- Verified correct recording device selected
- Checked frequencies in game
- Searched this forum for possible solutions
- Set my recording device to default and default comms
- Checked my AV to be permissive for IVC client
I’m not sure what else to check - will my DTC frequencies matter if I can hear the other players and my confirmed the correct frequencies on the UFC? I’ve not had a time where my frequencies don’t match my other elements.
I’m using mud’s profile on a warthog for keys, when broadcasting my UHF/VHF indicator goes inverted as expected.
Running Windows 10 64bit anniversary update, bitdefender AV, killed ASUS sonar suite or whatever that piece of software is, comms device is an astro a40 usb.
-
pressing F1 or F2 in flight is not a PTT, you will need to bind another button to be the in flight transmit button. In game, the F1 and F2 keys just press the COM1 and COM2 select buttons on the ICP.
-
Pre-planning F1 and F2 ptt work which is what I was referring to(thought that would be obvious), as I said I have my keys bound as per mud’s profile and the UHF and VHF go inverted in flight as expected but nobody can hear me.
To be completely clear as it seems I’ve been misunderstood, my ptt key is set as forward and aft comm switch on my warthog
-
Does the UHF/ VHF channel highlights in the DED when you are speaking ?
When you try again, can you make sure that the name in the IVC client is the same as your pilot callsign ? If you switched logbook after connecting to the server, those might not be the same, and you wont be able to transmit*.
*actually that is a bit more complicated… basically, you transmit, and the other clients will see that somebody is transmitting, but that somebody isnt a pilot in the game. And by default, those connections get filtered out by the other clients. More info in the BMS manual, section about IVC, look for the “outsider” argument. Plus, even if they could hear you, they wouldnt hear any radio distortion at all, it would be just like talking on a standard TS. Simply because the IVC clients of the other pilots would not know what is the position of the pilot transmitting, thus they wouldnt know how much distortion to apply, and revert to no distortion at all.
-
Yeah they do invert when I push to talk. I’ll double check the callsign and see if that helps but I’m definitely able to talk pre-flight with F1 and F2.
-
Yeah they do invert when I push to talk. I’ll double check the callsign and see if that helps but I’m definitely able to talk pre-flight with F1 and F2.
I know, and what I’m describing will not affect your ability to talk when in the UI Only in 3D.
-
Okay cool, I don’t recall changing my callsign the game before last but I definitely did last game. I’ll definitely double check when I get up again. Hope that’s it and thanks if it is
-
As long as you are pressing SimTransmitCom1 and SimTransmitCom2 not F1 and F2 (and F3) then this is the correct input. The fact that the DED labels are going reverse video is a good indication that you’re providing the correct inputs. I suppose also ensure that the reverse video highlight last as long as you hold down the input and just just a brief flash.
What would be helpful is having the buffer output from IVC_Server.exe’s command window. It spits out starting and stopping transmit and channel changes.
TeamSpeak 3 Server 3.0.3.2 (2015-06-10 10:47:37) SDK (c)TeamSpeak Systems GmbH Logging to file started (no console logging on Windows) 2016-10-18 18:24:25.842004|INFO |ServerLibPriv | |TeamSpeak 3 Server 3.0.3.2 (2015-06-10 10:47:37) SDK 2016-10-18 18:24:25.844506|INFO |ServerLibPriv | |SystemInformation: Windows 8 (9200) x64 (AMD or Intel) Binary: 32bit 2016-10-18 18:24:25.846508|INFO |ServerLibPriv | |Using hardware aes 2016-10-18 18:24:25.857018|INFO |Accounting | |Licensing Information 2016-10-18 18:24:25.858019|INFO |Accounting | |licensed to : Benchmark Sims 2016-10-18 18:24:25.859520|INFO |Accounting | |type : SDK-Offline 2016-10-18 18:24:25.861022|INFO |Accounting | |starting date : Tue Sep 21 00:00:00 2010 2016-10-18 18:24:25.862523|INFO |Accounting | |ending date : Mon Jan 01 00:00:00 2035 2016-10-18 18:24:25.864024|INFO |Accounting | |max virtualservers: 9 2016-10-18 18:24:25.865526|INFO |Accounting | |max slots : 288 2016-10-18 18:24:26.921031|INFO | | |Puzzle precompute time: 1054 Server running Server lib version: 3.0.3.2 [Build: 1433933257] SDK Create virtual server with 32 slots Binding virtual server to IP 0.0.0.0 2016-10-18 18:24:26.931419|INFO |VirtualServer |1 |listening on 0.0.0.0:9987 2016-10-18 18:24:26.932922|INFO |VirtualSvrMgr | |addServer() VirtualServer(1) started Create virtual server with 32 slots Binding virtual server to IP 0.0.0.0 2016-10-18 18:24:26.937426|INFO |VirtualServer |2 |listening on 0.0.0.0:9988 2016-10-18 18:24:26.939428|INFO |VirtualSvrMgr | |addServer() VirtualServer(2) started Create virtual server with 32 slots Binding virtual server to IP 0.0.0.0 2016-10-18 18:24:26.943933|INFO |VirtualServer |3 |listening on 0.0.0.0:9989 2016-10-18 18:24:26.945934|INFO |VirtualSvrMgr | |addServer() VirtualServer(3) started Falcon BMS IVC Server 1.1.1 commandline interface [q] - Quit [h] - Show this help [v] - List virtual servers [c] - Show channels of virtual server 1 [l] - Show clients of virtual server 1 [n] - Create new channel on virtual server 1 with generated name [N] - Create new channel on virtual server 1 with custom name [d] - Delete channel on virtual server 1 [r] - Rename channel on virtual server 1 [m] - Move client on virtual server 1 [C] - Create new virtual server [E] - Edit virtual server [s] - Stop virtual server Enter Command (h for help)> Client Duck-UHF joined channel Default Channel ID=1 on virtual server 1 Client Duck-VHF joined channel Default Channel ID=1 on virtual server 2 Client Duck-GRD joined channel Default Channel ID=1 on virtual server 3 Channel 243000 ID=2 created by Duck-GRD on virtual server 3 Client Duck-GRD moved from channel Default Channel ID=1 to channel 243000 ID=2 on virtual server 3 onClientStartTalkingEvent serverID=1, clientID=Duck-UHF onClientStopTalkingEvent serverID=1, clientID=Duck-UHF onClientStartTalkingEvent serverID=2, clientID=Duck-VHF onClientStopTalkingEvent serverID=2, clientID=Duck-VHF onClientStartTalkingEvent serverID=3, clientID=Duck-GRD onClientStopTalkingEvent serverID=3, clientID=Duck-GRD onClientStartTalkingEvent serverID=1, clientID=Duck-UHF onClientStopTalkingEvent serverID=1, clientID=Duck-UHF Channel 251 ID=2 created by Duck-UHF on virtual server 1 Client Duck-UHF moved from channel Default Channel ID=1 to channel 251 ID=2 on virtual server 1 onClientStartTalkingEvent serverID=1, clientID=Duck-UHF onClientStopTalkingEvent serverID=1, clientID=Duck-UHF Client Duck-UHF left channel 251 ID=2 on virtual server 1 Channel ID=2 deleted by server on virtual server 1 Client Duck-VHF left channel Default Channel ID=1 on virtual server 2 Client Duck-GRD left channel 243000 ID=2 on virtual server 3 Channel ID=2 deleted by server on virtual server 3 It's really unlikely that you aren't on the same frequency as they are if you can hear them. It would have to be something weird like they are transmitting on guard and you are listening to both active and guard but transmitting on active not shared by your intended listener. If you can talk both ways in 2D then it shouldn't be a sound device issue. [i]Somebody[/i] has gotten creative with the IVC Client.ini or their shortcut command line or possibly the shared data link between IVC and F4 is being prevented possibly by Windows's UAC. Working in 2D but not in 3D is a really narrow case.[/s][/r]