Radio Filter (Outsiders Switch)
-
@b.s.:
Setting my falcon outsiders to: all
and then entering 3d on computer A,when i transmit from an ivc client on a computer B
IVC crashes on computer A.
Hmm… Can you run with logging enabled and see if that generates a log file with this scenario please??
How are you setting outsiders?? Command line arg or ini file??
What is going on with computer B – just the IVC client, no copy of the game or…?? Need a little more info to get the scenario clear enough to try and repro that one.
-
Hmm. In 2D I dont hear any difference between taking a seat versus not - aside from the not being able to talk to those who have either not taken a seat or have, depending on the case.
-
Hmm. In 2D I dont hear any difference between taking a seat versus not - aside from the not being able to talk to those who have either not taken a seat or have, depending on the case.
Sorry, I’m going to need that in English…you lost me completely I’m afraid
-
In 2D, I dont hear the digital sound processing effects. IVC sounds “normal” in 2D. In 3D, I get all the cool sounding radio effects like mic clicks, range attenuation, HQ clicks, AC buzz, etc… if nothing else, Id like to hear the range attenuation in 2D.
-
Hi, I know this topic is old but it’s just what I was looking for.
It works the same way here. When we use IVC Client + 2D map, IVC just sounds like the 4.32 IVC without any sound processing or range effects.
Of course pilots in 3D have all correct effects. If range between them and awacs is too high they can’t receive comms from AWACS who is in 2D taking place on AWACS flight. Instead AWACS guy can hear every comm with no distortion and effects.
Is there a way to get it working in 2D too?
Thank you!
-
If the client is running before the game then it runs independently up until the “connect” button in the COMMs
UI page in the game is pressed to initiate a multiplayer game. At that time, provided the “force local control”
gadget in the client applet is not checked, the applet will slave itself to the Falcon4 BMS code.I do not find this to be the case. When IVC is connected prior to connecting to a server the applet is not slaved to BMS and continues on the initial frequencies even as they are changed in 3D. Note that the “IVC enabled” check box is not selected when connecting but the manual does not state this is required. With IVC Enabled I fear too much is overridden by Falcon (e.g. the server IP if required and overrides and who knows what else).
-
There is presently no way to get the radio sound filtering effects to work for 2D world use. This is by design. For what it’s worth the thinking was that VoIP use in the 2D UI would primarily be for briefings and the like meaning that half-duplex and reduced sound fidelity would actually be detriments not enhancements. The other issue is that lack of range and altitude information make some or all of the sound processing effects code moot (not mute ;)) anyway…i.e. the primary difference would in fact be making the UI half-duplex instead of full duplex and there’s already a way to do that.
It’s just software though so anything is possible.
-
It would be nice if, when you take a seat in for instance an AWACS, you got radio sound effects processing.
In fairness though, my thoughts are leaning in the direction of ‘it would be awesome if you went to 3D to be AWACS’ so there’s that option to think about too. Not that Id expect that to be easy or happen anytime soon.
-
I do not find this to be the case. When IVC is connected prior to connecting to a server the applet is not slaved to BMS and continues on the initial frequencies even as they are changed in 3D. Note that the “IVC enabled” check box is not selected when connecting but the manual does not state this is required.
Fascinating. It would never have occurred to me to run the IVC client and then not enable IVC in the network connect dialog. Well, gee, yes, if you do that then the client will not become slaved to the game. In so doing you lose a handsome slice of the capability of the client to interact with the game world though.
With IVC Enabled I fear too much is overridden by Falcon (e.g. the server IP if required and overrides and who knows what else).
Wow. Again it would not have occurred to me to imagine that anyone would be anxious about making the IVC client and the game code work together. Ya know there’s nothing super-secret going on when you enable the IVC in the network connect dialog – the only things that might change (provided of course you aren’t repeating values copied into the client on separate start up in which case there’ be no change) would be the one thing placed into the network connect dialog, i.e. the server IP, your callsign and the UHF and VHF frequencies. You can make the frequencies used in this case be anything you want to by setting those in the cfg file so it’s hard to see something harmful (in the sense of fear of override) going on there. Nothing else is overridden and even in the case of the things that game code does in slaving the IVC client you are in control: you can make what the game uses and what the client uses before the game starts be exactly the same at your option with just a little care in setting configurations for IVC and the game.
-
In fairness though, my thoughts are leaning in the direction of ‘it would be awesome if you went to 3D to be AWACS’ so there’s that option to think about too. Not that Id expect that to be easy or happen anytime soon.
The “fly” button works just fine when you take a seat in an AWACS flight so far as I’m aware.
-
Right… but its a little hard to then ACT as awacs. No 2D map, for instance. No 360 degree radar with L16 to make up for the lack of 2D map, for instance.
-
Right… but its a little hard to then ACT as awacs. No 2D map, for instance. No 360 degree radar with L16 to make up for the lack of 2D map, for instance.
Indeed – which is probably why that “option” request made no sense to me
-
So to clarify a little - my first option request was for the effects in the 2D UI. Then my second thought which I put in the post, was about how ideally you wouldnt need the effects in the 2D UI, because ideally you would do AWACS from 3D. The fact that we don’t is the reason for wanting those effects in the 2D UI.
-
With f4awacs you can play awacs without entering 3d. Awacs player has to take a seat in an awacs plane in the frag order though.
He’ll not have processing sounds but other players will listen him with disturbs according to the actual position of the awacs.
And imho f4awacs has an usable interface while 2d map is absolutely uncomfortable to use for awacs.
-
There is presently no way to get the radio sound filtering effects to work for 2D world use. This is by design. For what it’s worth the thinking was that VoIP use in the 2D UI would primarily be for briefings and the like meaning that half-duplex and reduced sound fidelity would actually be detriments not enhancements. The other issue is that lack of range and altitude information make some or all of the sound processing effects code moot (not mute ;)) anyway…i.e. the primary difference would in fact be making the UI half-duplex instead of full duplex and there’s already a way to do that.
It’s just software though so anything is possible.
Thanks Boxer, I misunderstood then.
Btw, since many vfw use the 2D map for atc and awacs purposes, it would be nice to include radio effects for it too. For briefing, we can still use a TS server with clean comms, just like we always do. It also would be great to see all contacts and not just the leader of each flight, but I think this is harder…
If I may ask a little OT, is there any chance to have the current QNH value in the briefing window like other weather data?
Thank you!
-
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
PasswordWhat else is altered by Falcon that is a valid parameter in the .ini?
Duplex?
Outsider?