frostycab

I rather suspect that the best thing to do is attach a track of it happening.

Short version: No. (EDIT: At least not yet) Longer version: Use the Linear Motion Compensator (LMC) on the TEDAC. It's NOT a target lock, and it;s not ground stabilisation. It's a angular stabilisation, so will keep the TADS looking along the same LOS from wherever you are or however the aircraft moves. If you turn it on, and then slide right 500m then you will be looking in exactly the same azimuth and elevation as you were, just 500m right of where you were. If you slew with MLC on then it "remembers" the direction and speed you were slewing in and maintains that, so you can *follow* a moving target, but you won't be *tracking* it. You can cancel out the motion by slewing in the opposite direction, but getting it to stop is virtually impossible. Best thing to do is turn it off and on again.

Nothing... probably. (Yet)

First, make sure you're looking at the CPG controls and not the pilot ones. (Control Setting page always opens in the PLT page when flying SP, so need to manually select it each time you open.) The TEDAC control grip functions are all listed beginning with either LHG or RHG (Left Handgrip/Right Handgrip). All the WAS controls are listed as "LHG Weapon Action (WAS) Switch ......"

The kneeboard MGRS coords are in the format XX########. You aren't given the preceding XX# grid because with them being 1000km across it's "assumed" that you won't be crossing to a new grid. By leaving them off I think mission designers are just trying to simplify things for the pilot, but it does cause issue in some cases, especially on the Caucuses map that crosses grids somewhere around Senaki and Kutaisi. Not understanding the system caused me so many headaches when I was learning the A-10 many years ago. In simple terms, it's not a bug. It's a choice made by the person who wrote the kneeboard page. Familiarity with a given region will help immensely in recognising when things look odd. Also, if you find that you are getting wildly different coordinates, such as CV######## and then KR######## then it's a heads-up that you need to look deeper. Fortunately all it normally takes is a quick look at the F10 map to know what's happened. Zoom out far enough and you can see the major grids with their identifiers, so you should be able to easily work out what you need to use.

Yup. I can confirm that this is 100% correct. As I said, your debug is currently reading the state of the button which is a momentary, whereas you need to read the lamp itself for it to stay latched. You can't get that offset from the ID Lookup with this plugin. You need to look in the lua file to find it.

Its not totally crazy for many aircraft, though the apache could well be different. Certainly in civil aviation if the aircraft has been moved since it was powered down then its position will need to be manually updated so the INS knows where a flight is starting. If it’s already set then I just like to think the ground crew have set it when they put the aircraft out on the flight line.

PP on the TSD will still give you your current grid while waiting for INUs, so if you do get impatient you can use that.

Far too tired to go through all that tonight, but will defo be having a look over the next day or 2. Thank you.

Press "C" Like the Hind, the controls are stowed until needed. When you press C you'll see the cyclic unfold in the usable position. Then you can fly from the front seat. I think when you switch to the front seat George as pilot will try to maintain heading, altitude and speed according to whatever the aircraft was at when you handed control over. When you switch back you just need to be a bit quick to correct any mismatch in the George controls and your own physical ones.

Thank you for responding. No matter what, it's a great tool you've created. One thing I've never been able to get working is the DCS_BIOS button type that you added a while back. When I set the path to DCS-BIOS in the setup page and click Update it doesn't do anything and doesn't save the path. Maybe I'm just doing it wrong. I'm not exactly au fait with all this stuff. I just press things in different combinations until they work.

You don't sound argumentative, so don't worry. I may not understand exactly what you're having trouble with, so excuse me if this is repetitve and not what you're looking for. When you manually press the button in DCS the debug goes to 1, correct?and then returns to 0 when you release the button in DCS or does it go to 0 while still holing it down with the mouse? If it's the former then it's correct. With the 403 Offset set in the Image Change section in the SD the button does exactly the right thing for me. I press the SD, and as long as I hold the button down the same button in DCS is pushed in. I release, it releases. Whether I press the button on the SD or in DCS, the icon on my SD changes to match the current state of the DCS button. I suspect that what you're doing right now is debugging the wrong thing. What DCS ID are you reading in the Title Change field? I set my Title Change DCS ID to 403 to match my Image Change ID and It stays at 1 when Guard is lit. Do you want to talk on Discord so we can really understand exactly what's up? As Bailey says, pictures of all 3 sections should clear things up pretty quickly I hope.

I'm sure they're already on it.

I think this may have been reported already. Seems to be related to cold starts.

But that's half the fun! Well, it is if you're the CPG. Gotta have something to do on the ride in.

I've never used TARGET, mainly because I just can't be bothered with it. Why on earth did you need to do the Harrier's 3-position switches manually though? It's one of the few aircraft that actually DID do it right. LOL Look in the Harrier's control bindings, and filter the list to "Joystick Switch Abstractions." They're all in there I believe. For example, the flaps can be CRUISE Else AUTO for up on the switch, and STOL Else AUTO for down. If not in either of those positions you get AUTO. Works fine on my Warthog. Probably a bit late to tell you that now though. Sadly, such abstractions haven't made their way into the Apache (yet.) Having said that, there aren't too many to do if you intend to do it manually in TARGET. For the pilot you'll probably only ever use it for the NVS Mode, though you could add the 2 for lighting, and the CPG only has the LMT Mode switch and the IAT Polarity as far as I can see.

Set your Image State Change ID to 403 and try that. The value you're seeing is the state of the signal being sent to DCS. You need to be able to see the state of the item within DCS, otherwise the button will just return a 1 while you're pushing it. If you look in the lua file and scroll down to the section "-- Warning Lights and Button Lights" you'll find the ID there. Edited: Had wrong ID

It comes with the Apache, but you need the Marianas map for it to show up for you.

Seems to fixed itself now. The page had opened, but 404'd when I clicked Download. Tried a few more times just now and eventually it worked. Possibly my interwebs being stupid.

Odd. I'm getting 404 Not Found when I try to download.

I've never tried Helios. Does it work with an iPad?

Yeah. I believe what happened there was confusion regarding units. They'd worked out figures in kg, but the actual fuel was loaded according to lbs. I'd need to look up the incident to go into detail about it (or see the pretty good "made for tv" film again.) I do remember the PIC being hailed in the same way that Sully was.

The autopaging always appears on the left MFD, doesn't it? If so then I would suggest always keeping your highest priority "I Can't Live Without It" page on the right. Hardly ideal, but better than nothing.

JATO system for when you just don't have time for a proper takeoff?

Usually, yes. There are a few caveats to that if you expand it beyond DCS. I believe most light GA aircraft have fuel gauges in volume. It can get a little bit confusing when you come to commercial aviation too. Fuel is bought and paid for by volume, but for obvious reasons the crew and flight management computers reference weight. This means that any time they uplift fuel they need to do a set of calculations based on things such as the tested specific density of the fuel being supplied at that airport on that day.