Kula66

Is this the annoying regular thumping noise discussed before?

Thanks, but using TX4, it seems to get it right most of the time! But perhaps not this one!

Interesting. Thanks I’ll give that a go. I guess it could work sometimes depending on whether I have my radio tuned to overlord at the time.

I guess so, but I haven't used much else; just things like, 'request taxi', 'rearming', 'tomcat ball', tanker calls, tune radios, TACAN ... they all work ok. I can get to 2 pages in the kneeboard, but not the rest - so I think its working to a degree. However, 'Jester options' and 'Link Host Overlord' are important - flying in a match and being the only one without AWACS is not good

I'm getting a bleep after the commands 'suggesting' (I really have no idea, but seems reasonable) that they are decoded correctly, then get lost somewhere.

I'm a beginner, so worth checking the basics. I'm using TX4 because it appears the easiest, and other commands are generally working ok, so I think TX4 is working as intended, ie. its switching between commands to Jester and AWACS correctly (apart from the 'Link Host Overlord' command). Its doing VP sudo-calls correctly, eg. 'Link host' (displays the options) and some full radio calls, like 'Bogey dope', 'request rearming', etc ... just not actioning the 'Link Host Overlord', despite decoding it ok and me repeating the call again and again. Oh, 'Jester options' wasn't working either, so its not just this command. Grrrrrrrrrrrrrrrr.

See log in my previous post ... '8:40:41.955 Have result, identified as command: Link Host Overlord'

Thanks, but I think its recognizing the phrases ok (see log), for some reason, its just not executing the commands.

More 'funnies' in a game last night: 'Overlord, bogey dope' worked 100%, 'link host' worked 100%, 'link mode tactical' worked 100%, but 'link host overlord' ... 0% Despite dozens of attempts in my best BBC English, even after a reboot. This is sooo nearly working! UPDATE: Had a similar thing in SP testing this morning, switch Host to 'Truman', then try switching back to 'Overlord'; these are the messages in the VA log: 8:40:42.446 Listening suspended 8:40:42.402 Joystick : 'Transmit TX4 release' 8:40:41.956 Done. 8:40:41.956 Constructing message... 8:40:41.955 TX4 | SEL/AUTO: [ Overlord ] , [ DL Host Overlord ] 8:40:41.955 Have result, identified as command: Link Host Overlord 8:40:41.954 Have result, identified as recipient: Overlord 8:40:41.953 Captured sentence: link host overlord But all I get is a click and no confirmation from Jester.

Just checked, and it is/was enabled.

During a couple of games last night, I could not get the 'Jester options' to appear in MP ... just get the static noise. Other voice commands were working. Worked ok earlier in the day in stand alone. The game was running a 'SATAL' standard mission. I even tried a reboot, but it didn't fix it. Is there an issue with the Jester option in MP? This was required for setting the navigation 'Fixed point' to Bullseye. Thanks.

From my minimal testing so far, the biggest missing one is setting the fixed point to bullseye. Everything else is just a question of getting used to the commands.

Ok, thanks all. So its the Jester wheel we all know and 'love' or VP. Very different from Baileys VA profile in syntax, but hopefully it will get easier with use - just have to give it a fair trial. Not sure how it was solved myself! Lots of clicking various options, and shouting at VA, DCS restarts, VA restarts ... and it started working. Not the easiest process.

Hi, purchased Viacom yesterday, so a very new user. I use VR and OB, and fly the 14. I'm having trouble getting the options menus to show; I say something like 'scan range', and I can see that VA has decoded the command ok, and displays a message about command built, but nothing shows on screen. Any ideas? I've tried switching various options on/off in VP, but nothing seems to help. A possible cause is my '\' key has some OEM scan code, which has caused issues in the past - could this be affecting it? UPDATE: Rebooted and it started working Thanks, James PS> Why does Viacom disbable the standard Jester menu system? I've got 'Jester options' working, but the cockpit disappears which is horrible!

In my experience, prior to 2.7, the Ace level AI used to notch immediately, the others didn't ... now at least Veteran do it too.

In overview, map RWS and TWS mapped to HOTAS buttons. Close in RWS to 20-40 miles and get a target on your nose and roughly co-altitude. Switch to TWS and allow the WCS to assign a target priority number, and Jester to do an IFF. Fire note the countdown to impact. Keep the target within the TWS scan cone until the countdown starts flashing. Simple. Works in PvP fine. Against the AI, since 2.7, the AI starts notching and chaffing as soon as you launch ... this causes the WCS to lose track and the missile goes stupid.

Same issue ... try cranking up the gamma as a temporary work around

Ok ... many thanks all same

Thanks Victory205, and how would that compared to a 14B in the subsonic realm?

I have a switch on my HOTAS to switch TWS/RWS ... search in RWS, get the bandits centered in the screen at roughly co-alt, then switch to TWS. The WCS should assign them priority numbers automatically, Jester should IFF them automatically - now shoot and keep the bandit in the TWS scan cone ... crank up to about 50 degress to reduce closure. Works in SP and MP No need to hop into the back. Jester is pretty good within his limitations.

I’ve noticed this too ... in a hard turning shot you have to lead the target despite a radar solution.

not sure of the original sources, but interesting summary: https://www.globalsecurity.org/military/systems/munitions/aim-54-variants.htm

I appreciate we all have different priorities, but I really don't understand why such a major issue hasn't been addressed in months ... but, hey, I do have a piece of string to watch

They do repair eventually in game, but you have to taxi to the hanger and sit there in the cockpit for 18 hours as punishment ... all realistic apparently.

I've tried voice and it work well, most of the time ... but always seemed to let me down, when I needed it most. Pogo ... thanks, not something I've tried beyond adding flares.