sobe

Two things. First I am using the open beta version only. Second, I had a typo in my question above and here it is corrected: No matter how I set the KB profile, the KB keeps showing up on the bottom right of my second screen INSTEAD OF the top left of my first screen per the setup in KB. Any thoughts. My guess is that sthompson (above) might be right.

In some missions, I seem to have an uncontrolled roll that I cannot stop with my Hotas buttons. Is any one else having this issue?

No matter how I set the KB profile, the KB keeps showing up on the bottom right of my second screen and the top left of my first screen per the setup in KB. Any thoughts?

Found the button. Thanks, but I still wish the HUD was darker.

No matter how many times I press the HUD brightness button, the HUD is still too light for me. Is there a mod that darkens the HUD like some other planes? The answer may be in Mods>aircraft>AJS37>Cockpit>scripts>HeadUpDisplay>Indicator>indication_page.lua local BASE_COLOR = {118, 230, 255, 150} -- green {255,255,255,255} -- white local BASE_COLOR = {118, 240, 145, 215} local TEST_COLOR = {118, 240, 145, 15} local TEST_COLOR_2 = {255,0,0,255} But I am not skilled enough to figure this out. Any thoughts?

wereferret: See

In the Easy-East Georgia spring instant action mission I cannot seem to get the wingman to do anything. I have tried the various engage commands, including making the trucks a SPI and telling him to attack my targets. Is it me or the game?

I dragged over the HMCS found in the latest Helios for the A10c Tank Killer into a blank space at the bottom of Panel B Right. I then coded the toggle switch for its 3 positions in both input and output. However, in game nothing happens when I move the toggle switch. It appears that my lack of understanding Helios is showing. Attached are pics of the input and output coding. What am I doing wrong?

When I use the HUD only view, the Left MFD shows up and I cannot get rid of it or make it smaller. Is there any way to do that?

Will test it soon.

I have found the Tacan Beacon (Man portable) TTS 3030 in the ME. However, I cannot figure out how to operate it or set up the Tacan frequency. Can some one please describe how you operate this Beacon? Does it need scripting?

I have also had issues with using both Viacom pro/Jester and Bailey's F14 programs and after much experimenting, I just go with Bailey's F14 profile without Viacom. With the update yesterday perhaps now that Bailey has Viacom, he can re-look at the two programs and see if they can work together. If not, hopefully Bailey will just update his F14 profile.

Has anyone using this profile also tried to use the Lantirn mod that puts the lantirn in the pilot cockpit? I am concerned about the viewport for the lantirn. Do I have to use my own viewports and not the ones in Helios 1.6?

When I try to set the Lat/Long for the destination or present position, I have to hold down the mouse button and then use the mouse wheel to change the numbers. Is that correct? If so, this is not easy to do. I have tried to use key commands with a button box, but that does not seem to move the dials. Any thoughts?

I cannot seem to save pages that I have pinned in the kneeboard for a particular plane. Is there a method to do so?

I have used this program for several years. Today, when I tried to load it, I got an error message below. The full path of my saved games folder is "C:\users\name\saved games\DCS.openbeta" so I am a little confused on what to do as the app automatically uses "C:\user\name\saved games". I AM RUNNING THE LATEST VERSION OF OPENBETA AND THIS APP. --------------------------- There was an error! --------------------------- Use Ctrl + C to copy this error and e-mail it to s13solutions@gmail.com : System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Users\13057\Saved Games\Mods\aircraft'. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileSystemEnumerableIterator`1.CommonInit() at System.IO.FileSystemEnumerableIterator`1..ctor(String path, String originalUserPath, String searchPattern, SearchOption searchOption, SearchResultHandler`1 resultHandler, Boolean checkHost) at System.IO.DirectoryInfo.EnumerateFiles(String searchPattern, SearchOption searchOption) at KneeboardBuilder.Viewmodels.MainViewModel.FindLuaFile(String _pathToSearch, String _fileNameToFind, String _aircraftName, String _optParam) at KneeboardBuilder.Viewmodels.MainViewModel.GetDeviceInitPath(String _dcsPath, String _dcsSavedGamePath, String _aircraftName) at KneeboardBuilder.Viewmodels.MainViewModel.SetupKneeboard(String _dcsPath, String _dcsSavedGamesPath, String aircraftname, ProfileModel _selectedProfile) at KneeboardBuilder.Viewmodels.MainViewModel.UpdateDefaultKneeboards() at KneeboardBuilder.Viewmodels.MainViewModel..ctor() at KneeboardBuilder.Views.MainView..ctor() --------------------------- OK ---------------------------

When I tried this several months ago, I ran into problems. Finally, Virpil stated that they do not support this change and will have nothing to do with it. So I gave up and just stopped using Target.

Interesting. I only have a F-14_v2.0b.hpf and not one just for the pilot?

I sent you a PM.

I followed your instructions but I seem to be missing or confused on something. Where did I tell the Hot Sync button to sync just certain switches-for instance the Off/Standby switch for the autopilot? In a cold start, the switch is off and generally in a hot start the switch is in Standby. So how does the Hot Sync button know to do this for only the autopilot off/standby switch and not the other switches (which I will have to determine after I solve this issue) ? Your FIL must have had some interesting stories to tell you about the cockpit. It has held up through a lot of changes. The only stories that I know are the force change on the joystick and the angle of the seat.

DeJohn: Success at last. The button now switches from blank to active and back. However, as the old saying goes: "No good deed goes unpunished." When the jet starts off cold, the button is in sync. However, if the jet starts off hot and in the air, some missions already have some switches in the on/active position while the button in Helios is still in the off/blank position. So the next step is how to do the "Input" tab in order to sync the button with the actual state of the switch. As I understand Helios, the "output" tab is for Helios > DCS and the "input" tab is for DCS > Helios. IS THAT CORRECT OR DO I HAVE IT BACKWARDS? When I go to the input tab for this button and then go to Input>interface>keyboard, nothing appears under the keyboard heading. In Input>interface>profile, there are several choices as well as several choices under the bindings column. I am confused as to what to do, if anything to sync the button. One alternative that is not my choice, is to have two profiles for the Skyhawk, one for a cold start and one for a hot start where the blank/active images are switched. I recall doing this to some degree for the F16 in BMS using Ice's old profile. But again, I don't really want to do that here.

Is anyone else having trouble loading this app after downloading today's DCS update? Maybe this update is the cause of my problem: "Upgrade cockpit kneeboard. Mouse drag and resize. Added clickable buttons for navigation and making bookmarks. Each new bookmark - new color. Route UI buttons callbacks to track."

That is what I have also.

DeJohn: Your instructions seemed simple enough, but apparently not for me. I could not find the generic interface info for the button to activate the search radar in the Skyhawk so I tried to follow your instructions using key commands. However, when I click on the "Input" button and go to Interface>keyboard nothing drops down for keyboard actions so I cannot bind anything. Going to Toggle Switch 1,0>TSwitch_1 changed and dragging it to "toggle indicator" did not seem to work either. BTW, do you use static valve or trigger value in the last column under value source.

I am trying to do a simple Helios profile for the A4E Skyhawk and have managed to do 2 gauges (air speed and radar altitude) using CaptZeen's Helios generic interface and instructions (http://captzeen.com/helios/creating_helios_profiles/#/), but I need some help in understanding how to make a button light up when on and go dark when off. For example, a simple Master Arm button would light up when armed and go dark when not armed. An example of the logic used by Helios would be greatly appreciated. If you do provide an example, don't worry about using the correct code for the button. Right now, I am just using simple keystroke commands for each button, but this is not a satisfactory long-term solution.