DeJohn

HornetUK; What I find the easiest way to deal with DCS and switches for the button board is to not try and program them through the options menu. Instead I enter what I want directly into the lua file. First make a folder on your desktop called A-10C, or which ever module you want to program for. Then goto you (Eagle Dynamics\DCS World\Mods\Aircraft\A-10C\Input\A-10C\Joystick) folder, and copy the Default.lua file. Then paste that into the folder you made on your desktop. Then paste it in the same folder again, you want the original and a copy in that folder. Now rename the copy 'ButtonBox Interface' or how ever your computer has named the card. Note... if there are numbers after the cards' name don't include them, just the words. Now open the the file you just renamed with notepad ++ Somewhere around line # 439 will be this line {down = iCommandBatteryPower , name = 'Battery power', category = 'Electrical power control panel'}, Now since this is an iCommand function you don't need to add values for down or up. Your going to add combos = {{key = 'JOY_BTN2'}}, to beginning of the line and up = iCommandBatteryPower , after the down command so that the line looks like {combos = {{key = 'JOY_BTN2'}}, down = iCommandBatteryPower , up = iCommandBatteryPower , name = 'Battery power', category = 'Electrical power control panel'}, Remember to change the button number to the one you want to use, When you are done making changes that you want you’ll click ‘save’. Then you highlite and copy your BottonBox Interface.lua file and paste it in the (Eagle Dynamics\DCS World\Mods\Aircraft\A-10C\Input\A-10C\Joystick) folder, and you’re done.

The Uh-1H is what brought me to DCS, its the one I fly the most even though I have most of the modules. I'm kind of a purest, fly the seat of your pants kind of guy, over letting technology do all the work for you. I'm really looking forward to the F-86F next month.

I don't see why not, there are maps out there. If you like to look at a few check out these sites. http://www.freewebs.com/jim4jet/maps.htm or this one, which has a lot of extra info and pictures http://www.rjsmith.com/topo_map.html#radcliff2

Demon {down = device_commands.Button_10, cockpit_device_id = devices.ELEC_INTERFACE, value_down = -1.0, value_up = 0.0, name = 'Main generator ON/OFF Switch', category = 'Ins Overhead panel'}, You told the program what the up value was, but you didn't tell it there was an up command. The line should read as follows.... {down = device_commands.Button_10, up = device_commands.Button_10, cockpit_device_id = devices.ELEC_INTERFACE, value_down = -1.0, value_up = 0.0, name = 'Main generator ON/OFF Switch', category = 'Ins Overhead panel'},

What trouble are you having programing your switches? -Info needed... - what function are you trying to program? - What type of switch are you trying to use (Actual toggle switch, momentary switch on joystick)?

The reason is because [Line 435] acts as a momentary switch, and not a standard toggle. Those lines act as an On/Off/Mom toggle switch

Dudester22; Have you figured out how to work with your Leo Bodnar card. If not PM me and I'll try to help you out as I also used the Bodnar's cards.

It happens even with the default monitor configs. It definitely is something in 128, but what I don't know. I just tried 1.2.7. and as the picture below shows everything is fine. BTW - its the same problem with 128 Openbeta. Only thing I can try is to un-install and try a fresh install ======================================= Well first I did a repair... and that got rid of the red.... however it replaced it with green screen. So I unstalled DCS and deleted all files and folders relating to DCS, rebooted the computer and re-installed DCS....Everything is back to normal now. Still don't know what caused it.

Yes it does it to both monitors when I switch then around. But its only DCS, all other games run fine.

Hi, I hope someone can tell me what I did wrong. Using two monitors was fine until the other day. Now the second monitor has a red background instead of the normal black, as you can see in the picture below. Any help will be appreciated.

Yurgon; Thank you! That was it. I've always just used the \ key to access the menu during missions. Didn't realize they used the easy communications setting.

Its a nice mission, except I must be doing something wrong because I only get the radio menu while I'm on the ground. I get no menu when in the air. Anyone have an idea of what I'm doing wrong?

Anyone still reading this thread...if so will this app work with BlueStacks?

If this has been posted already sorry in advance... 1) How about a little flexibility in the textures, be nice if all four crew members helmet texture was individual or at least the pilot's was. or 2) you could leave the helmet texture as one, but give us a texture mask for the helmet which would allow us to add graphics or text to the front or sides of one helmet without it being put on the others. 3) How about a layered psd file for the pilot and gunner textures.

PeterP's sling load mod was written for 1.2.5. The cargo camera still works in 1.2.6, but the sling doesn't show up. I guess ED has changed or moved the setting for the sling. So until some bright fellow figures out where that is, we will just have to wait.

yes... same key as when you want to view it (K) on your keyboard

{I'm wanting to build a Huey pit but with out gauge its a show stopper for me.} Showtime, I'm in the same boat. However I think I'm going to take a leap of faith (beleaving SimPlugins will come through) and start my build after the 1st of the year. {Someone made an app for Android and exported the gauges for the Huey, think it was free also, why not start there.} Cefs; I looked into that... it turns out that the app is not compatable with all Androids. As luck would have it, mine is one that its not compatable with.

As for total realism, join the military. Ummmmm I did and I got the Tshirts. 12 years including several tours in the Falklands, Bosnia, Iraq and Afghanistan. Cowboy; I will concede to you expertise. And I thank you for your service.

Sorry Misread your question. :(

Why did you put 1.2.7. on a different drive! Had you installed it in the same Eagle Dynamics folder as 1.2.6. Helios would work just fine.

The reason you can't have door guns on a slick is because there is no way to hang a bungee cord to support the gun. During Nam the only ways to have a gun was the gunner had to hold it, hang it in the doorway with a strap or bungee or mount it on a hardpoint. I don't blame ED for taking the easy way. Its a GREAT simulator but its still just a game. If you're looking for total realism join the military. Bless Your Heart! :)

Raven; Try these http://forums.eagle.ru/showthread.php?t=89345 http://www.digitalcombatsimulator.com/en/files/369734/

Well since I can't get a response from anyone else about how to export the guages for the Uh-1h, I went ahead and email 'SimPlugins' (makers of Panel Builder for DCS P-51D) last night and asked them if they were going to make the addon for the Huey. They responed back quickly with.... "Yes, we are planning an add-on for the DCS Huey. Scheduled for early 2014." Well I guess I can wait a little longer :thumbup:

Sorry if this is in the wrong place, but I didn't see it somewhere else. 1) Radar Alt now reading Meters instead of Feet. Fix for #1: Can't find where the problem is yet. 2) Left Door Gunner's Head in wrong position to view front sight. (causing shots tobe way low to what you're aiming at) Fix for #2: In your Eagle Dynamics\DCS World OpenBeta\Mods\aircrafts\Uh-1h\Cockpit\Scripts\Devices_specs\WeaponSystem.lua Line 44 -- pivot = {-0.121377, -0.1820260, -1.514663}, change to read -- pivot = {-0.121377, -0.138260, -1.514663}, This will place the gunners head in the proper view position for using the gun