Problem with custom "IVC Client.ini" … i'm lost
-
Hi guys,
i’m a bit lost with the new IVC functions and to configurate them with a custom “IVC Client.ini”. I’ve read the part of the BMS Manual back and forth, but maybe i’m lost in translation or just to dumb. Let me explain my problem:
Our squadron is in transition to 4.33. Too get them all on them same IVC config and to get also our human ATC in which is not starting BMS but only works with F4AWACS i’ve decided to spread a custom IVC Client.ini (see the content on the bottom). On Sunday we made the first tests on our squadron server.
We could never get into the 3D game, all times the IVC Client on the clients crashed so the tests failed. The situation was unbearable so i put the brakes on: all clients deleted the ini file so we connected with the defaults. After that IVC worked, but we still couldn’t get ATC in, we had to make a ATC flight she had to join so we could get together in 3D.
Here the content of the ini file. Can someone shed some light on me what i understood wrong? Thx in advance
duplex = 0 loudness = 1 uhf = 307300 vhf = 1234 key-hook = 1 quick = 1 hum-level = -18 hiss-level = -18 toneVol = +6 uhfVol = -1 vhfVol = +1 outsiders = all
-
heya
not really my area but I’ll try
save the ini file with say 58th.ini into the bin/x86/IVC folder
then in your shortcut to IVC add -i 58th
so shortcut looks like“D:\BMS\Falcon BMS 4.33\Bin\x86\IVC\IVC Client.exe” -i 58th
no need to add the .ini programme will add that for you that should point the IVC to your specific ini file the defaults for that file are
See chapter 14.5 of the BMS manual for detailed explanation of available options.
File to be saved in //localinstall/bin/x86/IVC/
#duplex = 0
#server = DNS OR IP TO IVC SERVER
#connect = 0
#nickname = CALLSIGN
#port = xxxx
#key-hook = 0
#quick = 0
#word = password
#capture = sound_device
#nofx = 0
#playback = sound_device
#tone =
#loudness = 0
#fuzz = 0
#hum-level = 0
#hiss-level = 0
#toneVol = 0
#uhf = 307300
#vhf = 1234
#uhfVol = 0
#vhfVol = 0
#outsiders = seat
#log = 0
#minimize = 0
#force-local = 0 -
Thx for your response. My intend using the name “IVC Client.ini” was that no one has to add the /i to there IVC shortcut so the configuration is as easy as it can be. I’ve understanded that with this filename it will be used automatically.
-
ahh ok yes my understanding is that it will automatically look for
IVC Client.ini
so if you don’t want to use a switch then changing that file will be the same as making your own and adding the switch
sorry cant help any further at the moment i’ll run some tests here and see if I can find the answer though -
What also puzzles me: in 4.32 i didn’t have to write the IP of the IVC in the Box “Dedicated IVC Server”, it connected automatically with the same IP as the Server.
In 4.33 this seems to not work anymore. Or have i again missed something? Is this connected to the non-existent “IVC Client.ini”? Didn’t it work because i had the two lines #server = DNS OR IP TO IVC SERVER and #connect = 0 in the ini i made?
-
What also puzzles me: in 4.32 i didn’t have to write the IP of the IVC in the Box “Dedicated IVC Server”, it connected automatically with the same IP as the Server.
It still does if you let BMS launch the IVC Client automatically when you hit COMMS > CONNECT. Entering the IP address is used if you want to access IVC when BMS is not running.
In 4.33 this seems to not work anymore. Or have i again missed something? Is this connected to the non-existent “IVC Client.ini”? Didn’t it work because i had the two lines #server = DNS OR IP TO IVC SERVER and #connect = 0 in the ini i made?
Any line that begins with a # will have no effect.
The code below will be included by default in Update 1. Please copy it into Notepad and save it as IVC Client.ini in your C:\Falcon BMS 4.33\Bin\x86\IVC folder. If that doesn’t work there is something wrong with your install, if it does then it’s your .ini file that’s the problem.
# See chapter 14.5 of the BMS manual for detailed explanation of available options. # File to be saved in //localinstall/bin/x86/IVC/ #duplex = 0 #server = XXX.XXX.XXX.XXX #connect = 0 #nickname = Callsign #port = xxxx #key-hook = 0 #quick = 1 #word = password #capture = sound_device #nofx = 0 #playback = sound_device #tone = #loudness = 0 #fuzz = 0 #hum-level = 0 #hiss-level = 0 #toneVol = 0 #uhf = 307300 #vhf = 1234 #uhfVol = 0 #vhfVol = 0 #outsiders = seat #log = 0 #minimize = 0 #force-local = 0
-
It still does if you let BMS launch the IVC Client automatically when you hit COMMS > CONNECT. Entering the IP address is used if you want to access IVC when BMS is not running.
Thx for your fast response. I just tested it with two different clients. If i leave the box blank IVC Client will not automatically start when klicking on CONNECT.
When i write the IP in the box the IVC Client starts automatically.
Checked falcon bms.cfg and VoiceCom is set to 1.
-
If i leave the box blank IVC Client will not automatically start when klicking on CONNECT.
Oh, you mean the phonebook window, I thought you were still on the subject of the .ini file. BMS Manual p84, yes you do need to put the IP address in the Dedicated IVC Server field.
-
Damn, missed that one …. thx for your help.
-
Back in 4.32 it would assume the same IP as the game server if left blank. Oddly that feature went away with 4.33. It used to but now it doesn’t. It has changed.
I think the crash issue was your IVC Client.ini values might be invalid. Try commenting out every single line (crash should stop) and removing the “#” from one line at a time until you find the crashing line.
-
Regarding IVC i have another question: how much clients can connect to an open IVC Server? Is there a limit?
Edit: i’ve read there are 32 slots for each 3 virtual server (UHF, VHF and GUARD) the IVC Server opens, but i’m not sure if that means the max. overall client number means also 32.
-
32 is the supported limit. This is a function of the TS3 SDK library license that we have the use of from TeamSpeak.
-
Thx for the info, all i need to know at the moment …
-
Hi Gents,
we made further test with our ATC lady connecting only with IVC and F4 AWACS, no BMS. We encountered two problems:
First, we are still in 2D an when she is connecting we can hear her only on VHF, UHF is not working until she changed the UHF frequency one time. Not a showstopper but can be forgotten.
Second, we Pilots enter 3D world and can hear us, but as soon as ATC try to talk all our IVC Clients crash immediatly.
We have tried with “outsiders = all” switch on client and ATC side and also removed the .ini on ATC for testing, no joy.
On the bottom our two ini files, first pilot, second ATC:
# See chapter 14.5 of the BMS manual for detailed explanation of available options. # File to be saved in //localinstall/bin/x86/IVC/ #duplex = 0 #server = xxx.xxx.xxx.xxx #connect = 0 #nickname = Callsign #port = xxxx key-hook = 1 quick = 1 #word = password #capture = sound_device #nofx = 0 #playback = sound_device #tone = loop:0 loudness = 1 #fuzz = 0 hum-level = -18 hiss-level = -18 #toneVol = -5 uhf = 307300 vhf = 1234 uhfVol = -2 vhfVol = +1 outsiders = all #log = 0 #minimize = 0 #force-local = 0
# 1st Glorywings IVC - ATC & AWACS # See chapter 14.5 of the BMS manual for detailed explanation of available options. # File to be saved in //localinstall/bin/x86/IVC/ duplex = 1 server = xxx.xxx.xxx.xxx connect = 1 nickname = ATC #port = xxxx key-hook = 1 #quick = 0 #word = password #capture = sound_device #nofx = 0 #playback = sound_device #tone = loudness = 1 fuzz = 0 hum-level = 0 hiss-level = 0 #toneVol = 0 uhf = 307300 vhf = 1234 #uhfVol = 0 #vhfVol = 0 outsiders = all #log = 0 #minimize = 0 force-local = 1
-
Have you turned on logging??
Does this IVC client crash happen with host and external ATC person only (i.e. only one player on the host system in 3D)??
-
I must say i didn’t think about turning on the log, will do next time.
We have a dedicated server, running the IVC server also but not “selfconnecting” there.
-
I was thinking about client logs but it’s possible that whatever the server console spits out might be telling as well; less likely I think but worth a look.
-
Will do next time so i can provide a crashlog.
BTW: when ATC is also connecting with BMS and “taking a seat” in the mission IVC is working fine with her.
-
It would be good to know what settings IVC is using if no ini is present and no command line parameters are used, thx in advance.
-
Defaults that are not obvious are listed in the manual. If the manual text doesn’t tell you what you need for one or other option, please comment on that specifically in a separate thread aimed for the documentation folks. Thanks.