RackMonkey

I would have to say that TVV/FLIR is for an "either/or" switch where both positions are "ON". The zoom functions can go to any momentary switch, I.E. a hat switch OR if you only need medium and zoom function you can map them to any 2 position momentary switch that all HOTAS have.

I looked at the file that Horus provided and it did everything that I was trying to do and more...THANK YOUR VERY MUCH Horus! In this zip is also a mod that thins the IHADSS symbiology to make it easier to sight the gun or just look around without your eyes being pulled to those FAT symbols. The root of the mod is DCS's mod folder. Let us know how it works for you and if you think there are any changes or additions that I might be able to do with my limited knowledge. AH-64D Single Pilot Mods.zip

There seems to be 2 or 3 different ways to get this to work. I'll give them all a try today and create the file with the best of them. I'll post it here when I get it done. I am using the Quaggles/Wolfmuck software to add commands for my encoders so I'll see if I can get it working from that direction also.

I did try it first in the installation folder on my D drive and when that didn't work I did try to but it in my SAVED GAMES folder. That didn't work either. I think I'll do like Needz and put it in the keyboard default.lua file and see if that works. I also tried putting it in a folder I use to modify the way my encoders work. It adds lines of code to make the encoders move faster. UPDATE Cut the line out of the "joystick" file and pasted them into the "keyboard" file. They are now showing up in DCS. I have to set them up and test them but it looks good so far. I think I'll try putting it into the 'saved games' folder so updates won't erase it all the time. If that doesn't work I'll make a package for OVGME that can be quickly enabled and disabled for updates.

Well...now that mcfleck said it work's for him I'll revert back to the original default.lua with the following add to the bottom of the file. It should be the exact lines that Horus provided. Still nothing shows up in my controls to indicate a selection for the TAD settings.

I do that a lot. In the most extreme cases it was to the left so I just chalked it up to retreating blade stall. I do get smaller dips to both the left and to the right and even the smallest correction seems to over correct it leaving me swinging back and forth under the blades. I am also seeing an almost complete loss of yaw authority at times and at other times it's so twitchy I can't keep the nose pointed in the right direction. After reading a lot of post concerning controllability I'm wondering if it might not be a difference in our input devices. Curves are not helping at all. I was hoping the last up date would at least dampen the problem if not fixing it completely but it doesn't seem to have done anything. ED may not have worked on it yet.

I tried this this morning and couldn't get it to work. I matched your lines to that of the CPG file and found them all EXCEPT for your first line and I don't believe it has anything to do with the DOV line.. There were modifications of course. I copied the original CPG lines into the PLT default.lua to see if that would work, but it didn't. My PLT default.lua file now looks like this...can you tell what's wrong with it? ------------------------------------------------ -- CPG commands for the pilot ---------------------------------- ------------------------------------------------ {down = tedac_commands.LHG_TADS_SENSOR_SELECT_SW, up = tedac_commands.LHG_TADS_SENSOR_SELECT_SW, cockpit_device_id = devices.TEDAC, value_down = 0.0, value_up = 1.0, name = _('Custom_LHG TADS Sensor Select Switch - TV/FLIR'), category = {_('Custom')}}, {down = tedac_commands.LHG_TADS_SENSOR_SELECT_SW, cockpit_device_id = devices.TEDAC, value_down = 1.0, name = _('Custom_LHG TADS Sensor Select Switch - FLIR'), category = {_('Custom')}}, { down = tedac_commands.LHG_TADS_SENSOR_SELECT_SW_FLIR, cockpit_device_id = devices.TEDAC_INPUT, value_down = 1.0, name = _('LHG TADS Sensor Select Switch - FLIR'), category = {_('CUSTOM')}}, {down = tedac_commands.LHG_TADS_SENSOR_SELECT_SW, cockpit_device_id = devices.TEDAC, value_down = 0.0, name = _('Custom_LHG TADS Sensor Select Switch - TV'), category = {_('Custom')}}, { down = tedac_commands.LHG_TADS_SENSOR_SELECT_SW_TV, cockpit_device_id = devices.TEDAC_INPUT, value_down = 0.0, name = _('LHG TADS Sensor Select Switch - TV'), category = {_('CUSTOM')}}, {down = tedac_commands.LHG_TADS_FOV_SW_Z, up = tedac_commands.LHG_TADS_FOV_SW_Z, cockpit_device_id = devices.TEDAC, value_down = 1.0, value_up = 0.0, name = _('Custom_TADS FOV Switch - Z (Zoom)'), category = {_('Custom')}}, { down = tedac_commands.LHG_TADS_FOV_SW_Z, Up = tedac_commands.LHG_TADS_FOV_SW_Z, cockpit_device_id = devices.TEDAC_INPUT, value_down = 1.0, value_up = 0.0, name = _('LHG TADS FOV Switch - Z (Zoom)'), category = {_('CUSTOM')}}, {down = tedac_commands.LHG_TADS_FOV_SW_M, up = tedac_commands.LHG_TADS_FOV_SW_M, cockpit_device_id = devices.TEDAC, value_down = -1.0, value_up = 0.0, name = _('Custom_TADS FOV Switch - M (Medium)'), category = {_('Custom')}}, { down = tedac_commands.LHG_TADS_FOV_SW_M, up = tedac_commands.LHG_TADS_FOV_SW_M, cockpit_device_id = devices.TEDAC_INPUT, value_down = -1.0, value_up = 0.0, name = _('LHG TADS FOV Switch - M (Medium)'), category = {_('CUSTOM')}}, {down = tedac_commands.LHG_TADS_FOV_SW_N, up = tedac_commands.LHG_TADS_FOV_SW_N, cockpit_device_id = devices.TEDAC, value_down = -1.0, value_up = 0.0, name = _('Custom_TADS FOV Switch - N (Narrow)'), category = {_('Custom')}}, { down = tedac_commands.LHG_TADS_FOV_SW_N, up = tedac_commands.LHG_TADS_FOV_SW_N, cockpit_device_id = devices.TEDAC_INPUT, value_down = -1.0, value_up = 0.0, name = _('LHG TADS FOV Switch - N (Narrow)'), category = {_('CUSTOM')}}, {down = tedac_commands.LHG_TADS_FOV_SW_W, up = tedac_commands.LHG_TADS_FOV_SW_W, cockpit_device_id = devices.TEDAC, value_down = 1.0, value_up = 0.0, name = _('Custom_TADS FOV Switch - W (Wide)'), category = {_('Custom')}}, { down = tedac_commands.LHG_TADS_FOV_SW_W, up = tedac_commands.LHG_TADS_FOV_SW_W, cockpit_device_id = devices.TEDAC_INPUT, value_down = 1.0, value_up = 0.0, name = _('LHG TADS FOV Switch - W (Wide)'), category = {_('CUSTOM')}},

I'm getting notifications that somebody has added to this topic, but I'm not seeing anything posted. So I can't respond to your post.

I'd like to see it static, shrunk and moved to the side a little. It's not easy for me to concentrate, find, then refocus on the list of targets and separate them from the forward instrument panel.

I don't have a problem moving around but in all the time I've had the Apache I've only been able to boresight the iHAADS ONCE. It's really a pain to try and fly with NVS when your seeing double images. I'm sure that part of the system needs some tweaking because I can't see a real pilot flying a combat mission like this.

I just saw a post from Wags that they are working on being able to switch seats on MP servers. I can wait for it.

Flying single seat in MP is there is a way to change the TAD between TV and FLIR? If I'm flying off of MP then I can jump to the CPG seat and change it from there but since I can't change seats I can't change it. I'm talking about bringing the TADS up on one of my MFD's to visually confirm what is being lased for the Hellfire.

I have made a couple of changes to the materials.lua files for the Apache and F-18 to help me. The change is only one line changing the color used in the HMD for the Apache and HUD for the F-18. Both of these changes work if they are placed in the DCS sub folder but only the Apache mod works if it is placed in the "saved games" sub folder. My question is, what keeps some mods from working when placed in the saved games folder when the exact change in the same folder of another acft works? By the way, I have placed the file manually and by using OVGME and when using OVGME I used OVGME to build the ZIP file.

Unfortunately I'm in the %10 of males that is red and green deficient in my color acuity. Because of this I sometimes have to change the colors of things in DCS. Right now I can't tell who has fire control, me or George. If I'm static on the ground I can see the colors change when I give George control but when I'm flying and only have a split second to check and the background is moving and changing colors I can't see it. Does anybody know where the definition files for these colors are? I think they are in the "materials.lua" but I don't see anything that strikes me as being for the George interface.

I got it working. 2.0 seems to be a good stroke for the display and I changed the "HMD_GREEN" to a neon orange in the materials file. It is so much easier to see against the clouds. I use VR with a G2 and the display is not GREAT as far as clarity. The default HMD_GREEN may be just fine for others.

That looks like what I'm looking for. I'll try changing it tonight...Thanks.

I fly VR and there is a difference from 2D. In VR the IHADSS display all looks like it is in a bold font and is hard to ignore and takes up way to much of the visual area when your trying to spot something outside. I've looked for a lua file to modify but I can't find what I'm looking for. To be honest, I don't know what I'm looking for. Just a blind squirrel looking for a nut.

You are %100 right and I'm a blind idiot. That answers almost all of my questions. I do have one question left that will probably never get answered...Who the hell decided GREEN meant "not ready" and RED meant that it was FMC? When I worked on F4's a long time ago a red slash in the maintaince log meant not FMC but flyable and a RED X grounded. Did the French decide on the color coding?

You misunderstand. I want to command the units from the F10 map while in a chopper. I know the basics but I can't find anything that tells what RED and GREEN are for or why are there formation movement commands if you can't select a whole formation. If a unit doesn't move why does changing the formation seem to work in getting them moving?

You know I haven't flown an Apache, but I do have 15K fixed wing in my log books and if I had a much trouble keeping the plane upright as this version of the Apache does, I would never be able to fly a visual let alone an ILS approach. I'd have to use all my concentration just keeping it upright. When I see an unbiased critical review of the flight characteristics of the Apache from a real pilot I'll with draw my comments. Curves should only be used to make adjustment for different control systems and not as a fix for poor flight characteristics programming.

Does anybody know where I can find a comprehensive set of instructions for moving and firing the units of Combined Arms from the cockpit? Nobody seem to think it was worth it to make a YouTube video of how to use CA from the cockpit. I would like to find out what all the options are for and how the work when I want to blunt a red force advancement but I can never tell if my fire mission has been accepted or not. It seems to take so long for a tank to even turn to face the enemy let alone fire on them. I tell a unit to move and nothing happens. It might move if I change the formation but a lot of time it just sits there,

Lets quit making excuses, it doesn't fly like the real bird! The real bird doesn't have "curves" and this thing acts WAY to twitchy and underpowered as DCS put it out. Actual flying should be second nature to a combat pilot but with this bird you have to concentrate %100 to bring it into a hover or keeping the nose point in the right direction. Forget about what your CPG needs to get a firing solution. Your to busy just keeping the bird from drifting into what ever your hiding behind. That is assuming you can get it to hover with out "settling with power". If the real thing flew like DCS's model and I was assigned the Apache coming out of UPT I would ask for transfer.

I'm using the community keybinds and its working great. I'm just waiting for some stuff from Digikey to build my button box. Until then I'm just learning what changing setting do to each item. What I'm really interested in doing is using the push function of the encoder as a modifier to switch between fast and normal. I want to be able to push and turn to change large heading changes and let it up to make the final few degrees of change. I'll download you code again. It was daunting to look at and even more so thinking about trying to use it.

@LASooner That was going to be my next question. You must be clairvoyant. After getting it installed and working I was wondering if it was possible to make the encoder depress a modifier so that in depressed that encoder would be "fast" and not depressed would be slow. This would also come in handy with other knobs that always seem the require you to twist your wrist off to get them to move.\ I just copied the example and god..what a long line of code. I'll try to mod it for the HDG and CRS but also lights, gain and brightness controls along with anything else that has a knob

Thanks guys. Looks like I have some reading to do to implement this mod. Gives me something to do until the encoders for the button box get here.