DeepDrummer

I back up the input folders for any I have modified the default.lua for. That backs up the joystick default.lua and the keyboard default.lua. I back up the saved games folder (a Gig). Pics attached for path:

I wrote a book and it got lost in the re-sign in. so here's the condensed version. It sounds like something is disconnecting your stick or throttle periodically and it is reverting back to the DCS defaults as one possibility. A loose usb connection, static electricity, a device sleeping then awakening are all suspects if it works at first and then midflight messes up. Sometimes plugging in and unplugging a device such as a cam can re-oerder things as well. Cortana grabs the cam driver from the get go if you use it as a mic and she does not let go. She will re-order usb devices to that end if you remove the cam. You could have changed a binding to another switch that formerly was a hold on a button spring loaded to off. If that were moved to a switch, that switch could be held on at all times when in that position if it wasn't changed to a pulse. (very common). The last pic is the last resort. Uninstall Target Disconnect your stick and throttle. Uninstall all HID devices and controllers except the two for the mouse. shutdown fully. Plug in everything you use except the throttle and stick and leave them there. DO not plug in anything new after the TM drivers are installed for the time being to test for a while. Boot up DO NOT do the firmware section. Many have tried that and let go of the button before the firmware update is finished. It takes a minute or two of painful holding down the buttons without breathing long after the beep. Look for the install scrolling on your screen bottom right if you ever go there but that can brick it at least temporarily if you wiggle and let go. The need to update firmware is not common. Don't go there. If re-enumerating doesn't work: Install the newest TM drivers 2018 H???_1 from July 2018 I still recommend you uninstall target until you have re-installed the drivers and then re-install it. Don't forget to go back and uncheck allow to sleep on all HID usb devices and controllers since windows will re-install the driver sand re-enable it when it does. Sometimes Windows updates will uninstall and re-install updated drivers and re-enable sleep mode as well. Check after windows updates each time.

Try this enumerate your devices. Other things to look for in the pics attached. You can re-install TM drivers over top of the old ones and it will rewrite everything. Just don't proceed to the firmware update where a common problem is people let go of the buttons when it beeps instead of waiting the full minute until your fingers turn blue until the firmware update is finished. One finger wiggle in that painful minute and you brick it at least temporarily. Attach every usb device you use except the TM combo before updating. Cortana captures cams if that is what you use for a mic as I do and she hangs onto it since she grabs it right on bootup and does never let go even when disconnect (trouble starts there). USB things get re-ordered by Windows. If you re-install drivers you must go back and uncheck the allow to sleep box in device manager. Do this for all Human interface devices and HID controllers. I uncheck both boxes. There is a more drastic approach fort contentious issues. Don't give up on it yet.

I keep a copy of my mods config input and saved games folders. It's just a copy paste to rebuild in seconds. I think it would be a difficult change to get it done in saved games and of course the MP world would lose control. Bit by bit some bindings are getting installed I think. It would be handy if the update notifications would identify when changes and what those changes are made to the control profiles so we could decide whether to update our default control bindings. I personally would not go back to defaults until all controls have proper off and ON options. It is not worth rebuilding half a profile.

I found the little switch under the throttle. U/C indicator on and more importantly U/C indicator OFF. Done deal.

There were a pile of switches without proper operations. I got what I needed by including this for keybinds. {down = device_commands.Button_3, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = 1.0, name = _('Landing Gear Up'), category = _('Systems')}, {down = device_commands.Button_3, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = 0.0, name = _('Landing Gear Down'), category = _('Systems')}, {down = device_commands.Button_12, cockpit_device_id = devices.RIGHT_SWITCH_PANEL, value_down = 1.0, name = _('Battery ON'), category = _('Systems')}, {down = device_commands.Button_12, cockpit_device_id = devices.RIGHT_SWITCH_PANEL, value_down = 0.0, name = _('Battery OFF'), category = _('Systems')}, {down = device_commands.Button_9, cockpit_device_id = devices.ENGINE_CONTROL_PANEL, value_down = 1.0, name = _('Starter Switch Cover OPEN'), category = _('Engine Control Panel')}, {down = device_commands.Button_9, cockpit_device_id = devices.ENGINE_CONTROL_PANEL, value_down = 0.0, name = _('Starter Switch Cover CLOSE'), category = _('Engine Control Panel')}, {down = device_commands.Button_2, cockpit_device_id = devices.FUEL_SYSTEM, value_down = 1.0, name = _('Fuel Shut Off Valve ON'), category = _('Fuel Control')}, {down = device_commands.Button_2, cockpit_device_id = devices.FUEL_SYSTEM, value_down = 0.0, name = _('Fuel Shut Off Valve OFF'), category = _('Fuel Control')}, {down = device_commands.Button_13, cockpit_device_id = devices.RIGHT_SWITCH_PANEL, value_down = 1.0, name = _('Generator ON'), category = _('Right Switch Panel')}, {down = device_commands.Button_13, cockpit_device_id = devices.RIGHT_SWITCH_PANEL, value_down = 0.0, name = _('Generator OFF'), category = _('Right Switch Panel')}, {down = device_commands.Button_7, cockpit_device_id = devices.LIGHT_SYSTEM, value_down = 1.0, name = _('Landing Lights ON'), category = _('Environment System')}, {down = device_commands.Button_7, cockpit_device_id = devices.LIGHT_SYSTEM, value_down = 0.0, name = _('Landing Lights OFF'), category = _('Environment System')}, {down = device_commands.Button_24, cockpit_device_id = devices.RIGHT_SWITCH_PANEL, value_down = 1.0, name = _('Recognition Lights ON'), category = _('Right Switch Panel')}, {down = device_commands.Button_24, cockpit_device_id = devices.RIGHT_SWITCH_PANEL, value_down = 0.0, name = _('Recognition Lights OFF'), category = _('Right Switch Panel')}, {down = device_commands.Button_7, cockpit_device_id = devices.TAIL_WARNING_RADAR, value_down = 1.0, name = _('Rear Warn Radar Power ON'), category = _('Right Switch Panel')}, {down = device_commands.Button_7, cockpit_device_id = devices.TAIL_WARNING_RADAR, value_down = 0.0, name = _('Rear Warn Radar Power OFF'), category = _('Right Switch Panel')}, {down = device_commands.Button_16, cockpit_device_id = devices.K14_GUNSIGHT, value_down = 1.0, name = _('Gunsight Gyro Motor Power ON'), category = _('K-14 gunsight')}, {down = device_commands.Button_16, cockpit_device_id = devices.K14_GUNSIGHT, value_down = 0.0, name = _('Gunsight Gyro Motor Power OFF'), category = _('K-14 gunsight')}, {down = device_commands.Button_14, cockpit_device_id = devices.RIGHT_SWITCH_PANEL, value_down = 1.0, name = _('Pitot Heat ON'), category = _('Right Switch Panel')}, {down = device_commands.Button_14, cockpit_device_id = devices.RIGHT_SWITCH_PANEL, value_down = 0.0, name = _('Pitot Heat OFF'), category = _('Right Switch Panel')}, {down = device_commands.Button_3, cockpit_device_id = devices.OXYGEN_SYSTEM, value_down = 1.0, name = _('Oxygen Regulator Auto Mix ON'), category = _('Systems')}, {down = device_commands.Button_3, cockpit_device_id = devices.OXYGEN_SYSTEM, value_down = 0.0, name = _('Oxygen Regulator Auto Mix OFF'), category = _('Systems')}, {down = device_commands.Button_1, cockpit_device_id = devices.OXYGEN_SYSTEM, value_down = 1.0, name = _('Oxygen Regulator Emerg Bypass ON'), category = _('Systems')}, {down = device_commands.Button_1, cockpit_device_id = devices.OXYGEN_SYSTEM, value_down = 0.0, name = _('Oxygen Regulator Emerg Bypass OFF'), category = _('Systems')}, {down = device_commands.Button_2, cockpit_device_id = devices.ENGINE_CONTROL_PANEL, value_down = 1.0, name = _('Supercharger Switch Cover Open'), category = _('Engine Control Panel')}, {down = device_commands.Button_2, cockpit_device_id = devices.ENGINE_CONTROL_PANEL, value_down = 0.0, name = _('Supercharger Switch Cover Close'), category = _('Engine Control Panel')}, {down = device_commands.Button_14, cockpit_device_id = devices.WEAPON_CONTROL, value_down = 1.0, name = _('Rockets to Delay'), category = _('Rocket Control Panel')}, {down = device_commands.Button_14, cockpit_device_id = devices.WEAPON_CONTROL, value_down = 0.0, name = _('Rockets to INST'), category = _('Rocket Control Panel')}, {down = device_commands.Button_1, cockpit_device_id = devices.VHF_RADIO, value_down = 1.0, name = _('Radio Power to ON'), category = _('VHF Radio')}, {down = device_commands.Button_1, cockpit_device_id = devices.VHF_RADIO, value_down = 0.0, name = _('Radio Power to OFF'), category = _('VHF Radio')}, {down = device_commands.Button_5, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = 1.0, name = _('Parking Brake ON'), category = _('Systems')}, {down = device_commands.Button_5, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = 0.0, name = _('Parking Brake OFF'), category = _('Systems')}, {down = device_commands.Button_26, cockpit_device_id = devices.RIGHT_SWITCH_PANEL, value_down = 1.0, name = _('Gun Heat ON'), category = _('Right Switch Panel')}, {down = device_commands.Button_26, cockpit_device_id = devices.RIGHT_SWITCH_PANEL, value_down = 0.0, name = _('Gun Heat OFF'), category = _('Right Switch Panel')}, Now I am cooking with grease on the P-51. Thanks guys for your help.

C:\Users\me\Saved Games\DCS\Kneeboard\whatever aircraft you are using. Then you can bring .jpg up on your kneeboard and bring that up in flight: "K" Kneeboard glance view Kneeboard "]" Kneeboard Next Page Kneeboard "RShift - K" Kneeboard ON/OFF Kneeboard "[" Kneeboard Previous Page Kneeboard

Installed and operational. Looking at the configuration of the Aircraft and the planned route, all I can say is YESSSS! Switches on. CLEAR!

If you are only running the Stable version as am I, you must always look at any post anywhere here as directed to the Beta players and updates or delivery often of newly purchased modules of any kind could be at least a week in the future for you and I. I always waste an hour or two figuring it out each time it comes around. I did read it in the troubleshooting section of that stuff. Again. Beta unless otherwise indicated seems to be the norm.

SRS sounds like the right idea. Does it work well globally regarding servers?

Understood petsild. I just avoid those areas for now. For a while, I will avoid bombs, tanks and altitude. I remain hopeful and do not doubt that it will continue to improve. If they would rather release a perfect Mk The 2 things that were winding me up were the Spitfire's "toggle" on the Gun Safety and the P-51's lack of a gear up and down rather than a toggle. Sometimes it is the little things that wind you up. Some of the fine folks in these forums taught me how to rectify that. I now have zero complaints and I am off to fire up the most perfect (Simulated)Spitfire the world has ever seen. My frown has definitely turned upside down. I got a bit scared when I read what was happening in a beta update at the time as well. Yikes! It is the little things. Ignore the little things and you ignore the whole. Ignore the whole and you may as well pack your bags.

Yes. It was strongly recommended for me to learn C way back when.

I edited the code to reflect your advice. I had to switch the Name= line to get it on the side of the switch I wanted. Oddly it worked before but maybe the second entry cobbled it's way around it. I changed the Button # to 3 to reflect the proper control as well and I thank you for your advice and information on that note. All in all this new code works perfectly for me now thanks to you. With snow starting to rear it's ugly head, I can see some lua learning as it pertains to DCS along with another scripting language I am learning. Thanks for all you do. Corrected code attached and I will change my other entry as well to reflect the change: {down = device_commands.Button_3, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = 1.0, name = _('Landing Gear Up'), category = _('Systems')}, {down = device_commands.Button_3, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = 0.0, name = _('Landing Gear Down'), category = _('Systems')},

Thanks LeCuvier. I figured the first set of 2 lines was one switch and the second set of lines was another. I'll drop the up out and change the button# to 3 as indicated in your messages and remove a couple lines. I knew when I looked at it that it couldn't be prim and proper but it did work. I'll mess with some more. Thanks for all you do. I am referring to your excellent pdf on the subject as well. Goods stuff!

If I read it all correctly, the Beta is the popular way to go. Since I have only room for one, the last fiasco in Beta would have caused me to rage quit without question. I have beta tested things since 95. Often the inefficiencies of Betas can really overwork one's machine and more so one's patience. We sure whipped "Chicago" into Win95 due to open Beta testing and I certainly see the value of it. After 23 years of Beta testing, I'd rather stay out of the Betas personally. I used the DCS Beta quite a bit for a while and did my due diligence reporting some items which never seem to get rectified before it goes to the Stable. I am not suggesting anyone keep mum on anything. Forget I said anything. Carry on with your buggy Betas and send your "do it my way or don't do it at all" comments into the trash.

As I stated my SSD is pretty full. I had to get rid of something. Even if folks would state what version they are posting about in forums it would help. I made the post in response to the controller problems happening in the Beta. That part obviously was not ready for the stable and I am simply saying wait until it has been done properly and I will add ED please notify us of any additions to the binding list. I would gladly reset to default to add a field but we need to know when that is available so we don't reset to default and lose bindings for no new additional fields. I.E. if they ever add Gear up and gear down to the P-51 or Gun safe off and On for the Spitfire. Someone posts something and often they are talking about the beta but don't say so it causes confusion. Then and only then would I reset that aircraft to default and redo all my bindings which would still be better than having to edit input mods every update. I agree finding folks to play with would be good but I operate at opposite ends of the clock to pings close to me. I know how someone with a bad ping can slow others down so I respectively don't mess that up for folks. Someday there will be a server near me or perhaps I will make one in the future. I also need a ton of dogfighting practice. I thought 30 + years of flight simming would be relevant but man was I wrong. I have to find some reading material about dog fighting techniques such as what do I do when my opponent does a certain move. I admit, I have no idea in this area. "Oh no, he is doing a split S, what do I do now?" as an example. I have to learn to not be just a target first. I did try MP twice. The last time, it was only myself in a Spitfire and an F15 pulled up on my wing. Why an F15 would be in the same MP session as an F15 is beyond me but I have to admit it was the coolest thing ever to know there was a human piloting that. I know one person that plays MP personally but he is in the city likely with a far better ping than my tin can and string. BS is a bit higher of a ping than I would personally find acceptable. Darn.

Simply not true. Page 26 of the Target manual explains how to sequence using the GUI to do just what you have indicated. Look for sequencing. Very easy. Over and over I see folks telling other folks that The Target GUI can't do things. It is a thousand times easier than scripting by hand. I find one script per aircraft works best. Multiple scripts tend to lean toward being an unacceptable compromise. Yes you have to exit DCS to switch scripts but one has to admit. DCS likes restarts to clear. Read both the Target Manual and the Target Script manual fully.

I don't use the script editor. I don't use anything but one .fcf file made 100% in the GUI. The only thing I have found the GUI would not do for me is remove layers that I originally set up. One can overwrite those but not remove them completely and so I had to go to the script to do that. I made a crappy video telling you everything you need to know to use the GUI successfully in DCS. Indeed there are some amazing scripts and things made by others in the past however I like things in certain places so I make my own after a taken a bit of time to learn Target. I assign my axis in DCS and do not do that in Target although I assign some LEDs to Axis in parallel in Target. My binding in game for the thrustmaster combined are all blank and instead I send the assigned keystrokes to DCS from the target script created in the GUI. There are really only a few key things one has to know without having to worry about script syntax and curly brackets. I respect script writers totally but I am simply just bad at getting things exactly how and where they belong. For non-coders like myself, I would recommend the GUI. Set up one single switch and you're away to the races. I am not a content creator so don't expect fancy or quality recording. it's all here as far as my current knowledge goes: https://www.youtube.com/watch?v=lhGrbYYmBck

I checked my TM16000 which is on the shelf and pressed into use when, not if, the sticks fail. There is definitely some play in the hat. I never even noticed it before. It is a $50 stick. I don't expect it to be much better. I found it worked extremely well. Cheap things are generally made of cheap stuff. My switches never gave too much trouble so far.

2 seperate switches to a keybind instead of a device so to speak After Captain and Lecuvier pounded into my head how to do similar with a toggle switch as a keybind instead of a controller setting, I was able to adapt this with a few alterations using the inputs keyboard\keyboard\default lua instead of the joystick.lua to get the gear down on one switch and the gear up on another as a keybind which I then assigned to a TM Hotas throttle to the forward and back of one of the 3 position switches which is so perfect since it is what I use for all my gear ups and downs. Thanks so much Captain for all you do. {down = device_commands.Button_4, up = device_commands.Button_4, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = 1.0, name = _('Landing Gear Down'), category = _('Systems')}, {down = device_commands.Button_4, up = device_commands.Button_4, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = 0.0, name = _('Landing Gear Up'), category = _('Systems')}, {down = device_commands.Button_4, up = device_commands.Button_5, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = 1.0, name = _('Landing Gear Down'), category = _('Systems')}, {down = device_commands.Button_4, up = device_commands.Button_5, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = 0.0, name = _('Landing Gear Up'), category = _('Systems')}, CORRECTED CODE HERE Thanks For straightening me out LeCuvier: {down = device_commands.Button_3, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = 1.0, name = _('Landing Gear Up'), category = _('Systems')}, {down = device_commands.Button_3, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = 0.0, name = _('Landing Gear Down'), category = _('Systems')},

As far as devices go, I would be fine with having no default device controller assignments. Is there anyone who doesn't make changes to the default device profiles? Just recognize the device and leave the controller assignments alone would be my wish. I like things my way. I like things left my way. No big deal.

Throw my name in the hat for a C-47. Flyable of course.

Philip Sayce Group I just ran across this band. The first song is perfect for night flights. We'll see how the rest of the album goes.

I have never seen anything so ridiculous. I lost 4 posts today due to time outs and inefficient and flawed routes back. I have never seen anything like it. Totally flawed logic. Stress city.

Looking into it, the only other one not offering off/ons/open/close is the Mirror toggle and I leave mine on and use glance a lot anyway so done deal. Perfection has been achieved. I wonder if I could dig deep enough to find a way to turn that little switch under the throttle off. I think it is not so simple and I can live with it. One mouse click to that button on mission end only required. I can handle that. Near perfection has been achieved if only temporarily. Thanks again. I just had a flawless flight with no stress. Goal achieved.