Dr Zaius

I think theres a bit of a misunderstanding as to how this feature works, as I understand it its a very subtle lighting effect that changes depending on the outside environment, an example would be taxing next to some green grass should result in a faint green tinge to the cockpit, as I say it it subtle though.

If you don't have anything designated on the DMT already then in CCIP mode a designation will occure via the CCIP crosshairs whenever the pickle button is pressed, I suspect its this that has happened as I just tried out both methods of function and they seem to be working as they should, are you able to replicate the issue and maybe include a trackfile for us to look at?

Hello, When I attempt to move the INS curser via the TDC (input mapped via a modifier on my TMWH joystick Castle Hat / AKA DMS) the controls are reversed; yet if I use the axis input of the slew control on the throttle it works correctly. I don't normally use anything else to control the TDC other than the slew control however not all of us have a HOTAS contoller, it should thereofre be corrected. OB 2.5.6.59625 Track attached. Control Reversal.trk

As with most of these bugs there often are workarounds, still it should be reported. How exactly are you able to get fine control using the point of view hat, are you able to dial in some accuracy via the control setup? I've reported it btw

I can't replicate the issue however I use the axis slew upgrade on my warthog, not the point of view hat which is what I think you’re using? I do have a backup mapped though via the use of a modifier and the castle switch on the joystick - the strange thing is that I can replicate the problem using this backup method which makes me think that the issue occurs only when using a non-axis inputs, thats why I recommended that you give it a try.

I stand corrected, follow this procedure and you can drop on 10 different targets, one after the other - the key is mark points created using the targeting pod!

The dreaded input reversal is back?! Last time this was reported it was to do with the Maverick input but they fixed that issue last update or so, I was new to the module back then and was certain it wasn’t just the Mavs that caused problems but couldn’t replicate and assumed I was wrong - out of interest do you map you tdc to an axis or button press? I mapped both and iirc it worked OK with one input but not the other, give it a try.

Mapping to the OSB commands worked really well, thanks for the tip! Add it to the list - suggest reporting it as a new post though, you'll also be asked to supply a trk. file

It's actually SSS left to change FOV not NWS, my mistake. I didn't realise you could map zoom in & out like that, I did try and map those commands to the china hat on my TMWH but it doesn't work very well, a press and hold does nothing and pressing it again and again is a bit hit & miss, or as you say wonky.

Hey good find, landing gear must be fairly beefy to handle all these 'drops'

Wow, simple and very effective!

I think the blue bar is supposed to be a ‘screen depth’ graphical effect to make it look more lifelike, though it does look a little odd at times.

What exactly have you got mapped to your axis? As i understood it the only zoom feature you have using HOTAS is changing wide to narrow FOV, are you able to make a small video of the problem? Iirc theres only 2 sensors on the aircraft that zoom, one is the targeting pod the other is Maverick optics, unless you’re referring to other aircraft in which case each the targeting pods do differ in their functionality.

Does anyone else think the pilot hit the deck a little on the hard side?

I watched a harrier documentry on YT the other night, one of our best Royal Navy / RAF pilots said the aircraft itself wasn't difficult to fly (including STOVL) but if you got it a little bit wrong then it can get very wrong very quickly - one of the things mentioned was control reversal when flying backwards over a given speed, he almost had a crash because of that little issue. Great vid btw

Distance did make more sense as the bombing computer will account for the harriers speed on release - I still can't believe the system would allow for a 9990 foot drop though, thats like a 3 kilometer separation!

So the flight profile of the bomb? Assume these terminal parameters would be entered via the ODU & UFC?

Now wouldn't that be an awesome feature to have, sadly I think our pre-planned attacks for multible drops are limited to entering tarket points via the F10 map, I very much hope I'm wrong though!

Appreciate it took a while to get this feature operational in the first place but I'm having trouble understanding the logic of it’s current operation. I think it may be in units of time (please correct me if I'm wrong) as opposed to distance, carrying out a low level run using a bunch of high drag Mk82’s and on a medium sized convoy a good separation is somewhere between 007 & 012, at no point does it feel like you’ll ever need to go any higher the 020 except perhaps on a runway - that then leaves the question as to what situation one would find themselves in to warrant the use of the first digit interval? Having done some testing it feels like 100 is a second interval between drops which if you think about it is an eternity when flying fast over a target area, Ive a suspicion then that something isn’t quite right.

Thanks, have you any idea of what it should do?

Can anyone shed some more light on what enabled / not enabled does please, I believe sss up changes between the 2

Yes please very much..

It is a little annoying yes, as are most of the in-game comms! I don't think you're doing anything wrong, just an overly cautious boom guy

I tried mapping the tdc to the castle hat and it moves around much better, slow control is next to impossible though. Fair play reporting it like you have, will be interesting to see if they have the same problems.

No I don’t bother with TARGET, everything is managed via the in game settings - its as if the problem stems from the transition of inputs, as though it doesn’t like a 2 input (diagonal movement) at once, thats why i initially had such a high deadzone but that somehow makes the problem worse.