Xilan2 Posted January 24, 2024 Posted January 24, 2024 Hi everyone, I have a problem with API calls attached to joysticks keys for “kneeboard.tab.nxt” and “kneeboard.tab.prv”. I have a plugin action via Other -> Advanced -> Execute an External Plugin Function, when I press a key or key combination for those commands. This keypress function has been working up to VAICOM PRO version 2.8. After this version the API calls have stopped working. Can someone confirm that this is a known bug in all versions after version 2.8. I trust that many people are using the Interactive Kneeboard functions and I would be very grateful if someone could check this out for me.
speed-of-heat Posted January 24, 2024 Posted January 24, 2024 No it is certainly working for me on 2.9.x... However do check that your joystick is still recognised in voiceattack, sometimes, unbinding and rebinding it can help 1 SYSTEM SPECS: Hardware AMD 9800X3D, 64Gb RAM, 4090 FE, Virpil T50CM3 Throttle, WinWIng Orion 2 & F-16EX + MFG Crosswinds V2, Varjo Aero SOFTWARE: Microsoft Windows 11, VoiceAttack & VAICOM PRO YOUTUBE CHANNEL: @speed-of-heat
Xilan2 Posted January 24, 2024 Author Posted January 24, 2024 Sorry, but disabled and enabled the joystick did not help. I been using VAICOM for more than 2 years now, and I really need the API calls for Interactive Kneeboard. Perhaps I should download the MSI file and start all over.
MAXsenna Posted February 11, 2024 Posted February 11, 2024 Sorry, but disabled and enabled the joystick did not help. I been using VAICOM for more than 2 years now, and I really need the API calls for Interactive Kneeboard. Perhaps I should download the MSI file and start all over.Can you copy those commands to an empty profile, export and post that profile here, so we can test/check? Like Speed I have no issues. Sent from my SM-A536B using Tapatalk
Xilan2 Posted February 28, 2024 Author Posted February 28, 2024 I forgot to say that this only applies to Openbeta. I am now back at version 2.8.0.0 which work just fine for both Stable and Openbeta. As you can see from the screenshot, this is my API calls. For all other versions above 2.8.0.0 the “VAICOM PRO Kneeboard” is not shown in DCS Openbeta. I trust that the next update with “Combined/Stable” will solve this problem.
MAXsenna Posted February 28, 2024 Posted February 28, 2024 I forgot to say that this only applies to Openbeta. I am now back at version 2.8.0.0 which work just fine for both Stable and Openbeta. As you can see from the screenshot, this is my API calls. For all other versions above 2.8.0.0 the “VAICOM PRO Kneeboard” is not shown in DCS Openbeta. I trust that the next update with “Combined/Stable” will solve this problem.Which module is this? If it doesn't work for you, while it works for us, I see no reason that the issue will fix itself even with another DCS update.Sent from my SM-A536B using Tapatalk
Xilan2 Posted March 2, 2024 Author Posted March 2, 2024 I did the test in F18-C and in VR. I followed your advice and decided to try to fix the problem now. After a lot of work with different settings, I happened to uncheck the “Use custom DCS path” in Config settings and all of a sudden, everything started to work again!!! I have one strange comment though in VAICOMPRO Log file: "Problems were reported during kneeboard initialization Cannot create a file when that file already exists.". I have no clue which file is being referred to, and the VAICOM kneeboard is in fact now working? Anyhow, thank you for your advice. Finally got to start flying, not just troubleshooting.VAICOMPRO.log Cheers 1
MAXsenna Posted March 2, 2024 Posted March 2, 2024 I did the test in F18-C and in VR. I followed your advice and decided to try to fix the problem now. After a lot of work with different settings, I happened to uncheck the “Use custom DCS path” in Config settings and all of a sudden, everything started to work again!!! I have one strange comment though in VAICOMPRO Log file: "Problems were reported during kneeboard initialization Cannot create a file when that file already exists.". I have no clue which file is being referred to, and the VAICOM kneeboard is in fact now working? Anyhow, thank you for your advice. Finally got to start flying, not just troubleshooting.VAICOMPRO.log Cheers Aha! Then you probably had a mismatch in the path, but correct path in the registry, would be my guess. I wouldn't worry about the error if it works, but if you want to get rid if it, you can probably shutdown VA and DCS. Perform a full repair of DCS, then start VA before you start of DCS. The file might have the incorrect permissions/attributes, so VAICOM is not able to remove it when shut down. Who knows. Cheers! Sent from my SM-A536B using Tapatalk
Recommended Posts