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!!

Yes that is the file but you must also make the change in every other file in that directory or it wont work since the other files settings will conflict with the default.lua file settings you changed. ALL the other controller files must match for those command lines even if you don't have that controller. also 0.1 and -0.1 are the correct numbers and they work great. Very controllable while not being too slow.

Yes it can be done....you need to edit your default.lua and all the other lua files in your input folder for the F5 . On the command lines in each file that say.. { pressed = iCommandPlaneRadarUp, value_pressed = 1.0, name = _('AN/APQ-159 Radar Elevation Antenna Tilt Control - CW/Up'), category = _('AN/APQ-159 Radar Control Panel')}, { pressed = iCommandPlaneRadarDown, value_pressed = -1.0, name = _('AN/APQ-159 Radar Elevation Antenna Tilt Control - CCW/Down'), category = _('AN/APQ-159 Radar Control Panel')}, change the 1.0 and -1.0 to smaller numbers like 0.1 and -0.1 and the tilt will slow down

If you read my previous post it tells you where the discrepancy comes from and again AOA HAS NOT A BLESSED THING TO DO WITH LEVELNESS OF THE Aircraft. I could be in level flight and still have my nose way above 5.5 deg of AOA since there are a number of factors that affect AOA including load, flap position, airspeed, thrust, winds, nozzle position...etc. point being that ..Who cares where the hat is pointing on the ground?...it's during landing before touchdown that matters.

Angle of attack has nothing to do with the levelness of the airframe. It is the angle between the relative wind and the chord line of the wing. It is not related to the witches hat at all. The aircraft wheels are arranged so that when the aircraft is 8 degrees nose up then both front and rear landing gear will touch down at the same time so that's why the witches hat is 8 degrees below the horizontal centerline of the fuselage and why the nozzles are set for 82 degrees when performing a vertical landing.By keeping the nozzles at 82 degrees and the witches hat on the horizon which equals to an 8 degree nose up attitude during descent then both wheels will touch down at the same time and thrust will be straight down and the AOA has nothing to do with it. Also the reason the witches hat is at 5.5 degrees or so on the ground is because with weight on the gear the front strut compresses and the nose settles downward a few degrees so the hat is now below the horizon line.

Problem Solved!!! go to game settings in DCS and uncheck the ScaleGUI checkbox. That scales the map to fit your screen but it scales the layers of background map and icons and labels at different scale rates. Thus the error. Turn it off and the Map is perfect again.

This has Never been fixed yet.

Is there any way to speed up the rate in which you zoom in VR? It takes over 2-3 seconds to fully zoom...I don't want to hear any responses about snap views... this is in VR! This is about instant VR ZOOM not a slow zoom in and out in VR ZOOM.

As a longtime warthog owner I'll just say that you SHOULD NOT! attempt to make the warthog stick any stiffer than it is. I've had my stick open several times to put in my stick extension and rewire the ribbon cable and those gimbals are simple not made to take the kind of stress your talking about. Regardless of whether you use spring or foam or rubber or whatever, those gimbals are just a kind of plastic and this stick is not designed for force sensing stresses. All you will do is wind up with a broken stick and a pile of heartache.

Once again.... the original poster pretty much specified that this idea was NOT JUST CIVILIAN ONLY! He was talking about armed scouts as well as low and slow armed ground support. As well as combat JTAC or ATC with the capability of carrying rockets and small bombs as well as marker flares and WP rockets. These planes have been used in the combat zone almost since they were invented so saying they are civilian only and dismissing them because they are not supersonic jets is very shortsighted and limiting for the Sim in general.

Which part of WEAPONIZED do you people not get? The original poster is mostly talking about an ARMED scout aircraft not a civilian model. Now personally I would actually like to also see an Antonov AN_2 in here as well. This could be used in places where other aircraft can't go and supplement the helicopters in the game as well. Just a thought...