Exposed Variables not working as intended - What am I missing ?

[BlackSharkAce]

Hi ,

I just updated to DCS OB to v2.7.7.15038, VAICOMPRO v2.5.26.0 and VA v1.8.9 and it looks like not all "exposed variables" work anymore.

Flying around in Caucasus in the FA-18C (free flight solo mission) I can get {TXT:vaicompro.serverdata.currentserver.theater} to work (returns Caucasus as expected) but both {TXT:vaicompro.playerdata.currentmodule.cat} and {TXT:vaicompro.playerdata.currentmodule.name} return "Not set".

In the attached picture we can see the module is detected and display in the VAICOMPRO configuration window, SRS also recognizes the module and switches to the correct profile.

It's a bummer because I use different button presses for my radios depending on the plane I'm flying.

Any clues ?

 

So far I tried the following:

-Running VA, VAICOMPRO, SRS, DCS as admin

-Repairing SRS & VAICOMPRO

-Searching for "vaicompro.playerdata.currentmodule" in the forums

-Verifying the command didn't change in the VAICOMPRO manual

 

Cheers,

Here is the VoiceAttack configuration. I expect it to output the currentmodule name and category along with the theater, but I only the theater seems to be working.

Here is the relevant page in the user manual.

Edited November 13, 2021 by BlackSharkAce

[Hollywood_315]

Can you try again with build 2.5.26.1 from the website thanks

Edited November 13, 2021 by Hollywood_315

[BlackSharkAce]

2.5.61.1 fixes the issue.

Thank you for your prompt support !

[Shiroka]

On 11/13/2021 at 2:15 PM, Hollywood_315 said:

Can you try again with build 2.5.26.1 from the website thanks

 

Thanks - I had this problem and it fixed it for me also. Just as an FYI for some reason it didn't work when I used the .msi installer file (I still had the same problem and it kept telling me that an update was available), only worked when I used the manual .dll installation.

[BlackSharkAce]

Thanks - I had this problem and it fixed it for me also. Just as an FYI for some reason it didn't work when I used the .msi installer file (I still had the same problem and it kept telling me that an update was available), only worked when I used the manual .dll installation.

Yes, the .msk kept on doing a « repair » without actually updating the version.

[Lt_Jaeger]

2 hours ago, Shiroka said:

Thanks - I had this problem and it fixed it for me also. Just as an FYI for some reason it didn't work when I used the .msi installer file (I still had the same problem and it kept telling me that an update was available), only worked when I used the manual .dll installation.

Could you elaborate a little how you did it?  I'm also getting the constant update notification

[BlackSharkAce]

Could you elaborate a little how you did it?  I'm also getting the constant update notification

Use the download link for manual installation, it’s on the same webpage as the installer. This will give you an archive containing the .dll file and documentation you need to update.

[AdrianL]

@Hollywood_315I do not believe the msi download has been updated to 5.2.26.1.

When I install from the msi VAICOMPRO.dll is 5.2.26.0. When I download the zip file (manual install) then VAICOMPRO.dll is 5.2.26.1.