DeJohn

Wilcox if you read my post above yours you'd see that helios isn't being supported by the dev, which makes helios a moot subject.

Yes I currently use Helios for the switch panel. Its one of the best and easiest addons I've ever used. While it works with A-10, BS and F-15, there is currently no interfaces for other aircraft. Gadroc has not said whether or not he will keep working on it, so that is a wait and see.

That is the Low RPM warning, the default keypress is W I do not know why its not working for you, the only thing I can suggest is to do a DCS repair. If you wish to do that, remember to remove any mods you have added before the repair.

HuggyBear; I can't fault you about it being over priced. The price someone is willing to pay or not is an individual choice based on that persons wants and needs. I'm not really a jet jockey, I'm more of a rotor head, so I've only been with DCS since the UH-1H came out even though I have all modules except FC. A real solution to this problem would be if ED would give us a basic set gauges that would work across all modules. Nothing fancy just something that could be called by all aircraft. I have found most the information as to the device and argument calls, and would make the gauges myself but the problem I'm having is I can't find anywhere on here or the internet that explains how to create a gauge to send the information to. So in order for me to be able to build a Huey SimPit, cost of a gauge pack is less of an issue for me. (considering the money I've spent already on equipment to build the pit.)

Merlin, there is no audible tone associated with the Master Caution, except for the Low RPM Warning. To silence the 'LRW' the switch is left of the Fuel switch.

Not to start an argument, because I don't want to, however that thinking makes no sense considering you're playing a game that you pay $49.95 for one aircraft.

I got email from Simplugins, they are concerned about the demand for a UH-1H gauge panel. (I guess the P-51 panel was not well received) They're a business and economics is the game, I can't blame them for that. The only way I see that they may do it, is if enough Huey pilots and pit builders send them email asking for the gauge panel. As for me, I have about 80% of what I need to build a huey pit, however that is on hold until the gauges problem can be solved.

If all you're looking to build is switches and knobs, then yes that is easy. However, if you don't need to use axis' then I would get Leo's BB32 rather than the BU0836 card it will save you some money. As a side note... SimPit building is a DRUG! You will only be finished when you stop simming. Good luck and enjoy.

hideki2 I've been using one for about a year and a half now. It works great for me. As far as fine control, I just adjusted the user curve to give me fine control between 25-35% on the torque gauge.

LWin + H brings up the AI status

UH-1H gauge panel

If a software company were to make a UH-1H gauge panel for use on a second monitor would you purchase it?

choose the ME on the main menu, when it opens, at the top of the window click on FILE, OPEN. On the left side of the window, click on UH-1H. On the right side of the window you should see three choices... 'Campaign', 'Quick Start', 'Single', choose Campaign...EN... then mission 15. When it loads edit what you want, then click save.

If you want to simulate a parking brake, you have to assign this function to a toggle switch. Otherwise you have to hold the toe brakes the entire time.

Never mind,

Did you check out post #3 of this thread http://forums.eagle.ru/showthread.php?t=113723

Chic I had the same problem with the throttle I was using for my collective. To solve the problem I clicked 'User Curve' and made manual adjustments. The numbers I'm using are as follows.... (0, 5, 10, 15, 20, 25, 30, 35, 40, 45, 75) Now those numbers work for me and are a good starting point, but you have to find what works for you. As far as the effect those numbers have for me when I move the collective I get an initial jump on the torque gauge to about 17%, but from then on the amount goes up slowly giving me very fine control. I can just about choose any altitude in a hover and maintain it.

Andi31; If you are talking about the roof top nav lights not lighting, I take it you are in a slick model. For some reason I don't under stand, when using the slick version, the roof nav lights are very dim.

I can't tell you why your tail light in DCS isn't flashing, but it does flash in mine.

If someone does it how I described above, they won't have a need to use it as a mod. But as I said, everyone can program their controllers as they wish. That's the great thing about information, you can use it or not. GOD bless the freedom of choice.

Flagrum; The Button Box Interface.lua file isn't a lonely file. It is a file for someone who has a Leo Bodnar BBI-32 interface card. (BBI = Button Box Interface, 32 - refers to how many buttons it can control) The only way to allow "more" options for assignments, is to add to, or alter the 'Default.lua' file. The problem with making changes to the default file is every time DCS does an update, or the user does a repair, the Default.lua will revert back to the original file. Thus undoing any changes you made, which will mean that you have to go alter the default.lua file all over again. (don't know about you but that’s a PIA for me). Now of course you could make the assignments to your BBI-32 card by way of the 'Options assignment menu' in the game, which will have the result of creating a file named 'Button Box Interface (a bunch of numbers)dif.lua' file in your save games config input folder. For those who don't know what the 'dif' stands for, it’s 'difference'. Difference in what, you may ask? The difference between what the 'Default.lua' file assignments are. Oh darn, we have a problem with using the 'Options assignment menu' for the controller assignments. It doesn't take in to account for toggle switches. How can we fix that, well we can alter the 'Default.lua' file to allow for the two positions of a toggle switch. Yeah that'll work! Oh wait, if DCS does an update, it will change everything I've done. What to do!!! However, buy making a copy of the default.lua file, and renaming it to the controller you wish to make assignments to, i.e.. 'Button Box Interface.lua', and making changes to that file, and having that file in the same folder as the default.lua file, then every time DCS does an update, it will not affect the assignments you made. And you won't even have to use the 'Options assignments menu' to program the BBI-32. Well, the decision of how to program your controller, is up to you. I know how I want to do it, and so far it’s worked for me without any problems.

doveman; I don't know about all the modules as I don't have them all, but of the ones I have the answer it 'no'. However, some use a dual switch...which is a double shaft with the inner shaft being a rotary encoder and the outer shaft being a rotary switch. If that helps you.

Dudester22; To start with, you should have never installed DCS in your Program Files directory. For future reference it should installed either into the root directory, or create a folder called Games or anything. How it is on my machine is... C:\Games\Eagle Dynamics\DCS World With that being said, on to the issue at hand.... You should NEVER use the default.lua as the name for your modified file. You should name it something like Button Box Interface.lua Then you won't have to use it as a mod for JSGME. You can save it directly into the game. Afterwards it would look like this..... C:\Eagle Dynamics\DCS World\Mods\Aircrafts\A-10C\Input\A-10C\Joystick\Button Box Interface.lua Remember if you make changes to your Button Box Interface.lua file, the changes won't take effect until you restart DCS.

I understand :)

Dudester22 it works, I wouldn't have said so unless I had tried. The following lines are right from my BU0836X Main Interface.lua file... --LandingLight Control { combos = {{key = "JOY_BTN1"}}, down = device_commands.Button_12, up = device_commands.Button_12, cockpit_device_id = devices.NAVLIGHT_SYSTEM, value_down = 1.0, value_up = 1.0, name = 'Landing light On/Off', category = 'Ins Collective Stick'}, { combos = {{key = "JOY_BTN7"}}, down = device_commands.Button_7, up = device_commands.Button_7, cockpit_device_id = devices.NAVLIGHT_SYSTEM, value_down = 1.0, value_up = 0.0, name = 'Landing light Extend', category = 'Ins Collective Stick'}, {down = device_commands.Button_7, cockpit_device_id = devices.NAVLIGHT_SYSTEM, value_down = 0.0, name = 'Landing light Stop', category = 'Ins Collective Stick'}, { combos = {{key = "JOY_BTN6"}}, down = device_commands.Button_7, up = device_commands.Button_7, cockpit_device_id = devices.NAVLIGHT_SYSTEM, value_down = -1.0, value_up = 0.0, name = 'Landing light Retract', category = 'Ins Collective Stick'}, And I've never had a problem with it.