@Boxer:
Fascinating. It would never have occurred to me to run the IVC client and then not enable IVC in the network connect dialog.
I wasn’t sure what that “IVC Enabled” actually did. Does it trigger IVC Client to be launched but if you don’t does it interact with an already-connected IVC Client anyway? I’m not thick just scientific. Obviously IVC Enabled shoves a bunch of data at the client causing it to connect to the server specified in the Falcon phonebook but that’s not what I wanted. I wanted to connect previously and not have to care what IVC Server address I did or did not put into phonebook. I was hoping there was a middle ground where I didn’t rehash the connection but it still was data driven.
Understand my motivation is to get the most out of IVC while making the least amount of extra work for the users. If it takes more work or produces any obstacles at all then all the benefits in the world mean nothing due to the people I fly with. The number of hours lost because of simple checks like controls, TrackIR, IVC, etc. being skipped in the lust to hurry it up is quite high. I’ve already reduced my ramp start timer to 15m because they won’t wait and insist on being ahead of the escort flight. I want to have reliable 2D-3D comms, improved audio features, and less work all while being easier to use. The change from 4.32 where you could leave the IVC server blank and it would copy from the game server IP (gone in 4.33) is the sort of thing that takes minutes to resolve.
Does AGC conflict with setting the AI/Human bias on the BU UHF volume knob? I’ve never gotten a noticeable effect out of that AI bias control.
Here is an example IVC Client.ini.
# Reference BMS Manual 14.5 for detailed explanation.
# File location //Falcon BMS 4.33/bin/x86/IVC/
#SERVER CONNECTION
nickname = Viper
server = 127.0.0.1
#port = 9987
connect = 0
#word = password
#CLIENT PARAMETERS
key-hook = 1
#minimize = 0
uhf = 243000
#uhfVol = 0
vhf = 1234
#vhfVol = 0
#force-local = 0
#capture = sound_device
#playback = sound_device
outsiders = all
#duplex = 0
#CLIENT PREFERENSES
#tone =
#toneVol = 0
#nofx = 0
#log = 0
#TRANSMISSION QUALITY
loudness = 1
fuzz = 1
hum-level = -1
hiss-level = -1
quick = 1
I don’t know what settings will persist after Falcon triggers a new connection. I already know/suspect the following parameters are overridden by Falcon:
Server IP
Auto connect
Nickname
Password
What else is altered by Falcon that is a valid parameter in the .ini?
Duplex?
Outsider?