Problem with custom "IVC Client.ini" … i'm lost
-
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.
-
I have tested this issue intensively because we have the same problem here. If you have an IVC Client not in the 3D-World and the option “outsiders = all” is set, either by ini-file or command line, all 3D-IVC-Clients crash as soon as the “standalone” IVC starts transmitting.
IVC Logs weren’t very helpful, since the logs stopped at the crash and didn’t show any error.I did also some testings with all clients in 3D-World and the option “outsiders = all” was set. I expected that with this option set on, you can hear each other even if the distance between two aircrafts was very big, but you couldn’t hear anything. Maybe I didn’t understand exactly what this options effects in IVC.
Hope we can find a solution for this “bug”, since human AWACS is so vital especially in complex missions and I wouldn’t miss it.
-
We had the same experience during our tests with our human ATC. Everytime our tower lady starts to transmit the IVC Clients of the pilots are crashing …
-
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.