lxsapper

Those hanging at 10% are you Vaicom users? If so, that's your issue, check the Vaicom tread.

First impressions - the new lightning looks really promising, really amazing in some instances, but inconsistent and downright wrong in other regards. For example you can be flying in a very clear full moon night, then a few minutes before sunrise the night will be become pitch dark, and the transition looks wierd as hell. Then the sun comes up looks spectacular but the darkness is not a bit consistent with what you were seeing 10 minutes before. Other lights including cockpit lights need some tweaking. Some AI units seem bugged to hell at least on some missions.

Ship wakes also looking a very unpleasant white when camera is down low. For example looking at another ship in the group when sitting on the carrier deck.

@Hollywood_315, I think there's a bug with Vaicom. Selecting manual DCS file managing does not stop vaicom from installing the files every time Voice attack is initiated.

F-16s purchased by Portugal included Blk15 and blk20 aircraft. Of the ones not retired all of that have received the MLU update bringing them to block50 Standart. Close enough for me.

Repair DCS, don't run VoiceAttack until we hear from Hollywood about a fix...

Thats affirmative Grimes! That's what I get on that box.

Even in the Encyclopedia it's not visible.

It's not visible even in the enciclopedia.

I think the file that actually stops DCS from loading is ...\Scripts\UI\gameMessages.lua

I made a very quick try of VRFX seemed fine, but I went back to using windows speach recognition because that is working fine for me.

Are you a Vaicom user? This should be related to some .luas related to Vaicom not beeing set properly. But Vaicom appears to be broken for this update.

@Hollywood_315 DCS open Beta Update seems to have broken something. It won't launch with the required Lua code to run Vaicom. EDIT: Did some experimenting here is what I did and my results. 1-Stoped Vaicom from managing DCS side files (manual managing). 2- Followed manual intructions on manual install. 3- speech.lua and common lua have a new path, they are no longer under \sounds but under scripts\speech\ -placed them in the new location 4- ignored gameMessages.lua as the file now seems to be more complex than the one given by Vaicom. Results: Can load the game, Vaicom recognizes commands, but only AIRIO commmands seem to be working. Other commands don't seem to be sent to DCS.

Stuck at 10% loading for me. Edit: Resolved after running repair. Still odd that a successful update would land me here...

Hi, not sure if I can help you much. I don't know what recognition engine Cortana uses. But my experience with Voice attack has been that single words are bad for commands. If you are trying to get "power" recognized on it's own, as you have found, might be troublesome. But for me personally after training with Vaicom training mode, I can say I get excellent recognition of commands. For example "Ground power on" get recognized every time. I found that most troubles that arise for me, are from me misspeaking of not understanding/forgetting the command structure on some of the more complex commands like radio tuning etc.

I'm not entirely sure of what you are describing or what you are trying to accomplish. But if you want to create a new command you must do it in the profile. The keyword editor is for adding/altering aliases to Vaicom commands.

Also sounds like you are trying to activate your control stick functions with your mouse. you can't really do that. You have to bind them to your joystick buttons or use keyboard binds.

I too would like to see my country in DCS. And even though we now have two aircraft, one that has been flown in Portugal and the other is a type in service, should not be an issue. There are lots of nations in DCS that for a very long time didn't have a plane flown by them in DCS. Probably there still are a few.

Apologies my mistake .

I believe only Hollywood can tell why he included the command. Like I said it's a pilot function, you have keybinds for it, or you can assign them to your HOTAS, even though in the jet that switch is on the left side wall not on the HOTAS.

@Hollywood_315 I Confirm, it's a AIRIO bug. It works well on Jester Wheel. Do you Mean VSL Hi and Lo? If so IDK why Hollywood included the commands in AIRIO because this are Pilot controlled modes, Jester can't control this modes, or maybe Hollywood decided to give that functionality through Vaicom anyway. But indeed it does not appear to be working. In any case I don't get a response from Jester, just the text acknowledging that the Command was received in DCS. Other than that appears to have no function.

They are definitely selling them but even TM is out of stock right now. They appear to have Joystick and throttle separate in stock, but that option costs a bit more. And this page is for Europe, IDK the equivalent US page. https://shop.thrustmaster.com/en_gb/

Target allows it. For a saitek device I believe you have to use something like Joystick Gremlin, but if you want an opinion that's a really bad way of flying. The problem with the F-18 isn't "sensitivity" it's spool time. And the way you are describing it, you actually want it less sensitive, not more. You want increased resolution in a limited range also known as axis zoom.

Unfortunately this command is not yet available for jester AI, it's a base vaicom command. It's available for all radios but to use you must TX the radio you want to change channels on.

Thanks for this Drakoz. And as a sidenote I didn't say swavplayer couldn't play files in a diferent directory. I didn't know how to do it with Target, because putting the path down was giving me syntax error. Thank you for solving it!