DeJohn

The Helios panel program would be the easiest solution for you. You could either use an existing panel profile or make your own to suit your needs.

Not quite sure what the trouble is

I've done several repairs. Issue is with both the OB and the Release versions. I had hoped to find a solution without editing files, however since I could not find in the lua file where the issue is, I just modified the file to move the panel into the main view port. I also edited the controlsindicator.lua to move that to the middle of the view port while in HUD only mode.

I believe if you look in the /DCS/Mods/Aircraft/aircraftname/Cockpit/Scripts/devices.lua You'll find what you're looking for

I'm not having any trouble with it crashing. Might you have the NS430 Navigation System installed. Its been know to cause some to crash.

Ok, I give up!!! At first I thought the issue might be with DCS, next maybe its Helios 1.6 (since before I got the F-16, I was mainly flying the UH-1 which doesn't have any exports, so I was always using just 1 monitor in the configuration.) However, there is nothing wrong with Helios monitor configuration, and after going over the g_panel_page.lua, on the surface it looks like DCS is compensating for multi monitors and making calculations based on the viewport. So what is my problem... First some facts about my setup. I'm using two monitors, #1 the main monitor is 2560 x 1440, this is my main viewport, #2 1920 x 1080, used for my Helios panels. This gives me a total resolution of 4480 x 1440. In the g_panel_page.lua at line 10 is where the calculations for a multimonitor are made. But somewhere along the way DCS is reverting back to the Full Resolution for its placement. I have checked this against the other monitor setups in DCS's MonitorSetup and the results are the same. Primarily this concerns the UH1 AI panel. But if you want to check whether the placement is figured correctly on your multimonitor setup... When in an aircraft of your choosing, open the Controls Indicator on your screen, is should be on the left side of your screen, at the (top, center or bottom). Now press LAlt + F1 to enter HUD only view,(which is how I fly when using Helios panels), if the indicator is not in the center of your viewport (top, center or bottom), but slightly off to the right of center, then the calculation is using your full resolution also. Good luck and Happy Flying to you all.

Found the issue. Its not an issue with DCS but with Helios. When using Helios 1.6 with the Helios Monitor configuration, if you go from an aircraft that has exports, ie F-16, A-10 etc, to something that doesn't have any exports like the UH-1. The Monitor configuration can't compensate for the lack of exports and DCS sees your full screen width and height. My main monitor used for the view port is 2560x1440 and 2nd monitor used for the Helios panel is 1920x1080, DCS sees this as a screen resolution of 4480x1440. Since the AI panel is normally placed in your lower right corner, this is sending it to an area that is off the bottom of the 2nd monitor, rather than using the view port resolution for its placement. So I'm off to fiddle with the g_panel_page.lua to try and change where DCS will place it.

Did something get changed? My AI panel won't open, pressing LWin + H does nothing. I've tried remapping the keybinds to something else, but it still won't open.

Quick answer...Yes. However, if the helmet you want to use has a different name then the one you're replacing it with you need to give your new helmet the same name as the one you are changing. otherwise you'll need to edit the description file.

Hi, found the problem, Nothing wrong with your programing. Fault lies in the in the DCS command function of the freq tuning, the values are backwards, decrease actually increases and increase actually decreases. To solve this issue with your profile, In the 6 lines that call for the key commands tobe sent to DCS just swap the letters around... Change the W to E, E to W, F to T, T to F, J to U and U to J. And it works as it should. Also make note in you pdf, to have the user change the "Decrease 1MHz" keybind from "LCtrl+LShift+R" to LCtrl+LShift+F" Since the keybind "LCtrl+LShift+R" actually doesn't do anything Thanks again for the profiles.

Hi, First let me thank you for the wonderful VA profiles you've made. I'm having a little trouble with the Huey UHF tuning. The log shows your profile is hearing what freq I asked for but its not tuning to that freq I think there maybe fault in the calculations in the UHF Com command. I have been using your example of '369.55', and have tried it on the sim's default uhf radio setting of '251.00' and its tunes to '343.45'. I've also done a 'quick reset frequencies' with a radio setting of '300.00', and it tuned to '241.45'. The log shows 'Tuning: [36] [Not set] [Not set]'. Tomorrow I'll take a closer look at the command and try and decipher if there is a problem or the problem is on my end. I am using the Sim's default keyboard.lua, and I didn't notice a difference between that and the keyboard file you had included in your zip file. But any help you can give will be much appreciated. Thanks

Did you assign a loadout for the door gunners. If your loadout doesn't have any weapons then you won't get door gunners.

The reason it won't allow you to assign a button is because that command doesn't exist in the default joystick file. So right now the only way to assign a button to it, is for you to add that command to the joystick 'default.lua' file.

Don't click 'solo fight' but do change your aircraft control priority to 'ask always' or 'equally responsible' otherwise you won't be able to leave the pilot seat

Know that any time you leave the pilots seat while flying alone, the heli will switch to autopilot, so you'll want to bind the lever flight and orbit to buttons or remember the keyboard shortcuts. The only thing you need to do different then before, is to set the aircraft control priority to ask always or equally responsible, otherwise you won't be able to leave the pilot seat.

1% isn't enough fuel to keep the engine running even set to unlimited. increase your fuel to 10% (that's less than the weight of one person)

sobe, Basically the instructions you just did to sync the radar button, you do for each button you want to change the condition of when you press the 'Sync' button. The switch you're describing, appears to be a 3 way toggle switch in the cockpit. However not having the mod I don't know what actions it takes. In Helios 3way toggle switches are selectable in 1 of 4 types... on/on/on, on/on/momentary, mom/on/on and mom/on/mom. You'll have to look in the cockpit to see how the switch moves each time you click it, to find out which type for the setting you should use on your panel. NOTE* if the switch or button doesn't have that 'set physical state' in its choices, Which is actually the case with toggle and rotary knobs, you would use the 'set position' insted. So you'll have to declair the position for the 'closed' and 'open' binding. In Helios, toggle switch positions are as follows... two position toggle, position 1 is top or up, 2 is bottom or down. three position toggle, position 1 is top, 2 is middle and 3 is bottom. Now in the case of your autopilot toggle, you will set the 'closed' state at position 2, and the 'open' state at position 3. If you do this right, and you have say 10 buttons/switches that the sync button has to change, then each of the sync button states (closed and open) will have 10 entries each in them.

sobe, First let me say that I'm not able to give you actual information on your A4E panel, since I don't have that mod on my system, and can not get DCS to show me values. Mainly because I am a rotor Head rather than a jet jockey. Though there are two jets that I fly on occation, F-86, (because one of my favorite movies is The Hunters, with Robert Mitchum), and the F-16, mainly out of respect and nostalgia, since my Father-in-law(GOD rest his soul) was the engineer who designed the cockpit for it. But I will give you any help I can, though my ideas may not be the best or the way others do things; sometimes you just have togo with 'what works for you' kind of fix. Now, as to your question. This was the part in my original post where I mentioned the switch, which is how you get DCS to talk to your panel through the interface. If I understand your posts, you are mainly using Helios as far as your buttons go, as a keyboard emulator for your inputs rather than using the interface for this function. Nothing wrong with that, its how many of us started using Helios before the advent of the interface. Originally, when I built my UH1 simpit I ran into the same issue of syncing of the panel with the different states that DCS would start an aircraft in. As you are not using physical switches like I am, your process can be straight forward, however a little time comsuming at first. 1st... take a piece of paper and number or name all the switches you use on your panel. (don't worry if your panel is not complete, you can add to this list in the future as you go). Next, run DCS and the A4E as a hot start on the ramp. Make note of which of your switches are in the ON state in the simulator. Then do the same thing for DCS starting in the air. Also for starting 'Cold/Dark',(this usually only concerns toggle switches and rotary knobs), yes even in this state DCS for what ever the reason in some aircraft will have switches in the ON state even though the aircraft is shut down. Now that you know which of your switches are on or off in different starting conditions, look to see which of your panel switches are different states between the Hot Ramp and In Flight. If they are the same in both starts, then you only need to put one extra button on your panel, if some are different you'll need to use two buttons. For the sake of these instructions, we'll assume that your buttons are on in both the Hot Ramp and Inflight starts. In Helios, on your panel, find an area that you will not be using for any thing else.(for this example lets say the upper left corner). From buttons in the Toolbox, click and drag which ever button you'd like to use, over to the upper left corner. In the properties pane, name the button sync, in the Text area put HOT SYNC (or what ever you want to show on the button), and under Behavior type 'Toggle'. Now with your 'sync' button highlighted, in the Bindings pane, click output tab, expand 'Monitors', then Monitor 2, then your panel, In there should be a list of the buttons on your panel. Unless you have multiple panels on your main panel. If that is the case, expand the panel that has the button you want to sync. When you find your button, expand it. We'll use the button we worked on in my last post. You'll have multiple choices for the button, one of them should be "set physical state". Click and drag that choice over to 'closed' in the Bindings section, and then repeat that step to the 'open' binding. Leave the value as trigger since that is all we are doing is triggering the look of the button rather than giving it an actual value. Save your profile under different name so that we don't mess up any work you did prior to this session (usually I just add a number to the name, 1,2...so on). Run your profile to test... Click on the Sync button, and what should happen is your search radar button should switch between unlit and lit, the same as if you clicked the button itself. However, clicking the sync button will send no commands to DCS, it will only change the look of the buttons you programed to change. Hope this helps DJ

sobe The reference I made to Toggle Switch 1,0>TSwitch_1 was just an example of where to look, not a suggestion on which one to use. The switch you would use is the one that 'you' assigned to that button in your profile. But lets forget about about that part for now, and focus on just changing the look of the button. As I said in my post you need to change the graphic or picture for your button/switch. Here you have several options, 1- create your own pictures, 2- use existing pictures from another profile and 3- modify an existing picture to look how you want it to. For 1 & 3 I use Photoshop, but you can use any program that handles (.png) format. #2 is by far the easist way to go, thanks to Capt Zeen and his wonderful profiles, he's done most of the work for us in this reguard. (Remember you need 2 pictures, one for the 'OFF' state and one for the 'ON' state of the button.) In CaptZeen's F16 profile there is are button pictures I think you might be looking for, if not it will give you an idea of what you're looking to do. If you don't have that profile, download it. Now, in the Helios Editor, Toolbox on the left, select Buttons, click and drag the 'Tactile Square' button onto your panel. Next with your new button highlighted, in the 'Properties' pane on the right, under 'Appearance' you'll see 'Images' two of them, 1 marked Normal(the off state) and 1 Pushed(the on state.) Click on the Browse icon to the right of the Normal picture and navigate to the F16 folder in the 'Documents/Helios/Images/Capt_Zeen/F16', there you will find the picture(active-stby_ACTIVE_OFF.png), select that one. Do the same for the Pushed picture but use (active-stby_ACTIVE_ON.png). Next scroll down the 'Properties' pane to the bottom, and where it says 'Type' change that to 'Toggle'. Save your profile, and run it to test. The button should change from off(not lit) to on(lit).

Hi Some one else may have an easier way to do it, but its actually not hard. For a simple toggle switch, you go to the left pane and select 'indicators', choose which you'd like to use (most of the time I use the green light one) left click on it and drag it onto your panel. In the Properties pane on the right, scroll down to the bottom and there you can choose the picture or graphic you like to use for the ON and OFF appearance. Next go to the 'Bindings' section, click the 'Input' tap, go down to the interface you're using (say DCS Generic), go down to toggle switch you're using for this (lets say #1), click and drag that over to 'Toggle Indicator' or which ever one of the choices you wish to use. Save Profile and you're done. Now when you flip the switch on and off it will change between the pictures you choose. Hope that helps DJ

"Hover Check!" Before flying, bring your ship into a 5'-7' hover. Look at the Torque gauge and see what it reads. This is the psi needed to keep you off the ground. Say the gauge reads 32psi, you now know when coming in for a landing as your speed drops below 20 knots you need to be at that psi so that when the bird comes into ground effect it will enter a hover and not hit the ground. Remember, as you fly you burn off fuel (which is weight), as your weight decreases, it may actually take less psi to slip into that 5'-7' hover. thats ok if you end up in a 10'+ hover at least you didn't hit the ground. However if you pick up troops your weight may be more than when you did your hover check, so it may take a few psi more to keep you in a hover. Pratice at different gross weight settings and see how the psi changes.

dpj463; level flight mode is on by default. You need to select the mode (give command to copilot ...orbit, etc) before giving control over to copilot(turning on autopilot). Once you change the mode it will remain on that one for the duration of the mission unless you change it. Note: place the helicopter into the orbit you would like before giving control to the copilot.

The mouse moves because you don't have to turn the mouse wheel, You can left click on the knob and drag your mouse up/down to rotate the knob.

Backdraft Can you post a track with the controls indicator open so we can see what is happening and what your inputs look like.

kidogofoto; Out of curiosity, what is the reason you want an autopilot annunciator?