TonyZ

Having the same problem as OP but in VR as well.

Found the problem thanks to LeCuvier. All item that were set for my ns430 gps were the ones that would not work in the A-10C II..Cleared all controls for the NS430 garmin and all is working now...that is something that needs to be looked at on DCS end. Thanks to LeCuvier for his help.

I have a switchbox I made using a Bodnar BUO836X board and it has 2- dual rotary encoder as well as an 8way hat and numerous switches and rotary pot knobs...The box works fine in the original A-10C aircraft and all functions are seen by the controls setup page in DCS as well as the aircraft itself....However after picking up the NEW A-10C II aircraft and setting up all controls the box is still seen by the controls options setup page in the new plane but nothing is seen in the aircraft except the 8 way hat function...all other controls have no effect in the actual aircraft even though the controls setup screen sees all buttons switches and rotary knobs just fine.....at this point I am stumped and wondered if others are having similar issues with the new A-10C II plane not seeing their Bodnar controllers. I have already tried copying my control input luas from A-10C to A-10C ii with no effect.. Made no difference. both in my saved games folder and in the main program directory. Is the New A-10C II input just broken?

see this post and look at what he did in the image https://forums.eagle.ru/showthread.php?t=288865

I have a switchbox I made using a Bodnar BUO836X board and it has 2- dual rotary encoder as well as an 8way hat and numerous switches and rotary pot knobs...The box works fine in the original A-10C aircraft and all functions are seen by the controls setup page in DCS as well as the aircraft itself....However after picking up the NEW A-10C II aircraft and setting up all controls the box is still seen by the controls options setup page in the new plane but nothing is seen in the aircraft except the 8 way hat function...all other controls have no effect in the actual aircraft even though the controls setup screen sees all buttons switches and rotary knobs just fine.....at this point I am stumped and wondered if others are having similar issues with the new A-10C II plane not seeing their Bodnar controllers. I have already tried copying my control input luas from A-10C to A-10C ii with no effect.. Made no difference. both in my saved games folder and in the main program directory. Is the New A-10C II input just broken?

disregard--solved..garmin ns430 controls were superceding all other inputs to other modules

I think this post needs to be bumped since there has been no response from the DEV and this issue has needed to be addressed for a couple of years now.Especially the missing keyboard/button commands for the INTERVAL SELECTOR KNOB on the RIGHT WEAPON PANEL.

Do you have your stick curves set so you don't overcontrol it?

I think this post needs bumping. I agree that the localizer needle in the HUD is ass backwards and appears to never have been fixed. You always fly to the line not the line to the fpm. The fpm is the plane and the line shows the direction from the fpm or waterline TO the ILS indicator.

My physical IPD is 71 but I find that the sim setting works best between 53 and 58 or so depending on the aircraft. I have always felt that the mirage looks like a toy sittin the cockpit and everything is way too small to read. \ meanwhile the A-10 seems just right to me.

Once again because of the confusing and erroneous naming by ED users are not understanding what IPD is and that there are two types. As stated earlier IPD is Inter Pupillary Distance and is the physical measurement between the pupils of the users eyes when looking directly forward. This number is what gets set in the RIFT or VIVE when setting the IPD for the headset lens spacing. This is completely unrelated to the setting in the DCS settings menu called IPD which is actually nothing of the sort and should be called World Scale or Virtual eye camera spacing. That setting is to determine the distance between the virtual eye positions in the VR world and affects how the scale of objects appear in the "WORLD" of DCS. Smaller numbers make all the objects and cockpits seem larger and larger numbers make everything seem smaller. DO NOT SET THIS NUMBER TO YOUR PHYSICAL IPD AS MEASURED ON YOUR FACE!! They are two COMPLETLY different thing and ED really needs to rename that setting to avoid this kind of confusion in future. If your physical and virtual IPD numbers happen to be the same it is purely coincidence and a fluke.

Shadows are frame rate killers. Don't set above flat settings. Lens flare and dirt are totally unnecessary. Human eyes don't have lens flare or dirt so unless you are streaming or making a movie then turn them OFF! Anything above Pixel Density of 1.8 is a total waste and unnecessary. Also turn off anisotropic and keep msaa as low as possible.

Once again because of the confusing and erroneous naming by ED users are not understanding what IPD is and that there are two types. As stated earlier IPD is Inter Pupillary Distance and is the physical measurement between the pupils of the users eyes when looking directly forward. This number is what gets set in the RIFT or VIVE when setting the IPD for the headset lens spacing. This is completely unrelated to the setting in the DCS settings menu called IPD which is actually nothing of the sort and should be called World Scale or Virtual eye camera spacing. That setting is to determine the distance between the virtual eye positions in the VR world and affects how the scale of objects appear in the "WORLD" of DCS. Smaller numbers make all the objects and cockpits seem larger and larger numbers make everything seem smaller. DO NOT SET THIS NUMBER TO YOUR PHYSICAL IPD AS MEASURED ON YOUR FACE!! They are two COMPLETLY different thing and ED really needs to rename that setting to avoid this kind of confusion in future.

I really wish people would STOP trying to shove that totally crappy TARGET software option down peoples throats when they ask about switch files. TARGET sucks...it has ALWAYS sucked.. and unless Thrustmaster changes management and support completely it will continue to suck. If you cant answer the original post question then for pity's sake just don't post at all. Now in answer to your Original question there are two things you can look up that make the switch LUA's editing very clear.. First is a you-tube vid at this link and second is a PDF which I will try to link .. How to Edit Control Binding Files by Hans-Werner Fassbender https://forums.eagle.ru/attachment.php?attachmentid=161709&d=1493988359 I have been trying to make sense of this esoteric black-magic art for years but these two docs make it all clearer. Also when you edit the default.lua file in the a/c input folder you must also add the change to ANY OTHER lua files in that folder ..Even if you do not have the controller those files are for or they will conflict with each other.

I do exactly the same. JSGME for modded switch LUA's and no worries for updates. Also T.A.R.G.E.T SUCKS!!