TAW_Impalor

I meant VSPX Processing = ON in Vaicom preferences + Unrecognized Speech Delay = 700 in Voice Attack - Options -Recognition tab. This helps me say things in one go.

Try switching the recognition engine from Windows to internal one (see manual). It fixed for me similar issue with wingman (awaiting further info loop).

@Hollywood_315 Hello and thanks for your work! Some questions. ATC 'Suppress auto' does suppress auto replies by the pilot, but then DCS gives no time to say anything manually nor awaits that reply. For example, I say 'marking mom's', get bunch of numbers from Marshall, and immediately hear 'readback correct'. Same with 'switch approach' and other messages - ATC does not care if I reply or not. So turning this option on reduces realism, not increases it. Another problem for me, adding "state X.X" or "angels X" to a keyword prevents it from being recognized. Same with Side Number, i.e. '313 established angels 6' does nothing. I learned to make '313' (my squad MODEX) an alias to Marshall, and now '313 established', '313 commencing', '313 hornet ball' etc work fine. But I am still to find a way how to get 'angels X' and 'state X.X' parts of the message ignored. I can't make them an alias to anything, because the numbers always change... Third issue, Disable Player Voice in multiplayer works wrong. It mutes my voice for me (correct) but also mutes for me all F-menu-generated voices of other players. I cannot hear what they do anymore, unless everyone like myself talks to SRS and Vaicom Pro with one PTT. And if they do not use Vaicom or did not Disable Player Voice on their side, they will still hear me speaking twice - via SRS and with robot voice. Ideally, this setting should disable my robot voice for me and for all users on the server, but what I can hear should be controlled on the side of each player. I hope this makes sense. Any ideas?

Left DDI has space reserved for info lines, like HOME FUEL etc. Not good for HSI or SA

A few times already I received an LSO grade out of context. I.e. flying 100 miles away from carrier and interacting with JTAC (and before any approaches or traps). The mission was very long, but next time it happens quickly I'll attach it. Edit: ah, maybe I sent my AI wingman home with bingo fuel. Why do I care to see his grades?

Dear Hollywood, I long tried to understand how to create new aliases. The manual says 'Use the Keyword editor to change the phrase into something that is better recognized by the engine (PRO license feature)' with no further details. Say, I want 'in the break' to be an alias to 'Kiss off'. I choose 'Kiss off', press 'Add new', it creates 'Kiss off1'. Now what? I can't rename it into 'In the break'...

Thanks. I missed 'stable-open beta' slider in right bottom corner. Somehow it did not matter just yesterday...

ATC plugin and/or update broke my OB! Loading always stops at 10%. Must repair and delete Viacom scripts, then it loads. Disabling ATC extension in the settings is not possible, to test if it is the cause ((

Any ETA on the SC licence? The carrier keywords in place suggest that the code is already there and just awaits activation??

Bare bones Voice Attack is pretty bad at voice recognition and scripting flexibility. I spent all day today trying to make Bailey's scrips dial a manual frequency, read the manuals etc, but then gave up. Windows engine just cannot tell '12' from 'one to'. VAICOM Pro adds some dll's that do some heavy lifting under the hood, it has a section to dial radios, but it also does not work for F18 for some reason. Their scrips are a blackbox, cannot debug them. They promise to sell an extension for Supercarrier ($3.50), but who knows how good it will be. I still bough the Pro license in anticipation of the carrier, just to call the ball ))

Yes, Alt + Enter prevents this problem. Is there no technical possibility to launch DCS in full screen by default? With no monitor and visible keyboard in VR it is hard for me to remember doing that.

OK, maybe it's just me, so the post is in wish list and not in bugs. My PC screen is 1920x1080 and I like my taskbar to auto hide at the bottom. Some events, like Oculus notifications, cause the taskbar to sometimes unhide when I'm in VR. This makes the low placed buttons of DCS interface unclickable - like Exit/New Sever/Join buttons and the Briefing button in MP. When I try to click them DCS loses focus and they grey-out. 'Cursor confined to game window' is ON, but cannot prevent it, as the taskbar becomes on top of the game window! Well, actually there remains a narrow margin at the top of the buttons maybe one pixel wide that I can still click, but this is still very annoying. And I usually don't even turn my monitor/TV on to see the taskbar and make it hide again. Been like this since I remember myself, both in Windows 7 and 10. I don't really understand why having mouse cursor at the center of my view in VR causes it to click the taskbar, but it does. Must me some quick hack how you operate the menus from VR. So, my suggestion is, since DCS cannot seem to stay on top of the taskbar, move those UI buttons a few pixels higher and make the lower part of the UI always static.

I am stuck at this mission too. I don't know why the chopper feels so unstable in it. I can't hover steady and lock any targets - Schkval just keeps drifting away. I have no problem in other missions. Is it lighting issue?

Set Pixel Density = 2 in DSC Settings' VR tab

Hi LeCuvier, good catch! Must be a new thing in OB compared to Stable. This is still a bug in that DCS does not warn us when the binding is already taken!

LSHF-V cannot be set to anything in OB F18...

Hi! Anyone looked into this?

The mouse cursor is not recorded in the track, but I still attached it with my log. I pushed the button with a mouse click in the end. Curiously, assigning another button (J) to this control triggers it, but what I have (LSHF-V) does not. The button is held, not pressed (see screen 2). I have this mapping in all my other modules, and it works fine with F-18 in DCS Stable, so I am not keen to re-program in TARGET. This is not a VR-only bug... sj.trk dcs.log.rar

I was thinking about it, but how in the track I can show that I do actually press the bound button??

Yes, I started this campaign in Stable, and most of the time was taking off in the dark. But the sun was up soonish. Ok, good to know, and thanks for the campaign!

And how come in OB this is a day mission, while in Stable I launch in the dark? My OB is in English, while Stable in Russian language, if it matters...

I updated my mission files, now I can't take off (at least not in Alfa Strike Mozdok).

I have this bug in OB only. In the Stable it works fine. The binding is highlighted in the settings ok, but in the cockpit I must push the button with mouse.

I fly both Stable and OB in VR. DDI Day setting in OB is really bright now, hard to see clearly. So I switch to Night during the day, and only switch to Day when the sun is directly behind me. Very tiresome in a fight! I much prefer Stable version for now, both for FPS and bugs like this.

Love the campaign, except my wingman drives me nuts! He just flies around not doing anything. He ignores my commands to attack targets, cover me, etc. So I run out of ammo, and he has all his missiles intact AND fuel tanks still attached. Arrr!!!! Who wants to fly this campaign together (I can set up a server)?