sthompson

When I push the up/down buttons in NRML or MULTI I get the error "thud" sounds. Is that what you mean by "normal?" I get no sound at all when I push the same buttons in SNGL or INV, same as you. I don't think it has anything to do with your HOTAS software, since I'm having the same problems with completely different HOTAS setup.

The problem is present even if DCS is not running, so it is not likely to be related to what's in the lua files.

Yes. There is no way to uninstall it separately as nearly as I can tell.

As I stated in another post (https://forums.eagle.ru/showpost.php?p=4517468&postcount=6104), I tested with and without DCS running, using both the current release version and the current open beta version, in several different modules, with SRS selected or not, and with a clean VAP profile. None of that helped. The problem is there consistently. Yes I'm using the mouse to press the up/down arrow buttons on the PTT page. They are not responsive. The same problem is present in INV mode. The buttons are equally non-responsive. I'm wondering if this is a side effect of some other change on my system. A Windows update perhaps, or change in a common DLL or API. Is there any way to see what's going on under the hood?

I tried that already. It did not help with the problem.

A couple of comments on this. First, while I do not currently use SNGL mode, I used it previously when I was learning VAICOM. Its purpose is well documented in the manual. From the manual: "SNGL: Select this mode if you prefer to have just a single PTT hotkey in your setup for all aircraft. Modules with multiple PTT hotkeys will now be mapped to a single TX node. Use the Up/Down buttons to select which TX to use." I used it with TX4 (AUTO) so that VAICOMPRO would automatically select the correct radio based on the selected recipient using a single PTT key. So I'm a bit puzzled by the questions about "what are you trying to accomplish." Second, I have a fairly vanilla installation and generally VAICOMPRO works fine for me. However I tried testing SNGL mode and found that I also could not change the TX selection using the up/down keys. It is stuck on TX1, same as Tomeye. This used to work, so something has changed. To make sure it wasn't a configuration issue, I did a full repair of DCS and then restarted VA. No errors or problems recorded in the debug log. But the problem remains. It remains no matter which version of DCS I use, whether or not SRS is active, whether or not I'm in a module, and whether or not I first press various TX keys. I tried in the Huey and in the MiG-15 with same results. I also tried installing a fresh profile by using the Export function to generate a clean VAP file and then loading that. It did not help. So I think it may be a bug and suggest that Tomeye start a new bug notice thread in the main VAICOM forum at https://forums.eagle.ru/forumdisplay.php?f=733 rather than continuing in this thread.

Sniperpr1: According to your log, VAICOMPRO thinks that you have version 2.5 (release version) at E:\Program Files\Eagle Dynamics\DCS World and the open beta version at D:\DCS World OpenBeta\bin. It's getting the 2.5 release version path from the registry entry, and the open beta path from your use of the "custom path" option in VAICOM. Is that where you have them installed? It's having trouble finding the 2.5 release version. Also, I don't see anything in your log suggesting which version of DCS you are using for your tests, or even that you are testing after starting DCS and dropping into a module. So which version are you using? And is your log saved after dropping into the F-14 module in a mission? Do other DCS commands such as contacting the ground crew (not Jester commands) work?

Per the manual, VAICOMPRO only supports hot mic for ARIO (Jester). You must use PTT for all other VAICOM PRO commands. This is true even if you have the hot release button selected on the PTT page. According to the manual, that is there to enable you to activate your own commands, and "All VAICOM PRO communications commands still require PTT to be used."

Yes, that's exactly what I do. I find that often I don't even need the repair, but that depends on the update. Starting VA before starting DCS is very important, because VA needs to update the lua files before DCS starts.

I have found that I never have to delete export.lua and in fact can skip the steps highlighted in red. Perhaps I'm charmed, but it's also possible that the order matters. Here is my export.lua: local Tacviewlfs=require('lfs');dofile(Tacviewlfs.writedir()..'Scripts/TacviewGameExport.lua') local vaicomlfs = require('lfs'); dofile(vaicomlfs.writedir()..[[scripts\VAICOMPRO\VAICOMPRO.export.lua]]) pcall(function() local dcsSr=require('lfs');dofile(dcsSr.writedir()..[[Mods\Services\DCS-SRS\Scripts\DCS-SimpleRadioStandalone.lua]]); end,nil);

Suggest you enable debugging and tell us what is in the VA log when this happens.

Then use Num4 and Num6 to rotate left or right.

This isn't completely accurate. First, for the most part VAICOM PRO edits the DCS files by appending new code to them rather than replacing them. Second, the exact code that gets inserted can be found by running the "Export" function from the editor tab and then looking in the Export folder that opens. All of this is well documented in the VAICOM PRO manual in the section that describes how to manually manage the DCS lua files yourself rather than using the automatic procedures. When you run a DCS repair these modifications are detected and replaced with the original files. The backups that get saved (if you choose to save them) are the edited files, which are not the same as the originals, but are not entirely from VAICOM either.

The command "Mission, Options" takes you straight to the F10 menu, saving a step.

When I switched off SRS Mode the in-cockpit radio did show up using MULTI but connected to TX2. It's still a mystery to me why no radios show up when I have the SRS mapping button selected. Is that by design? Using MULTI with SRS selected works fine in the P-51.

As in the subject line. I purchased the P-47 today and VAICOM PRO was not responding when I was in the module. Looking at the VAICOM PRO configuration screen shows that the module is recognized but no radios are recognized in MULTI mode or in INV mode. See screenshot below. I usually use MULTI so that TX6 will be available. I can see the module radio on TX1 if I rotate the switch to NORM, but then there is no TX6, which seems to be a common problem across many modules for reasons that have never been explained.

Skunk. Try doing a DCS repair and then start VA _before_ you restart DCS. That way DCS can't interfere with the lua editing that VA wants to do. Your latest log suggests that you are starting DCS before VA. Try it the other way around. That's what works for me.

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.

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.

"Just go VR?" LOL. Not on my ancient rig. But seriously, is contact spotting easier on VR?

Works just fine for me in MP. Sorry to hear that others don't have the same experience.

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.

Interesting tool but I don't see how to use it to determine best FOV in DCS.

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?

I experience this fairly often too. Seems to be related to me being impatient when DCS is loading slowly. If I Alt-TAB to another application while it is loading there is a good chance that when I come back to DCS I will only have the black background splash screen with version number display, and no way to display the GUI, which clearly is running in the background (music playing, etc.). If I do not interrupt the DCS startup then it works fine. I'm running an Nvidea 1060 with up-to-date drivers.