sthompson

I suspect you mean you copied it to a new location. I'm not sure what you mean by "pointed the missions etc" but you can't just copy it and expect everything to work in the new location. The original is a system folder. The copy isn't.

My understanding is that you can force DCS to use a specific subfolder of Saved Games through the variant.txt file in the DCS root directory. (For example, if it has the word "openbeta" in it then DCS will use Saved Games\DCS.openbeta.) However you can't force it to use a second Saved Games folder. There should never be two Saved Games folders for one user since this is a system folder. To find out where Windows thinks the folder is, fire up RegEdit and browse to the section [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders]. Then look for the registry key {4C5C32FF-BB9D-43B0-B5B4-2D72E54EAAA4}. The default value is something like "C:\Users\yournamehere\Saved Games" Whatever is in that key is where Windows thinks your Saved Games folder is. If you deleted the folder or moved it somewhere else then Windows doesn't know how to find it, and DCS probably won't find it either. If you know what you are doing you can edit that entry to point to the actual location. In the future, if you want to move the Saved Games folder do it the right way -- by opening its folder properties and then using the "Location" tab.

Perhaps, but that big delta wing is pretty unforgiving if you have a slow speed departure. I found landing the Mirage to be challenging when I was learning it. It's easy to get low and slow without enough thrust to recover. Otherwise agree with your assessment.

Check the transparency slider in the VAICOM settings widget.

I hope they don't roll it out until the AI knows how to deal with it. This may not matter for immobile AAA defense units, but for airborne AI units its not enough to just block their vision through clouds. You need to change the way they approach engagements when clouds present potential challenges and opportunities, just as they affect the way human pilots fly against each other now that clouds are coordinated in MP. In other words, the technical challenges likely involve more than just making sure AI units can't see through clouds. That said, my experience so far flying missions against airborne AI enemies is that the clouds give them a real advantage. In missions where the AI is hidden by clouds, they know exactly where I am, have full SA, but I'm lucky if I can find them.

You do realize you are complaining about a Microsoft feature, not VAICOM, right? When I got started with VAICOM I learned I needed to upgrade my microphone before I could start getting reliable voice recognition. Also, turn off your speakers and switch to headphones. The phrases that the voice recognition system is prompting in the example include the correct word "chief" echoed more than once. So I think you have a problem with echos being heard by the speech recognition software. It's not a VAICOM problem.

Well that's how VAICOM version 1 worked. It's still available out there for free if you want to try to use it. But Hollywood created the PRO version in part because maintaining a version that used the menus directly required constant updating as well as some difficult mods that modified the menus themselves. (I know, because I contributed some of the mods.) The new system actually works a lot better.

Unfortunately, that is correct behavior. You need to select the supercarrier as recipient before giving the inbound or marking moms call if there is another valid ATC that is closer. It was true before 2.7.

When I played last night the second cloud layer topped out around 26,500 ft. They were definitely below that. And I'm impressed you found the bandits on radar. I was searching for them, but I've never had much luck with the F-5 radar. It sometimes seems blind even to planes I'm spotting visually right on my nose.

There is a bug thread on the End Mission bug. See https://forums.eagle.ru/topic/192116-quotend-missionquot-button/. Someone has figured out the bug and posted a lua fix, but ED does not seem to have picked up on that.

Mission 2 is, shall we say, interesting, with the new clouds. I've tried it once and never did see any of the enemy aircraft due to visibility issues.

If you haven't tried the old Instant Action missions with the new 2.7 clouds system I recommend giving them a shot. The Caucacus Intercept and Ground Attack missions in particular. The intercept mission, which was too easy before, is still pretty easy, until you need to land in close to zero visibility! And Ground Attack in a winter snowstorm is a lot more challenging.

I do have notifications for followed content turned on there. I don't see anything in those settings that distinguishes between followed threads and followed forums, however, and I am receiving notifications about new postings in followed threads, but not about new threads in followed forums. My Followed Content settings are as follows: [Edited because cut and paste didn't work very well. Here is a partial screenshot instead.]

I've had this problem for a long long time. I've learned to live with it. I just push the \ key twice as needed. The usual shutdown VA, repair DCS, restart VA, restart DCS advice has no impact.

If you are asking whether I resubscribed to the subforums, the answer is yes. When I select the profile dropdown at the top of the page and then click "Manage Followed Content" and then Forums on the left side, the subforums I am subscribed to are listed and the notification setting for each is "immediate." If you are asking about some more general setting that controls forum notifications, I have looked for such a setting and not found it.

Sounds similar to the problems others have reported with tankers. VAICOM gets confused about units whose callsigns can change from mission to mission. You might try the AWACS, Options approach to give an initial command, and then see if it stays selected when you give later "bogey dope" commands.

I run VA as an ordinary user typically without any problems. However, be aware that VAICOM wants to modify some of your DCS files and also its own files. If these are stored under c:\program files then an ordinary user will not have privileges to modify those files and this will cause failures under some circumstances. I found that if I modify Windows security to give me read/write privileges on the relevant directories then everything works fine running as an ordinary user. BTW, I have recently started seeing VA crashes too. Had one last night in the middle of giving VAICOM a command. I had gotten the "recipient recognized" beep but VA crashed during the short pause before I gave the rest of the command. So it's not just related to idle status. I'm wondering if anyone has brought this up in the VoiceAttack forums to see if there is a way to debug the cause. I do not run any plugins other than VAICOM PRO.

This is probably the wrong place, but I can't find a forum to discuss problems with the forum software itself. I know we used to have such a place, but I can't find it. Moderators, please move as appropriate. In any event my issue is that ever since the new forum software was rolled out I get no notifications about new threads in forums or subforums that I am following. I do get notifications about new posts in threads I am following. I've searched the settings but have gotten nowhere in solving this problem. Can anyone advise on how to restore notifications when a new thread is created in a forum or subforum I'm following?

Just flew Mission 5 and the wingman always replied "unable" or "negative" when I asked him to attack ground targets. I gather I should try "cover me." My work around was to land and rearm/refuel then go attack again myself. BTW, I got a "mission complete" message when flying near Krymsk on RTB but not yet on the ground. After I landed and shut down the plane I did the usual ESC Quit sequence, which brought up mission score window as usual. But the "End Mission" button wouldn't work. Nothing happened when I pushed it. Pretty frustrating.

I'm wondering if fixing this will make it into the new versions you are rolling out with the new weather.

Just experienced this for the first time after completing a mission in Black Sea Resolve (F-5E DLC campaign). This was the first time I flew a campaign mission after upgrading to OB 2.7.

Just a guess, but I'll bet that Voice Attack is not installed in the usual location when you buy it through Steam. You might have to download the zip file version of VAICOM Pro and do a manual install. It's as simple as unzipping it to the correct directory and then importing a profile once you start VA.

Can anyone please explain to me which sounds are controlled by the World, In-cockpit, and Helmet audio sliders? The others are obvious. Thanks.

In my experience its better to get the DCS registry entries corrected and then turn off the custom path options in VAICOM config. The VAICOM options are needed only if your DCS registry entries are not pointing to the install locations for stable, OB, etc.

This is a common problem with various solutions in other threads. For me the one that works is to turn off the option in SRS where the radio selection button also serves as PTT. Then when you push a VAICOM button it will also select an SRS radio but will not transmit on SRS. You then assign a new button for SRS PTT. There are other solutions in the VAICOM manual that do not require a separate button, but I find them rather awkward in practice.