frostycab

Just to update things, has anyone seen todays newsletter from ED? It seems they are already working on voice control. Whoop!!!

I suspected as much. So in order to use it to accomplish the same result you would need a second profile within the X52 software mapped to another mode on the switch. This would have to trigger key binds within DCS rather than mapping to buttons within the sim, which would also mean hours of finding spare keys to assign to currently blank commands AND mapping them in the X52 software. I think this way is easier, at least for me.

That is exactly the functionality that I was going for, but for controllers that don't have mode dials. I'm currently waiting for my Virpil CM3 throttle to arrive, which does have a mode dial, but until that arrives I won't know if DCS itself is capable of reading the state of a mode dial or whether it needs to be set up within the appropriate software for your HOTAS. I did have an X-55 before my current Warthog kit, and never tried it. If DCS can read the state of the dial then great, but if not then to get the same functionality you would need to map all of the controls within the controller's own software. In itself I wouldn't imagine this would be any more work that doing it my way in DCS. However, not all DCS aircraft controls are mapped to keys by default, so you'd need to go into DCS, map keystrokes to them, and then map all of those in the external profiles. Also, the taking the CM3 as an example, let's say you have 5 modes on your HOTAS. This gives you 5 sets of mappings, but I can see this meaning that you may have to come out of DCS and load a different set of profiles into your HOTAS software if you want to fly an aircaft that isn't in that set of 5. I might be making it sound more complicated than it is, but won't know until I get my hardware to try it on. Regarding the lack of latching switches on the X-52 (the first proper HOTAS I ever owned!) you can accomplish things with my method by setting up your modifier in the box on the right of the Add Modifier panel (labelled "Switches") as this will allow you to use a momentary button as an On/Off toggle for the modifier. As I said, I just prefer to use a latched switch if available as I can just look or feel to see if the modifier is on or off, and don't have to try and remember if I've lost focus for a minute.

Can't you do that already? It's been so long since I've used VA, but the only problem with using it for George right now *might* be the long-presses for some of his commands. However. I seem to remember having the ability to adjust timings very precisely within the VA editor, so I'm going to dust it off and have another look. The tricky part is going to be getting VA to keep track of what George is set to. I can see myself needing to set up quite a few internal flags, and I guarantee I'll get it all to go out of sync at some point.

I haven't come across any long/short press functions on the TEDAC *yet*

The "C2" is definitely a typo. MGRS format is always 2 letters, and never a letter and a number. MGRS (or UTM if you prefer) has a set format. In your example 55T is the major grid square (always 2 numbers and a letter), followed by the CS (always 2 letters) which denotes the smaller grid within that which is 10kmx10km. You then enter (depending on the aircraft and required accuracy) 6,8 or 10 numbers to denote coordinates within the smaller grid square. 6 numbers are accurate to 100m. 8 are accurate to 10m, and 10 gives you a 1m square. I've found a few typing/editing errors on the kneeboard coordinates for the included EA missions, so if something looks wrong when you enter it then it probably is wrong. Make a report in the Missions and Campaigns sub-forum and they'll get sorted out in time.

I think the issue for Mange is that he's not using a Virpil base. In order for all the functions on the stick to work the base has to be able to pass the signals to the software, but I've been told that some 3rd party bases are obviously not designed to support all of the buttons on newer grips. It does mention something about it on the Virpil site where it talks about using their grips with a Warthog base, warning you that some functionality may be lost. In any case, he said the Virpil software doesn't work for his base. Google "Brunner force feedback" to get an idea of how good his setup must be though!

Yup. 5 hats (plus one for George!), 7 or so rocker switches (some with 3 positions), 2 slew controls, 2 dual-stage triggers and a myriad of buttons.... It's like trying to map an entire keyboard onto your controller. I think it *might* just be doable for me, but I've got the Streamdeck for backup if I need it. I can see a lot of people dipping their toes into the wonderful world of modifiers in the near future! I do like your suggestion though!

Thank you! I found constantly pressing and releasing a modifier to action mixed commands a pain, and always forgot what everything did. This way it acts pretty much like the mode dial you get with setups like the CM3 or X-56.

If you want to keep everything on your HOTAS but you're running out of buttons, hats and axes then you could try what I've done. It works quite nicely for me. I'm still tweaking a few things and moving stuff around so I'll try to get my whole control layout done on a template in the next couple of days, but here's the methodology I've used:

Yep. I've played about with it in my head how it would work if you were supporting a line of tanks advancing towards an enemy stronghold. Right now you'd be telling him where to look, and then guessing from a list of 20 targets, and each time you try again the list repopulates in a different order or with different units depending on the orientation, so it doesn't seem like you can even filter them out in your head once you've tried them once.

I'm actually quite impressed with how George handle trees right now. He tracked a tank moving down a bushy, tree-lined road the other day for me and did quite a good job of reacquiring the target if if became masked for a second or 2. Granted he did lose it ever so often in bushier areas, but redesignation and waiting for an open shot was easy enough.

I agree that an ideal CPG would probably be able to make some sort of differentiation. However, a more concerning issue is how to use George effectively if you have any friendly forces at all between you and the enemy. If it's a difficult task to get him to recognise specific vehicles it would be helpful if he could at least tell the difference between BlueFor and RedFor. The risk of friendly fire is very high with the system as it stands right now. Same for the Hind. However, I accept that there are many, many more pressing things to be done with the module over the next few months.

What about cycling to a different ACQ source?

At the moment LOBL only seems to allow DIR shots. I don't know if this is WIP or correct as is. I would *guess* that it is correct though, as I would expect the missile seeker to lose view of the lased target point while being lofted in HI or LO profiles.

Have you tried cycling George to the gun to see if that frees it up?

Oh. I've never used it myself, but I've heard that in the past a bit of software called JoyToKey adds some functionality to some controller configurations. It's fairly old software now I think, and I have no idea if it would work, but might be worth a look to see if it can offer a workaround.

I think we'll probably have to wait until the COM page is a little more complete and functional.

That's a bit worrying. Mine is arriving next week. Have you tried recalibrating through the Virpil software?

Just to troubleshoot this a bit: If George is set to LOBL-DIR, you must first press right-short to switch to LOAL before you are able to select LO or HI. Conversely, if he is set to LOAL-HI or LOAL-LO you need to press right-long again until you cycle back to DIR before you are able to select LOBL again. Does that solve the problem?

Have you checked that it's still correctly bound in the controls settings?

If you're running out of physical controls to use I've made a little guide on how to set up modifiers. I got this mod kit a couple of years ago and haven't looked back since! TM made a really mistake by using that tiny little slew "nipple" thing, and the mod totally changes it. I NEVER used the stock slew control as it was impossible to get any fine control over it. Half the time it didn't even slew in the right direction. If anyone is considering the upgrade, do it! (And just FYI, it's only a 10 minute job to install it.)

To add to what WinterH said, in the controls settings you need to look for RHG MAN TRK in either the axis or button settings.

It *should* use whatever ACQ point you have set, whether you've CAQ'd the lased and stored point or have a waypoint as the target or whatever. Picture this: You have 2 targets ahead of you. One at max range and one at relatively short range. Both could be engaged using a LOAL shot. If you wanted to shoot at the nearby target you would set that as you ACQ source, because otherwise the missile might actually pass the target before pointing down enough to see the laser. Conversely, If you were to shoot for max range, but the missile nosed over too early it may not have the energy to reach it. The missile can't allow for a random target that may or may not be within its whole range of search and flight parameters, so you need to give it a clue where top head for and then steer the last bit with the laser. That's a very simplified and analogous way of looking at it, but hopefully it makes some sense. EDIT: Something you said just hit me. Can you describe the steps you did? I wasn't aware that you could set the ACQ through the TADS. I use TADS to create a target position but have to set it as ACQ either through the ACQ menu on the WPN or TSD pages, or via the CAQ. Perhaps I've missed something.

As things stand, it seems that George is not capable of determining if something is a target or not until you command him to search along the PHS line of sight using the up-short command. If he detects something you get presented with the usual list so you can determine which target to engage. The key difference is that if George is set to weapons-free he will engage as soon as the target is within weapon constraints. Otherwise you need to give him consent to fire. With Hellfires being what they are at the moment this means that if he is weapons-free and his first missile misses he will automatically engage again if still within launch constraints. At least that has been my experience so far.