sobe

Capt Zeen Thanks, but how are your tutorials coming along on Helios 1.4?

Snowtiger I have both VA and VAC. Both work with win10. VAC is much simpler to learn and use, but is also less powerful. I created simple commands with VAC, mainly the comms menu F keys and it works fine. VA is a major step up in complexity but is far more powerful, especially when combined with Viacom. Since you already have VAC, I would suggest using it for the comms menu and maybe just a few other things. If you like using it, then make the jump to VA. VA has a free trial version to compare with VAC. VA is far more advanced than VAC, but at a cost of complexity.

"I had to use 'custom' as the DCS version and path to get it working (and as admin)" That was it. Thanks.

I cannot recall where the OB was first installed. It might have been to my old D drive. Now it is in F:/Eagle Dynamics/OpenBeta.

In preferences, the openbeta directory is correctly shown as in the F drive and the saved games folder is correctly shown as in the C drive. I am running this app from the F drive. No joy on the modify command.

majapahit Just tried to run it as administrator, but still the Modify did not show up.

Capt. Orso You don't have Options -> Kneeboard Profiles -> Modify? NO. I do not. That is what is so weird.

noony What do you mean by "for the offset of the screens of FA18". My profile is running fine after the update.

ANE Could you please upload this doc in word?

When I go to the options drop down and then go to kneeboard profiles, the only choice I am given is RESTORE DEFAULTS. I had previously made an F18 profile, but know I cannot get to it. Why? When the kb is in the task bar and I left click it, I get a drop down that includes PROFILES>f18>MY F18 profile.

Ramsay Thanks for the info. When you state: the lower right BE is to the target from the link-16 info Do you mean from BE to the target?

Just to be clear, the call on the upper left of the SA is from BE to TDC and the call on the last line of the lower right is from BE to ownship? What is the bug on the last one?

What is the call in the upper left portion of the SA screen and what is the purpose of the two BRA calls in the lower right of the SA screen? I believe that the second line in the lower right is from the cursor to ownship, but I am confused on the other two calls (upper left and lower right).

Very nice

dafiew Will you be doing one for the f-14?

My export file just to double check: local lfs=require('lfs'); dofile(lfs.writedir()..'Scripts\\Helios\\HeliosExport.lua') local dcsSr=require('lfs'); dofile(dcsSr.writedir()..[[scripts\DCS-SimpleRadioStandalone.lua]]) -- VAICOM PRO server-side script -- Export.lua (append) -- version 2.5.3 -- do not edit next line: -- xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx local vaicomlfs = require('lfs'); dofile(vaicomlfs.writedir()..[[scripts\VAICOMPRO\VAICOMPRO.export.lua]]) local Tacviewlfs=require('lfs');dofile(Tacviewlfs.writedir()..'Scripts/TacviewGameExport.lua')

Nagilem I have been using Helios and Capt Z's profiles for several years with the original Helios. When problems occurred, it was generally user error. When the F18 profile came out with the new Helios, I went with that and have no issues with either the 1.4 helios or the F18 profile. I have a system somewhat similar to yours so I am wondering why you had so much trouble. While your primary monitor is larger than mine, all else is about the same. One thing you might consider is changing how windows views your screens. In my case, while I have my primary monitor on top and my touch screen on the bottom, for windows purposes, they are treated as side by side with the touchscreen on the right. Another issue that I had is that windows numbering of the monitors does not appear to be the same as the internal numbering of the monitors based on what graphics ports are being used. However, since you got everything to work in 1.3, I have no understanding of why it is not working in 1.4. Keep us posted.

Does anyone have the Viewport coordinates for the F18 module for a 1920x1080 monitor?

Tiramisu I would like a guide.

Hollywood When I get the notice that the keyword database was updated, I do the update dance-click the orange Finish button, then Ctl A, delete, Ctl V in the "when I say" box in the AI Comm banner. My issue is that after I do the foregoing, and restart VA, the notice again appears and sometimes I have to go through this procedure several times before the Finish button does NOT go orange. I also notice that most times the number of commands do not change. So my question is-is this normal or user error?

TM WH Throttle panels I recently purchased the TM WH throttle panels from Debolestis and have found them very useful. The new panels are black and completely cover over the existing throttle panels so that the green lights do not show through. The new panel package consists of two sets of panels with each set consisting of a top panel that goes around the two throttles handles and a bottom panel for the bottom 3 switches and 1 button. The top panel was made so that it goes around the two throttle handles without the necessity of removing the handles. You could use the new panels in two different ways. First, you could use the new panels by putting them on top of the existing panels and then placing sticky labels next to each switch and button. Since you have 2 sets of panels, you could do this for two planes. Alternatively, you could do what I did. Place the new panels on top of the existing panels and then using the new panels, make a cardboard template of the panels for each plane that you fly and then place the cardboard template over both the original and new panels. You can then label each cardboard template separately for each plane. Everything fits nicely and no screws have to be removed. I used Blue Tac to place the new panels over the original panels and then used Blue Tac to put the cardboard template on top of the new panels.

Oakes Just wanted to let you know that I am still using your program and will use it a lot more when the F14 is released.

debolestis The throttle panels arrived today. They fit perfectly over the existing throttle panels without the need to remove the original A10 panels. A little blue tac holds them in place. After using them for awhile, I will send write a small review. Thanks Sobe

On page 22 of the latest manual, it states that SRS PTT mapping: maps the PTT TX slots according to the radio layout used by the SRS software. Could someone explain this a little clearer for my thick skull. For the F18 module, I have TX1 button 4 set to Comm 2 and TX 3 button 6 set to Comm 1. On my joystick, I have 2 buttons set for SRS 1 and 2.

Could someone post a simple HARM mission so I can look at the ME and perhaps understand how to use the triggers, trigger zones, etc in the ME.