Problem with custom "IVC Client.ini" … i'm lost
-
I think I have found a solution for this problem, or let’s call it a workaround.
If you set “outsiders = all” in the IVC Client.ini file, the AWACS/ATC operator has to be at least in the 2D-World and connected to the multiplayer-game. Then the other clients won’t crash and you can transmit as ATC/AWACS via IVC with no range limitation.
Find below a step by step description of my successful testing today. I will test the whole thing next week with our squadron and hopefully it will also work with more than just two clients (as in my testlab).
PROCEDURE DELETED -> see later post for correct procedure!!!
Cheers
Pitbull -
this sequence is for the awacs guy only? and all (server and clients) must follow the same ini setting?
-
Yes, the sequence is only for the AWACS operator, except the ini file. All clients need to have to place the ini-file with the outsiders option set to “all” in the …\bin\x86\IVC\ folder.
Pitbull
-
I’ve been a little busy with, shall we say, non-development tasks of late. However, I was able to repro this case today and I know what the problem is and in fact how to fix it once and for all (urm, well I hope once and for all). Of course don’t ask me when you might be able to have said fix.
-
Well thanx Boxer, we wouldn’t ask when any way but as you think once and for all we fear the same for releases…
It’s reaching one month soon… -
-
Yeap read it already.
-
Yesterday we wanted to test the procedure in a mission with our squadron and unfortunately the IVC-clients crashed again . So I did a retesting tonight and found out, that the procedure I have described above is wrong.
After several successful tests today I am now convinced that the following procedure works for AWACS operations:- set “outsiders = all” in the IVC Client.ini file
- start BMS and connect to the host,you have to select “Enable IVC” in the Comms window
- select the online-TE and go to the 2D-World
- change to the IVC client and select the option “Force Local Control”. The IVC client will disconnect automatically. Connect again and set the desired frequencies again.
- leave BMS in the 2D-World
- start F4AWACS
It is important, that you follow the procedure exactly as described above. If you start IVC client as standalone first, it won’t work.
Cheers
Pitbull -
I think that the IVC Client.ini file is impactless when “Enable IVC” button is green in Falcon UI.
I’ve tried to change the default freqs but when IVC is connected through the above procedure the freqs are 307300 and 1234 regardless the changes i’ve done in the ini file so the “outsider” command will have no impact too i thnk
I think that the only thing we need to do so the ivc will not crashe is just run IVC through the “Enable IVC” button in Falcon.
-
The ini has impact, at least in respect to set the levels of sound processing (Have-Quick-Click, HISS, HUM etc.) and aktivating the logfile.
@Pitbull: AFAIK you will test it online in your squadron, plz let us know how it works, thx in advance.
-
We have tested it yesterday and I can confirm that it works as described in my last post.
Cheers
Pitbull -
To be clear, the procedure is ONLY for the ATC / AWACS client, right?
-
Yes, only for AWACS/ATC.
-
Today i tested the IVC issue again. It worked perfectly when i run the client by ‘‘standalone’’ method and the Enable IVC button.
We were only 5 clients.
-
I think I have found a solution for this problem, or let’s call it a workaround.
If you set “outsiders = all” in the IVC Client.ini file, the AWACS/ATC operator has to be at least in the 2D-World and connected to the multiplayer-game. Then the other clients won’t crash and you can transmit as ATC/AWACS via IVC with no range limitation.
Find below a step by step description of my successful testing today. I will test the whole thing next week with our squadron and hopefully it will also work with more than just two clients (as in my testlab).
(((- set “outsiders = all” in the IVC Client.ini file
- start IVC Cient (standalone)
- start BMS and connect to the host, but DO NOT select “Enable IVC” in the Comms window
- select the online-TE and go to the 2D-World
- leave BMS in the 2D-World
- start F4AWACS)))
Cheers
PitbullI’m afraid this procedure is not a cure-all for the IVC-Problems. Yesterday we had serveral clients whose IVC Client kept crashing
-
The procedure you have used is outdated and I have posted a new procedure in a later post. Sorry for the misleading two procedures (I have deleted the old one now).
The correct procedure is as follows:
- set “outsiders = all” in the IVC Client.ini file
- start BMS and connect to the host,you have to select “Enable IVC” in the Comms window
- select the online-TE and go to the 2D-World
- change to the IVC client and select the option “Force Local Control”. The IVC client will disconnect automatically. Connect again and set the desired frequencies again.
- leave BMS in the 2D-World
- start F4AWACS
Cheers
Pitbull -
Is that the one you gave to Dro16?
I also have now the radio-log.txt from one Client who crashed:
21:12:30: New TS volume_modifier for radio[0]: -1.0 (raw 1522) 21:12:30: New TS volume_modifier for radio[2]: -1.0 (raw 1522) 21:12:30: New TS volume_modifier for radio[1]: 1.0 (raw 1087) 21:12:35: OnF4CheckTimer: BMS is taking over at this point... 21:12:35: ProcessAnyUpdates: re-connect because of IP address - is in BMS(xxx.xxx.xxx.xxx) was in client(Enter IP) 21:12:35: ProcessAnyUpdates: re-connect because of nick - is in BMS(Bluebird) was in client(noname) 21:12:35: ProcessAnyUpdates: handling the re-connect 21:12:35: ProcessAnyUpdates: ui controls updated host: xxx.xxx.xxx.xxx, nick: Bluebird 21:12:35: ConnectToHost: host: xxx.xxx.xxx.xxx, nick: Bluebird 21:12:35: ConnectToServer: server handle ID[0] = 1, host(xxx.xxx.xxx.xxx) nick(Bluebird-UHF) Port(9987) Pass() 21:12:35: Connect status changed: status = 1 error = 0x00000000 on conID[1] 21:12:35: SetConnectionStatus: handleID(1) status(1) theRadio(0) 21:12:35: SetConnectionStatus: UHF initiating connection to server side 21:12:35: ConnectToServer: successful return from ts3client_startConnection 21:12:35: PushTalk: PRESS on radio(0) 21:12:35: PushTalk: RELEASE on radio(0) 21:12:35: ConnectToServer: successful return from ts3client_flushClientSelfUpdates 21:12:35: Radio[0] - Toggled VAD off. 21:12:35: Connect status changed: status = 2 error = 0x00000000 on conID[1] 21:12:35: SetConnectionStatus: handleID(1) status(2) theRadio(0) 21:12:35: onNewChannelEvent: conID[1] chID[1] parentID[0] 21:12:35: onNewChannelEvent: New channel: name (Default Channel), ch ID[1] 21:12:35: Connect status changed: status = 3 error = 0x00000000 on conID[1] 21:12:35: SetConnectionStatus: handleID(1) status(3) theRadio(0) 21:12:35: SetConnectionStatus: UHF connected and visible server side 21:12:35: New client: Bluebird-UHF 21:12:35: onNewChannelEvent: conID[1] chID[6] parentID[0] 21:12:35: onNewChannelEvent: New channel: name (359300), ch ID[6] 21:12:35: Connect status changed: status = 4 error = 0x00000000 on conID[1] 21:12:35: SetConnectionStatus: handleID(1) status(4) theRadio(0) 21:12:35: SetConnectionStatus: UHF established, startup for VHF 21:12:35: ConnectToServer: Radio[0] indicates connected 21:12:35: ConnectToServer: server handle ID[1] = 2, host(xxx.xxx.xxx.xxx) nick(Bluebird-VHF) Port(9988) Pass() 21:12:35: Connect status changed: status = 1 error = 0x00000000 on conID[2] 21:12:35: SetConnectionStatus: handleID(2) status(1) theRadio(1) 21:12:35: SetConnectionStatus: VHF initiating connection to server side 21:12:35: ConnectToServer: successful return from ts3client_startConnection 21:12:35: PushTalk: PRESS on radio(1) 21:12:35: PushTalk: RELEASE on radio(1) 21:12:35: ConnectToServer: successful return from ts3client_flushClientSelfUpdates 21:12:35: Radio[1] - Toggled VAD off. 21:12:35: Connect status changed: status = 2 error = 0x00000000 on conID[2] 21:12:35: SetConnectionStatus: handleID(2) status(2) theRadio(1) 21:12:35: onNewChannelEvent: conID[2] chID[1] parentID[0] 21:12:35: onNewChannelEvent: New channel: name (Default Channel), ch ID[1] 21:12:35: Connect status changed: status = 3 error = 0x00000000 on conID[2] 21:12:35: SetConnectionStatus: handleID(2) status(3) theRadio(1) 21:12:35: SetConnectionStatus: VHF connected and visible server side 21:12:35: New client: Bluebird-VHF 21:12:35: onNewChannelEvent: conID[2] chID[5] parentID[0] 21:12:35: onNewChannelEvent: New channel: name (138050), ch ID[5] 21:12:35: onNewChannelEvent: conID[2] chID[8] parentID[0] 21:12:35: onNewChannelEvent: New channel: name (138100), ch ID[8] 21:12:35: onNewChannelEvent: conID[2] chID[10] parentID[0] 21:12:35: onNewChannelEvent: New channel: name (126200), ch ID[10] 21:12:35: onNewChannelEvent: conID[2] chID[16] parentID[0] 21:12:35: onNewChannelEvent: New channel: name (133150), ch ID[16] 21:12:35: onNewChannelEvent: conID[2] chID[18] parentID[0] 21:12:35: onNewChannelEvent: New channel: name (138200), ch ID[18] 21:12:35: Connect status changed: status = 4 error = 0x00000000 on conID[2] 21:12:35: SetConnectionStatus: handleID(2) status(4) theRadio(1) 21:12:35: SetConnectionStatus: VHF established, startup for GUARD 21:12:35: ConnectToServer: Radio[1] indicates connected 21:12:35: ConnectToServer: server handle ID[2] = 3, host(xxx.xxx.xxx.xxx) nick(Bluebird-GRD) Port(9989) Pass() 21:12:35: Connect status changed: status = 1 error = 0x00000000 on conID[3] 21:12:35: SetConnectionStatus: handleID(3) status(1) theRadio(2) 21:12:35: SetConnectionStatus: GUARD initiating connection to server side 21:12:35: ConnectToServer: successful return from ts3client_startConnection 21:12:35: PushTalk: PRESS on radio(2) 21:12:35: PushTalk: RELEASE on radio(2) 21:12:35: ConnectToServer: successful return from ts3client_flushClientSelfUpdates 21:12:35: Radio[2] - Toggled VAD off. 21:12:35: Connect status changed: status = 2 error = 0x00000000 on conID[3] 21:12:35: SetConnectionStatus: handleID(3) status(2) theRadio(2) 21:12:35: onNewChannelEvent: conID[3] chID[1] parentID[0] 21:12:35: onNewChannelEvent: New channel: name (Default Channel), ch ID[1] 21:12:35: Connect status changed: status = 3 error = 0x00000000 on conID[3] 21:12:35: SetConnectionStatus: handleID(3) status(3) theRadio(2) 21:12:35: SetConnectionStatus: GUARD connected and visible server side 21:12:35: New client: Bluebird-GRD 21:12:35: onNewChannelEvent: conID[3] chID[2] parentID[0] 21:12:35: onNewChannelEvent: New channel: name (243000), ch ID[2] 21:12:35: Connect status changed: status = 4 error = 0x00000000 on conID[3] 21:12:35: SetConnectionStatus: handleID(3) status(4) theRadio(2) 21:12:35: SetConnectionStatus: GUARD established; now fully connected 21:12:35: ConnectToServer: Radio[2] indicates connected 21:12:35: New Intercom volume for device[0]: 2.0 (raw 861) 21:12:35: JoinNewChannel: 359300 on radio[0] initially using ChID[6] 21:12:35: JoinChannel[0](cd: 6, r: 0) 21:12:35: JoinChannel: moving radio[0]into channel[6] 21:12:35: JoinNewChannel: 138100 on radio[1] initially using ChID[8] 21:12:35: JoinChannel[2](cd: 8, r: 1) 21:12:35: JoinChannel: moving radio[1]into channel[8] 21:12:35: JoinNewChannel: 243000 on radio[2] initially using ChID[2] 21:12:35: JoinChannel[4](cd: 2, r: 2) 21:12:35: JoinChannel: moving radio[2]into channel[2] 21:12:35: ProvideStatusUpdates: set clientactive flag 21:12:35: ProvideStatusUpdates: set connected flag 21:12:35: New client: Fatality-VHF 21:12:35: New client: Bluebird-VHF1 21:12:35: New client: Sledge-UHF 21:12:35: New client: Caesar-UHF 21:12:35: New client: Joker-UHF 21:12:35: onClientMoveEvent: on conID[2] successful chan move from chID[1] to chID[8] 21:12:35: New client: Fatality-UHF 21:12:35: New client: Ziri-UHF 21:12:35: New client: Paladin-UHF1 21:12:35: New client: Bluebird-UHF1 21:12:35: New client: Sneakpeek-UHF 21:12:35: onClientMoveEvent: on conID[1] successful chan move from chID[1] to chID[6] 21:12:35: New client: Sledge-GRD 21:12:35: New client: Caesar-GRD 21:12:35: New client: Joker-GRD 21:12:35: New client: Fatality-GRD 21:12:35: New client: Ziri-GRD 21:12:35: New client: Paladin-GRD1 21:12:35: New client: Bluebird-GRD1 21:12:35: New client: Sneakpeek-GRD 21:12:35: onClientMoveEvent: on conID[3] successful chan move from chID[1] to chID[2] 21:12:47: onClientMoveTimeoutEvent: connection lost for Bluebird-GRD1, ID(351293449678356508) 21:12:47: onClientMoveTimeoutEvent: connection lost for Bluebird-UHF1, ID(349757431934353436) 21:12:48: JoinNewChannel: 9999 on radio[0] initially using ChID[0] 21:12:48: createChannel request sent for 9999 on radio[0] 21:12:48: onNewChannelCreatedEvent: name 9999 chID[30] on conID[1] 21:12:48: CTeamSpeak::MuteRadioVolume muting UHF 21:12:48: New TS volume_modifier for radio[0]: -40.0 (raw 10000) 21:12:48: JoinNewChannel: 9999 on radio[1] initially using ChID[0] 21:12:48: createChannel request sent for 9999 on radio[1] 21:12:48: onNewChannelCreatedEvent: name 9999 chID[21] on conID[2] 21:12:48: CTeamSpeak::MuteRadioVolume muting VHF 21:12:48: New TS volume_modifier for radio[1]: -40.0 (raw 10000) 21:12:49: onClientMoveTimeoutEvent: connection lost for Bluebird-VHF1, ID(350596771623206940) 21:13:08: JoinNewChannel: 307300 on radio[0] initially using ChID[0] 21:13:08: createChannel request sent for 307300 on radio[0] 21:13:08: onNewChannelCreatedEvent: name 307300 chID[31] on conID[1] 21:13:08: New TS volume_modifier for radio[0]: 6.0 (raw 100) 21:13:08: CTeamSpeak::UnMuteRadioVolume un-muting UHF 21:13:08: JoinNewChannel: 1234 on radio[1] initially using ChID[0] 21:13:08: createChannel request sent for 1234 on radio[1] 21:13:08: Channel ID 30 deleted by Server (64424509440) 21:13:08: CTeamSpeak::WipeChannelName removing Channel Map[0][9999] - 30 21:13:08: onNewChannelCreatedEvent: name 1234 chID[22] on conID[2] 21:13:08: Channel ID 21 deleted by Server (64424509440) 21:13:08: CTeamSpeak::WipeChannelName removing Channel Map[1][9999] - 21 21:13:08: New TS volume_modifier for radio[1]: 6.0 (raw 100) 21:13:08: CTeamSpeak::UnMuteRadioVolume un-muting VHF 21:13:08: CTeamSpeak::MuteRadioVolume muting GRD 21:13:08: New TS volume_modifier for radio[2]: -40.0 (raw 10000) 21:13:28: onNewChannelCreatedEvent: name 240900 chID[32] on conID[1] 21:13:36: onNewChannelCreatedEvent: name 377200 chID[33] on conID[1] 21:13:36: Channel ID 32 deleted by Server (64424509440) 21:13:36: CTeamSpeak::WipeChannelName removing Channel Map[0][240900] - 32 21:13:44: onClientMoveEvent: on conID[2] successful chan move from chID[16] to chID[8] 21:13:44: Channel ID 16 deleted by Server (64424509440) 21:13:44: CTeamSpeak::WipeChannelName removing Channel Map[1][133150] - 16 21:14:29: ProvideStatusUpdates: connected but host tells us time to quit 21:14:29: CTeamSpeak::Disconnect 21:14:29: isConnectedToServer: status: 4, conID[1] 21:14:29: onClientMoveEvent: on conID[1] successful chan move from chID[31] to chID[0] 21:14:29: Connect status changed: status = 0 error = 0x00000000 on conID[1] 21:14:29: SetConnectionStatus: handleID(1) status(0) theRadio(0) 21:14:29: SetConnectionStatus: UHF disconnect status registered 21:14:29: Disconnect: UHF disconnected 21:14:29: isConnectedToServer: status: 4, conID[2] 21:14:29: onClientMoveEvent: on conID[2] successful chan move from chID[22] to chID[0] 21:14:29: Connect status changed: status = 0 error = 0x00000000 on conID[2] 21:14:29: SetConnectionStatus: handleID(2) status(0) theRadio(1) 21:14:29: SetConnectionStatus: VHF disconnect status registered 21:14:29: Disconnect: VHF disconnected 21:14:29: isConnectedToServer: status: 4, conID[3] 21:14:29: onClientMoveEvent: on conID[3] successful chan move from chID[2] to chID[0] 21:14:29: Connect status changed: status = 0 error = 0x00000000 on conID[3] 21:14:29: SetConnectionStatus: handleID(3) status(0) theRadio(2) 21:14:29: SetConnectionStatus: GUARD disconnect status registered 21:14:29: Disconnect: GUARD disconnected 21:14:35: OnF4CheckTimer: BMS is releasing client control now...
-
The procedure you have used is outdated and I have posted a new procedure in a later post. Sorry for the misleading two procedures (I have deleted the old one now).
The correct procedure is as follows:
- set “outsiders = all” in the IVC Client.ini file
- start BMS and connect to the host,you have to select “Enable IVC” in the Comms window
- select the online-TE and go to the 2D-World
- change to the IVC client and select the option “Force Local Control”. The IVC client will disconnect automatically. Connect again and set the desired frequencies again.
- leave BMS in the 2D-World
- start F4AWACS
Cheers
PitbullHi Pitbull,
i’m answering here so all can benefit from the discussion and maybe a dev can shed some light on it.
What i don’t understand: yet the ATC IS actually connected to the online mission in BMS, that means somewhere is his/her callsign name in the ATO of the TE.
So, why using “outsiders=all”? As far as i understand this option is only for clients NOT connected to the TE. In our case this option causes several IVC Clients to crash, wouldn’t it be smarter to use the “outsiders=awacs” for the ATC instead?
And for the normal pilots there has to be not an “outsider”-option at all as the ATC is connected to the TE.
The BMS Manual is very cryptical for some IVC options, hopefully there will be an update.
-
I agree that the option “outsiders=all” actually makes no sense if you were connected to an online mission. I have never tested the “new” workaround without the “IVC Client.ini” file present, since it always works as desired the way I described it earlier.
For me the option “outsiders=awacs” is not very useful, simply because I don’t want to have any range limitation as AWACS operator, so it’s easier for all pilots (they always can hear AWACS) and the TE builders (they actually can place the AWACS aircraft wherever they want).
Maybe I can do some tests in my LAN with the different IVC Client.ini settings and for sure I will post my results here.
Did you also have IVC Crashes with the newest procedure?
Cheers
Pitbull -
Yeah, the BMS Manual is somewhat confusing there (could also be just my limited english grammar knowledge) and IMO contradictory.
We have still some clients with crashing/re-connection IVC Clients. Some of them “cured” it by commenting the “outsider”-line with hashtag to deactivate this option. But that means we have a mixed IVC operation config-wise, IMO another malfuntion source.
I hope the IVC Pro’s from BMS can help here, now that the licensing case is closed and 4.33.1 on short final they will have more time to check our issues.