Jetsi Posted January 15 Posted January 15 I apologize if this has been covered already, I have searched and did not find an answer but my search engine game is not very good. I have gone in and mapped out all the arguments that I could find for the F-15E and have successfully made triggers work with all manner of switches, such as the I/P switch, EMIS LIMIT switch, taxi light, landing light, speed brake, etc. The one I am having trouble with is the push-to-talk switch. Using my HOTAS I can see all the switches move in my virtual cockpit as I manipulate them, except for the PTT (labeled here as the microphone selector switch). I want to be able to have me making a radio transmission act as a trigger. Since the switch does not move in the cockpit, using argument 694 with a value range of 0.5 to 1 for UHF doesn't accomplish anything. So I am looking for possible solutions. Here are the ones I have come up with as possible but I don't know the values to use as I can't access the console function: Is there a key bind that I am using incorrectly on my HOTAS. I have it set to MIC Switch FWD (Radio 1 VOIP), would switching it to (Call Radio 1 Menu) make it work? This could be done in single-player ops but would cause difficulties in multi-player environments. Is there a parameter that is made when transmitting on a radio that could be found? Similar to the one for UHF1_FREQ as being selected, is there another for sending a message, something like UHF1_TRANS? Could I make the trigger work off of the T displayed on the UFC when a radio is transmitting using the X: cockpit indication text is equal to ???? . If this would be possible, where would I find the indicator ID number? Are there any other possibilities I am missing? Any help with this would be great, thanks in advance.
MAXsenna Posted January 15 Posted January 15 @Jetsi VOIP = Voice over Internet Protocol and is only for chatting during multiplayer, so that's definitely the wrong binding. Use the menu one I guess. Not at my computer so can't verify. Sent from my SM-A536B using Tapatalk
Jetsi Posted January 15 Author Posted January 15 Changing the binding to the "Call Radio 1 Menu) option does move the virtual switch in thew cockpit when using my HOTAS. So that option is available but I would to see if there is an alternative that would allow me to keep VOIP on that binding.
MAXsenna Posted January 15 Posted January 15 Changing the binding to the "Call Radio 1 Menu) option does move the virtual switch in thew cockpit when using my HOTAS. So that option is available but I would to see if there is an alternative that would allow me to keep VOIP on that binding. Why? I thought you were gonna use it for mission triggers. It's only for multiplayer. Sent from my SM-A536B using Tapatalk
Jetsi Posted January 16 Author Posted January 16 More that I dont want to have to change my settings every time I run missions and then hop into multiplayer servers.
MAXsenna Posted January 16 Posted January 16 More that I dont want to have to change my settings every time I run missions and then hop into multiplayer servers.Well, bind both or use a toggle. You're asking for something that already is there. Sent from my SM-A536B using Tapatalk
Jetsi Posted January 22 Author Posted January 22 Sorry for the long delay in response, was busy at work. I apologize if I am not making myself clear in this. I don't want the comms menu to come up, I plan on not using any of the system comms in these missions to the greatest extent possible. I play in VR and want this to be as immersive as possible. So, if anyone has console access and wants to help on that front or can tell me a way to disable the comms menu from displaying I am all ears.
MAXsenna Posted January 22 Posted January 22 Sorry for the long delay in response, was busy at work. I apologize if I am not making myself clear in this. I don't want the comms menu to come up, I plan on not using any of the system comms in these missions to the greatest extent possible. I play in VR and want this to be as immersive as possible. So, if anyone has console access and wants to help on that front or can tell me a way to disable the comms menu from displaying I am all ears. Well, if you're not gonna use the radio at all. Just don't bind it. Use it for VoiP or SRS instead. I assume you gonna do MP comms. Or are we still talking about triggers in a mission?Personally I don't do MP. I like immersion as well, so I never use the menu. I use the free VAICOM plugin for VoiceAttack, and speak all my comms. It has the option to completely hide the menu and all text on screen for that mather. Join the VAICOM Discord and ask how to achieve it, or have a look at the source code.I guess I'm out. I haven't the faintest clue to what you are actually trying to do. Hopefully someone else understand. Cheers! Sent from my SM-A536B using Tapatalk 1
Recommended Posts