DigitalEngine Posted August 11, 2020 Posted August 11, 2020 Using the Su-25T, w/ SRS When calliing ATC, the ATC will respond on any/all channels, For example, at Mozdok, no matter what channel I've selected or radios using SRS, when calling ATC for startup, ATC will respond. How do I force that the radio must be tuned to the correct freq, in this case 137.00, for ATC, or if not tuned to correct freq, no response from ATC? I've set up SRS and Viacom as per the Viacom manual (page 25). Any help please? CPU = Intel i7-6700K Motherboard = ASUS ROG Maximus VIII Hero Alpha, w/ the Intel Z170 Chipset, RAM = 64 Gigs of Ripjaws V F4-3400C16Q. GPU = Zotac GTX980ti Amp Extreme Hard-drive = Samsung V-NAD SSD 950 PRO M.2
MAXsenna Posted August 11, 2020 Posted August 11, 2020 Hi! Are you asking how to tune the radio in a Flaming Cliff aircraft? Sent from my ANE-LX1 using Tapatalk
DigitalEngine Posted August 12, 2020 Author Posted August 12, 2020 (edited) Hi! Are you asking how to tune the radio in a Flaming Cliff aircraft? Thanks Max, I'm not asking how to tune the radios in a FC3 + SRS aircarft, that I can do with the SRS radio overlay, and speak (or not speak) to other warm blooded clients just fine. What I'm referring to is this, for example in the TF-51D, to contact Mozdok ATC; One must preset one of the channels to frequency 137.00 in the M.E. (let's say channel 2). Then one must select that channel (2) on the aircraft radio control panel in the cockpit in order to talk to Mozdok ATC, otherwise Mozdok ATC will not hear you, as you are not transmitting on frequency 137.00. However, with FC3 aircraft (for example the Su-25T), and using the SRS Radio Overlay to select let's say frequecy 124.00 (or any frequecy, for that matter), the Mozdok ATC will hear and respond, even though the Mozdok ATC should only hear me and respond on frequency 137.00 (VHF, that is). I do have DCS Easy communication unchecked. Edited August 13, 2020 by DigitalEngine CPU = Intel i7-6700K Motherboard = ASUS ROG Maximus VIII Hero Alpha, w/ the Intel Z170 Chipset, RAM = 64 Gigs of Ripjaws V F4-3400C16Q. GPU = Zotac GTX980ti Amp Extreme Hard-drive = Samsung V-NAD SSD 950 PRO M.2
MAXsenna Posted August 13, 2020 Posted August 13, 2020 As far as I know, you cannot change radio frequency in FC3 aircrafts. That's why I'm asking. I just say "Select Mozdok" in VAICOM if I want to contact Mozdok ATC. As far as I remember. Took the Su-25 up to test FFB the other day. And now the TX layout has changed again... So I didn't bother contacting ATC, as I didn't have a VAICOM profile with TX3 configured, as that was what VAICOM wanted now. I have no clue if something changed in VAICOM or DCS. But first time I used VAICOM it was TX1, then changed to TX2 or vice versa, now it's TX3. Sent from my ANE-LX1 using Tapatalk
MAXsenna Posted August 13, 2020 Posted August 13, 2020 Okay. I tested. VAICOM does not work for me in the Su-33 or Su-25T. Only FC3 modules I have. Probably something has changed in DCS. Both stable and OB, but they are the same now, so I didn't expect a different result. Little unfamiliar with SRS, but I would actually expect your result in any FC3 aircraft, as I don't think they really have radio channels in that sense. Only Hollywood can answer this. Landed at two different airports in the Gulf, both asked me to park without me ever contacting them in the first place. Sent from my ANE-LX1 using Tapatalk
DigitalEngine Posted August 13, 2020 Author Posted August 13, 2020 Max, As far as I can tell, VAICOM, with latest versions DCS/VA/VAICOM, is working as advertised for me, as far as sending/getting commands from the ATC, other than with the FC3's "internal radio" seeming to TX/RX to on all frequency's at once (that is, to AI entities). I now suspect this is a core of DCS FC3 radio communications limitation, as it is. I haven't worked with Lt.Bot (AI pilots) yet. Maybe Hollywood could chime in on this please? :music_whistling::helpsmilie: CPU = Intel i7-6700K Motherboard = ASUS ROG Maximus VIII Hero Alpha, w/ the Intel Z170 Chipset, RAM = 64 Gigs of Ripjaws V F4-3400C16Q. GPU = Zotac GTX980ti Amp Extreme Hard-drive = Samsung V-NAD SSD 950 PRO M.2
MAXsenna Posted August 13, 2020 Posted August 13, 2020 Maybe I was unclear. VAICOM works perfectly for me. Except for FC3 modules, the two I have. Because suddenly radio is on TX3, in the control panel that is. I might send a screengrab. How did you change radio frequencies in FC3 before? I never could. Of course I could change ATC by "Select... (insert random airfield). But now I get the dreaded "listening suspended", as my TX won't work as they have been on TX1 or TX2 in the past. Does FC3 work for you apart from SRS? Sent from my ANE-LX1 using Tapatalk
DigitalEngine Posted August 13, 2020 Author Posted August 13, 2020 (edited) Max, no I'm not having that issue. I just did a quick test, "request start-up" to Mozdok ATC in the Su-25T, the VIACOM Configuration Window PTT tab indicates that I'm transmitting on TX1. Got a reply back from Mozdok ATC. However, my SRS R-862 radio was set to frequency 124.00, where as the Mozdok ATC freq. is 137.00. You have to use the SRS Overlay to change FC3 freqs. or set up custom controls on you HOTAS or keyboard. Edited August 13, 2020 by DigitalEngine CPU = Intel i7-6700K Motherboard = ASUS ROG Maximus VIII Hero Alpha, w/ the Intel Z170 Chipset, RAM = 64 Gigs of Ripjaws V F4-3400C16Q. GPU = Zotac GTX980ti Amp Extreme Hard-drive = Samsung V-NAD SSD 950 PRO M.2
MAXsenna Posted August 13, 2020 Posted August 13, 2020 That's really strange! It looks completely different for me. Don't get any of those radios to show up in the control panel when I get into the Su-25T. But I ment, does it work for you in single player? Or are you using SRS in SP as well? Just tested something. I can make it work by turning the dial to multi. Obviously something is wrong here on my end. I can select other ATCs than Mozdok, but I don't get any reply. I'm gonna try that navigation mission to see what happens. After that. Repair. Sent from my ANE-LX1 using Tapatalk
sthompson Posted August 13, 2020 Posted August 13, 2020 On what settings? Do you have the TX SRS keymapping selected in Vaicom Pro options? Is your TX rotary selector switch on Normal or something else? Maybe I was unclear. VAICOM works perfectly for me. Except for FC3 modules, the two I have. Because suddenly radio is on TX3, in the control panel that is. I might send a screengrab. How did you change radio frequencies in FC3 before? I never could. Of course I could change ATC by "Select... (insert random airfield). But now I get the dreaded "listening suspended", as my TX won't work as they have been on TX1 or TX2 in the past. Does FC3 work for you apart from SRS? Sent from my ANE-LX1 using Tapatalk I'm Softball on Multiplayer. NZXT Player Three Prime, i9-13900K@3.00GHz, 64GB DDR5, Win 11 Home, Nvidia GeForce RTX 4090 24GB, TrackIR 5, VKB Gunfighter III with MCG Ultimate grip, VKB STECS Standard Throttle, CH Pro pedals
MAXsenna Posted August 13, 2020 Posted August 13, 2020 On what settings? Do you have the TX SRS keymapping selected in Vaicom Pro options? Is your TX rotary selector switch on Normal or something else?Exactly what I wrote. It started working when I turned rotary to multi. So now it works with a workaround. So I'm happy. Gotta found out why though. 'Cause somethings up with my system. Only FC3, normally set to normal. I don't really do MP, hence no SRS, but I've got it installed though, but not checked on VAICOM control panel. Sent from my ANE-LX1 using Tapatalk
sthompson Posted August 14, 2020 Posted August 14, 2020 Sorry I missed that. I've generally found that VAICOM PRO is less predictable with the dial set to "Normal." I've noted in several posts that TX6 is not available in some modules with the switch on Normal and have asked for an explanation, but I don't think one has been given. I don't want "Options" or "Take" or orders to ground crew going out over SRS and so I use TX6 for those, and use the Multi setting to make sure that TX6 is available. Exactly what I wrote. It started working when I turned rotary to multi. So now it works with a workaround. So I'm happy. Gotta found out why though. 'Cause somethings up with my system. Only FC3, normally set to normal. I don't really do MP, hence no SRS, but I've got it installed though, but not checked on VAICOM control panel. Sent from my ANE-LX1 using Tapatalk I'm Softball on Multiplayer. NZXT Player Three Prime, i9-13900K@3.00GHz, 64GB DDR5, Win 11 Home, Nvidia GeForce RTX 4090 24GB, TrackIR 5, VKB Gunfighter III with MCG Ultimate grip, VKB STECS Standard Throttle, CH Pro pedals
MAXsenna Posted August 14, 2020 Posted August 14, 2020 Sorry I missed that. I've generally found that VAICOM PRO is less predictable with the dial set to "Normal." I've noted in several posts that TX6 is not available in some modules with the switch on Normal and have asked for an explanation, but I don't think one has been given. I don't want "Options" or "Take" or orders to ground crew going out over SRS and so I use TX6 for those, and use the Multi setting to make sure that TX6 is available.Ah! I had totally forgotten about TX6, and the way I had planned to use it. Pretty much like your way. That's actually a good idea in MP. Can't remember why I don't though. I think I mistook it for intercom at first and it didn't work as expected. Anyway, this issue I have with FC3 is the first time, and I know it worked for me last year. So somethings changed, but I cavite for the love of my life understand what I changed on my end. Sent from my ANE-LX1 using Tapatalk
sthompson Posted August 15, 2020 Posted August 15, 2020 As nearly as I can tell AI communications for planes without clickable cockpits do not use frequencies. The SRS tuning is therefore irrelevant to the AI communications in these modules, whether you use the overlay or some other method to tune SRS. I think this is a DCS "feature" that has nothing to do with VAICOM PRO. I can verify the experience you describe below but I believe it is by design. BTW, The SU-25T is not an FC3 module, although it behaves like one in all respects as far as I know. Max, no I'm not having that issue. I just did a quick test, "request start-up" to Mozdok ATC in the Su-25T, the VIACOM Configuration Window PTT tab indicates that I'm transmitting on TX1. Got a reply back from Mozdok ATC. However, my SRS R-862 radio was set to frequency 124.00, where as the Mozdok ATC freq. is 137.00. You have to use the SRS Overlay to change FC3 freqs. or set up custom controls on you HOTAS or keyboard. I'm Softball on Multiplayer. NZXT Player Three Prime, i9-13900K@3.00GHz, 64GB DDR5, Win 11 Home, Nvidia GeForce RTX 4090 24GB, TrackIR 5, VKB Gunfighter III with MCG Ultimate grip, VKB STECS Standard Throttle, CH Pro pedals
sthompson Posted August 15, 2020 Posted August 15, 2020 Max: I just tested all of the FC3 modules (I have all of them from the FC3 bundle) and found the TX assignments to be exactly as expected in every one of them. This is whether I had SRS mapping on or off and with the selector switch in the NORMAL setting. I suspect you need a repair. Or perhaps the standalone versions are not exactly identical to those in the FC3 bundle as advertised. Maybe I was unclear. VAICOM works perfectly for me. Except for FC3 modules, the two I have. Because suddenly radio is on TX3, in the control panel that is. I might send a screengrab. How did you change radio frequencies in FC3 before? I never could. Of course I could change ATC by "Select... (insert random airfield). But now I get the dreaded "listening suspended", as my TX won't work as they have been on TX1 or TX2 in the past. Does FC3 work for you apart from SRS? Sent from my ANE-LX1 using Tapatalk I'm Softball on Multiplayer. NZXT Player Three Prime, i9-13900K@3.00GHz, 64GB DDR5, Win 11 Home, Nvidia GeForce RTX 4090 24GB, TrackIR 5, VKB Gunfighter III with MCG Ultimate grip, VKB STECS Standard Throttle, CH Pro pedals
MAXsenna Posted August 18, 2020 Posted August 18, 2020 Max: I just tested all of the FC3 modules (I have all of them from the FC3 bundle) and found the TX assignments to be exactly as expected in every one of them. This is whether I had SRS mapping on or off and with the selector switch in the NORMAL setting. I suspect you need a repair. Or perhaps the standalone versions are not exactly identical to those in the FC3 bundle as advertised.Thanks for replying! Done repairs. No go. Will try it again. But for now, well something what was released last night... And Syria tomorrow! I'm pretty happy anyway as I have fix. Cheers! Sent from my ANE-LX1 using Tapatalk
DigitalEngine Posted August 21, 2020 Author Posted August 21, 2020 OK, so back to the original issue/question, as in the quotes below. I'm now suspecting this is a core of DCS FC3 module radio communications limitation, as it were. Could Hollywood chime in on this please? :) Using the Su-25T, w/ SRS When calliing ATC, the ATC will respond on any/all channels, For example, at Mozdok, no matter what channel I've selected or radios using SRS, when calling ATC for startup, ATC will respond. How do I force that the radio must be tuned to the correct freq, in this case 137.00, for ATC, or if not tuned to correct freq, no response from ATC? I've set up SRS and Viacom as per the Viacom manual (page 25). Any help please? I'm not asking how to tune the radios in a FC3 + SRS aircarft, that I can do with the SRS radio overlay, and speak (or not speak) to other warm blooded clients just fine. What I'm referring to is this, for example in the TF-51D, to contact Mozdok ATC; One must preset one of the channels to frequency 137.00 in the M.E. (let's say channel 2). Then one must select that channel (2) on the aircraft radio control panel in the cockpit in order to talk to Mozdok ATC, otherwise Mozdok ATC will not hear you, as you are not transmitting on frequency 137.00. However, with FC3 aircraft (for example the Su-25T), and using the SRS Radio Overlay to select let's say frequecy 124.00 (or any frequecy, for that matter), the Mozdok ATC will hear and respond, even though the Mozdok ATC should only hear me and respond on frequency 137.00 (VHF, that is). I do have DCS Easy communication unchecked. As far as I can tell, VAICOM, with latest versions DCS/VA/VAICOM, is working as advertised for me, as far as sending/getting commands from the ATC, other than with the FC3's "internal radio" seeming to TX/RX to on all frequency's at once (that is, to AI entities). I now suspect this is a core of DCS FC3 radio communications limitation, as it is. Maybe Hollywood could chime in on this please? :music_whistling::helpsmilie: CPU = Intel i7-6700K Motherboard = ASUS ROG Maximus VIII Hero Alpha, w/ the Intel Z170 Chipset, RAM = 64 Gigs of Ripjaws V F4-3400C16Q. GPU = Zotac GTX980ti Amp Extreme Hard-drive = Samsung V-NAD SSD 950 PRO M.2
Hollywood_315 Posted August 23, 2020 Posted August 23, 2020 This is a core DCS limitation: FC3 modules do not have radio devices modelled. Thanks There is no spoon. VAICOM PRO plugin for DCS World www.vaicompro.com
MAXsenna Posted August 23, 2020 Posted August 23, 2020 That's what I thought. But would you have any suggestion/clue to why FC3 planes maps my radio to TX3 now? Unless I set the dial to single/multi? Sent from my ANE-LX1 using Tapatalk
DigitalEngine Posted August 25, 2020 Author Posted August 25, 2020 (edited) That's what I thought. But would you have any suggestion/clue to why FC3 planes maps my radio to TX3 now? Unless I set the dial to single/multi? That I don't know MAX, however, I think if I had this issue, even though it'd be a pain, only way I'd konw to fix it, is to remove all mods, do a DCS clean/repair/ rename the Export.lua file, clean the saved games scripts folder, uninstall VA and VIACOM, basically do a complete uninstall and reinstall/setup. This is a core DCS limitation: FC3 modules do not have radio devices modelled. Thanks Thanks Hollywood, realizing your time resources are likely limited, so, I'm not really requesting this, as much as asking if this is feasible. Would it be possible to write some type of "script layer", such as, if you are in a FC3 module, and you are using the SimpleRadio Standalone app with VIACOM, that to contact ATC, the active SRS radio must be tuned to the correct ATC frequency, or the request would be filtered/blocked, simulating selection of the correct frequency as imperative? Same for commanding the AI pilots? Edited August 26, 2020 by DigitalEngine CPU = Intel i7-6700K Motherboard = ASUS ROG Maximus VIII Hero Alpha, w/ the Intel Z170 Chipset, RAM = 64 Gigs of Ripjaws V F4-3400C16Q. GPU = Zotac GTX980ti Amp Extreme Hard-drive = Samsung V-NAD SSD 950 PRO M.2
MAXsenna Posted August 26, 2020 Posted August 26, 2020 That I don't know MAX, however, I think if I had this issue, even though it'd be a pain, only way I'd konw to fix it, is to remove all mods, do a DCS clean/repair/ rename the Export.lua file, clean the saved games scripts folder, uninstall VA and VIACOM, basically do a complete uninstall and reinstall/setup. Thanks Hollywood, realizing your time resources are likely limited, so, I'm not really requesting this, as much as asking if this is feasible. Would it be possible to write some type of "script layer", such as, if you are in a FC3 module, and you are using the SimpleRadio Standalone app with VIACOM, that to contact ATC, the active SRS radio must be tuned to the correct ATC frequency, or the request would be filtered/blocked, simulating selection of the correct frequency as imperative? Same for commanding the AI pilots?Thanks. But this question was actually intended for Hollywood as I've already tried what you suggested, to no avail. Cheers! Sent from my ANE-LX1 using Tapatalk
Recommended Posts