Captain Orso

Yeah... that's the question - TILT!! So, I was trying out the new ACLS system in Case III Recovery, and after landing I noticed I had TILT in the HUD at the upper right. Anyone know why, and what exactly it means?

Radar Elevation Control is the same as FLIR zoom, because... of course it is. Not that long ago I changed to using the Slider for Radar Elevation Control. I still have trouble remembering to zero it before starting a new aircraft. For what ever reason--heeeeeey, it's user friendly - he said in his best Steve Martin voice. That was the issue. Many thanks for reminding me of what I already should have known.

Thanks for the replies. -- Well I don't get it. I thought it might have been because I had done LST just before - tried without LST, no difference. Maybe because I did an air-start. Did a cold start on the ground, still the same. I don't get it. Did a repair, no difference. Did a repair with foreign files, threw out a buch of stuff left over from old patches, it looks like, but no difference. I just don't get it.

Since the update yesterday--maybe earlier, but I haven't been flying the Hornet lately *cough*cough*Apache*cough*, I only just noticed it yesterday--I cannot zoom the view with the Litening TGP. Switching between NAR and WID views WAD, but the zoom buttons (L1 & L3... ummm OSB3 and 5 hehe ) don't do anything. Anyone else having this issue?

Have you checked to see if your link is still set to "Run this program as an administrator"? Windows updates sometimes change this.

Please refer to this post: for what the goal is.

You didn't select CPG Site at R2 first.

Yes, you can pick any weapon, but you must assign one to the CPG for the TADS to appear on T6. Picking the HF just makes the most sense, since the CPG is going to be firing it anyway.

HF? I know it's probably something simple I ought to already know, but... what's HF?

Let's take a quick look at George, in general. George is passive, still, unfortunately. He will not proactively search the landscape for targets. If the mission you are playing allows for labels, you better turn them on, especially in VR, or else you will only find enemy units when they shoot at you. If you tell George to search an area, he will search a very wide arch, like a minimum of 45° each left and right of the point you designated; probably more, but I haven't specifically tested it. I think there may be some limit on the number of units he finds, which is probably good, because in a TRE he might pull up a couple dozen targets. I think he starts from the point you designated and works outwards from there, and when he's fund his limit, he says "locked and saved" or something like that, and you get the list of targets from which to choose, in order of importance. ==> BIG TIP HERE <== Here's a BIG TIP I haven't seen mentioned here yet. Before even lifting off, do the following: Pull open the George command rose Select Hellfires (left-short once) so that in the command rose the selected weapon is Hellfire. Go to your right MPD Press VID Press L2 (CPG Sight) Press T6 (TADS) Press L3 (Z-oom) This will put George's zoomed, TADS view onto the right MPD. Every target Georges aims at, will be zoomed in on, in the right MPD. You can see if there are tree branches in the way, if the target is between two buildings and you might easily wander off it, if it is just above the trees or a roof and if you drop even a little, you will block the laser from painting it. You will see nearly everything you will need to know, to make a shot good, before authorizing George to shoot, and what you need to do to make it easy--and possible--for George to stay on target with the laser. In the right MPD you will also see, just above the FOR (Field Of Regard) box, any message in while, which indicates why George is not ready to fire, such as HELLFIRE NOT READY, BAL LIMIT, or BACKSCATTER. If you get HELLFIRE NOT READY Check if the selected channel and LRFD codes are the same. If you've already fired an Hellfire, it is likely they are, unless you've changed either. Check the WPN page if the white Hellfire (selected) has any code inside the icon other than just "L". Anything else is an issue. Visually look at the pylons. I've had half wings shot off while the selected HF was "hanging" on the missing half wing-stub, and the WPN page didn't notice anything wrong . In such a case, select ONLY the missing pylon, on the Stores Jettison Panel, and press the jettison button. Now the system will recognize that the missing missile are not there, and pick another to fire next. It's important that you use the right MPD, because any time you get a "rotor rpm low" or ".. high", the left MPD will pull up the ENG page, thus throwing out your CPG TADS view. Put TDS or WPN on the left. They can be pulled back up with a single button press. -- The only one situation, in which you can let George "Go Wild"; if there are numerous unarmored targets. Give George the Gun, and give him Consent To Fire (command rose: up-long, text in command rose will change from yellow to green). Now simply point towards soft targets and up-short once to tell George which direction to attack and he will let loose for as long as there are targets he can find You still have to pay attention to what he's doing, because if he starts in on a tank he cannot kill, he will simply fire on it until the ammo runs out. So you may have to guide him to a different target, in such cases. If new targets are found, you will have to designate them with up-short, so if you are attacking a convoy up a road, and the end of the convoy was not in sight when you started the attack, you will have to designate the vehicles at the end of the convoy for George to attack them. Hope this helps. Now go have fun!

I wanted to hear if others are experiencing the same issue, before referring it to the bug zoo. BTW I'd have also asked, whether it were a Lightning Bug or a Dung Beetle, but I though I'd spare you too much of my insectoid humor.

I'm only piloting. George is CPG. I point in the direction I want him to look--using labels to recognize where the enemy is--and George is not finding a target, ie un-slaving. Since I have my right MPCD set to VID -> CPG Sight (R2) -> TADS (T6) -> Zoom (L3), I can see that George is always in FLIR, even on the brightest of days. Why? I have no idea. I though George was supposed to be the expert on his station.

I am seeing a lot of especially armored vehicles hit by Hellfires an look like they're burning and dead, but are still marked with a label. If I tell George to target such a vehicle, he immediately scrutinizes it with the TADS, but then unslaves and doesn't lock it, so for him it's dead. I don' recall seeing dead, but labeled vehicles anywhere else. Is anyone else seeing this? Is this an AMG-114K bug? A George bug? A label bug? Not a bug, it's a feature?

From my understanding, LOBL means the target is being lazed by the aircraft carrying it. Part of the procedure to fire it is for the Missile to confirm it is locked on the laser signal. When fired the missile flies directly to the laser signal on the painted target, thus the description DIR. LOAL is mainly used for attacking a target painted by a foreign source (eg: another Apache or a JTAC). It can also be used if there is too much signal scatter, because for example a tree branch is in the way or the surface of the vehicle is to obtuse and cluttered with stuff. Putting the missile into LOAL TRAJ HI tells the missile to take a high flight path, but look for a scattered or possibly weak signal while in flight (I read that a laser source with more than 2° deflection from the missile is considered a scattered signal).

No, I never said any such thing. "Channel 1 is set to R, 2 to Q, 3 to P, and 4 to N. Then I change LST and LRFD to R" "I set Q to 1681" "I have (sic.) George permission to fire and he confirmed, but no fire, repeat, repeat, repeat, no firing." Until I changed 1 back to A it was on R. While ! was on R LST and LRFD were on R as well. I have only used LOBL, which is automatically DIR.

Thanks for the reply, admiki. Hellfires were only in LOBL. LST and LRFD were in R, the same as the primary channel. If I take charge of the Hellfires and set them to LOAL, how do I tell George to laze the target, and how can I confirm that He's actually doing it?

On MP I always change ALL the set laser channels to something else, so that there is never a conflict with another player. Generally I just go down the right side. So Channel 1 is set to R, 2 to Q, 3 to P, and 4 to N. Then I change LST and LRFD to R. If I change nothing else, this works. Yesterday I was getting ready to use a JTACing Predator to fire some Hellfires. This is a 4YA European Caucasus PVE server. In the F10 menu you can check which Predator is using which frequency. The one I was getting ready to use, used 1681, so I set Q to 1681 in preparation and went on my merry way. By the time I got to where the Predator was flying, all of it's targets had already been eliminated, so I went to to a different target location. When I get into position, I had George find a target. I always set VID -> CPG Sight (R2) -> TADS (T6) -> Zoom (L3) so that I can see exactly what George is targeting and if there are obstructions or anything I need to pay attention to. FOV was perfect, no building or trees nearby, target in the open with no obstructions. I have George permission to fire and he confirmed, but no fire, repeat, repeat, repeat, no firing. On a hunch I flew by behind the ridge I was looking over, landed and changed the Hellfire channels to 1 = A, 2 = B, 3 = C, and 4 = D, because no other aircraft where anywhere nearby, and set LST and LRFD to A. I returned to my firing position, had George target the same unit, and let him fire -- VOOSH -- and the Hellfire was off and hit. So what was wrong with channel Q having been manually changed and Q assigned to the Hellfire's secondary channel? I don't get what's going on here. Can anyone shed some light on this?

Management Summery I was on a European 4YA Caucuses PVE server and tried to replenish flares and chaff at a FARP. After rearming, I never had what I set I wanted 90 chaff, but it would only give 30. I don't recall everything I tried, but it was a mess, and I never got what I asked for.

Glad you found one I'm not sure if there were actual medevac units during Vietnam. There were heli-transport units and air-cav units in close support, which AFAIK basically did everything. If the troops on the ground needed ammo and supplies, they flew it in. If there were wounded or dead to be taken out, they did that too.

Have you looked in the user downloads? I'm sure there are lots of them. There's like 38 pages of skins to download for the Huey alone.

Yes, exactly. I want to use a switch as a mode selector, so that I can use use my HOTAS, for flying the Apache as the CPG, or for controlling the TEDAC. Windows absolutely DOES recognize the Off state of a switch. It's call the off or unasserted state. In the Gaming Devices -> properties section, switching a switch to the unasserted or off state causes the indicator light to be extinguished. That's not coincidence, that is an on-purpose, positive control. Here's an example of using the "off" setting of a switch, I wrote years ago for the P-51D: {down = device_commands.Button_4, up = device_commands.Button_4, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = 0.2, value_up = 0.1, name = _('Landing Gear Down else UP'), category = _('Systems')}, Both "value_down" (button pressed or switch at the asserted position) and the "value_up" (button released, or switch at the un-asserted position) are evaluated. In the "up" state, "0.1" is transmitted to "device_commands.Button_4" causing the undercarriage lever to be moved to the raised position, and the landing gear to be raised. In the "down" state, "0.2" is transmitted to "device_commands.Button_4" causing the undercarriage lever to be moved to the lowered position, and the landing gear to be lowered. ED has started to add such configurations themselves in many cases, in many newer aircraft. But if you have specific wishes, you must generally DIY.

So, you are printing all this stuff with a 3D printer? My first thought was, "NEED MOAR!" I want to build a couple of mostly universal controllers, which I can use for numerous aircraft. To one I want to add in a break lever for my Spit-Quito , and radar antenna elevation control (someone builds the plastic part of the switch, you just need to add a hall sensor and wiring, and of course a controller to hook it up to). I'd like some dials to use for lighting, because I hate trying to fumble around with the mouse at night (I'm not that kind of guy, and it's not that kind of mouse ), mom-off-mom switches for course and heading in the F/A-18, so many things I want want want Since you've built your own sticks, throttles, and collectives, are you using hall sensors? What board are you using for the basis? Any suggestions you might want to pass on?

Cheat! LOL So to prove me wrong, you built a controller JK I can see how that would be easier to use in DCS, but are you still limited to 32 individual DirectX switch identities? Just curious.

That would be absolutely awesome

That would be the most unusual toggle switch on a controller I'd ever seen. There are On-On toggle switches, but why would anyone use them on a controller? If in Windows under Game Controller Settings -> Properties, when you toggle the switch, and one indicator light goes on and one goes off, then your switch is On-On. If toggling your switch up and down only makes one light go on and off, then it is a standard On-Off switch, just like all the others. ??? Controllers don't send single pulses. They work like light switches or door bell buttons. As long as the circuit is closed, current flows; the light is on, or the door bell rings. Thanks for the suggestion. I've looked at RS Mapper once before. A second layer of programming the same controls over again, and doubling the work as setting up a configuration doubling the complexity really turned be off to it. I'm looking for something like setting up the a bind in default.lua to work with toggle switches. Only the bind is affected, and nothing else.