markcam4

Hi all , I am new to the target script editor, but have got a working .tmc file working , thanks to all contributors on here and their invaluable information. This leads me to some questions! I have created some throttle axis custom curves. Now, is this the correct place to make use of this functionality or shall I remove them from the script, but then add them in the DCs combined throttle axis mappings under controller settings? What would happen if they are declared in both places? The advantage of removing the custom curve entry from the script is that I can create different curves for different aircraft by editing within DCS, unless of course someone could suggest a way of programmatically selecting a particular curve within the script when a particular aircraft is flown within DCS? Any thoughts welcome, kind regards Mark

This is a headsup on my recent trials and tribualations of installing the "new" @Draken35 script with included keyboard layout extensions. I read all pages in this forum thread to completely understand the installation process- i had a previous installation of scratchpad mod from a while ago, and thought the additional and fabulous option to have a VR keyboard and option to insert waypoints direct into aircraft was well worth this effort. Well, 2 days later, I finally got it working- but a gotcha , that for me caught me out. Initially, no matter what I seemed to do, I could only get the scratchpad without any keyboard layout, no matter what I did! All files were in the correct saved games folder and not under the dcs installataion folder as previous comments indicated could be a problem. I then resorted to installing microsoft sysinternalls package to capture what was going on- and this helped! see screenshot image- Im my \scripts\hooks folder- I had re-named older scratchpad-hook.lua files , thinking they would not be actioned in anyway- how wrong was I- so I got rid of these files- just leaving the scratchpad-hook.lua and that was the issue resolved! Maybe this will help those that have had a similar experience. Thanks all who helped contribute to this great little add-on!

Older version of the open composite also fixed for me. Thanks for the help in tracking down,

Hi @TimSell75, I will have a look on discord and see if that helps- will keep you updated, thanks for the pointer, mark

Hi all, thanks for all the postings and keeping the community informed. Unfortunately, I still have issues with the kneeboard! It doesnt populate with any mission details at all. Also, I cannot manually call the ingame comms menus up (either RAlt \ or RCtrl \) when running 2.8 and the new downloaded VAICOM Pro. Or even communicate using VIACOM to say a tanker or airfield or carrier. I have also noticed that easy comms ON in the VAICOM Pro PTT display, when in fact I have EASY COMMS OFF ingame.- they seem to get out of sink. Has anyone else overcome these issues? kind regards mark

I really hope so @Tshark as A lot of us rely on Vaicom ,so will be hard not to have this installed! Fingers crossed @TimSell75!!

Hi all, Did this issue ever get resolved? I have version VA 1.10.3.20 pre-release, and get this problem! I can't confirm, but am wondering if this started when i reconfigured VAICOM pro to have MP tab-VOIP control to Tx Link , and MP only checked? plus some VA hotkey long press thresholds set from 700 to 100 , so that a double quick TX press doesnt get transmitted to other players in MP mode,and a long Tx press does get transmitted to MP players- the idea being that VA command are not heard by other players in game. Thanks mark

Had a recent HP reverb G2 error- where all of a sudden, the headset was complaining that the USB port was not version 3.0 !! A new V2 cable (free replacement if in warranty) fixed this issue.