CubPilot

My UFC solution Nice solution GregP & you other guys too. This is what worked for me given the physical restraints I had to work with. My goal was to have a working UFC that fit between my MFCD's mounted on my desktop panel. I would have loved to make a UFC replica, but it won't fit between my MFD's this isn't for a full cockpit Having the UFC above the MFD panel isn't an option for me, it would block the bottom of the main monitor. I chose a Genovation 682-U Keypad (USB version shown above) as it would fit between the MFD's. It has 35 programmable keys and a second key layer that adds 35 more (using one key as a shift key to choose key layers). Each key can be programmed to do multiple key strokes or with key modifiers (CTRL, ALT,SHIFT, etc) with one push of the programmed key. I tried to keep the original UFC key layout as best I could except for those keys that are not used by the sim. The keys that were left I used for other things I thought would be handy to have on the keypad. The CTR Track IR key is on this keypad because the keypad has F 13 - F24 keys that can be assigned. By using F13 I don't have to use any other keys for the Track IR centering key that conflicts with the default sim key assignments. I plan to take the top and bottom enclosure off the UFC keypad/PCB unit. Then fire up the router to lower the keypad/PCB unit into the panel so the keys aren't sticking out so much from the panel. So here's the front view with everything hooked up and DCS A-10C running. At the lower left I have a piece of wood under the panel base to tip it up slightly, just testing now to find the proper angle. I will attach two blocks to each side after the testing period. The bottom lip is below the desktop so the panel will not move away from me in the heat of battle. For more details go here.

Maybe, I don't have Simpeds myself. Tried getting them once but it didn't work out. That's when I modified my RCS's, I'm happy with them. My thought was to make an adapter that would allow converting the Cougar DB15 connector and its rudder w/toe brake wiring scheme to be able to attach Leo Bodnar's USB cable adapter. That way the rudders could be used with a Cougar or standalone with USB by simply using, or not using the adapter. The prototype adapter allows connecting to USB when added between the RCS DB15 cable that connects to the Cougar and Leo's G25 USB adapter cable.

Succellus, good to hear that those sensors are still ticking. Hassata, I thought I had seen your online name in my database. I use the easy menu option because I can't dive into this that much time wise (have other things to do that takes me away from this [wonder that that is :doh:]). So I thought, easy menu.... options listed on screen vs. memorizing command phrases and/or writing it down somewhere ...................... on screen won out and it isn't on screen all the time. I figure I have enough to remember with all the other procedures needed to deploy weapons, etc. (Gun & Mavericks I'm good with, Bombs..... haven't got a clue yet.). At least I'm not using game mode! :lol: The AutoHotKey script I found was promising in that it would output any number of different key assignments (that it stored in a table) with the same button, press radio button up, first key assignment sent, press second time, second key assignment sent, etc. It looked good in Notepad, but in the sim it would not work. I might try it again later. P.S. => Don't toss the RCS's yet. I might come up with a USB adapter for them and toe brakes are not dead either. Good to bump into you guys!

Guilty as charged.................... but I don't know what "All sensors" are. ;) Good to hear you are still kicking. By the way...... how are those Hall Sensors holding up?

Hassata, thanks for your help! :thumbup: I set mine up using F14 to activate VAC, that way I didn't need to change any conflicting default assignments. I also used the Default mode in the VAC Profile Activation Keys setting instead of the Arm mode. I like to keep the button pushed down as I access and use the COMMS Menu (like a MIC button would work). I'm using the easy COMMS option that displays the COMMS choices on screen and the Default mode works better for me. Only thing, I wish that I could code AutoHotKey to first send a "\" key to the sim to open the COMMS Menu, then send the "F12" key to turn VAC on using the same Radio UP button. If this could be done with one joy key press doing both actions ..... Priceless! If it could be done with two key presses, well that would be OK too. I tried "messing" with the code to do this but came up short as far as it working in the sim (found some code that would store multiple key assignments in a table, first key press outputs first key assignment, second key press outputs second key press, etc., NO JOY). Presently I say "COMMS Menu" to open the COMMS Menu. I'm not a programmer!

VAC - Thumbs Up! I had GC2 way back in Win98-XP days. It worked quite well. VAC is very good, as good as or better than GC2 or GC3 IMHO (GC3 was just like GC2 with mouse commands added). The author does ask $18 for it (worth every penny IMHO). The demo version is the full version with a time limit on it (30 days if I remember correctly). This is one of the few VC software out there that will work with 64bit OS's and it is currently being updated regularly ( I found that all of them I tried will program in 64bit, but not all will actually work with 64bit sims like A-10C). Most of the other choices out there appear to be dead as far as updates are concerned. VAC uses Win7 voice recognition software. A short training session with the Win7 VR software and it will help accuracy quite a bit. I highly recommend it! :thumbup:

Must be missing something, won't work for me 1.WH Throttle Mic Switch UP is button #3. CHECK 2. Assign the WH Throttle as the Preferred Device. CHECK 3. Copy & Pasted your script below the default script text. CHECK 4. Save, then Compile, set "Green H.exe" to run as admin. CHECK 5. Run Green H.exe., make sure it's turned ON. CHECK 6. Set VAC A-10C profile PTA setting = Scroll, save. CHECK 6. load VAC profile and turn ON. Check 7.load A-10C.... Scroll Lock works when throttle radio button pushed up (my keyboard puts up a graphic on screen when Scroll Lock state is changed). CHECK.... :D 8. Push radio button Up (more than once), No response from VAC with voice commands (voice commands work outside of sim in test mode) NOT SO MUCH, UN-CHECK! :cry: Question, VAC sends key presses into the sim, does it read key presses from the throttle radio button & AutoHotKey? [ :joystick: . VAC said,"What did you say Mr Joystick??"] So, what small (or big thing) thing am I missing here? :helpsmilie:

After trying the current crop of voice command programs and finding that most will not work in game with Win7 64bit (most are older versions and may or may not be updated), I found VAC (Voice Activated Commands). Very nice program, not hard to program, very good voice recognition (uses Win7's VR program). I have my own VAC file that mostly deals with the Comms menu (Easy Communications mode). I was wondering how you bound the mic button on the HOTAS Warthog throttle to the VAC software without using TARGET. I read one way was to Assign the middle button on the mouse scroll wheel in the VAC software as the mic on/off button, then assign that in the sim Controls Menu to the throttle button, but my mouse is not allowed custom assignments there. There is a way to modify a .lua file to allow additional Control Menu assignments, I did it in Beta4, but for the life of me I can't find that .lua file in the final version. :( So, twig05...... how did you do it?

Just a heads up. When programming your Keyboard/keypad be sure to set your UFC key assignments as "repeating" keystrokes. I didn't do that at first and as a result the buttons & rocker switches did not always move on the main monitor UFC, only every 4th or 5th keypad push would result in the main monitor UFC switches moving. Setting the UFC keys as repeating keys fixed the problem. The other non UFC keys I have on my keypad don't need to be repeating keys.

I'm not sure if this will help in your case. In Beta4 I was setting up a programmable keypad to use as my UFC. I found when programming the keys that if I programmed a key assignment that output only one "a" for example, then the cockpit keys would not always click in the cockpit view. The key press would trigger the desired result, but the button or rocker would not always move as if you were using the mouse to do the key press. I found the way to fix this was to program the key as a repeating key (hold the key down and it outputs "aaaaaaaaaaa" as long as the key is pressed). If your keypad or keyboard is not programmable I don't think my solution is viable for you. But, at least it might point to what the problem is.

MFCD Panel Thought I would post about the UFC that I have setup for my MFCD panel. This panel isn't in a full blown cockpit, it just sits on the desk and houses the TM MFD units with 8" monitors (#YN8088AV 8" VGA AV TFT LCD RCA XGA Display Monitors I bought off eBay) behind them and soon my poor man's UFC, the main monitor sits behind this panel. The panel in it's construction phase is shown above, is made of 1/2" MDF board. When it gets warmer I will paint it. The pic above shows the back of the panel and how the 8" monitors are attached. The screws for the four shinny tabs screw into the wood blocks at each side of the monitor. The TM MFD's are stuck to the monitors with double sided tape at the top and bottom (keeps the tape off the monitor screen). I used the back half of the case the monitor was enclosed in to cover up the wiring and hold the monitor PCB's. I cut the bottom front half of the case off that has the monitor control buttons on it and placed it at the top, attached with a couple small nails. The wood blocks at each side of the monitors are used to hold the screws to secure the monitors to the panel, much better than using MDF material that doesn't deal with screws as well as wood. The long dado below the monitors will allow a MDF piece (not shown) to be attached at 90 degrees to main panel and shims used under it to tilt the panel slightly when set on the desk top. The main panel below this piece will be below the desktop and stop the panel from moving away from the user while pushing buttons. Poor Man's UFC I would have loved to make the UFC replica posted elsewhere in the forums (the guy who did this did a fantastic job!), but it won't fit between my MFD's. Having the UFC above the MFD panel isn't an option for me, it would block the bottom of the main monitor. I chose a Genovation 682-U Keypad (USB version shown below) as it would fit between the MFD's. It has 35 programmable keys and a second key layer that adds 35 more (using one key as a shift key to choose key layers). Each key can be programmed to do multiple key strokes or with key modifiers (CTRL, ALT,SHIFT, etc) with one push of the programmed key. I tried to keep the original UFC key layout as best I could except for those keys that are not used by the sim. The keys that were left I used for other things I thought would be handy to have on the keypad. The CTR Track IR key is on this keypad because the keypad has F 13 - F24 keys that can be assigned. By using F13 I don't have to use any other keys for the Track IR centering key that conflicts with the default sim key assignments. I plan to take the top and bottom enclosure off the UFC keypad/PCB unit. Then fire up the router to lower the keypad/PCB unit into the panel so the keys aren't sticking out so much from the panel. This keypad has two layers activated with the upper left key. When the second layer is active a LED will be lit on the key. I plan to have keys for Communications use plus other things with the remaining keys of the second layer. I will need a key map below the keypad (or somewhere) to show the second layer key assignments. To get this to work I first determined my own key assignments for the various UFC keys (taking into account what key assignments A-10C Beta4 uses for other things in the sim) and programmed them into the keypad. The key assignments are then programmed and loaded into the keypad using the keypad software. The code is saved to a file, then downloaded and stored in the keypad, no need to load it for each use. The next thing was to edit the Keyboard.lua file so that the UFC key assignments are available for modifying them by the user (me) in the Options/Controls screen. NOTE: The Keyboard.lua file does not need editing in DCS A-10C Final Version, skip this step and continue with the next paragraph. After that it was a simple matter to open the sim to the Options/Controls screen and select the UFC item from the list and add the new key assignments by pressing the appropriate key on the UFC keypad. I now have a working UFC that interfaces with the HUD and MFCD's without having to use the main keyboard (with multiple key presses/command) or using the mouse to click in the screen cockpit UFC. My modest UFC keypad keeps my hand on the stick, much better! UPDATE I fired up the router to make room for the keypad and did some painting ( and to add to the spam :megalol:). The front view routed out for the keypad and its PCB's. It required three depths of routing due to the design of the metal keypad base and the PCB'S. Back view of the keypad mounting. If the MFD panels were any closer together I would not have room for the keypad, whew.... :gun_sniper:dodged a bullet there!! The keypad fits! The two notches (middle top & bottom of the keypad metal base) will be used to fasten it to the panel with two small screws. I made a molding to go around the keypad to finish it off (after a bit of swearing on my part). Epoxy is a great fix for those brain farts while using the router! Can you find my brain fart above (hint, the router bit is round)? Rear view of keypad. The white connector at the right is for the keypad USB cable. The TM MFD Panel is installed into its panel cutout. The USB cable routes out the back side of the panel and cannot be seen from the front. I put a piece of black electrical tape vertically (not shown) on each side of the MFD panel where it meets the main panel to block any light from the monitor coming through the crack. The tapes sticky side is towards the TM MFD panel and the main panel so it doesn't get onto the monitor screen. The monitor screens and covers were installed next. Rear view of both TM MFD Panels, the monitors (#YN8088AV 8" VGA AV TFT LCD RCA XGA Display Monitors I bought off eBay), and the keypad installed. I added a four port USB hub as I was running out of USB ports on my computer. It can be used unpowered or powered. The keypad only draws 10ma, but Im sure the MFD panels draw much more with all the LED's that are in them, so I have the USB hub powered. I haven't had any problems using this USB hub with these components. The monitors run on 12v DC, so they are supplied with 120v AC to 12v DC transformer/plugs (shown at left and right). The USB hub also has a transformer/plug (shown in the middle). The VGA connectors on the monitors point straight down. The horizontal MDF panel (below the monitors on the back side) prevents hooking the VGA cables to the monitors VGA connector, so a 90 degree VGA adapter is used to remedy that situation. The cables not shown hooked up are the two VGA cables and the USB hub to computer USB port cable. So here's the front view with everything hooked up and DCS A-10C running. At the lower left I have a piece of wood under the panel base to tip it up slightly, just testing now to find the proper angle. I will attach two blocks to each side after the testing period. The bottom lip is below the desktop so the panel will not move away from me in the heat of battle. What commands I want assigned to the keypad is still a work in progress, but it is easy to change as I determine what items are the most important to have in front of me and one key press away. Only problem is the keypad keys are not lighted so a dark room it is a problem. I plan to make a ledge similar to the top of the A-10C instrument panel where the fire extinguisher handles are. I have some green LED's coming, along with a dimmer, and I hope that the LED's mounted under the ledge will be enough to illuminate the keypad keys properly. I may have to modify my keys colors due to the green LED's, but that is easily changed. :pilotfly: NOTE: To see the latest evolution of this little panel GO here to post #25. This thread got hijacked just a bit, the link may save you some time.

This has been mover here.

Thanks Kuky, that would be great. I was hoping the MFD info would be there no matter what the main monitor was showing, just asked to be sure it was so. I have been bit before with a "gotcha" because I didn't ask enough questions. What do you plan to use the middle monitor for?

Questions about your MFD setup Kuky, Very, very nice setup you have there for the MFD's!! :thumbup: :thumbup: :thumbup: I do have a few questions. How much of a performance hit do you take with this setup? I guess it would help to also know your system specs to give us some idea how our own system measures up. I'm using Win7 64bit. i7 920 oc'ed, ATI 5870 (I have another ATI card here somewhere to use for the MFD monitors if I can find it!). Do the MFD's have to be shown in the main monitor to be seen in the small MFD monitors? I guess what I am asking is if you use Track IR and look outside the cockpit will the MFD info go away until your view includes the MFD"s on the main monitor? I assume that this setup will not work for Falcon 4 as they (Virtual Thunderbirds) are using USB monitors with some third party software and some sort of hack to Falcon to get the job done. Waiting for the Warthog! :joystick: ........:pilotfly: