sthompson

You might try "Mystery" instead of "Mission" since the former is listed in the manual's table of miscellaneous recipients and the latter is not. This seems to be an inconsistency in the documentation. Personally I haven't tried either one and am away from my DCS rig so can't test now.

You also need to use the PTT for the proper radio when using SELECT or when transmitting.

Thanks for putting this together. It was a blast, even though it felt a bit like a suicide mission for the MiGs today since we were small numbers. I'm really surprised to hear that we won! At least two of us blew ourselves up unintentionally by dropping bombs too low. Out of curiosity, how do you evaluate the score? Looking at a Tacview replay I can't see the targets so it's hard to tell who destroyed what or how many, except for the A2A kills.

Fang, the VoiceAttack administrator has closed your thread on their site because you have never answered the question as to whether VoiceAttack behaves incorrectly when you disable Voiceattack plugins, which is a completely separate thing from disabling the DCS hotplug feature. You were asked this multiple times but never gave an answer. If I were in your shoes I would completely uninstall DCS, Voiceattack, and VAICOM, then start reinstalling one thing at a time. No one can help you unless you can accurately and completely describe an installation procedure that produces a failure.

I've found that in some modules TX6 is disabled with the PTT rotary switch in VAICOM settings in the Normal position. This is true even if it is mapped properly to a button. TX6 is greyed out. Same goes for TX5. I do not understand why TX6 would ever be greyed out since it isn't supposed to correspond to a radio. You can re-enable it by changing the the rotary switch position to "multi."

That has not been my experience with the PTT switch set to Normal.

Note that the PATH advice in the FAQ is for STABLE. The registry key for Open Beta is different. On my system it is... Computer\HKEY_CURRENT_USER\Software\Eagle Dynamics\DCS World OpenBeta\Path I imagine things could go bad if you mixed these up. Could be different for Steam. I don't use that.

Thought I would make a practice mission with a large formation of B-17's carpet bombing Maykop as a warm up to the next event, so that I can practice shooting them from my MiG. But I find that only the lead bomber in each group of three drops its bombs. The other 8 bombers just fly in formation without doing anything. Can anyone point me to a mission with proper carpet bombing to help me understand what is going wrong? Alternatively, are there instructions somewhere? I've done everything according to the example in the manual.

I don't recall that. Perhaps you are referring to the instruction to roll back VAICOM if you want to roll back DCS OB to 2.5.5. That's in the manual (p. 4) ... "2.5.5 Open Beta is not supported: for this, revert back to plugin version 2.5.15."

Brings a new interpretation to "playing" DCS!

I hope we get some details about that here soon! :thumbup:

This is super news. Will look forward to seeing how it develops!

I don't understand. If a wounded bomber has aborted its attack without releasing its bombs why wouldn't that count? Seems like you are saying MiGs should not shoot down bombers who have aborted their attack.

Congratulations on getting post #5000. Can we please have a subforum? This thread is ridiculously long and unwieldy.

Yes. I have both installed in separate directory trees.

Is this for the Sabre only or will there be slots for the MiG-15bis?

I'm surprised to see this advice given so often since it seems totally unnecessary on my system. I suspect that those who need it do not have the correct registry keys set up for DCS and the issue may be related to how you installed DCS Open Beta. For example, on my system I have these registry keys for OB: [HKEY_CURRENT_USER\Software\Eagle Dynamics\DCS World OpenBeta] "Path"="D:\\Program Files\\Eagle Dynamics\\DCS World OpenBeta" "Version"="2.5" "Language"="EN" You might check to see if you have something similar and whether the path is correct. I imagine that these could have been corrupted or not installed properly if the installation folder has been moved or if you installed OpenBeta by converting another installation rather than doing a full fresh install from the website, which is what I did. I imagine there could also be an issue if you installed OpenBeta from one user ID and are now running VAICOM from another user ID, since these keys are tied to "current user" and are not system wide. Perhaps that could occur if you are running VA as administrator, for example. I have found that I do not need to run it as administrator, provided I set folder permissions to give my regular user ID full control permissions on the folder ...\VoiceAttack\Apps\VAICOMPRO I'm speculating of course since I don't experience the problem that others have reported that seems related to vAIcomPro not finding the OB installation.

Wikkus already reported P-51B. I'm getting it in the modules reported by Wikkus and also on D:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\SA342\bin\SA342.dll D:\Program Files\Eagle Dynamics\DCS World OpenBeta\_downloads\Mods\aircraft\C-101\bin\ABase.dll Some of the detections occurred first time I ran DCS OB after the last update. Others when I tried to repair. Is there any word from ESET? I'm still having this problem days after it was reported. And I can't find the reported virus in their threat database.

A post from developer Hollywood of VAICOM Pro today said to expect the next update to be coordinated with the SC release. So we may have voice recognition interaction with the SC from day one!

This! I bought it on sale not expecting much but have had a lot of fun with it. First off it is a difficult plane to learn because it is just terribly unstable on takeoffs and landings. Thus a real sense of accomplishment once you figure that out. Once in the air it is a joy to fly and very agile, if not fast. It comes with one of the very best ground attack instant action missions. It has the most complicated landing gear of any plane, but there are shortcuts programmed so you don't have to memorize the complicated sequences. It's a good plane for aerobatics (but does not like negative g's or sustained inverted flight).

Literally the very first sentence in this thread is about solo formation flying with a track recording! I think it's a great idea. It reminds me of "ghost" recordings in auto racing games where you can race against your previous best run on a track.

Hey Hollywood, glad to see you back in the forum and appreciate the update. We are rapidly approaching post 5000 for this thread. Is there any chance you will launch a subforum or other means of bug reporting / customer assistance / support? Following this thread is becoming increasingly burdensome as a means of finding information about problem solutions, and the number of times the same issue is raised anew seems to be increasing.

I've been flying the P-51 training missions and did most of the A2G missions in the included campaign successfully. I"m trying to move on to dogfighting and really struggling. Seems like I'm constantly stalling or experiencing uncontrolled rolls while maneuvering. The Mustang seems to not give much in the way of clues that I'm too close to the edge of control. Any tips would be appreciated as well as any tips about ACM in this bird. The only time I've gotten hits on a rival is in a furball where the AI are going at it and I manage to get behind someone who is trying to evade another pilot. Have not tried MP yet. Thought that could be a disaster since I can't seem to shoot down an "Average" opponent 1v1. My sense from watching videos is that people go into the merge at max RPMs and MP. I've been doing that. I've also tried using two notches of flaps when I get into a turning fight. And I've set a good bit of curves in my controls, which helped. But still struggling.:dunno:

Actually you don't know that because it isn't true. Yes you can still run the main build if you install the stable and OB versions separately. I do it all the time. You will however need enough space for two copies of the game if you do that.

Or VAICOM Pro, which is a paid plugin for Voice Attack that integrates it with DCS so you don't need to use the menus anymore at all. It already has checkboxes to enable functionality with the Super Carrier comms. They don't do anything yet, but the developer has been unusually silent, making me wonder if he's frantically working with ED for a simultaneous release. He was on top of Jester compatibility almost from day one when the F-14 came out.