Problem with custom "IVC Client.ini" … i'm lost
-
-
outsiders = awacs #squadron standard - DO NOT CHANGE!
…does not work how you were hoping.
-
Umm, I said it was a bug a while ago – sorry if that wasn’t clear before.
Hm, must have missed that. Anyway, it’s clear now.
Is there another way to get comments in the ini-file itself? No biggie if not, i have to make a small doc then.
-
You mean other than what is already documented for inserting comments?? No, sorry – just the one way.
-
Still having clients crashing with “outsiders = awacs”, no luck. Unfortunatly no logfile. Guess we have to stick without “outsiders” until 4.33.1.
-
I can say “outsiders” works perfect now, thx for the bugfixing and ongoing support!
-
Well, thank goodness for that!
-
I can say “outsiders” works perfect now, thx for the bugfixing and ongoing support!
Hmm, with us it doesn’t seem to work?
All our pilots plus myself as ATC have outsider=all in their IVC Client.ini. I place myself in Awacs seat in 2D but don’t go into 3D. If I understand the manual and the explanation in this topic correctly, as long as I’m not in 3D, and all our outsiders-values are set to all, they should hear me fine, no?
However, they here me 4 to 5 by 5 once airborne and relatively close the the Awacs AI in 3D. But from 100NM on the ground at the airbase they here me 0 to 1 by 5. -
The purpose of “all” is to allow voice from people who are using the client outside the context of being connected to a Falcon4 session to reach your ears. If you choose “all” and then connect to the game anyway then you get “seat” behavior in terms of how signal propagation works. Thus, in the scenario you describe, I would expect players on the ground at long distance to be unable to hear or reach AWACS clearly.
Keep in mind that the overall design intent is to try and replicate real world radio performance – or at least provide a plausible model thereof. In the real world you probably would not get far distant air stations easily on aviation radios and looking at the math for the signal propagation model in the code you certainly won’t. Once the antenna height of the players remote from the AWACS start increasing, and any LoS issues are resolved as a result, then I’d expect signal to start getting through crackly at first and strengthening as player altitudes climb.
In other words, I think it’s working as designed from what you say.
If you want omnipotent signal strength AWACS the way to do that would be to start the IVC client for the AWACS player before the game, set it for “local control”, then join the game having made sure that all other players have “all” set in their client settings. I would expect that to turn off the signal propagation model for the AWACS player.
-
The purpose of “all” is to allow voice from people who are using the client outside the context of being connected to a Falcon4 session to reach your ears. If you choose “all” and then connect to the game anyway then you get “seat” behavior in terms of how signal propagation works. Thus, in the scenario you describe, I would expect players on the ground at long distance to be unable to hear or reach AWACS clearly.
Keep in mind that the overall design intent is to try and replicate real world radio performance – or at least provide a plausible model thereof. In the real world you probably would not get far distant air stations easily on aviation radios and looking at the math for the signal propagation model in the code you certainly won’t. Once the antenna height of the players remote from the AWACS start increasing, and any LoS issues are resolved as a result, then I’d expect signal to start getting through crackly at first and strengthening as player altitudes climb.
In other words, I think it’s working as designed from what you say.
If you want omnipotent signal strength AWACS the way to do that would be to start the IVC client for the AWACS player before the game, set it for “local control”, then join the game having made sure that all other players have “all” set in their client settings. I would expect that to turn off the signal propagation model for the AWACS player.
Thx for the reply Boxer!
I understand, and love, the LOS & distance aspect. I was under the assumption the outsiders=all takes those out of the equation and lets people inside BMS 3D hear me from 2D without these distortions. But if I now understand correctly, the IVC client doesn’t take outsiders parameter into account whenever the one who’s talking is having a seat in 2 or 3D; right?
The way I work now for ATC/GCI is connect with BMS server, join the MP TE. Take a seat in the Awacs.
Then disconnect from IVC server by clicking force local control and reconnect manually. I was under the assumption by disconnecting and reconnecting IVC, the BMS state of my seat was mute.So I will try again by not joining BMS TE and just starting IVC manually standalone and connect.
-
Update: when I don’t run BMS, all pilots say the comms are crystal clear. So indeed it was because I had a seat in BMS it used the seat instead of “all” it seems.