sthompson

When I read comments like this (and I don't want to pick on Razorback specifically since there are lots of comments in this thread that are similar) I have to wonder whether people are bored with the features already present. Personally I feel as if I have years of learning to do and enjoyment to be had even if no new features are released. And I've been flying DCS for years now. Why all the urgency for new features? The old ones are fantastic! Yes I want bugs fixed and promised features delivered on products I bought based on those promises. But I'd rather that whole new modules and updates are released when they are ready and don't see any need for date promises.

Interesting. I'm seeing the same thing. Seems to be a copy of the files added to DCS as part of VAICOM's kneeboard extension. I agree that it shouldn't be there. I suggest you report it as a bug in a separate thread in the main VAICOM forum. This thread is so long that it will be easy for the dev to miss your report. BTW, nothing about these files is reported in the VAICOM log even with debug turned on. Seems like these files should be in the list of files "reset" upon initialization.

I've thought it too bad that you can't optionally specify that a client plane be displayed as a static object if not selected. I'm imagining a mission where you drive down the flight line in a Humvee (using Combined Arms) and then stop and select the plane you want to fly from among those in front of you. It doesn't work like that now because you can't see clients until they spawn with a human pilot in them.

I have read in other forums that sometimes a copy of config\view\snapviews.lua gets embedded in a mission file and causes this effect by over-riding the one in the Saved Games directory. If the mission file is then used as the basis for other missions it gets carried over. So it would be easy for it to happen without the mission designer even realizing it. I was able to open one of your mission files in the mission editor and found copies of snapviews.lua and snapviewsdefault.lua in the config\view subfolder among other files. Unless your missions have some need to over-ride the user's view settings you should be able to just delete that folder entirely from your missions. I tested this on your mission 2 and it solved the problem. Of course next time I do a repair it will be back.

I have a few custom snap views set for the F-5. For example I frequently use the "view in" snap view (KP0) to get a close up view of the instrument panel. When I fly these missions my custom snap views are not available and I get the defaults instead. I suspect they are being over-written by config files in the missions. After flying one of these, if I then fly an instant action F-5 mission my custom snap views reappear. Can you delete the snap views from the missions?

No it doesn't. That is optional, and not turned on by default.

VoiceAttack has its own forums that are monitored by the devs. Suggest you ask there. Link via support on their website. I've found them quite helpful. Also, earlier in the thread you wrote "Most gaming headsets suffer the same problem where mic (in) picks up headphone sound (out) or vibration specific to that word so you end up in a feedback loop." I can't speak for "most gaming headsets" since I only have a simple Logitech one, but it doesn't have that problem. I would avoid a headset where the mic picks up what is coming out of the earcups.

Looking back at your log, VAICOM is not recognizing the word "Texaco" as a recipient. Instead it seems to think the recipient is "Approach." This is not a valid tanker recipient and so it substitutes the generic Tanker as the recipient, and that defaults to whichever tanker is currently selected. This suggests that the issue is that you are not pausing long enough between saying "Texaco" and saying "Approaching for Refuel." Try a longer pause and/or going into training to train on the word Texaco. I suggest you keep Audio Hints turned on and then try saying Texaco with the PTT held down. If you don't get a beep in response then VAICOM has not identified the recipient. Keep holding the PTT and give the "Approaching for Refuel" command only after you hear the first beep. You should then hear a second, higher pitched beep indicating that the command has been understood. These suggestions are for use with VSPX turned off. I have no experience with using VSPX, and possibly things work differently with it on. FYI, I created a small mission with two tankers Shell and Texaco and me flying the Hornet. VAICOM switched between them flawlessly when I used the correct call signs. That was with Instant Select turned on. The commands went specifically to Shell or Texaco if I included them in the command, with a suitable pause before "Approaching for Refuel."

You are using the LEFT Control and Alt keys? Sorry you are pissed off. Remember that most people helping out here are volunteer users just like you.

Did you try giving a "nearest tanker, select" or "Texaco, select" command before making the call? VAICOM does tend to select closest recipients at spawn (or when you restart VAICOM if already spawned). In theory it should switch to Texaco if you name Texaco in the Approach for refuel command, but only if you have enabled Instant Select in the options. Otherwise you need to give a select command first. Tuning the right frequency is not good enough to automatically select the recipient.

If you say "Mission" instead of "Option" it will jump straight to the F10 radio menu and then you can use "Take" to select one of the options. This cuts a step when you are in a hurry!

Which version of DCS are you using? If Steam, then that is the problem, since VAICOM is not detecting a Steam version. You might also look at the DCS log to see if there are any errors when DCS loads export.lua.

That server does force Easy Comms on. But I'm not sure that explains why the radio would change tuning once tuned in to a valid recipient. Would help to know which module and the specific command that caused the tuning to change, and whether you have "Instant Select" enabled. I'm completely incompetent on AAR but I've practiced on that server and have not had the problem. Here is my guess: There is often more than one Texaco or Arco etc flying at once on that server and so if you are using Instant Select and call "Texaco, approaching for refuel" you may not get the one you want, and DCS might change the tuning at that point depending on which one Texaco VAICOM selects. You can solve that problem by using the radio menu to make the initial call instead. (I wish VAICOM had a means to distinguish recipients with the same call sign because Instant Select is unpredictable in that setting.) Once tuned to the correct tanker, if you call "Texaco, ready precontact" then it might switch the tuning to the other Texaco. That might explain what is going on. But if you just call "Ready precontact" then the tuning does not change, as long as you are already tuned to a valid tanker.

The "pin" function in DCS is the same as "make shortcut" and applies to individual kneeboard pages. You certainly can make a voice command in voiceattack to execute that command, provided you first bind it to a key in DCS. And you could make voice commands to go to the next or previous shortcut. None of that would have anything to do with VAICOM PRO, however. You mention "subpages" and by that I assume you mean the tabs on the VAICOM page. You can't pin those individually, but you can pin the VAICOM page and then use the VAICOM voice commands to choose among the tabs. Unfortunately the shortcuts all disappear when you exit a module, however.

Just a guess since I've never tried using this feature of Kneeboard Builder, but I suspect that that feature was broken by recent DCS updates that made the kneeboard moveable and resizable within DCS itself.

Else. The voice command is "Approaching for Refuel." It's in the manual.

The extension adds one extra page to the regular kneeboard but that page has many tabs and so it seems as if there are many additional pages. VAICOM confusingly calls the individual tabs "pages" even though they are not separate kneeboard pages. In particular, the ordinary DCS next/prev kneeboard page commands treat the VAICOM page as one page and do not work to switch between tabs on that page. The shortcut commands treat the VAICOM page as one page too, so you can't make shortcuts to individual tabs. You cannot click on the tabs to select them. Without extra programming the only way to switch between tabs on the VAICOM page is to use voice commands. On the other hand, the voice commands do not provide a general means of navigating between other pages of the kneeboard other than the one added by VAICOM. The extension also includes a voice command for opening and closing the kneeboard, or for opening it directly to one of the VAICOM tabs. Otherwise it is all the regular kneeboard. You do not gain or lose any functionality with respect to other custom or default pages. Pages added by individual modules (e.g. F-14) are still there for example, as are pages for mission briefings, maps, etc., to the extent that they were there already.

I don't have VR (someday maybe when I upgrade my rig). But I find that the immersion factor for night flying is much greater if I turn off the lights in the room. My flying is usually in the RL evening or night so this works well, even without VR.

You could do a complete reset using the reset tab and then only add back the extensions that you want.

LIcense numbers must be entered one at a time, and you need to delete the text in the box first. Same with the email address field, which is required to validate a license. If there is any doubt about whether your license has been accepted push the "LIST" button the same page. That should open a dialog box that shows your licenses as known and recorded by the software. On the other hand, if the FINISH button does not copy anything to the clipboard then you have a bigger problem, since you should be getting all of the default commands even if the add-on commands are not available. You might be able to solve this by going to the Reset tab and reset the keywords database. Possibly yours has become corrupted somehow. You will need to do the FINISH step again after that.

The title of this thread is "SU-33 pilot cannot land and take off from the new Kuznetsov carrier." That's not true. Your complaint is about the pricing, not whether you can take off or land from the new carrier. You also mention the "free" su33. There is no such thing. Bundling it with the Supercarrier does not make it "free." If you buy it standalone or part of FC3 you can use it on the older Kuznetsov, which is still available for free. But if you want to use the supercarriers you must buy the supercarriers. It's a straightforward policy.

Consider making this into a file and posting it to the user files section of the main DCS website. These may be in a lua file somewhere associated with each map. If you can find it, post the information heree so we can look for the corresponding file in the other maps.

I'm not clear on what you are looking for or trying to do. The VoiceAttack documentation is extensive. See for example https://voiceattack.com/VoiceAttackHelp.pdf. Conditional execution based on the value of an exposed variable is documented starting on page 83 at header 'Begin a Conditional (If Statement) Block.' On the other hand, if you are just trying to use separate buttons for a given TX node depending on the module then all you need to do is duplicate the TX PTT definitions in your profile (one for press, the other for release) and then program the duplicate to activate with a different button. It's then up to you to decide which one to use. You could add a conditional execution block to each copy so that it only works when a given module or set of modules is active. BTW, I suggest you not use dark mode when posting in these forums since it makes your posts almost impossible to read.

I don't think that is a workaround. The problem is that while VA is in listening mode it keeps thinking it recognized something. This is true even if the words that are recognized are not valid commands so that VAICOM takes no action. You still get a lot of unnecessary activity, including sound cues, while this is happening. It's also an issue when you are taking a human RIO role since VAICOM does not respect the switch in the back seat and so you can't turn listening off when you are RIO. The workaround for me has been to never use hot mic. This requires binding a separate key for intercom if you want to communicate with your RIO in SRS.

I suggest that feature requests are more likely to be seen if they get their own thread in the subforum rather than appearing on page 260 of this one. FWIW, I agree that VAICOM should have an option to not use hot mic even if the cockpit switch is turned on.