Sokol1_br

This happens when you make changes in device, e.g. change name or number of axes but keep the same VID/PIP. Then Windows continues look for the old name. Solution remove the old name from Windows registry, or use different VID/PID (you have 9999 options). ;) BTW - Despite the controller don't show in Windows Games controller, they work in games (I have tested) and joy testers, another suggestion that Windows Games controller is obsolete. :D

Seems that OP wishes for 1k controllers (each) will be fulfilled. :) https://forums.eagle.ru/showthread.php?t=235433

An HAT positions became fail (don't click) due wear in the plastic button of micro-switches (4 or 5) installed inside or in the HAT plastic pole that press then. This picture is from a topic about failing (warthog) "CMS" - see the micro-switch inside: <a href='https://postimg.cc/K1QHJLTr' target='_blank'><img src='https://i.postimg.cc/K1QHJLTr/HAT-CMS.jpg' border='0' alt='HAT-CMS'/></a> Practical and cheap solution: replace the micro-switches (use OMRON B3F 6x6mm), they cost ~$1 - require make solders. An possible workaround (that work for me in an 1990's CH HAT), a square of very thin plastic/Mylar under the micro-switch, this raise then a bit and he start "click" again. ;)

Or if don't have use for buttons in joystick base, and want the features of "dry-clutch", Gunfither base + Kosmosima grip.

Saitek soft - or any other keymapper, will not change this, you can use one 'mode" per time. You must choose the functions of each mode well, e.g. one for ground functions, other for flight functions. For momentary only functions use "shift" (momentary modifier) in "pinky" button.

JoytoKey have "Axis to Button" function, and work in Windows 10.

Up to $ 120 you are limited to buy new: Thrustmaster TFRP ~$ 89,00. CH Products PRO Pedals ~$ 120,00. Logitech G PRO Flight Rudder Pedals (ex Saitek) will cost more ($150/160) and don't worth the additional cost, neither have any differential that justify this. CH is slight more wide than TFRP, but in electronics is "obsolete" (8 bits), anyway is the most durable/reparable of the three options, with the best cost/benefit.

TheNoobifier "review": nyLQV62pnmc

Is just one guy opinion, most people will consider VKB casting better, but he give lower note for this - probable due issue with embed bolt nuts in some (VKB) grips. VKB grip electronics are completely different - and has advanced features, than Warthog/VPC, but he give same note for Warthog/VKB. VPC/Warthog grip electronics is the same (CD4021 shift register).

In this you are right, Tm HAT's construction use an dedicated spring for add "weight" in HAT operation, VKB/VPC/CH/Saitek use just the micro-switch copper membrane.

Pot's tab are: Power Signal Ground By invert Power and Ground invert pot reading direction, then the only critical wire is signal. Probable Power and Ground wires are shared with all pot's. Signal wire are individual for each pot. An good replacement cable is microphone cables, they are insulated and strong, but first assure that channels in pedal structure have space for them. Picture of connector is too bad to defines, but looks a micro-JST* connector. If you take a better picture of connector helps identity. * Problem with this kind of connector is that require a specific crimping tool (not cheap), but you can buy then crimped with cables, sample (assure first that is this type that you need): https://produto.mercadolivre.com.br/MLB-1023508243-mini-micro-conector-jst-sh1-4-vias-125mm-macho-e-femea-_JM?quantity=1 In Brazil, well... "voce esta no mato, sem cachorro". :D But look if this shop still in business. https://pilotovirtual.com.br/assistencia-tecnica-saitek/ If not, be creative (DIY). ;)

Good point. VKB TECS approach is not an "replica" (like Bugeytech) for an semi-replica cockpit, but an desktop game controller, with best ergonomics possible for this basic use and features that attend games needs and incorporating some real throttle look/features. Basic module + front and rear expansion modules, mount support, probable became close to 1k mark. But will offer an best cost/benefit than just a "replica" of F/S-XY plane throttle. ;)

A nice metal gimbal with "spherical plain bearing" for Warthog/T16000M/X52 "3D" sensor (MLX90333): More pictures in > (spoiler). This gimbal mod don't have springs, apparently only the rubber boot help keep stick (more or less) in center. BTW - Don't know if maker sell this. :)

Now only if your are in "airlines jet" business, their F-18 venture don't went well, apparently for both sides - manufacturer and consumers. ;)

An Bugeyetech (or similar) made throttle - besides their nice "real" look will be a better game controller than an Warthog or Virpil throttle? For ones that want build a close to real cockpit this 1K price may justify - more by the "form than by the function".

And why not? He don't find any "game stop". Is know since day one that VPC grips shells, buttons, HAT's are made in plastic (and not in jewelry metal) - cast receive 8.5 note, seems fair compared with 10 of the previous teardown - Warthog. Switches under plastic cap are OMRON (used too by CH and VKB) - better than open copper membrane use in an "famous" stick or switches in Saitek's. The hot glue fixing connectors make interior looks "handicraft" but are common in low production electronics. Saitek's love this. :D Wires look's a bit more thick than in CH sticks - know for last decades. Opera resume: grip assembly are not in Iphone standards, but seems functional. :joystick:

DCS will recognize F-22PRO (+TQS) buttons - if Windows recognize then as "game controller". Their issue is be a gameport controllers, gameport is no longer officially supported by Windows after XP. Hence need replace their electronics with USB controller, if interest in this, look at Rel4y parts.

Looks this: https://www.amazon.com/Stainless-Steel-Bracket-Restroom-Partition/dp/B0758NNXRJ

The more "universal" setup that you can buy* actually is: VKB Kosmosima grip + Gunfigther base VPC throttle Good amount of axes, rotaries, lever, encoders, switches, press buttons, HAT's (analog/digital) without much compromise in "be replica" of this or that "badass" fighter. :joystick: Since their are from different manufacturers, can "program" (keyboard emulation) with Joystick Gremlin. * Be buy = have luck in be able to fill an order when they are momentary available, in that "planet alignment". :D And will cost more than Warthog H.O.T.A.S. - but specially VKB base mechanics justify the major price. Anyway consider in Warthog price + ~60 Euros for "slew" upgrade and ~$15/20 of Nyogel damper grease for address they major flaws.

Still working, I did a test - had some occasional unwanted F-12 view camera. Like author say is for guys that want keep hands ON stick or throttle, although seems nice at start, navigate between F1 and F12 - e.g select an ATC, with HAT became boring fast. :D Since is an external program - an AutoHotKey script, use ~2/3% of CPU; IMHO better use Voice Attack.

Perhaps something in LUA change for this new plane... If you make a test with TF-51D can confirm. The only jet I have installed is MiG-21, test with then too and work. By "test" I mean start a mission and use COMM pressing stick buttons.

Here the guy use just a small flat screwdriver:

I change the code because I move "Menu Items" from General to Communications category, just for convenience. But test your attached code with lines added - option for set joystick buttons for "menu items" will appear in General - don't find Communications category in this plane. I don't have this module to test. https://forums.eagle.ru/attachment.php?attachmentid=205929&stc=1&d=1552072108 default.lua

Just add the lines "ICommandMenuItem1... in -- Communication section of joystick default.LUA, after the last existing entry, that is _('COMM Push to talk'), -- Communications {down = iCommandPlaneDoAndHome, name = _('COMM Dispatch wingmans - complete mission and RTB (easy communication only)'), category = _('Communications')}, {down = iCommandPlaneDoAndBack, name = _('COMM Dispatch wingmans - complete mission and rejoin (easy communication only)'), category = _('Communications')}, {down = iCommandPlaneFormation, name = _('COMM Toggle formation (easy communication only)'), category = _('Communications')}, {down = iCommandPlaneJoinUp, name = _('COMM Join up formation (easy communication only)'), category = _('Communications')}, {down = iCommandPlaneAttackMyTarget, name = _('COMM Attack my target (easy communication only)'), category = _('Communications')}, {down = iCommandPlaneCoverMySix, name = _('COMM Cover me (easy communication only)'), category = _('Communications')}, {down = iCommandAWACSHomeBearing, name = _('COMM Ask AWACS home airbase (easy communication only)'), category = _('Communications')}, {down = iCommandPlane_EngageGroundTargets, name = _('COMM Attack Ground Targets (easy communication only)'), category = _('Communications')}, {down = iCommandPlane_EngageAirDefenses, name = _('COMM Attack Air Defenses (easy communication only)'), category = _('Communications')}, {down = iCommandToggleCommandMenu, name = _('COMM Communication menu'), category = _('Communications')}, {down = ICommandSwitchDialog, name = _('COMM Switch dialog'), category = _('Communications')}, {down = ICommandSwitchToCommonDialog, name = _('COMM Switch to main menu'), category = _('Communications')}, {down = iCommandPlane_P_51_PTT_on, up = iCommandPlane_P_51_PTT_off, name = _('COMM Push to talk'), category = _('Communications')}, {down = ICommandMenuItem1, name = _('Command menu item 1'), category = _('Communications')}, {down = ICommandMenuItem2, name = _('Command menu item 2'), category = _('Communications')}, {down = ICommandMenuItem3, name = _('Command menu item 3'), category = _('Communications')}, {down = ICommandMenuItem4, name = _('Command menu item 4'), category = _('Communications')}, {down = ICommandMenuItem5, name = _('Command menu item 5'), category = _('Communications')}, {down = ICommandMenuItem6, name = _('Command menu item 6'), category = _('Communications')}, {down = ICommandMenuItem7, name = _('Command menu item 7'), category = _('Communications')}, {down = ICommandMenuItem8, name = _('Command menu item 8'), category = _('Communications')}, {down = ICommandMenuItem9, name = _('Command menu item 9'), category = _('Communications')}, {down = ICommandMenuItem10, name = _('Command menu item 10'), category = _('Communications')}, {down = ICommandMenuItem11, name = _('Command menu item 11'), category = _('Communications')}, {down = ICommandMenuItem12, name = _('Command menu item 12'), category = _('Communications')}, -- View

For map in joysticks buttons open the "default.LUA" in MOD/Aircraft/"aircraft name"/Input/Joystick and add the following to the general section: {down = ICommandMenuItem1, name = _('Command menu item 1'), category = _('General')}, {down = ICommandMenuItem2, name = _('Command menu item 2'), category = _('General')}, {down = ICommandMenuItem3, name = _('Command menu item 3'), category = _('General')}, {down = ICommandMenuItem4, name = _('Command menu item 4'), category = _('General')}, {down = ICommandMenuItem5, name = _('Command menu item 5'), category = _('General')}, {down = ICommandMenuItem6, name = _('Command menu item 6'), category = _('General')}, {down = ICommandMenuItem7, name = _('Command menu item 7'), category = _('General')}, {down = ICommandMenuItem8, name = _('Command menu item 8'), category = _('General')}, {down = ICommandMenuItem9, name = _('Command menu item 9'), category = _('General')}, {down = ICommandMenuItem10, name = _('Command menu item 10'), category = _('General')}, {down = ICommandMenuItem11, name = _('Command menu item 11'), category = _('General')}, {down = ICommandMenuItem12, name = _('Command menu item 12'), category = _('General')}, Not sure about "general section", but think is top of "default.LUA" inside joystick folder, where are entries for start procedure cheat. Don't forget to make backup before change.:thumbup: EDIT - Test adding code in plane > joystick and work, and don't affect F1-F12 default assignments. Test changing _('General') with _ ('Communications') and place under ---Communications will be more easy to find for change joy buttons. Tested (offline) OK: