Greyman

When you open powershell, just type "cmd" and you are in the cmd shell.

Maybe check your bindings, for a controller switch that is set in a particular direction, selecting AA, as that would prevent you moving it away from that setting.

This happened when 2.5.6 came out, with quite a few AV programs, and appears to be connected to the changes that ED have made to the access control for a number of modules. You should probably report them as potential false positives to your AV program developer and possibly add the flagged files to the exclusion list, but only if you totally trust that they are false positives. If it's any help, I have McAfee, which was flagging a couple of files, which i did report, but then added them to the exclusions list, pending McAfee sorting out the issue. Suffice it to say, my exclusion list is now empty again.

at around 3:15, for evidence that pilots do "walk the throttles". He doesn't say it explicitly, but you should see from the movement of his hand that he isn't going to be moving both levers together on approach.

Yes. Maybe fire up a free flight mission, get to below 250kts and deploy gear and flaps. With throttles at idle, wait for speed to drop to say 150kts, using airbrakes if necessary, and then add some gas, at the same time as trimming the nose up to get the flight vector indicator aligned with the centre of the "E" bracket. You should then just need to adjust your throttle(s) to find a speed that keeps you on the level and with the desired AoA. Retract aibrakes btw, That speed will depend upon your aircraft's weight, but you'll find it quick enough.

I vaguely remember @Lex Talionis, a RL pilot who does some excellent videos, stating that the delay seemed a little too long, compared to the real Hornet, from his first impressions, but not sure of whether his view has changed or whether there is a bug or not.

Like I said, in my post, some people will be able to cope with one axis, better than i can with 2 and you are apparently proof of that. As for using the throttle levers individually, RL pilots use that technique for landing, and AAR, so i guess you are just special.

I wouldn't expect to see a space in "@openbeta". Maybe try it again, without the space.

You can add aliases for any of the commands, so there are no real limits. I might just add an alias or two to the engage command. "kick the c**p out of", "Rip a new one for", "make friends with", "destroy", "exterminate" being perhaps less-than-creative possibilities. :)

With just one throttle axis, you will probably be forced to make twice as many adjustments, each of which will make twice the difference to the total thrust than you perhaps need. It's not impossible and I am sure that there will be some super-skilled sim-pilot that can do a far better job with one axis than i can do with two, but 2 axes should certainly make it easier. As for the lights, for after-dark case IIIs, i just try and bisect the island and the "ball", which are lit up. Suffice it to say I don't always succeed and, perhaps thankfully, i only play in SP. :)

By coincidence, I've just done a perhaps less than perfect Case III recovery, but largely managed to keep it on the glide slope for the whole approach, by "walking the throttles". That is, making regular and minor adjustments, in turn, to each of the two throttle levers, anticipating and countering the rises and falls, before they happen. I can't say for sure that the length of the delay, between moving the levers and seeing the desired outcome, is entirely accurate, but it does feel good when you get it right. :)

The issue appears to be more about the DCS AI, as you would get the same behaviour if you used the comms menus rather than Vaicom Pro. It may be that ED will look at improving the AI or making the radio comms more specific to a particular target. For example, "engage AAA at Waypoint 2". As it is, the current AI does add to the "fog of war". :)

If you omit the direction, which is only optional, the AI pilot(s) will probably take the most direct route. I say "probably", as DCS AI understanding/behaviour can apparently be unreliable at times. :)

Please tell me you don't fly airliners in RL :)

Deleting export.lua and restarting voice attack and dcs will solve that problem.

Good job @GunSlingerAUS Just get into the habit, following every DCS update, of deleting the export.lua file and most, if not all, VP issues will be avoided.

For 71.000 the band selection option doesn't exist, so there is definitely something different about how the Hornet handles it. Could it be that it is incorrectly defaulting to FM, instead of AM, when the frequency is entered via the keypad, but VP is somehow able to explicitly set the band, when it sets the frequency behind the scenes?

When tuning the hornet radios in Manual, i am fairly sure that you need to press the ENT key, after entering the frequency, so make sure you're doing that.

The only way i could replicate what you are experiencing was by having both of my toe brakes mapped to 'Wheel Brake' (the command for both wheels) and having the axis on one toe brake inverted and one un-inverted. To check this is not the case, maybe set taxi power and fully depress one of your toe-brakes. If the aircraft doesn't move, then try releasing it and fully depressing the other one. Of course, if you have each toe brake allocated to one of the left and right commands already, then this theory falls over. Unless you have the 'Wheel Brake' command also mapped of course.

Have you assigned left wheel brake and right wheel brake to their respective toe brakes on your rudder pedals and cleared any wheel brake mapping or have you mapped wheel brake to both of your pedal toe brakes? Either way, you may need to invert the axis on both toe pedals, as just one axis being in the wrong direction will resist you rolling. The latter option will make inverting both axes more complicated, if not impossible.

If you have something like the Logitech G keys on your keyboard or even the ability to record a keyboard macro against a controller button, then maybe assign a key combination(s) to one or more of those. You would probably need to make sure that you start from a known state, maybe with F12 being the first keypress, but then it should just be a matter of inserting the keypresses that would open the comms menu for the right radio and then navigate to and execute your desired command.

Isn't the tune frequency command set part of AIRIO and therefore only for the F14B?

it's well worth upgrading @Razor18

The server has been having some issues today and that might have caused what you are experiencing. It looks like the authentication process might have not logged you in properly and therefore cannot find your licences. Maybe try again and/or try logging in to your account on the ED website and check out the store. Your modules should still be marked as purchased, but either way, I'm sure that ED will restore them if they have gone missing. Good luck and stay safe

It works fine with VAICOM Pro, as long as you have deleted the export.lua file, in ../Saved Games/<DCS Folder>/Scripts and restarted DCS & Voice Attack, after every time you have updated DCS.