Menessis

Ya that's what I am thinking No1....But you can add a 16 bit ADC to the Leonardo (I think). That's what I will look into next. Well that didn't take long.....Check this out:->

My Cougar specs say 16 bit resolution on x and y and 14 on the throttles. So that's 2 to the power of 16 or 2 x 2 x....16 times right? Which is 65536. I have been tinkering with Arduino's now for a while and was thinking of getting a Leonardo to use for a Huey setup. Full size. So I see here, a library stating it has 16 bit joystick support. OK cool I'm thinking. But the Leonardo says it's 10 bit. So what am I missing here? Do I need an external Analog to Digital Controller add on? Thanks Menessis

For a long while we couldn't use TACAN Y for the tankers. Now I see that working but for some reason I'm not getting Call Sign up in the HUD? Also the HSI is displaying Bearing information, and CallSign even though I don't have TACAN boxed. Has something changed recently? Thanks Menessis

Thanks Frost

Hello Silver. So Zoom Normal is the num pad enter. Is this what you are talking about? Menessis

I'm trying to setup the FOV (not zoom or Snap Views) for each aircraft. The goal is to be able to smoothly see the cockpit correctly using my TIR . I get it looking good but can't seem to save it. R CTRL + Pause Break brings up the specs on screen. The FOV value there doesn't change as I make realtime changes. So I guess I'm missing something here. I hope there is a solution! Thanks Menissis

While using the 154a's and setting up the HT I see new parameters. I have looked for info about the use of the Heading and Velocity settings. Can't seem to find anything. Is this not implemented yet? Thanks Menessis

I'm using the right shift and right Ctrl along with the / and* on the num pad to move my head position forward and aft. I can't figure out if it saves that info with R Alt + num 0 or not.

Thanks RazorBack. I have that on. After a lot of tinkering I think it has to do with how I am seated when I tap the button to re center my TIR?

While trying to tweak my head position and my Track IR profile I found out that the "R ALT + Num 0" isn't saving the settings. I get back in next time and I'm sitting all the way back again. So what's the trick?

My comms switch is sticking. Any way to lube it and what to use? Menessis

I did figure it out by going through something I had hit upon a few days earlier. I comes down to the order in which the way point actions are put in, ie "bomb" can't come before "reaction to threat" otherwise they must bomb before they do the next instruction. Menessis

Hey Habu_69..Thanks for the helpful tip. The thing is I did search it and came up with very little. Maybe you can help me with my searches?

Hi Nealius. I used your numbers along with setting the bombers to Evade if shot at. They will fly the route and bomb the target. BUT! if I have a even a hint of a SAM they fly the route, fly right over the target, drop chaf and flares but no bombs! The SEAD mission was in support of the bombers using the new PB mode. We have flown it where not one SAM is fired but no bombs are dropped. Menessis

So what's the trick? Bomber at 20k, 20 nm from target. And another steer point 10 nm beyond the target all in a straight line. The bombers dive in one time. Fly flat and level the next. Make crazy "S" turns for no reason. Do everything but a barrel role or drop bombs! I renamed the miz file and stripped everything out but the bombers and my F-18 SEAD flight. I did get them to work there. But not consistently. Then I did the exact same set up back in the original but no luck. They fly right over the target, drop chaf and flares and keep right on going. I am about to test this idea out. Any ideas? Menessis

I have been wondering about the way a tanker behaves. Is it realistic to have a tanker cut short a race track pattern to suit a an incoming flight? i played around with some triggers and a 4 steer point pattern. The idea is if I approach the tanker track the tanker will turn 180° and role out in front of me. So I made use of a moving 100000’ trigger zone on the tanker that had it change from steer 2 to steer 4. I was kinda excited when I tried it the tanker began a 5 nm left turn ! But it was short lived when it came through 90° and the reversed the turn into a 270° right turn! I tried tweeking a bunch of things to fix it. Stretched the pattern from 6 to 9 did get it to work once! But only if my flight was no where near it. I wonder if the AI code has a feature to keep it from doing this? Menessis

Too bad my mouse can't give it a good slap! Menessis

I'm finding that I cant get VHF 119.55 (in this case) radio in the Huey working. While trying to get the radio turned on it seems like it's on but when I press the Test button I don't get any squelch. I turned it on and off a bunch of times and then It started working. A few buddies seem to have the same problem. So what gives? Thanks Menessis

Well Thanks Bunny! That's a lot of effort you put into that. Good work. Menessis

Where can I find a chart showing the Hotas Functions for the F-18 like this one I found for the A-10c II https://forums.eagle.ru/showthread.php?t=287614 I like that I can print it and keep it handy if I get stuck until I learn it. Thanks Menessis

Thanks LeCuvier. Seems kinda like command sense! The thing is DCS sees the keystrokes from the X Keys Menessis

LeCuvier. I know the key strokes work in the setup window. But that doesn't transfer to the pit. I think the default.lua is set up to use key binds or a direct x hardware. The X Keys is not direct x....it just sends the key strokes. I also know it doesn't make sense to me! If DCS is getting a key stroke why not use it right? I flip the switch it shows in the setup window. I turn off the switch and the other keystroke lights up in the setup window. But get in the pit and nothing happens! :( I never tried this until now. While in the pit and the switch not working I pressed the u on the key board and the switch flips up. As well as the other keys. So to recap. 1)the X Keys sends the key. 2)DCS gets the key stroke from X Keys verified in the setup window 3a)Go into the sim toggle on X Keys moved to up position. Nothing happens b)Move toggle with mouse to up position and then do the same on the X Key toggle and then return it to off position. The switch in game moves to off position. c)after putting in your two lines I am able to use a switch as normal on Warthog of course. 4)Your switch code is greyed out in the keyboard column so I can't add a key to it. Prior to last update I was able to add the key to my hacked switch code and it worked. Menessis PS Did you ever think that looking at all our key profiles would be your full time job? 71 pages so far!

LeCuvier :) The X Keys generates a key press down and a key press release when I flip the switch up. So In my case i used a "u". But at the same time it is programmed that when I return that switch to the off position it generates a key press down and a key press release (or up). In my case a "v". And in DCS I have to put the "u" in for Alt Hold and the "v" in for A/P Off. But the way the lua file is now there is a key stroke for A/P Off but not for Up or Down. Remember that the X Key board is not direct x and therefore does not show as a controller in DCS. DCS doesn't know it exists. DCS is just getting key strokes from the X Keys. The Roll switch works. So maybe I should compare the two and see if I can figure it out that way. Menessis

Hi LeCuvier. Yes they are shortened. I took out the up part. They didn't work with it in before. The X Keys is running software that I have set up to generate the key presses up and down. So I flip a switch to the on position and the X Keys sends an key press and a key release (key down and up). Then I have to go in the game and set the same key for that function. That part all works fine. I can flip switches and watch the DCS setup screen and each one is hi lighted in turn. But does not work in the sim. So that means it's down to the lua. Do you see what I am talking about now? Thanks Menessis

F-16 AutoPilot troubles I was trying to get my old X Keys box working in the Viper. Finally got back around to it and worked through a few of the problems and got to the point that I was satisfied that the X Keys is working. The key strokes are making it to DCS as they should. But the one last Pitch Auto Pilot switch would not work. I would return to the center off position but would not move in either direction. So I figured since the one position (A/P OFF) worked I should have a look at the lua and see why it's different. The ALT Hold & ATT Hold both had Down and Up values. So I figured what the hell. I took out the Up part and renamed it. And presto one happy camper. Don't know why it worked because I am a newbie with all this. But !!! Did the update. Replaced the lua with my modded version. And Im back to not working. Looks like a lot of changes in that default lua. So I put the updated lua back in and then cut and pasted my two lines of code. The new code shows up in the game but I can not select them to add the keystroke to it. It is "greyed out". -- MISC Panel --Edited April 5 2020 Removed the Up = parts of both { down = control_commands.ApPitchAtt, cockpit_device_id = devices.CONTROL_INTERFACE, value_down = -1.0, name = _('Autopilot PITCH Switch - Down Menessis'), category = {_('Instrument Panel'), _('FLCS')}}, { down = control_commands.ApPitchAlt, cockpit_device_id = devices.CONTROL_INTERFACE, value_down = 1.0, name = _('Autopilot PITCH Switch - Up Menessis'), category = {_('Instrument Panel'), _('FLCS')}}, -- { down = control_commands.ApPitchAlt, up = control_commands.ApPitchAlt, cockpit_device_id = devices.CONTROL_INTERFACE, value_down = 1.0, value_up = 0.0, name = _('Autopilot PITCH Switch - Up'), category = {_('Instrument Panel'), _('FLCS')}}, { down = control_commands.ApPitchAtt, up = control_commands.ApPitchAtt, cockpit_device_id = devices.CONTROL_INTERFACE, value_down = -1.0, value_up = 0.0, name = _('Autopilot PITCH Switch - Down'), category = {_('Instrument Panel'), _('FLCS')}}, { So any thoughts out there? Menessis