sthompson

I'm mostly SP but still benefit from community contributions. Especially VAICOM for voice control of the AI. Also SRS when I do fly MP. And there are a few mods that make setting up my HOTAS the way I want to so much easier.

Try starting VA using the -showcommandnames flag. It's described in the manual. This should cause VoiceAttack to report to the log which commands it is executing, which might provide a clue as to what is triggering this.

I tried, and got this. No clues as to where I should sign in. I'm already signed in to Youtube.

I have had a similar experience except that I never import the F10 menu. So I do not think that is the cause, or at least not the only cause. There may be an underlying problem that can be activated in more than one way. The problem word is always "for," which makes me think this is a bug.

I have had the same issue for a long time. I assume it has something to do with the difference between homophones four and for but I've never tried to track it down. Doesn't really seem to matter for my usage.

A long time ago I posted a request for more flexible filtering. In particular, since skins represent a huge percentage of the user files it would be convenient to have a mechanism to filter them out while looking at all other files relevant for a particular module. Otherwise, looking to see what is new for a given module requires skipping over many, many new skins to see if there is anything else. Right now the only way to avoid skins in the results is to pick one of the other categories and go through them one at a time.

The announcement specifically says the reworked SU-25A will be "high" fidelity, not "full" fidelity. You must have missed the sentence "Based on the Flaming Cliffs series, aircraft operations will be tailored towards ease-of-use aiming to establish bindings and modes of operation." Therefore it will not have a clickable cockpit. Basically they are making two changes to the existing module (1) making it free and (2) upgrading the visual model.

Don't fly straight towards them. Fly an intercept course instead. You need to steer to where they are going, not to where they are. One way to do this is to try to keep their bearing constant. Make repeated Bogy Dope calls to the AWACS to get bearings to the bogeys. If the bearing is drifting right you need to change your course to the right. Or steer more to the left if the bearing is drifting left.

The comms menus are context dependent and so what you are requesting cannot be done without modifying the underlying comms code. As an example, the default comms menu will show the available ATCs in an order that depends on your position on the map (closest ATC's first, if I recall correctly). And so the function key sequence to call, Batumi, for example, will change while you are flying. VAICOM version 1 worked by having VoiceAttack manipulate the comms menu as you propose. But that couldn't work without a mod to replace the default comms menus with ones that were not context dependent. And that mod had to be frequently updated when DCS changed the underlying code, added new maps or modules, etc. I was involved in those efforts. In the end VAICOM PRO was developed that lets you bypass the menus altogether because it communicates with DCS via a plugin rather than by emulating key presses. Check it out. It used to cost a small amount but now is free. You might also look at Bailey's VoiceAttack profiles for VoiceAttack. I haven't experimented with those, but they might do what you are attempting to do via some other means. See

As I wrote previously, it would help to turn on VAICOM debugging, restart VoiceAttack, try one of the commands, and show us the VoiceAttack log of what happens when you try to execute one of these commands.

When you say these commands "are recognized" I assume you mean that they show up as recognized phrases by VoiceAttack, but that they trigger no actions. If that is the case, open the profile editor for your VAICOM PRO profile and open the options tab. There is a check box there labeled "Exclude Global Profiles." Make sure it isn't checked. If it is checked, that is the problem. If it isn't checked then there is another problem somewhere, and it would help to turn on debugging and show us the VoiceAttack log of what happens when you try to execute one of these commands. Also, I'm assuming that the commands are NOT in your VAICOM PRO profile since if they are then the version in the VAICOM PRO profile takes precedence over the global profile command.

As a sailor I'm going to start complaining about the sailboats that fly their spinnakers (a downwind type of sail) and do not heel over no matter the wind direction or strength! Totally immersion breaking for me. Or maybe I'll just focus on the amazing flight dynamics modeling. Thanks ED! BTW, I agree that things we paid for should get fixed when they break. The MiG-19 campaign for example. But I think there are probably higher priorities for this than sailboats and trains.

"No incentive" is too strong. There is some incentive, but perhaps not enough to justify an announcement. An announcement could push some buyers who have held off buying because they are undecided at the lower price, or are waiting to see how the module evolves, or just because they haven't gotten around to it, to make a purchase. Some of those buyers might not buy at all at the higher price. So an announcement of a planned price increase could increase overall sales revenue in theory. There is a tradeoff to consider. Lots of businesses pre-announce price increases as an inducement to buy now.

If all you want to change is the angle then just tilt your head up a little when you recenter the TrackIR view. Then when you look ahead normally you will be looking down.

As @baltic_dragon himself said, excuses should not interest us. I'm disappointed that promises made a long time ago but not fulfilled are now dismissed as irrelevant. I won't be spending any more money on his products.